For some reason, each time I upgrade to a new version of unraid, I can't route to outside the network. I discovered it's because the default route is missing.

 

In the file attached, you can see the line I have to add manually in order to restore outbound network access.

 

Any thoughts as to how I can fix this?

 

Thanks!

You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread.

Go to Settings -> Network Settings and make sure a Default Gateway is specified for eth0. If that doesn't help we'll need diagnostics

Default gateway was already set on `eth0`.

Diagnostics attached. I appreciate the help.

tower-diagnostics-20230628-1002.zip

Edited June 28, 20233 yr by bfeist

The issue is probably that both eth0 and eth2 are assigned to the same subnet with the same gateway.

 

Fix Common Problems has been warning of this:

Jun 26 11:00:24 Tower root: Fix Common Problems: Error: Multiple NICs on the same IPv4 network ** Ignored

 

 

If you go to Settings -> Network Settings, how many Network Interfaces do you see? If you can see eth2, set the "IPv4 address assignment" to none and reboot. If you don't see eth2, make a dummy change to eth0 and hit apply, then reboot. Please upload your diagnostics afterwards so I can confirm the dummy change worked, if it didn't then we will need to manually edit a file.

 

Note: once the networking issue is resolved, there is an issue with your GPU that is filling the syslog with:

Jun 27 04:40:03 Tower kernel: radeon 0000:00:01.0: ring 6 stalled for more than 28698819msec
Jun 27 04:40:03 Tower kernel: radeon 0000:00:01.0: GPU lockup (current fence id 0x00000000000012ef last fence id 0x00000000000012f0 on ring 6)

We'll need someone else to help with that.

I see two (see below)

I performed the following as you instructed:

• Made a dummy change to eth0 - I changed the default gateway, applied changes then changed the value back, applied changes
• Rebooted. Default route missing again, no route to internet. Screenshot below. Diagnostics after reboot attached.

 

 

Last year I did make an attempt to add a usb-based NIC but it's no longer connected. This might be the root of the problem.

 

Thanks again.

tower-diagnostics-20230628-1211.zip

Try editing /boot/config/network.cfg and delete this part:

 

IFNAME[2]="eth2"
DESCRIPTION[2]="eth2"
PROTOCOL[2]="ipv4"
USE_DHCP[2]="no"
IPADDR[2]="192.168.0.15"
NETMASK[2]="255.255.255.0"
GATEWAY[2]="192.168.0.1"

 

Also change

SYSNICS="3" to "2"

Then reboot

Thanks very much. That did the trick!

 

Ben

Great! I was testing a theory on whether making a dummy change would clear out that old nic, good to know for sure it requires a manual update.