BBLV Posted May 12, 2019 Share Posted May 12, 2019 Appears something broke my network connection, although I didn't change anything when updating Unraid to 6.7.0?? I'm getting the error: "Interface Ethernet Port 1 is down. Check cable!" Any tips? Not sure where to start! Hardware in my sig. Link to comment
Squid Posted May 12, 2019 Share Posted May 12, 2019 24 minutes ago, BBLV said: Any tips? Not sure where to start! Hardware in my sig. Post your diagnostics instead You can do it from the local command prompt by typing in diagnostics Link to comment
BBLV Posted May 12, 2019 Author Share Posted May 12, 2019 59 minutes ago, Squid said: Post your diagnostics instead You can do it from the local command prompt by typing in diagnostics Here you go. Thanks Squid. By the way, I can access the web GUI just fine on my LAN, which was odd to me when it gave me the network down error.. bserver-diagnostics-20190512-0249.zip Link to comment
Squid Posted May 12, 2019 Share Posted May 12, 2019 Because you've got 3 ethernet ports, and a cable is only plugged into one of them (and it's not port 1) Settings for eth0: Supported ports: [ TP ] Supported link modes: 100baseT/Full 1000baseT/Full 10000baseT/Full 2500baseT/Full 5000baseT/Full Supported pause frame use: Symmetric Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 100baseT/Full 1000baseT/Full 10000baseT/Full 2500baseT/Full 5000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on MDI-X: Unknown Link detected: yes driver: atlantic version: 2.0.3.0-kern firmware-version: 3.0.33 expansion-rom-version: bus-info: 0000:07:00.0 supports-statistics: yes supports-test: no supports-eeprom-access: no supports-register-dump: yes supports-priv-flags: no -------------------------------- Settings for eth1: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: Symmetric Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: Symmetric Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Speed: Unknown! Duplex: Unknown! (255) Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: on MDI-X: off (auto) Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000007 (7) drv probe link Link detected: no driver: igb version: 5.4.0-k firmware-version: 3.11, 0x80000469 expansion-rom-version: bus-info: 0000:03:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes -------------------------------- Settings for eth2: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: Symmetric Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: Symmetric Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Speed: Unknown! Duplex: Unknown! (255) Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: on MDI-X: off (auto) Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000007 (7) drv probe link Link detected: no driver: igb version: 5.4.0-k firmware-version: 3.11, 0x80000469 expansion-rom-version: bus-info: 0000:05:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes -------------------------------- But the error is probably coming via Settings - Network Settings Link to comment
BBLV Posted May 12, 2019 Author Share Posted May 12, 2019 Worked just fine for 2+ months on 6.6.7, weird.... Wonder what change in 6.7.0 is incompatible with my previous settings. I would imagine many more people are going to hit this same issue when updating. I'll do some tweaking and see what I can do to fix it and report the fix back here. Link to comment
Cyberalien Posted May 12, 2019 Share Posted May 12, 2019 same question. Server cannot access the internet. I ping the local network is fine ,but cannot ping the ip address outside like 8.8.8.8, it says system error. the dock and vm network is fine . so now I roll it back to 6.6.7 how I can fix this ? check the diagnostics.zip ? Link to comment
Squid Posted May 12, 2019 Share Posted May 12, 2019 Is the Gateway set properly in Settings - Network? Worst case solution you can always rename /config/network.cfg on the flash drive which restores the config to factory defaults. And posting the diagnostics is always the best thing to do Link to comment
BBLV Posted May 12, 2019 Author Share Posted May 12, 2019 I can't figure this out... Nothing changed except the update from 6.6.7 to 6.7.0 and my network won't connect. Tweaking network settings isn't getting me anywhere. I lost remote accessibility from screwing with the network settings, so I had to plug a monitor into the server to access the web GUI. Link to comment
BBLV Posted May 12, 2019 Author Share Posted May 12, 2019 Rolled back to 6.6.7 and my network connection is working immediately without touching any settings.... I'll sit tight and wait for 6.7.1 to have a fix for this. Link to comment
bonienl Posted May 12, 2019 Share Posted May 12, 2019 3 hours ago, BBLV said: Rolled back to 6.6.7 and my network connection is working immediately without touching any settings.... I'll sit tight and wait for 6.7.1 to have a fix for this. Your network configuration is wrong. It has duplicate assignments for eth1 and eth2 interfaces. IPADDR[0]="192.168.1.49" NETMASK[0]="255.255.255.0" GATEWAY[0]="192.168.1.1" IPADDR[1]="192.168.1.49" NETMASK[1]="255.255.255.0" GATEWAY[1]="192.168.1.1" IPADDR[2]="192.168.1.49" NETMASK[2]="255.255.255.0" GATEWAY[2]="192.168.1.1" You can open the "network.cfg" file in the /config folder on your flash device and delete all [1] and [2] references. Then set SYSNICS="1". File content should look like this # Generated settings: IFNAME[0]="br0" DHCP_KEEPRESOLV="yes" DNS_SERVER1="192.168.1.1" DHCP6_KEEPRESOLV="no" BRNAME[0]="br0" BRNICS[0]="eth0" BRSTP[0]="no" BRFD[0]="0" PROTOCOL[0]="ipv4" USE_DHCP[0]="no" IPADDR[0]="192.168.1.49" NETMASK[0]="255.255.255.0" GATEWAY[0]="192.168.1.1" USE_DHCP6[0]="yes" SYSNICS="1" Save the file and reboot the system. Link to comment
bonienl Posted May 12, 2019 Share Posted May 12, 2019 4 hours ago, Cyberalien said: same question. Server cannot access the internet. I ping the local network is fine ,but cannot ping the ip address outside like 8.8.8.8, it says system error. the dock and vm network is fine . so now I roll it back to 6.6.7 how I can fix this ? check the diagnostics.zip ? Post your diagnostics, very likely you have a wrong network configuration. Link to comment
Cyberalien Posted May 12, 2019 Share Posted May 12, 2019 7 hours ago, bonienl said: Post your diagnostics, very likely you have a wrong network configuration. After read your reply , I upgrade system to 6.7 and reconfig the network.cfg in the /config folder in usb stick then I reboot the system . the system can access the internet now . Thank you all . Link to comment
BBLV Posted May 12, 2019 Author Share Posted May 12, 2019 9 hours ago, bonienl said: Your network configuration is wrong. It has duplicate assignments for eth1 and eth2 interfaces. IPADDR[0]="192.168.1.49" NETMASK[0]="255.255.255.0" GATEWAY[0]="192.168.1.1" IPADDR[1]="192.168.1.49" NETMASK[1]="255.255.255.0" GATEWAY[1]="192.168.1.1" IPADDR[2]="192.168.1.49" NETMASK[2]="255.255.255.0" GATEWAY[2]="192.168.1.1" You can open the "network.cfg" file in the /config folder on your flash device and delete all [1] and [2] references. Then set SYSNICS="1". File content should look like this # Generated settings: IFNAME[0]="br0" DHCP_KEEPRESOLV="yes" DNS_SERVER1="192.168.1.1" DHCP6_KEEPRESOLV="no" BRNAME[0]="br0" BRNICS[0]="eth0" BRSTP[0]="no" BRFD[0]="0" PROTOCOL[0]="ipv4" USE_DHCP[0]="no" IPADDR[0]="192.168.1.49" NETMASK[0]="255.255.255.0" GATEWAY[0]="192.168.1.1" USE_DHCP6[0]="yes" SYSNICS="1" Save the file and reboot the system. I applied this change to network.cfg in 6.6.7 and then rebooted. Internet access still worked fine, but was getting the "Interface Ethernet Port 2 is down. Check cable!" error when in the network settings screen. I then updated to 6.7.0 and am back to having no internet access from the server, but still web GUI access.... Weird. Updated diagnostic file attached. bserver-diagnostics-20190512-1727.zip Link to comment
Vr2Io Posted May 12, 2019 Share Posted May 12, 2019 24 minutes ago, BBLV said: I applied this change to network.cfg in 6.6.7 and then rebooted. Internet access still worked fine, but was getting the "Interface Ethernet Port 2 is down. Check cable!" error when in the network settings screen. I then updated to 6.7.0 and am back to having no internet access from the server, but still web GUI access.... Weird. Updated diagnostic file attached. bserver-diagnostics-20190512-1727.zip 101.21 kB · 0 downloads Most should be DNS problem, could you verify domain could be resolve. Does ping outside BY IP success ? Link to comment
bonienl Posted May 12, 2019 Share Posted May 12, 2019 18 minutes ago, BBLV said: Weird. Your diagnostics show there are still (wrong) duplicate entries in network.cfg. Try again. Update the file to the settings mentioned above, and reboot. Link to comment
BBLV Posted May 12, 2019 Author Share Posted May 12, 2019 10 minutes ago, bonienl said: Your diagnostics show there are still (wrong) duplicate entries in network.cfg. Try again. Update the file to the settings mentioned above, and reboot. You were right. For some reason the network.cfg file wasn't saving (I had flash security set to secure - changed it to public and verified that it saved the changes to network.cfg). I rebooted and checked network settings and FINALLY it shows network interface 1 & 2 as inactive. Unraid server network connection is working now on 6.7.0. Thanks for the quick responses and help! Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.