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 you if you want to upgrade or not.
I highly recommend a factory reset and setup from scratch if you choose to.
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.
125 Replies
I applied the new firmware to my RBR850 and RBS850 devices today (router mode). I have had 0 disconnects. Seems to be working correctly
Thanks for letting us know. Be sure to save a back up configuration to file for safe keeping.
Enjoy. :smileywink:
- Weird all the issues. I didn't even notice the new FW until today and I'm not experiencing any issues. But I have to say, I'm not using a lot of functions. Just running wired backhaul and and in AP mode, mainly for wifi. All stable actually :)
Only hate there is no IGMP Snooping support so my stupid TV decoders won't crash when I want to watch programs back, doesn't work anymore since I have Orbi :(If your RBS are wired, is there a switch in between the RBR and RBS? Or are the RBS directly wired to the RBR?
There seems to be one problem with v10.11 in AP Mode with using LAN switches between the RBR and RBS:
Not seen in router mode with LAN switches in between.
Jeffoz wrote:
Weird all the issues. I didn't even notice the new FW until today and I'm not experiencing any issues. But I have to say, I'm not using a lot of functions. Just running wired backhaul and and in AP mode, mainly for wifi. All stable actually :)
Only hate there is no IGMP Snooping support so my stupid TV decoders won't crash when I want to watch programs back, doesn't work anymore since I have Orbi :(- Directly wired as what I wanted first doesn't work at all. Connect both Satellite and Router to Modem from internet provider. Your Satellite must be behind the Router wired otherwise it doesn't work, so it's cabled like that and I experience zero issues.
This is what I have done to fix my disconnect issues. I can confirm that this fix has worked for the last 2 days, and I have experienced 0 disconnects since I have made the changes. My RBR850 is setup in router mode.
- I downgraded the router and satellite firmware to version 3.1.5.23 ( that fixed the problem) intermediately
- Changed RTS/CTS to 2347
- blocked the following
- http.fw.updates1.netgear.com
- http.fw.updates1.netgear.com/rbs/default/ww
- https://http.fw.updates1.netgear.com/rbs/default/ww
- https://http.fw.updates1.netgear.com
- updates1.netgear.com
Go to http://<router IP address>/debug.htm and check "enable telnet"
- Telnet into the router and run the following
nvram set orbi_auto_upgrade=0
nvram set auto_check_for_upgrade=0
nvram set auto_update=0
nvram set auto_upgrade_enable=0
nvram set install_fw_upgrade_latest=0
nvram set ver_check_enable=0
nvram commitNow when I log into the router and check the firmware versions my RBR850 is on 3.1.5.23 and my RBS850 is on 3.2.9.2 (the satellite upgraded on its own after the downgrade). The different firmwares between the satellite and the router have not been an issue. When I go to the firmware section of the router and it check for new firmware I am getting a "service unavailable" for the RBR850.
I see NG just posted v10.11 acutal files for download:
https://kb.netgear.com/000061769/RBR850-RBS850-Firmware-Version-3-2-10-11
Users may want to download these and apply them manually using IE11 or FireFox. I highly recommend a factory reset on the entire system after the RBS and RBR have been updated with these files. RBS first, then RBR lastly. Set up from scratch.
Be sure to check your CTS and RTS values. If they are at 64, please change both to 2347. Reboot both RBR and wireless devices.
Thank you.
I am still using Firmware v3.2.10.11 and didn't go back to prevous version.
After few restarts my 2nd RBS50 is working fine.
All my satellites are connected with wired method. My wired PC has a problem only with one
backgammon site dropping connection.
My CTS and RTS values were at 64 and I changed it to 2347.
What improvements should I expect?
I too use wired backhaul, the new firmware seems to make the wired backhaul connection unstable (blue light on all the time, briefly flips to magenta once in a while). That's after the router updated to v3.2.10.11. Do you see the same thing? It doesn't look like many of us use wired/ethernet backhaul around here.
Got word from a forum moderator. NG will be removing v10.11 from there update servers and from the support site. NG is still working on this. Please be patient.
- I have my satellites connected wired and my Arlo Ultra base stations all wired to them but after this update and after increasing the CTS & RTS values up I still am getting my devices that are hard wired specially my Ultra Base stations constantly disconnecting... NETGEAR has to push a new firmware out ASAP!!!!
- I disconnected my RBR850 router and satellite and reconnected my Velop. So glad I hadn’t listed them on eBay yet. Successfully up and running with zero WiFi calling fall drops. The RBR850 was dropping connections and calls every 5-10 minutes. I can’t believe I spent almost $700 for what I was hoping was the future of WiFi?!? Why does NG not QA their firmware before releasing? Why do they fix something that isn’t broken?? This AP workaround and setting changes is absurd. Really, this product line has been around for 3+ years?? Eero, google, velop doesn’t experience problems like this.
While on the phone with a level 2 NG tech yesterday we reverted my firmware back to 3.1.5.23. We initially had just set the RBR850 to AP mode, but out of curiosity I went ahead and put it back to full router mode. That has completely eliminated dropped connections and I'm not experiencing any issues.
What ever was broken in 3.2.11 seems to have also been broken in 3.2.9.2. I wasn't keeping up with the firmware version numbers that my RBR850 had installed prior to having 3.2.11 but it seems it was not 3.2.9.2.
I hope this helps!
- 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.
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?
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.
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.
- 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.
For those of you experiencing problems after v11. FW was loaded yesterday. Can one or two of you experiencing this problem while in router mode, set up and enable capture WAN and LAN and Debug logs for a short while or however long it takes for you to see the problem appear.
Open a web browser to http://192.168.1.1/debug.htm in a web browser will bring you to the RBRs debug page. Check mark each of these two options and then begin normal use. When you notice the problem. Go back in to the debug page and select capture logs button. This will download the logs from the RBR and send them to your default browser download location. If you can upload this .zip file to a drop box or cloud file service then share the download link, we can get this to NG for them to review and hopefully help them figure out whats going on with those of you who are seeing this problem. Hopefully this will help narrow down where the problem maybe in FW. Still odd that some of us are not seeing this. Hopefully NG can pin point it. :smileyfrustrated:
Thank you for your time.
I would be happy to, but I actually had to pull my system down entirely and replace it with my previous Google Wifi system. I'm in the middle of planning for a product release and I won't have the time over the next couple of days to put the system back up.
What seemed to bewilder me about this is that even after reverting back to 3.2.9.1_2.4 I had the very same issues. I'm confident that I did not start seeing this issue until 3.2.11 was released, but now my system is completely toast. I'm truly scratching my head over this one, but I agree logs should help NG sort this out.
Has anyone else reverted firmware, and if so are you still seeing the issues like I am seeing?
One or two others reported downgrading and resetting and getting there systems back to stable.
Be sure that your CTS and RTS values read 2347 for both 2.4Ghz and 5Ghz under Advanced Tab/Advanced Settings/Wireless Settings
If you can't seem to get your system back to stable, please contact NG support. Open a support ticket.
xnolightx wrote:I would be happy to, but I actually had to pull my system down entirely and replace it with my previous Google Wifi system. I'm in the middle of planning for a product release and I won't have the time over the next couple of days to put the system back up.
What seemed to bewilder me about this is that even after reverting back to 3.2.9.1_2.4 I had the very same issues. I'm confident that I did not start seeing this issue until 3.2.11 was released, but now my system is completely toast. I'm truly scratching my head over this one, but I agree logs should help NG sort this out.
Has anyone else reverted firmware, and if so are you still seeing the issues like I am seeing?
FYI to everyone with Orbi AX and v3.2.10.11. NG is now aware of the problems here in the forum. I've asked them to remove this version from there auto update servers as soon as possible. They will be looking into this issue.
Please file a support ticket and let them know.
For effected users, please downgrade to v3.2.9.2. Manually download the FW files for the RBS and RBR. Apply the file to the RBS first then RBR. After all has been process. Press the reset button on the back of the units for 15 seconds then release and then setup the system from scratch. I would power off the ISP modem or ONT for 30 seconds after the reset on the RBR to ensure the RBR gets fully connected to the modem or ONT. Hopefully this brings your system back to a stable state.
Thanks, I'll try this after I get home from work.
I saw it was available yesterday but I dithered ... lots happening in my house including a sewer "fill up" which spewed level 3 sewage water in my family room, contaminating my lower level (where the RBR850 is).
Today I took a look, and my current version is 3.2.10.11.
Didn't know that they auto-applied firmware any more, but all seems fine.
Time to take another back up ...
Eeeks sorry to hear about the sewer spillage. Hope things will get cleaned up for you.
v11 seems pretty good. I have it loaded on mine. Finally get to run in router mode with a xbox game console. Could not do that before this version.
Back ups are good.
VerneArase wrote:I saw it was available yesterday but I dithered ... lots happening in my house including a sewer "fill up" which spewed level 3 sewage water in my family room, contaminating my lower level (where the RBR850 is).
Today I took a look, and my current version is 3.2.10.11.
Didn't know that they auto-applied firmware any more, but all seems fine.
Time to take another back up ...
I am now seeing intermittent drops on nearly all of my devices on the network after 3.2.10.11 has been loaded automatically on my system.
