October 5, 20232 yr Hi All, I recently moved to a new house and since moving I cannot get my server to connect to the internet. I'm able to boot and access it from my monitor. ifconfig eth0 returns the following: eth0: flags=6147<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500 ether XXXXXXXXXXXX txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ifconfig br0 returns the following: br0: flags=4163<UP,BROADCAST,RUNNING,RUNNING,MULTICAST> mtu 1500 INET 169.254.150.55 NETMASK 255.255.0.0 BROADCAST 169.254.255.255 ether d4:5d:64:d2:02:1d txqueuelen 1000 (Ethernet) RX packets 18 bytes 2594 (2.5 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 289 bytes 35143 (34.3 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 The router has not changed but the default gateway has and is now 192.168.0.1. I have tried deleting the network.cfg and network-rules.cfg files on the boot drive and rebooting but no luck. Bridging is enabled but for some reason I seem unable to change and network settings even when I have stopped all dockers and VMs. I have been running the server for a while but have never had to deal with an issue like this so any help is greatly appreciated!
October 5, 20232 yr Community Expert 3 minutes ago, appropriate-snake4282 said: but for some reason I seem unable to change and network settings even when I have stopped all dockers and VMs. The array also needs to be stopped to change network settings. The information you posted suggests you are not getting an IP address because no DHCP server is being found. You should post your system's diagnostics zip file so we can get a better idea of what is going on.
October 6, 20232 yr Author Thanks for replying! Here are the system's diagnostics. Please let me know if you have any suggestions. tower-diagnostics-20231006-1306.zip
October 6, 20232 yr Community Expert Your diagnostics show that eth0 does not have an active link so cannot get a valid IP address. Have you perhaps swapped some cables around? Also you seem to have at least one docker container continually crashing spamming the logs. You might want to disable docker until your network issues are resolved.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.