x86intel

This worked for me as well. Thank you! Previously, when I had the WireGuard issue, I turned off Unraid for the night; but few days later, I came back to boot the Unraid machine; and I noticed this on console startup: ------ I suspect some bad network config was persisted during my previous shutdown. I was able to get WebUI working temporairly enough to get to the Settings > Network tab; and I did the following: 1. Unbonded the NICs; gave everything separate IPs --- NIC/eth0 is the only port connected to LAN --- NIC/eth1 was never really bonded at the begining (i dont recall, I left this network config as-is after fresh install); and also eth1 was never connected to LAN --- applied settings 2. Rebonded the NICs; this time explicitly specifying eth0 + eth1 --- applied settings 3. This seemed to work. and now I don't have the console startup error anymore: --- Only thing I get now is RTNETLINK `Operation not supported` .... but that's fine by me. =) Also, now I can confirm WireGuard is working (and no manual edits are necessary).

hi @ljm42 I'm a new unraid user, and just setup a new server; I also ran into the same issue as everyone described above. When I click the "Inactive" toggle switch it fails to stay enabled for `Tunnel wg0`. Here is my output: root@nas:/tmp# php testnet.php Array ( [DHCP_KEEPRESOLV] => yes [DNS_SERVER1] => 1.1.1.1 [DNS_SERVER2] => [DNS_SERVER3] => [DHCP6_KEEPRESOLV] => no [BONDING] => yes [BONDNAME] => [BONDNICS] => eth0,eth1,eth2,eth3 [BONDING_MODE] => 1 [BONDING_MIIMON] => 100 [BRIDGING] => yes [BRNAME] => [BRNICS] => bond0 [BRSTP] => 0 [BRFD] => 0 [DESCRIPTION:0] => [PROTOCOL:0] => [USE_DHCP:0] => no [IPADDR:0] => 192.168.0.8 [NETMASK:0] => 255.255.255.0 [GATEWAY:0] => 192.168.0.1 [METRIC:0] => [USE_DHCP6:0] => [IPADDR6:0] => [NETMASK6:0] => [GATEWAY6:0] => [METRIC6:0] => [PRIVACY6:0] => [MTU] => [TYPE] => access ) BRIDGING: 'yes' BRNAME: '' BONDING: 'yes' BONDNAME: '' ethX: 'eth0' device: '' HEY dev is empty! root@nas:/tmp#