NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Orbi Firmware v3.2.10.11 seen on your RBRs FW update check page?
Just curious if anyone out here in the public forum are seeing this version pop up as available on there RBRs web page? IF so, please post what version of FW you currently have loaded. Up to y...
Problems seen on v10.11 since 3/9 have been addresses and fixed by NG. They reported that it was something having to do with there cloud systems. v10.11 FW was put back up on there auto update servers for users to download as of 3/19. These problems have been resolved.
If users are noticing any futher problems please make a new post about it or contact NG support.
Enjoy.
Be sure to set CTS and RTS values from 64 to 2347. Under Advanced Tab/Advanced Settings/Wireless Settings
Sevo123 wrote:
Firmware v3.2.10.11 Causing a whole bunch of issues with my Arlo Ultra base stations... going offline its a mess... couldn’t access my cameras all day after the update. Keeps disconnecting. I was notified by my arlo support that this latest firmware is causing issues with Arlo.
The tech on the phone did have me set the CTS/RTS threshold values to 2347, but I had no luck with this.
I was able to put the system back in place yesterday evening and capture logs while the problem was still occuring on 3.9.2. I'm going to submit those today to my open ticket in hopes that they will review them.
Has anyone truly had success reverting the firmware, or am I the only one dead in the water?
Thanks for letting us know. There was been some that have downgraded. If this still fails to work right even after a factory reset and setup from scratch, you might temporarily pull out your prior router if you have one and set it up as your main host router and configure the RBR for AP mode while your system and support ticket gets reviewed. Make contact with Christian_R as well:
xnolightx wrote:The tech on the phone did have me set the CTS/RTS threshold values to 2347, but I had no luck with this.
I was able to put the system back in place yesterday evening and capture logs while the problem was still occuring on 3.9.2. I'm going to submit those today to my open ticket in hopes that they will review them.
Has anyone truly had success reverting the firmware, or am I the only one dead in the water?