lafrance Posted April 25, 2017 Share Posted April 25, 2017 I'm still experimenting with unRAID and it's capabilities seem endless. As things have gone well I'm just about to transfer everything to the main box and start setting up. However, I've just hit on an unusual problem and wondered if anyone else has seen this particular issue. On the network settings I've been running DHCP. Things have gone fine everyday. Ultimately I want the full time machine to be on a static IP. I'm running version 6.3.3 and as soon I fixed the IP and DNS addresses to Google when I rebooted the br0 link was reported as down. Initially I thought this could be a router problem and ran the machine up on a separate network with exactly the same result. In the sys log there is the following error. probe link rx_err and tx_err hw When I go back to DHCP on the IP address and DNS everything is fine. If I then opt for DHCP on the IP and static on the DNS addresses again everything is fine but as soon as I set a static IP the link is down. There's only one NIC on the test machie(s) I've tried and all display the same problem. There's nothing unusual in the BIOS either. Has anyone got any suggestions as to what a fix might look like? Your help would be very much appreciated. Quote Link to comment
Squid Posted April 25, 2017 Share Posted April 25, 2017 Far from a network guy, but is the static IP you're attempting to use already in use? Quote Link to comment
lafrance Posted April 26, 2017 Author Share Posted April 26, 2017 9 hours ago, Squid said: Far from a network guy, but is the static IP you're attempting to use already in use? Morning Squid Thanks for the reply but no. That's one of the things I checked. It is all very odd as I've now tried this on two completely different machines and got the same result. Quote Link to comment
joedotmac Posted April 26, 2017 Share Posted April 26, 2017 (edited) When you change the config to the static IP, can you still connect to the web GUI? Or are you using the system console? Are you attempting to use the same static IP that was assigned by the DHCP server? Have you tried using a disparate IP that's not inside your DHCP scope? On the command line perform: ifconfig -a Paste output here. Guessing at this point, something goofed with arp cache. Rebooted after the change to static IP? Edited April 26, 2017 by joedotmac Quote Link to comment
unevent Posted April 27, 2017 Share Posted April 27, 2017 Post a diagnostics file. What is running your DHCP server? Quote Link to comment
lafrance Posted April 27, 2017 Author Share Posted April 27, 2017 13 hours ago, joedotmac said: When you change the config to the static IP, can you still connect to the web GUI? Or are you using the system console? Are you attempting to use the same static IP that was assigned by the DHCP server? Have you tried using a disparate IP that's not inside your DHCP scope? On the command line perform: ifconfig -a Paste output here. Guessing at this point, something goofed with arp cache. Rebooted after the change to static IP? Thanks joedotmac It is weird as my test rig is the only think connected to a router with a DHCP range set at 100 - 254. If I boot with unRAID set for DHCP it normally gets allocated .100. I can log into the GUI without problems and everything is fine as eth0 is linkup. If I then reset to static either in or out of the DHCP range the machine boots with link down. I can still get access to the GUI but no internet. If I reset to DHCP on unRAID everything is then fine. The ifconfig -a output looks like the below with DHCP set in unRAID: br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.0.100 netmask 255.255.255.0 broadcast 192.168.0.255 ether d0:27:88:a9:f7:f0 txqueuelen 1000 (Ethernet) RX packets 2343 bytes 277060 (270.5 KiB) RX errors 0 dropped 7 overruns 0 frame 0 TX packets 2721 bytes 1119668 (1.0 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500 ether d0:27:88:a9:f7:f0 txqueuelen 1000 (Ethernet) RX packets 2372 bytes 317176 (309.7 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2721 bytes 1119962 (1.0 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 gre0: flags=128<NOARP> mtu 1476 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1 (UNSPEC) 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 gretap0: flags=4098<BROADCAST,MULTICAST> mtu 1462 ether 00:00:00:00:00:00 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 ip_vti0: flags=128<NOARP> mtu 1364 tunnel txqueuelen 1 (IPIP Tunnel) 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 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.255.255.255 loop txqueuelen 1 (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 tunl0: flags=128<NOARP> mtu 1480 tunnel txqueuelen 1 (IPIP Tunnel) 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 With the IP set to 192.168.0.10 as static using the default DNS: br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.0.10 netmask 255.255.255.0 broadcast 0.0.0.0 ether d0:27:88:a9:f7:f0 txqueuelen 1000 (Ethernet) RX packets 983 bytes 103099 (100.6 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1301 bytes 959728 (937.2 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500 ether d0:27:88:a9:f7:f0 txqueuelen 1000 (Ethernet) RX packets 988 bytes 117813 (115.0 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1301 bytes 959836 (937.3 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 gre0: flags=128<NOARP> mtu 1476 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1 (UNSPEC) 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 gretap0: flags=4098<BROADCAST,MULTICAST> mtu 1462 ether 00:00:00:00:00:00 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 ip_vti0: flags=128<NOARP> mtu 1364 tunnel txqueuelen 1 (IPIP Tunnel) 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 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.255.255.255 loop txqueuelen 1 (Local Loopback) RX packets 4 bytes 312 (312.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 4 bytes 312 (312.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 tunl0: flags=128<NOARP> mtu 1480 tunnel txqueuelen 1 (IPIP Tunnel) 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 Any ideas? Best Regards Lafrance Quote Link to comment
lafrance Posted April 27, 2017 Author Share Posted April 27, 2017 3 hours ago, unevent said: Post a diagnostics file. What is running your DHCP server? Thanks for the reply unevent. I've attached the two files. 0824 is with DHCP set on unRAID and 0836 is when the IP is set at static 192.168.x.10. For the test rig the machine is the only thing connected to the router so there's no chance of any IP conflict. The router has a DHCP range set to 100 - 254. Best Regards Lafrance tower-diagnostics-20170427-0824.zip tower-diagnostics-20170427-0836.zip Quote Link to comment
lafrance Posted April 27, 2017 Author Share Posted April 27, 2017 14 hours ago, joedotmac said: When you change the config to the static IP, can you still connect to the web GUI? Or are you using the system console? Are you attempting to use the same static IP that was assigned by the DHCP server? Have you tried using a disparate IP that's not inside your DHCP scope? On the command line perform: ifconfig -a Paste output here. Guessing at this point, something goofed with arp cache. Rebooted after the change to static IP? Thanks joedotmac It is weird as my test rig is the only think connected to a router with a DHCP range set at 100 - 254. If I boot with unRAID set for DHCP it normally gets allocated .100. I can log into the GUI without problems and everything is fine as eth0 is linkup. If I then reset to static either in or out of the DHCP range the machine boots with link down. I can still get access to the GUI but no internet. If I reset to DHCP on unRAID everything is then fine. The ifconfig -a output looks like the below with DHCP set in unRAID: br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.0.100 netmask 255.255.255.0 broadcast 192.168.0.255 ether d0:27:88:a9:f7:f0 txqueuelen 1000 (Ethernet) RX packets 2343 bytes 277060 (270.5 KiB) RX errors 0 dropped 7 overruns 0 frame 0 TX packets 2721 bytes 1119668 (1.0 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500 ether d0:27:88:a9:f7:f0 txqueuelen 1000 (Ethernet) RX packets 2372 bytes 317176 (309.7 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2721 bytes 1119962 (1.0 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 gre0: flags=128<NOARP> mtu 1476 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1 (UNSPEC) 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 gretap0: flags=4098<BROADCAST,MULTICAST> mtu 1462 ether 00:00:00:00:00:00 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 ip_vti0: flags=128<NOARP> mtu 1364 tunnel txqueuelen 1 (IPIP Tunnel) 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 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.255.255.255 loop txqueuelen 1 (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 tunl0: flags=128<NOARP> mtu 1480 tunnel txqueuelen 1 (IPIP Tunnel) 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 With the IP set to 192.168.0.10 as static using the default DNS: br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.0.10 netmask 255.255.255.0 broadcast 0.0.0.0 ether d0:27:88:a9:f7:f0 txqueuelen 1000 (Ethernet) RX packets 983 bytes 103099 (100.6 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1301 bytes 959728 (937.2 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500 ether d0:27:88:a9:f7:f0 txqueuelen 1000 (Ethernet) RX packets 988 bytes 117813 (115.0 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1301 bytes 959836 (937.3 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 gre0: flags=128<NOARP> mtu 1476 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1 (UNSPEC) 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 gretap0: flags=4098<BROADCAST,MULTICAST> mtu 1462 ether 00:00:00:00:00:00 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 ip_vti0: flags=128<NOARP> mtu 1364 tunnel txqueuelen 1 (IPIP Tunnel) 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 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.255.255.255 loop txqueuelen 1 (Local Loopback) RX packets 4 bytes 312 (312.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 4 bytes 312 (312.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 tunl0: flags=128<NOARP> mtu 1480 tunnel txqueuelen 1 (IPIP Tunnel) 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 Any ideas? Best Regards Lafrance Quote Link to comment
lafrance Posted April 27, 2017 Author Share Posted April 27, 2017 4 hours ago, unevent said: Post a diagnostics file. What is running your DHCP server? Thanks for the reply unevent. I've attached the two files. 0824 is with DHCP set on unRAID and 0836 is when the IP is set at static 192.168.x.10. For the test rig the machine is the only thing connected to the router so there's no chance of any IP conflict. The router has a DHCP range set to 100 - 254. Best Regards Lafrance tower-diagnostics-20170427-0824.zip tower-diagnostics-20170427-0836.zip Quote Link to comment
bonienl Posted April 27, 2017 Share Posted April 27, 2017 (edited) Everything looks fine. Instead of using your router 192.168.0.1 as DNS server use the google DNS servers 8.8.8.8 and 8.8.4.4 Ps. Your connection is only 100Mbps, does your router not support 1000Mbps? Edited April 27, 2017 by bonienl Quote Link to comment
lafrance Posted April 27, 2017 Author Share Posted April 27, 2017 3 hours ago, bonienl said: Everything looks fine. Instead of using your router 192.168.0.1 as DNS server use the google DNS servers 8.8.8.8 and 8.8.4.4 Ps. Your connection is only 100Mbps, does your router not support 1000Mbps? Thanks for the suggestion. I've actually tried this and it doesn't make any difference at all. Soon as the machine is rebooted if i set the IP address to 192.168.0.10 it reports: 192.168.0.1/24 dev br0 proto kernel scope link src 192.168.0.10 linkdown Quote Link to comment
JorgeB Posted April 27, 2017 Share Posted April 27, 2017 1 minute ago, lafrance said: Thanks for the suggestion. I've actually tried this and it doesn't make any difference at all. Soon as the machine is rebooted if i set the IP address to 192.168.0.10 it reports: 192.168.0.1/24 dev br0 proto kernel scope link src 192.168.0.10 linkdown Have you actually tried to connect to server? More than once I've seen linkdown reported in the console and the link is up and working. Quote Link to comment
bonienl Posted April 27, 2017 Share Posted April 27, 2017 Quote I can still get access to the GUI but no internet The usual suspect is DNS when this occurs, but you say that google DNS isn't working either... Another possbility is your router not allowing communication for unknown hosts (read: no DHCP assigned hosts), might be a security setting on your router. Quote Link to comment
joedotmac Posted April 27, 2017 Share Posted April 27, 2017 (edited) unraid doesn't have dig or nslookup binaries load. Why? I'm certain there's sound reasoning. Issue these commands paste output here: arp -an This will dump the ARP cache with any hosts that unraid is exchanging ethernet frames with on the local wire, your br0/eth0 interface. cat /etc/resolv.conf This should provide a list and order of DNS servers being used netstat -rn |more routing table Try using telnet on port 80 with a hostname and with an IP address as noted below. If connectivity is successful you'll get the line with the escape character line and the shell will appear to hang. You'll have to ctrl c and or ctrl z a few times to dump out of it. root@unraid:/etc# telnet www.ibm.com 80 Trying 23.210.3.4... Connected to www.ibm.com. Escape character is '^]'. Connection closed by foreign host. root@unraid:/etc# telnet 23.210.3.4 80 Trying 23.210.3.4... Connected to 23.210.3.4. Escape character is '^]'. cat /etc/nsswitch.conf will give you the order of name resolution methods. The line your looking for is: hosts: files dns wins mdns Some ISP's will limit DNS queries outside of their infrastructure, forcing users to use the ISP's DNS. This is usually done to limit or mitigate DNS cache poisoning attacks. Might want to try using your ISP's primary and secondary DNS. Edited April 27, 2017 by joedotmac Quote Link to comment
unevent Posted April 27, 2017 Share Posted April 27, 2017 3 hours ago, lafrance said: Thanks for the suggestion. I've actually tried this and it doesn't make any difference at all. Soon as the machine is rebooted if i set the IP address to 192.168.0.10 it reports: 192.168.0.1/24 dev br0 proto kernel scope link src 192.168.0.10 linkdown Are you setting the IP to the static address in the unRAID GUI and then rebooting? DNS looks fine, I am assuming a correctly configured DNS on router since under DHCP you connect to Internet fine. What kind of router are you using (brand/model)? Using the original firmware with it? Any settings in the router to restrict only to DHCP clients? Since you say under static IP you can connect to the unRAID GUI, but cannot connect to the Internet (from unRAID?) it sounds like a possible gateway issue which points to the router configuration since the gateway address in unRAID is being set correctly. Reboot the router first and test, then go from there with providing more details on your router. Quote Link to comment
lafrance Posted April 30, 2017 Author Share Posted April 30, 2017 On 27/04/2017 at 4:10 PM, joedotmac said: unraid doesn't have dig or nslookup binaries load. Why? I'm certain there's sound reasoning. Issue these commands paste output here: arp -an This will dump the ARP cache with any hosts that unraid is exchanging ethernet frames with on the local wire, your br0/eth0 interface. cat /etc/resolv.conf This should provide a list and order of DNS servers being used netstat -rn |more routing table Try using telnet on port 80 with a hostname and with an IP address as noted below. If connectivity is successful you'll get the line with the escape character line and the shell will appear to hang. You'll have to ctrl c and or ctrl z a few times to dump out of it. root@unraid:/etc# telnet www.ibm.com 80 Trying 23.210.3.4... Connected to www.ibm.com. Escape character is '^]'. Connection closed by foreign host. root@unraid:/etc# telnet 23.210.3.4 80 Trying 23.210.3.4... Connected to 23.210.3.4. Escape character is '^]'. cat /etc/nsswitch.conf will give you the order of name resolution methods. The line your looking for is: hosts: files dns wins mdns Some ISP's will limit DNS queries outside of their infrastructure, forcing users to use the ISP's DNS. This is usually done to limit or mitigate DNS cache poisoning attacks. Might want to try using your ISP's primary and secondary DNS. Hi Joedotmac Apologies for the slow reply but work commitments got in the way. I really appreciate your help with this and will take a look in the next couple of weeks. I have a feeling this is a combination of a real problem coupled with me being a bit thick. I'm away at the moment and will get back on the case when I get back. The OS is really great and does everything we need in the house so fixing this has a priority. Again many thanks for your help. LaFrance Quote Link to comment
lafrance Posted April 30, 2017 Author Share Posted April 30, 2017 On 27/04/2017 at 5:58 PM, unevent said: Are you setting the IP to the static address in the unRAID GUI and then rebooting? DNS looks fine, I am assuming a correctly configured DNS on router since under DHCP you connect to Internet fine. What kind of router are you using (brand/model)? Using the original firmware with it? Any settings in the router to restrict only to DHCP clients? Since you say under static IP you can connect to the unRAID GUI, but cannot connect to the Internet (from unRAID?) it sounds like a possible gateway issue which points to the router configuration since the gateway address in unRAID is being set correctly. Reboot the router first and test, then go from there with providing more details on your router. Hi Unevent Thanks for this as the suggestions are very helpful. I'm away at the moment and will get back onto this when we return. LaFrance Quote Link to comment
lafrance Posted April 30, 2017 Author Share Posted April 30, 2017 On 27/04/2017 at 1:50 PM, johnnie.black said: Have you actually tried to connect to server? More than once I've seen linkdown reported in the console and the link is up and working. Hi Johnnie Thanks for this as your suggestion made me check on a couple of things. LaFrance Quote Link to comment
lafrance Posted April 30, 2017 Author Share Posted April 30, 2017 On 27/04/2017 at 1:58 PM, bonienl said: The usual suspect is DNS when this occurs, but you say that google DNS isn't working either... Another possbility is your router not allowing communication for unknown hosts (read: no DHCP assigned hosts), might be a security setting on your router. Bonienl Apologies for the tardy reply. This seems to have been a combination of things which I'm still figuring out. One of which as you say was an issue with what is in fact an old router coupled with a flaky ISP connection. Thanks for your help. LaFrance 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.