225redstick Posted February 13, 2019 Share Posted February 13, 2019 #ifconfig eth0 unraid eth0: flags=4416<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500 Link to comment
225redstick Posted February 13, 2019 Author Share Posted February 13, 2019 dosent show ip here like it use to: eth0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500 ether XXXXXXXXXXXX txqueuelen 1000 (Ethernet) RX packets 2318 bytes 1020947 (997.0 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1831 bytes 1402158 (1.3 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 20 memory 0xdfb00000-dfb20000 Link to comment
Hoopster Posted February 14, 2019 Share Posted February 14, 2019 21 minutes ago, 225redstick said: dosent show ip here like it use to: eth0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500 ether 00:25:90:a3:ff:87 txqueuelen 1000 (Ethernet) RX packets 2318 bytes 1020947 (997.0 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1831 bytes 1402158 (1.3 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 20 memory 0xdfb00000-dfb20000 Your router leased 192.168.1.5 to br0 not to eth0. Do you have bridging enabled for eth0 in Settings --> Network? What does ifconfig show for br0? Link to comment
225redstick Posted February 14, 2019 Author Share Posted February 14, 2019 "Your router leased 192.168.1.5 to br0 not to eth0" i do remember trying to reserve that ip in router settings for DHCP unraid initial assignment? no reservation in router settings is showing up since I reset the router. "Do you have bridging enabled for eth0 in Settings --> Network"? yes it was turned on, i dont remember doing that but maybe for an earlier docker install. i just tried turning it off. Link to comment
225redstick Posted February 14, 2019 Author Share Posted February 14, 2019 root@unRAID:~# ifconfig br0 br0: error fetching interface information: Device not found Link to comment
225redstick Posted February 14, 2019 Author Share Posted February 14, 2019 the other thing i tried earlier in an attempt to return to the default DHCP configuration was to pull the usb unraid boot drive and to delete the boot/config/network.cfg and boot/config/network-riles.cfg files. Link to comment
225redstick Posted February 15, 2019 Author Share Posted February 15, 2019 bond0: flags=5443<UP,BROADCAST,RUNNING,PROMISC,MASTER,MULTICAST> mtu 1500 inet6 XXXXXXXXXXXXX prefixlen 64 scopeid 0x20<link> ether XXXXXXXXXXXXX txqueuelen 1000 (Ethernet) RX packets 954 bytes 130622 (127.5 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 749 bytes 802552 (783.7 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.7 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 XXXXXXXXXXXXX prefixlen 64 scopeid 0x20<link> ether XXXXXXXXXXXXX txqueuelen 1000 (Ethernet) RX packets 773 bytes 83939 (81.9 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 308 bytes 771747 (753.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500 ether XXXXXXXXXXXXX txqueuelen 1000 (Ethernet) RX packets 954 bytes 130622 (127.5 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 749 bytes 802552 (783.7 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 20 memory 0xdfb00000-dfb20000 eth1: flags=6147<UP,BROADCAST,SLAVE,MULTICAST> mtu 1500 ether XXXXXXXXXXXXX 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 device interrupt 16 memory 0xdf900000-df920000 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 2 bytes 140 (140.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2 bytes 140 (140.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Link to comment
225redstick Posted February 15, 2019 Author Share Posted February 15, 2019 I think i figured it out for now, somehow bonding and bridging were on "yes" and seemed to be preventing the new router from connecting and configuring eth0. Thanks for suggestions and help and a little bit of trial and error I was worried my jump drive and/or network card were shot. eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.7 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 XXXXXXXXXXXXXX prefixlen 64 scopeid 0x20<link> ether XXXXXXXXXXXXXX txqueuelen 1000 (Ethernet) RX packets 1645 bytes 267297 (261.0 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 957 bytes 750155 (732.5 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 20 memory 0xdfb00000-dfb20000 Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.