NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Keep getting NETWORK CHANGED message since upgrading to 6.9.0
Yesterday I upgraded the firmware on my RN 316 to the latest firmware 6.9.0. Since upgrading I have noticed that I keep getting the words NETWORK CHANGED on the NAS display which will then change to ...
Thanks for the detailed information. We are now able to duplicate the issue using a Nighthawk S8000 switch. After updating the firmware to the version I mentioned earlier, the problem went away. You can now download 6.9.1-T119 here, and it should resolve the issue. Please confirm if it works for you.
Hi,
Please don't forget the RN214 (ARM processor). Since I upgraded to 6.9.0, I have the message:
Fri Nov 3 2017 13:35:37 System: Bond interface bond0 has slave interface eth0 offline
I tried to use Static IP or DHCP, same issue.
Logs for eth0:
root@viking-nas:~# dmesg -T | grep "eth0" [Fri Nov 3 13:34:44 2017] al_eth 0000:00:01.0 eth0: AnnapurnaLabs unified 1Gbe/10Gbe found at mem fe000000, mac addr a0:63:91:9c:1b:fa [Fri Nov 3 13:34:47 2017] al_eth 0000:00:01.0 eth0: using MSI-X per Queue interrupt mode [Fri Nov 3 13:34:47 2017] al_eth 0000:00:01.0 eth0: phy[4]: device 8:04, driver Atheros 8035 ethernet [Fri Nov 3 13:34:47 2017] al_eth 0000:00:01.0 eth0: phy[4]:supported 2ef adv 2ef [Fri Nov 3 13:34:47 2017] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [Fri Nov 3 13:34:51 2017] al_eth 0000:00:01.0 eth0: Link is Up - 1Gbps/Full - flow control rx/tx [Fri Nov 3 13:34:51 2017] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [Fri Nov 3 13:35:05 2017] al_eth 0000:00:01.0 eth0: al_eth_down [Fri Nov 3 13:35:05 2017] bond0: Adding slave eth0 [Fri Nov 3 13:35:05 2017] al_eth 0000:00:01.0 eth0: using MSI-X per Queue interrupt mode [Fri Nov 3 13:35:05 2017] al_eth 0000:00:01.0 eth0: phy[4]: device 8:04, driver Atheros 8035 ethernet [Fri Nov 3 13:35:05 2017] al_eth 0000:00:01.0 eth0: phy[4]:supported 2ef adv 2ef [Fri Nov 3 13:35:05 2017] bond0: Enslaving eth0 as a backup interface with a down link [Fri Nov 3 13:35:09 2017] al_eth 0000:00:01.0 eth0: Link is Up - 1Gbps/Full - flow control rx/tx [Fri Nov 3 13:35:09 2017] bond0: link status definitely up for interface eth0, 1000 Mbps full duplex [Fri Nov 3 13:35:19 2017] NETDEV WATCHDOG: eth0 (al_eth): transmit queue 3 timed out [Fri Nov 3 13:35:19 2017] al_eth 0000:00:01.0 eth0: al_eth_reset_task restarting interface [Fri Nov 3 13:35:19 2017] al_eth 0000:00:01.0 eth0: al_eth_down [Fri Nov 3 13:35:19 2017] al_eth 0000:00:01.0 eth0: free uncompleted tx skb qid 3 idx 0x0 [Fri Nov 3 13:35:19 2017] al_eth 0000:00:01.0 eth0: free uncompleted tx skb qid 3 idx 0x1 [Fri Nov 3 13:35:19 2017] al_eth 0000:00:01.0 eth0: free uncompleted tx skb qid 3 idx 0x2 [Fri Nov 3 13:35:19 2017] al_eth 0000:00:01.0 eth0: free uncompleted tx skb qid 3 idx 0x3 [Fri Nov 3 13:35:19 2017] al_eth 0000:00:01.0 eth0: free uncompleted tx skb qid 3 idx 0x4 [Fri Nov 3 13:35:19 2017] al_eth 0000:00:01.0 eth0: free uncompleted tx skb qid 3 idx 0x5 [Fri Nov 3 13:35:19 2017] al_eth 0000:00:01.0 eth0: free uncompleted tx skb qid 3 idx 0x6 [Fri Nov 3 13:35:19 2017] al_eth 0000:00:01.0 eth0: free uncompleted tx skb qid 3 idx 0x7 [Fri Nov 3 13:35:19 2017] al_eth 0000:00:01.0 eth0: free uncompleted tx skb qid 3 idx 0x8 [Fri Nov 3 13:35:19 2017] al_eth 0000:00:01.0 eth0: free uncompleted tx skb qid 3 idx 0x9 [Fri Nov 3 13:35:19 2017] al_eth 0000:00:01.0 eth0: free uncompleted tx skb qid 3 idx 0xa [Fri Nov 3 13:35:19 2017] al_eth 0000:00:01.0 eth0: free uncompleted tx skb qid 3 idx 0xb [Fri Nov 3 13:35:19 2017] al_eth 0000:00:01.0 eth0: free uncompleted tx skb qid 3 idx 0xc [Fri Nov 3 13:35:19 2017] al_eth 0000:00:01.0 eth0: free uncompleted tx skb qid 3 idx 0xd [Fri Nov 3 13:35:20 2017] al_eth 0000:00:01.0 eth0: using MSI-X per Queue interrupt mode [Fri Nov 3 13:35:20 2017] bond0: link status definitely down for interface eth0, disabling it
Logs for eth1:
root@viking-nas:~# dmesg -T | grep "eth1" [Fri Nov 3 13:34:44 2017] al_eth 0000:00:03.0 eth1: AnnapurnaLabs unified 1Gbe/10Gbe found at mem fe020000, mac addr a0:63:91:9c:1b:fb [Fri Nov 3 13:34:47 2017] al_eth 0000:00:03.0 eth1: using MSI-X per Queue interrupt mode [Fri Nov 3 13:34:47 2017] al_eth 0000:00:03.0 eth1: phy[5]: device 18:05, driver Atheros 8035 ethernet [Fri Nov 3 13:34:47 2017] al_eth 0000:00:03.0 eth1: phy[5]:supported 2ef adv 2ef [Fri Nov 3 13:34:47 2017] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready [Fri Nov 3 13:34:51 2017] al_eth 0000:00:03.0 eth1: Link is Up - 1Gbps/Full - flow control rx/tx [Fri Nov 3 13:34:51 2017] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready [Fri Nov 3 13:35:05 2017] al_eth 0000:00:03.0 eth1: al_eth_down [Fri Nov 3 13:35:05 2017] bond0: Adding slave eth1 [Fri Nov 3 13:35:05 2017] al_eth 0000:00:03.0 eth1: using MSI-X per Queue interrupt mode [Fri Nov 3 13:35:05 2017] al_eth 0000:00:03.0 eth1: phy[5]: device 18:05, driver Atheros 8035 ethernet [Fri Nov 3 13:35:05 2017] al_eth 0000:00:03.0 eth1: phy[5]:supported 2ef adv 2ef [Fri Nov 3 13:35:05 2017] bond0: Enslaving eth1 as a backup interface with a down link [Fri Nov 3 13:35:09 2017] al_eth 0000:00:03.0 eth1: Link is Up - 1Gbps/Full - flow control rx/tx [Fri Nov 3 13:35:09 2017] bond0: link status definitely up for interface eth1, 1000 Mbps full duplex
Firmware version:
root@viking-nas:~# dpkg -l |grep readynasos ii readynasos 6.9.0+4 armel ReadyNASOS base system
Is someone had the same issue with a RN214 ? (and solved it ?)
vikingfmo, your issue would be completely different from everything else in this thread, as it has nothing to do with Intel's driver. From your logs, your eth0 interface was not working from the beginning of that boot. Does unplugging and replugging the cable fix it? How about rebooting? Do you see any kernel messages about mdio reads failing?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
