October 17, 201015 yr I am almost 100% that the problem is in the Router (configured as switch) You don't need to waste your time on 1st router, you should focus on switch <---------> unRAID, as even in DHCP mode, the layer 2 is also down. as long as this link remain down, there is no traffic. meanwhile for the sake of confirmation, make sure in BIOS you did not disable on board LAN port. Oct 18 10:10:36 Tower logger: /etc/rc.d/rc.inet1: /sbin/ifconfig lo 127.0.0.1 Oct 18 10:10:36 Tower logger: /etc/rc.d/rc.inet1: /sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo Oct 18 10:10:36 Tower ifplugd(eth0)[1242]: ifplugd 0.28 initializing. Oct 18 10:10:36 Tower kernel: r8169: eth0: link down <------------- layer 2 down, no DHCP IP request could be sent out Oct 18 10:10:36 Tower ifplugd(eth0)[1242]: Using interface eth0/1C:6F:65:24:91:10 with driver <r8169> (version: 2.3LK-NAPI) Oct 18 10:10:36 Tower ifplugd(eth0)[1242]: Using detection mode: SIOCETHTOOL Oct 18 10:10:36 Tower ifplugd(eth0)[1242]: Initialization complete, link beat not detected.
October 17, 201015 yr Author In both cases the Syslog shows Link Down so I guess that the problem is in the Router ----> switch -----> UnRaid connection. From now on, keep static IP address assignment, don't switch back to DHCP. The syslog for static IP mode, shown your link between switch/unRAID is not good, this could be (a) the switch port unRAID connect to has problem. (b) the lan port at your unRAID has problem © line between switch and unRAID has problem. since you mention MAC machines have no problem, so unplug one of MAC machine and plug this same line with same switch port it used to unRAID and reboot unRAID. once unRAID is up, check your syslog to find out if link is up or not. If link is still not up, then the problem is (b), if link is up then the problem is either (a) or © you need to figure it out The bottom line, as long as your layer 2 ethernet is not up, you can forget about getting any IP traffic regardless you are in static IP mode or DHCP IP mode. Oct 18 10:05:09 Tower logger: /etc/rc.d/rc.inet1: /sbin/ifconfig lo 127.0.0.1 Oct 18 10:05:09 Tower logger: /etc/rc.d/rc.inet1: /sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo Oct 18 10:05:09 Tower ifplugd(eth0)[1242]: ifplugd 0.28 initializing. Oct 18 10:05:09 Tower kernel: r8169: eth0: link down <----------------- layer 2 is not up, forget about IP layer Oct 18 10:05:09 Tower ifplugd(eth0)[1242]: Using interface eth0/1C:6F:65:24:91:10 with driver <r8169> (version: 2.3LK-NAPI) Oct 18 10:05:09 Tower ifplugd(eth0)[1242]: Using detection mode: SIOCETHTOOL Oct 18 10:05:09 Tower ifplugd(eth0)[1242]: Initialization complete, link beat not detected. OK. so I tried This: a) Switch port and cord between mac and Unraid. Syslog shows link down (syslog LINK1 Attached) b) Switch just ports, using the same cord. Syslog show link down. (Syslog Link2 Attached) c) I Check the Bios, everything is fine. d) Last thing that i tried. I plug my MAC directly to the UnRaid. Set up Static IP in both (192.168.1.10 for the mac / 192.168.1.20 for the UnRaid) Reboot and voila, connect right away. I can add the tower to my inder window and use the web interface. i can ping from the mac to the tower and also log in a telnet session and powerdown the UnRaid. So I guess that the problem is not the NIC in the UnRaid box, right? (SyslogMAC Attached) ANy info that you need to help me out just let me know. And thank you so much for all the time and effort that you are putting in this post. Thx syslogLINK1.txt syslogLINK2.txt syslogMAC.txt
October 17, 201015 yr a) Switch port and cord between mac and Unraid. Syslog shows link down (syslog LINK1 Attached) Oct 18 14:48:16 Tower logger: /etc/rc.d/rc.inet1: /sbin/ifconfig lo 127.0.0.1 Oct 18 14:48:16 Tower logger: /etc/rc.d/rc.inet1: /sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo Oct 18 14:48:16 Tower ifplugd(eth0)[1242]: ifplugd 0.28 initializing. Oct 18 14:48:16 Tower kernel: r8169: eth0: link down Oct 18 14:48:16 Tower ifplugd(eth0)[1242]: Using interface eth0/1C:6F:65:24:91:10 with driver <r8169> (version: 2.3LK-NAPI) Oct 18 14:48:16 Tower ifplugd(eth0)[1242]: Using detection mode: SIOCETHTOOL Oct 18 14:48:16 Tower ifplugd(eth0)[1242]: Initialization complete, link beat not detected. d) Last thing that i tried. I plug my MAC directly to the UnRaid. Set up Static IP in both (192.168.1.10 for the mac / 192.168.1.20 for the UnRaid) Reboot and voila, connect right away. I can add the tower to my inder window and use the web interface. i can ping from the mac to the tower and also log in a telnet session and powerdown the UnRaid. So I guess that the problem is not the NIC in the UnRaid box, right? (SyslogMAC Attached) Oct 18 15:11:36 Tower logger: /etc/rc.d/rc.inet1: /sbin/ifconfig lo 127.0.0.1 Oct 18 15:11:36 Tower logger: /etc/rc.d/rc.inet1: /sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo Oct 18 15:11:36 Tower ifplugd(eth0)[1242]: ifplugd 0.28 initializing. Oct 18 15:11:36 Tower ifplugd(eth0)[1242]: Using interface eth0/1C:6F:65:24:91:10 with driver <r8169> (version: 2.3LK-NAPI) Oct 18 15:11:36 Tower ifplugd(eth0)[1242]: Using detection mode: SIOCETHTOOL Oct 18 15:11:36 Tower ifplugd(eth0)[1242]: Initialization complete, link beat detected. Oct 18 15:11:36 Tower kernel: r8169: eth0: link up Oct 18 15:11:36 Tower kernel: r8169: eth0: link up Oct 18 15:11:36 Tower ifplugd(eth0)[1242]: Executing '/etc/ifplugd/ifplugd.action eth0 up'. Oct 18 15:11:36 Tower logger: /etc/rc.d/rc.inet1: /sbin/ifconfig eth0 192.168.1.20 broadcast 192.168.1.255 netmask 255.255.255.0 Oct 18 15:11:36 Tower logger: /etc/rc.d/rc.inet1: /sbin/route add default gw 192.168.1.1 metric 1 Oct 18 15:11:36 Tower ifplugd(eth0)[1242]: Program executed successfully. I think it is very clear your switch (The one from Zyxel) has problem to handshake with your unRAID at layer 2 level. At this moment, i think the options are (a) connect unRAID to router (not switch) and verify if link is up during boot up time. From your posts, router is from Linksys and switch is Zyxel, right? (b) Replace this Zyxel switch with another one. if you don't have spare switch then you might want to find out if there is any known issue for this Zyxel switch with certain ethernet chips. in the mean time, what kind of motherboard you use for unRAID?
October 18, 201015 yr Author I am giong to try now the same but pluged in to the Linksys router. And ill be posting the Syslogs for that I have a GIGABYTE GA-880GA Mobo
October 18, 201015 yr I have a GIGABYTE GA-880GA Mobo This MB has Realtek 8111D, according to unRAID Wiki, this one is not in Hardware Compatibility list yet. Not sure the driver for RTL8169 is going to be fully compatible or not. http://lime-technology.com/wiki/index.php?title=Hardware_Compatibility#Network_Controllers Oct 18 15:11:36 Tower kernel: r8169: eth0: link up
October 18, 201015 yr Author I have a GIGABYTE GA-880GA Mobo This MB has Realtek 8111D, according to unRAID Wiki, this one is not in Hardware Compatibility list yet. Not sure the driver for RTL8169 is going to be fully compatible or not. http://lime-technology.com/wiki/index.php?title=Hardware_Compatibility#Network_Controllers Oct 18 15:11:36 Tower kernel: r8169: eth0: link up So the problem is that mi NIC is not compatible?? Well that sucks for me. Im pretty sure that i asked beforehand. Anyways. Any idea or any solution for me? Should i get a new NIC or im screwed forever? And how is that when i plug it directly works fine? I dont understand that. Thx
October 18, 201015 yr I have a GIGABYTE GA-880GA Mobo This MB has Realtek 8111D, according to unRAID Wiki, this one is not in Hardware Compatibility list yet. Not sure the driver for RTL8169 is going to be fully compatible or not. http://lime-technology.com/wiki/index.php?title=Hardware_Compatibility#Network_Controllers Oct 18 15:11:36 Tower kernel: r8169: eth0: link up So the problem is that mi NIC is not compatible?? Well that sucks for me. Im pretty sure that i asked beforehand. Anyways. Any idea or any solution for me? Should i get a new NIC or im screwed forever? And how is that when i plug it directly works fine? I dont understand that. Thx That is just ONE of possibilities. As I say before "It takes two to tango". In networking, both sides need to talk the same language and run at same pace. That is also the troubling parts in so called "compatibility". Your options, at this moment, are (a) Update system BIOS if there is one available for updating LAN. Board vendors do release new BIOS for this purpose from time to time. New BIOS might fix this problem. (b) Look for latest LAN driver can run at unRAID that particularly support this chip set. © Use an add-on LAN card with known compatible chip for example Realtek 8111C. Mine is using this chip and it has been working great since day one. (d) Replace switch, different switch vendor might use different chips. By using different switch when handshaking with unRAID using r8169 driver + Realtek 8111D chip, both sides might work together. (e) Move unRAID to router, reason is same as (d), different switch vendors might use different chipset.
October 18, 201015 yr Author I have a GIGABYTE GA-880GA Mobo This MB has Realtek 8111D, according to unRAID Wiki, this one is not in Hardware Compatibility list yet. Not sure the driver for RTL8169 is going to be fully compatible or not. http://lime-technology.com/wiki/index.php?title=Hardware_Compatibility#Network_Controllers Oct 18 15:11:36 Tower kernel: r8169: eth0: link up So the problem is that mi NIC is not compatible?? Well that sucks for me. Im pretty sure that i asked beforehand. Anyways. Any idea or any solution for me? Should i get a new NIC or im screwed forever? And how is that when i plug it directly works fine? I dont understand that. Thx That is just ONE of possibilities. As I say before "It takes two to tango". In networking, both sides need to talk the same language and run at same pace. That is also the troubling parts in so called "compatibility". Your options, at this moment, are (a) Update system BIOS if there is one available for updating LAN. Board vendors do release new BIOS for this purpose from time to time. New BIOS might fix this problem. (b) Look for latest LAN driver can run at unRAID that particularly support this chip set. © Use an add-on LAN card with known compatible chip for example Realtek 8111C. Mine is using this chip and it has been working great since day one. (d) Replace switch, different switch vendor might use different chips. By using different switch when handshaking with unRAID using r8169 driver + Realtek 8111D chip, both sides might work together. (e) Move unRAID to router, reason is same as (d), different switch vendors might use different chipset. (e) I already tried the UnRaid in my router with no luck. Im looking now for a new Bios or LAN Driver Probably would be easier and faster for me to get on add-on LAN card, any recommendation on this?
October 18, 201015 yr Author I have one update. Looking for a Driver to mi R111D I came across this post in a Ubuntu forum. In this post they explain that this NIC has a problem with the WOL and can't get the connection up again once is going in suspension mode. Anyway, I didn't change absolutely anything, just unplug my tower for 20 secs, turn ON again and everything is working fine. I can ping / see the tower in the network and the tower did get IP address right away. I have Internet in all the macs and can access the Web GUI from all the Mac's too. I guess that now i have to figure out how can i solve this problem. I don't want to unplug the server every time that goes on suspension mode. Maybe i can deactivate that on the Bios. Going to take a look at that in the ubuntu forums. Tank you so much GK20 for your time. I really apreciate your help on this. If you ever come down to Chile ill buy you a drink ! Thank you!
October 18, 201015 yr I have one update. Looking for a Driver to mi R111D I came across this post in a Ubuntu forum. In this post they explain that this NIC has a problem with the WOL and can't get the connection up again once is going in suspension mode. Anyway, I didn't change absolutely anything, just unplug my tower for 20 secs, turn ON again and everything is working fine. I can ping / see the tower in the network and the tower did get IP address right away. I have Internet in all the macs and can access the Web GUI from all the Mac's too. You can check and manage WOL setting on your Ethernet by ethtool command. By default is should be set to "wake up by magic packet" (the g option). to check up, use "ethtool eth0". http://linuxcommand.org/man_pages/ethtool8.html Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000033 (51) Link detected: yes
October 18, 201015 yr Author weird. I have exactly the same thing, except for the speed Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised auto-negotiation: Yes Speed: 100Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000033 (51) Link detected: yes
October 18, 201015 yr Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised auto-negotiation: Yes Speed: 100Mb/s Just to confirm, are you using Cat5e or Cat6 cable? if not, you should otherwise you will not have GE speed. If you do, This meant, even with this "workaround" after negotiation, both sides settle down on the speed of 100Mbps. That meant your unRAID will have only 100Mbps speed, not good but at least 1st step. Try to manipulate WOL option see if it helps, if not then most likely with current kernel version and driver with this switch, that is what you can get.
October 18, 201015 yr Author All the cables are Cat6, except the one going from the Swith to the UnRaid! Lol I am going to try replace it by tomorrow, but im not sure if it's going to make any difference. Im not sure about the Switch Speed.
Archived
This topic is now archived and is closed to further replies.