RBR850 Frequent Disconnects Starting March 9th AM EST

It may not appear as something available to update. "No need to do anything as this will be auto pushed for users who are using RBK852/RBK853S."

This will be pushed by NG when they trigger this. 

For those who have blocked the update servers, you'll need to unblock them to be sure your RBR gets the push. 

It's not push, it's more like fetch, despite what they say (happy to share wiresharks, I was one of the ones who helped others block the NG servers). Either the firmware is available for fetch/pull by the router, or it's not. It's not.

Were you able to get your system re-updated? 

---

MeGrimlock wrote:

I'm only seeing 3.2.9.2 as the auto downloaded FW?

---

migsta wrote:
Orbi AX is just garbage. No connection to any outdoor cameras, indoor Arlo is horrible and there is no outdoor strength on these things. Tried all settings for WiFi Chanel’s and RT and CT settings but nothing. Time to sell this piece of garbage.

---

thanks for that help ful post!

migsta

Have you tried disabling the AX feature on RBR850 to see if the issue goes away with the cameras? A lot of these issues with AX routers occur due to developers of the wireless clients, cameras, IoT devices and etc. are lagging in keeping up with technology updates. Most of the issues with Nest Cams, Ring Doorbell, Alexa, Arlo, etc. can be resolved by having those clients updated. Theses issues you are seeing are most likely related to the client devices having issues with one or more new features introduced in the 802.11AX wifi standard. We all had the same issues before when 802.11N and 802.11AC standards first came around it took a while for end-user client manufacturers to catch up to the router manufacturers.

If you are having issues with getting the cameras connected to Orbi AX try the following. Disable AX feature on your Orbi AX and let the cameras connect once connected enable the AX again and see if you have issues with connectivity. Also, make sure that your client devices are fully up to date with software and firmware.

My two NEST controllers and 3 D-Link cameras are working well with Orbi AX. Though my cameras are not outdoors. 

Glad you found a solution that works. I seriously considered the nest but have used netgear for years and wanted AX. 

And did the last FW re-load fix your problems on the WoW services? 

---

McLong wrote:

Glad you found a solution that works. I seriously considered the nest but have used netgear for years and wanted AX. 

---

One issue I found with this firmware that I didn't have with previous firmwares is that is doesn't reserve static IP addresses  that I assigned to devices and hands them out in order.  When the device that the static IP address was assigned to "asks" for it, it does get it, but the other device, that got it originally, never gets a new one, and stays off the network. A simple reboot does not solve the issue. The only way to figure out what didn't get one is go through the list and see what's not showing up and then reboot that particular device.  Never had to do that before this firmware. 

Please make a new post about issues your seeing. This thread is mostly for the frequenct disconnects seen during the time frame NG was having problems with there cloud services. Which has been resolved. 

Thank you. 

---

RafS wrote:

One issue I found with this firmware that I didn't have with previous firmwares is that is doesn't reserve static IP addresses  that I assigned to devices and hands them out in order.  When the device that the static IP address was assigned to "asks" for it, it does get it, but the other device, that got it originally, never gets a new one, and stays off the network. A simple reboot does not solve the issue. The only way to figure out what didn't get one is go through the list and see what's not showing up and then reboot that particular device.  Never had to do that before this firmware. 

 

---

I thought this would be why some people are still having disconnects and why I posted it in here.  If two devices are sharing an IP address, they would obviously continue to disconnect from the network. The two devices shared an IP address and while that's not supposed to happen, that's exactly what did happen and it's what may be happening to folks who may still be experiencing issues, like with the cameras. 

Most of the disconnects were when the NG cloud services became problematic. Most of the disconnects should be resolved. Also changing of the CTS and RTS values can held as well. If there is a problem with IP addressing, I would make a new thread about it and lets discuss it there. Also know that there are differences between STATIC and Reservation IP addresses. 

---

RafS wrote:

I thought this would be why some people are still having disconnects and why I posted it in here.  If two devices are sharing an IP address, they would obviously continue to disconnect from the network. The two devices shared an IP address and while that's not supposed to happen, that's exactly what did happen and it's what may be happening to folks who may still be experiencing issues, like with the cameras. 

 

---

All of us have put a lot of time and effort trying to resolve our unique network issues (no firmware is an answer to all people and all issues) but I did try reverting to 3.2.9.2 (my RBK 852 is in AP mode). The router and satellite indicated an update available (3.2.10.11) and when I clicked the update button both units upgraded without a hitch. I did a hard reset on both units and setup as a new system using the Orbi app (same SSID and password before the reset and did NOT reload a previous config file). Both 5G and 2.4G wireless channels were set on a channel to avoid interference locally, CTS/RTS set to 2347, 20/40 coexistence deselected on the 2.4G wireless channel. My previous issue with 3.2.9.2 (2.4GHz and 5GHz wireless channels) and my PS4 Pro connectivity has vanished. No issues or dropouts experienced to date (now 2 days operative). 

---

pedroy wrote:
New firmware posted... this firmware works!

---

What?! Now I'm scared. It's been working soooo well for the past few days 😱

---

pedroy wrote:
I’ve been testing it for a week now. I don’t have issues so far...

---

Wait, are you talking about 3.2.10.11? It's not new as of today... You scared me.

3.2.10.11_2.1.12 is the same firmware that started this mess.  It isn't new.  I have seen reports that Netgear claims the issue was "in the cloud" with no additional explanation of how or why that would impact LAN/WiFi performance.  I have, to this point, still been having issues.  I recently disabled the AX WiFi setting/features, and that may have improved connectivity with my WeMo devices and Pixel 2 XL phone that were seeing regular disconnection issues.  Yesterday was particularly bad for my WeMo devices.  Before I disabled AX features on my WiFi yesterday, 90% of them had been offline (not connected to WiFi, so nothing to do with Belkin's cloud...not able to connect to my LAN) for hours.

v10.11 was reposted on NGs download site I believe last week sometime. So users can have access to actual files again.

https://www.netgear.com/support/product/rbk853.aspx#download

It has been posted on the site however was remove after users complained of having problems. This has since been resolved due to the issues not being related to the actual FW or files that came down from NG. The issues were on there cloud systems which have been fixed. 

Users have been posting good operation after NG fixed the issues on there side on 3/19.

For users continuing to have problems after 3/19, please make a new post and we can being troubleshooting the problem to see where it maybe. This thread is getting long and the topic of this thread has been fixed. 

---

TURBOGUARD wrote:

---

pedroy wrote:
I’ve been testing it for a week now. I don’t have issues so far...

---

Wait, are you talking about 3.2.10.11? It's not new as of today... You scared me.

---