Rig2 Posted April 10, 2020 Share Posted April 10, 2020 All, Lurked for years and have appreciated all everyone does in these forums. Have helped me out immensely over the years! In the process of migrating to a new gaming VM/home server build after 6 years and am going through some clean-up (clearing old apps/dockers, migrating to newer HDs, etc.). I want to finish up the migration to newer HDs prior to migrating to the new hardware. When upgrading to 6.6.7 to 6.8.2 or 6.83 (haven't tried 6.9 beta), I no longer able to reach the internet via ping in terminal, docker, or community apps. I've seen a couple posts echoing the similar behavior, with resolution involving with fresh usb install with clean network.cfg, resetting eth0, & motherboard compatibility, though I am unsure if my behavior is directly related. Just wondering if anyone could take a gander at the below & attached and provide some thoughts before I attempt anything. If this is better suited within a related thread I can migrate the Ask. It appears that my default route after upgrading to 6.8.3 changes to 192.168.2.1 (br1) rather than maintaining eth0 (192.168.1.1): Is there a reason for this? Why would it be utilizing the a previously setup docker route? Is the fix as simple as changing the default route back to eth0? From both 6.6.7 & 6.8.3 builds: Terminal Commands below network.cfg attached diag.zip attached 6.6.7 ping 8.8.8.8 = success ip route: default via 192.168.1.1 dev eth0 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.113 192.168.2.0/24 dev br1 proto kernel scope link src 192.168.2.2 route -n: Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 br1 ifconfig: br1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.2.2 netmask 255.255.255.0 broadcast 0.0.0.0 inet6 fe80::10a0:c3ff:fefd:14ea prefixlen 64 scopeid 0x20<link> ether 12:a0:c3:fd:14:ea txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 95 bytes 15382 (15.0 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.113 netmask 255.255.255.0 broadcast 0.0.0.0 inet6 fe80::62a4:4cff:fe42:8d00 prefixlen 64 scopeid 0x20<link> ether 60:a4:4c:42:8d:00 txqueuelen 1000 (Ethernet) RX packets 1328 bytes 386864 (377.7 KiB) RX errors 0 dropped 13 overruns 0 frame 0 TX packets 1274 bytes 931107 (909.2 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 52 bytes 3253 (3.1 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 52 bytes 3253 (3.1 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 6.8.3 ping: 8.8.8.8 = 192.168.2.2 icmp_seq=1 Destination Host Unreachable ip route: default via 192.168.2.1 dev br1 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.113 192.168.2.0/24 dev br1 proto kernel scope link src 192.168.2.2 route -n: Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 0 br1 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 br1 ifconfig br1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.2.2 netmask 255.255.255.0 broadcast 0.0.0.0 ether fe:b2:4a:cd:28:1c txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 924 bytes 49888 (48.7 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.113 netmask 255.255.255.0 broadcast 0.0.0.0 ether 60:a4:4c:42:8d:00 txqueuelen 1000 (Ethernet) RX packets 6430 bytes 1448683 (1.3 MiB) RX errors 0 dropped 13 overruns 0 frame 0 TX packets 2685 bytes 1679217 (1.6MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 1624 bytes 111790 (109.1 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1624 bytes 111790 (109.1 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Thanks!! Rig2 6.6.7.diag.zip 6.8.3.diag.zip 6.6.7_network.cfg 6.8.3_network.cfg Quote Link to comment
Rig2 Posted April 13, 2020 Author Share Posted April 13, 2020 UPDATE: Starting with default network.cfg resolved the behavior when upgrading to v6.8+. I was able to assign static IP reboot. However, still unsure as to why my previous network.cfg worked fine within v6.6.7 and not v6.8.2+. After upgrade (previously existing network.cfg), ip link set br1 down brought eth0 to default and I was able to access the internet, though it didn't persist after reboot. Only deleting network.cfg and rebooting resolved issue fully. Feel free to close out thread. Thanks! Quote Link to comment
itimpi Posted April 13, 2020 Share Posted April 13, 2020 1 hour ago, Rig2 said: UPDATE: Starting with default network.cfg resolved the behavior when upgrading to v6.8+. I was able to assign static IP reboot. However, still unsure as to why my previous network.cfg worked fine within v6.6.7 and not v6.8.2+. After upgrade (previously existing network.cfg), ip link set br1 down brought eth0 to default and I was able to access the internet, though it didn't persist after reboot. Only deleting network.cfg and rebooting resolved issue fully. Feel free to close out thread. Thanks! I believe that earlier releases of Unraid were more tolerant of certain types of error in the network.cfg file. That is why the advice to delete the existing one to revert to default settings is often given. Quote Link to comment
Rig2 Posted April 13, 2020 Author Share Posted April 13, 2020 @itimpi Thanks for the follow-up and context! Glad to be putting the final touches on the migration! Quote Link to comment
Recommended Posts
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.