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.
I followed these specific directions and did indeed get both router and satellite downgraded back to 3.2.9.2
However, upon coming back to the setup screen on the web-based interface, it is clear to me that 3.2.10.11 is still a valid "signed" firmware version on the Netgear servers - i have several points of evidence for this:
1) The top of the setup web page has the purple oval flag saying there is a "new version of Firmware available (3.2.10.11)
2) The firmware update page under advanced/administration also shows new firmware when it checks for both router and satellite
3) Within 15 mins after being online, the router and satellite both auto-upgrade BACK to 3.2.10.11
Dropouts are horrible, especially with my iphone (Xr) using AT&T wifi calling - every 5-10 mins at least, consistently. Never saw this with 3.2.9.2.
This is so disappointing - longtime Orbi user with the old RBR50/RBS50 and now with the AX version, how many flawed/ruined auto upgrades have we had? This is insanity. Can we please have NETGEAR remove this flawed firmware? It's clearly problematic for many of us...
Be sure that CTS and RTS values are changed to 2347 under Advanced Tab/Advanced Settings/Wireless Settings
Please contact Christian_R
He's now working with those of you effected by this FW update.
Thank you.
ehl1 wrote:I followed these specific directions and did indeed get both router and satellite downgraded back to 3.2.9.2
However, upon coming back to the setup screen on the web-based interface, it is clear to me that 3.2.10.11 is still a valid "signed" firmware version on the Netgear servers - i have several points of evidence for this:
1) The top of the setup web page has the purple oval flag saying there is a "new version of Firmware available (3.2.10.11)
2) The firmware update page under advanced/administration also shows new firmware when it checks for both router and satellite
3) Within 15 mins after being online, the router and satellite both auto-upgrade BACK to 3.2.10.11
Dropouts are horrible, especially with my iphone (Xr) using AT&T wifi calling - every 5-10 mins at least, consistently. Never saw this with 3.2.9.2.
This is so disappointing - longtime Orbi user with the old RBR50/RBS50 and now with the AX version, how many flawed/ruined auto upgrades have we had? This is insanity. Can we please have NETGEAR remove this flawed firmware? It's clearly problematic for many of us...
Sorry- i immediately changed CTS and RTS to 2347 - still having issues...
Will contact ChristianR as you recommend - thanks
Did you reboot the RBR and RBS and all wireless devices after making the change?
NG is aware of this and seems to be working on it. No idea when a fix will be forth coming so don't ask. :smileywink: Hopefully soon.
ehl1 wrote:Sorry- i immediately changed CTS and RTS to 2347 - still having issues...
Will contact ChristianR as you recommend - thanks
I had issues with devices dropping on 10.11 but after getting home and changine the RTS and CTS values to 2347 from 64, then rebooting the system, everything is working great. I would say things are actually connecting a lot smoother than they did before the update. Rebooting the system after changing the values is a big factor here that I have a feeling a lot of people are skipping due to the Orbi going offline when you apply the changes so they figure that takes care of the reboot. But anyhow, 10.11 seems to be working fine for me at this point.
