NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
FURRYe38
Mar 09, 2020Guru - Experienced User
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...
- Mar 20, 2020
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.
FURRYe38
Mar 10, 2020Guru - Experienced User
What Firmware is currently loaded?
Be sure to check the CTS and RTS values Under Advanced Tab/Advanced Settings/Wireless Settings. Set them from 64 to 2347 for both 2.4G and 5G radios. Save and apply the setting. Reboot the RBR, RBS and all of your wifi devices. Was noticed that 64 is not a good value on v11 which it should be 2347. May help solve some wifi issues.
Disabling of auto update was never supported officially though others found ways. You can try those on Orbi AX. Doubt it will work.
I've already asked NG to review this and asked them to pull this version of FW from the update servers. Will have to see if that happens.
If you can't seem to get your system back to stable, please contact NG support. Open a support ticket.
dragonmastr wrote:I'm having a lot of connection issues with 3.2.10.11 as well. Downgrading to 3.2.9.2 resolves those connection issues. Does anyone know how to disable the firmware auto-update in order to prevent the router from re-installing 3.2.10.11? I did some Google searches but the answers I found so far only apply the original Orbi router and not the AX6000.
xnolightx
Mar 10, 2020Star
I managed to get the 3.2.9x version to stick while on a call with support. It’s been a long day of swapping hardware out because restoring 3.29x did not work, but I believe these were the steps:
1) Hard reset using the pin on the back of the router.
2) Hard wire to the router and browse to orbilogin.com
3) During the factory restore when the device list is displayed (I think the page title was firmware upgrade) choose to revert the satellite.
4) Finish the reset and browse to the Administration page to perform the downgrade of the router.
The satellite definitely has to be reverted before the main router.
1) Hard reset using the pin on the back of the router.
2) Hard wire to the router and browse to orbilogin.com
3) During the factory restore when the device list is displayed (I think the page title was firmware upgrade) choose to revert the satellite.
4) Finish the reset and browse to the Administration page to perform the downgrade of the router.
The satellite definitely has to be reverted before the main router.
- ehl1Mar 11, 2020Guide
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...
- FURRYe38Mar 11, 2020Guru - Experienced User
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...
- ehl1Mar 11, 2020Guide
Sorry- i immediately changed CTS and RTS to 2347 - still having issues...
Will contact ChristianR as you recommend - thanks
- orbipoweruser23Mar 11, 2020InitiateAlso experiencing significant WiFi Calling drops. I was able to downgrade to 3.2.9.2 and did the telnet thing to try to block the upgrade. It’s remaining at 3.2.9.2 but still experiencing WiFi Calling call drops. Theorized that perhaps “work from home” corona is overwhelming spectrum, as it’s still happening on 3.2.9.2. Spent waaaay to much time troubleshooting this today. Any other folks experiencing WiFi calling issues?
- ehl1Mar 11, 2020Guide
Yes - wifi calling is exactly where I am seeing the issue, even after going to 2347, resetting RBR and RBS, and resetting the iOS devices in question.
It's consistent...and remember I am the one who did not telnet the settings so I am back on the 3.2.10.11...