Keep getting NETWORK CHANGED message since upgrading to 6.9.0

---

Skywalker wrote:

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 Skywalker

Is that the same image for the RN316 machines? I notice the URL mentions X86, but isn't the 316 processor an AMD chip?

I just want to check before I install and potentially brick my box.

---

Skywalker wrote:

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.

---

I've installed the image on my RN314. I also re-enabled link aggregation on ports 6 & 7 of my S8000. While I still can't ping my NAS, I CAN access the shares and all is working fine otherwise. I have copied a 42Gb test file from the NAS to a local drive and have a peak speed of 108 Mb/sec and average speed of 95.7 (my usual speed pre 6.9.0). Copying the same file back is also as pre 6.9.0 (peaks at 75.9, ave 66.7)

Logs are reporting no bond issues. I'd say this looks fixed with the update. :smileyhappy:

Skywalker ignore the question about whether the firmware update is for RN 316's, I saw that someone else had loaded it onto their 314 and I know that the 316 has the same processor as them.

I have loaded the update onto my 316 and put through quite intensive data writes with two laptops copying via a GB network 100GB of data from each laptop to the server while at the same time the server being connected via DLNA on my tv with video streaming.

There were no problems at all, the copy processes completed with no network disconnects, the display on the NAS stayed completely blank and the DLNA streaming continued uninterrupted - so I would say that you have managed to resolve the issue (at least from my perspective).

Thanks to everyone who helped get this fixed, including end users who provided logs to Netgear for investigating :smileyhappy:

I have just completed transferring 260GB of files each ranging from 6.6GB to 19.3GB without a problem.

At the same time DLNA was uninterrupted.

It appears that the problem has been solved. Would it be correct that it is 314x specific and if so does that mean that future updates might again be a problem for the 314 design? (It is not the Nighthawk switch as I don't have one - I have the FVS318G router).

Thank you sincerely to everybody at Netgear and in the community who have obviously worked very hard and with the customers to solve this problem.

David

Skywalker Good morning Sir.

After applying the supplied image, and battering the RN with heavy R/W, I can not reproduce the same error I have seen before.
4 clients doing Timemachine backups, 2 nfs-clients doing md5sum-checks on various files and one iscsi-vmware-initiator doing its thing.

High load expected on the RN, but no signs everywhere of flapping.

I must say I'm very impressed on the speed that you have solved this.
5-6 days (Weekend included) after people starting to notice the issue, you have  pinpointed the bug, eliminated it and deployed a fix to the "public".

Good job guys, keep it up.

// T

Thanks mdgm.

I guess Netgear (and other vendors) are in a no-win situation here as you, as we do, assume drivers provided to you work properly.

I have never met such an animal as bug-free software.

You are right - future drivers (or updates) are taken on faith, not guarantee. I think anybody who expects bug-free softwre deludes themselves.

Anyway, at the end of the day, a sincere thanks for working so hard on this. That has been my experience for several years now - a good record ...

---

Skywalker wrote:

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.

---

This beta did indeed fix the teaming issue in my case as well (LACP to an HP 1820-8G).  Unfornately, I had to revert to 1.9.0 due to another issue.  I was unable to get Docker to install with this beta, and I've been using Docker.  So I had to revert to 6.9.0 for now and live with the network issues.

The official 6.9.1 Beta 1 has been posted, and should work fine for Docker.

Beta version solved it for me as well. Thanks!