MR60 / MS60 - Firmware Update v1.0.6.102

Hi Christian,

Thanks for asking and here is my feedback, I'm afraid I am still stuck on Firmware Version 1.0.4.98 (MK63) with 20WiFi + 12 wired devices, this is fairly stable(not perfect), I have tried the below firmwares more than once but keep going back as like many others I am working from home and need stability, I have had to disable auto updates, my speeds are good.

I have also suffered from the port forward bug https://community.netgear.com/t5/Nighthawk-Mesh-System/Nighthawk-MK62-Port-forward-list-empty/td-p/1946565/jump-to/first-unread-message, but found a work around not a fix.

1) Firmware Version 1.0.5.102(Many disconnects) of both the satellites & wifi clients after completing a factory default & new setup.

2) Firmware Version 1.0.6.102(Many disconnects) of both the satellites & wifi clients after completing a factory default & new setup.

Kev in the UK

Has anyone had issues with ethernet connectivity with the new firmware update? My new setup was working fine for several days, Nighthawk Mesh MR60 with 2 satelites. Router connected to a Netgear switch, which in turn has two other switches downstream. Combination of wireless and wired devices. All of sudden in the middle of the day all the ethernet devices stopped working, the computers can't get an IP address. Rebooted everything a million times, swapped cables etc no luck. 

Thought I should close my loop for whomever might be reading this thread. After days of troubleshooting and pulling out what little hair I have left, I finally found my issue. It wasn't with the Nighthawk itself, it was with a new TP Link downstream switch I had installed at one of our computers. The timing of everything made it appear that this was unrelated, but after doing a lot of other things I finally had the notion to unplug every device from all my switches (I've actually got 4 on my network) and then plug each device in one by one and see if it caused any issues. I guess the bad device was somehow causing a loop, all the ports with cables plugged in when it was malfunctioning would blink together in unisom, not the normal erratic blinking when each port is processing traffic. So, thanks for the help and suggestions, and good luck to anyone who is struggling with these types of issues.

Ok I'm giving Firmware Version 1.0.6.102 another go, MK63 Router/Sats all reset to factory default & working perfectly 17:00 (UK)

I will keep you posted.

Kev

Firmware Version 1.0.6.102 update

Disconnects
Day 1 – 27/08/2020
1) No problem
Day 2 – 28/08/2020
1) Echo show (17hrs) – had to manually reconnect.
2) Network Map – (17hrs) noticed that satellites are in series not the star connection, 1hr later shows back to star config.
Day 3 – 29/08/2020
1) 16:00 Red light at the front of MR, everything disconnected whilst eating dinner, 4 minutes later everything re-connected apart from 1 x echo spot, 1 x echo show & 3 x smoke detectors.
2) 17:15 PLEX will not run without buffering, Rebooted MR, red light showing for approx. 4 mins
(i) 32 x devices reconnected out of 37.
(ii) 3 x smoke detectors solely on the Guest network did not reconnect.
(iii) Ref (ii) Guest network is now unticked and disabled in settings.

Kev

Day 4 – 30/08/2020

1) No problem

Day 5 – 31/08/2020

1) AM: Woke to find everything disconnected including smoke detectors, red lights on all nighthawk units.

2) Rebooted MR & Satellites, had to switch off/on most devices before they would reconnect.

3) After reboot guest network was disabled.

4) For safety regarding my smoke detectors I have gone back to Firmware Version 1.0.4.98 as I get at least 12 days plus, before a MR reboot.

christian, again here is my feedback, If I can help pin this down please feel free to raise to the techs

Kev

This router is not working for me, so I have decided to return it. But I thought that I would offer my opinion that the problem may lie in the implementation of the S protocol. Because of the topology of my home, I often spend a significant portion of time in the overlap area between the router and the one satellite that I have deployed, and even spend a fair amount of time in an area that is almost exactly at the midpoint between the two; I seem to get the most network connection drops when I am in that overlap area. I think it's entirely possible that when a strong signal is present from both the router and the satellite, the S protocol implementation gets confused and switches between the two stations, which can take some time and it is possible that it gives up because it can't decide which station to connect to. It is conceivable that the thresholds for abandoning an existing connection to a station in favor of a new connection to a different station are not appropriately set and/or that the signal strength variability of the router is too great to properly assess the most appropriate station to connect to.

im experiencing the same issues as Kev has anyone else had issues trying to login to the routers web interface? Sometimes it will work then other times it will tell me my password is incorrect several times and when i reset it i will try to ligin again for it to tell me it is still incorrect. :\

I bought this as it was the most expensive in the store and I wanted the best possible wifi experience at home (which I also work from)

Sadly after trying everything from community, other online forums, youtube, and of course updating to 1.0.6.102, I am still finding my phone + smart TVs dropping out 

the consistent "cannot find IP address" issue that I am starting to lose confidence owning another Netgear device.

Sadly I wanted to love this device but the idea that I have to reset the router every single day numerous times a day or every time I turn on my television is just something I don't think justifies the high price tag for this product.

I have had zero problems with any of the previous Firmware versions.  I have always updated via the upload button in the web interface when I happen to be in it and see that there was an update rather than do it manually, so I unfortunately didn't have a copy of any previous versions.  This one (1.0.6.102) has broken my system.  I was able to back track to 1.0.4.92 from the support page, but .98 isn't downloading for me.  I was able to get 1.0.5.102 but that led to more "cannot get IP" messages.  I don't believe I was previously on 1.0.5.102.  Thankfully 1.0.4.92 has gotten things back to normal.  It's ironic that the update to address wifi connectivity broke mine.  #2020.