NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RBR850 / RBS850 Firmware Version 3.2.15.32 - Hot Fix-Firmware Update
Addresses security issues-get it here: https://kb.netgear.com/000062077/RBR850-RBS850-Firmware-Version-3-2-15-32-Hot-Fix FURRYe38
Very odd. Is the system working ok?
Only thing I can think of is to downgrade back to v11, then re-up-load the v32 file again. I would besure to download the v32 file again from NG download page.
Somenthing that i'm posting to let users know that NG now recommends using the default CTS value of 64 on Orbi AX. I was informed by NG that orbi AX that there are settings and or drivers in the FW that are effected by any CTS changes and they feel that 2347 may cause problems for some. I can attest to this as my 3rd gen NEST would not keep connected to Orbi AX if I set the CTS value to 2347 which does work on other AC model routers. After changing back to 64, the NEST has been connected with out any problems. Over all my Orbi AX on v32 has been up and online and stable with the default CTS value.
So seems the Orbi AX maybe different from all the others in regards to CTS value and usage so even though 2347 works for most other system, Orbi AX seems to be the odd one out for this setting.
I recommend that users first try the default CTS value. If you run into problems first try a factory reset if one hasn't been performed. You can try 2347 and use it if seems to help. Though I would suggest that users having problems with CTS value of 64 please report your problem to NG and let them know so they can review and make changes if they can.
Hope this helps.
I am changing mine from 2347 to 64 -- even though I have had no issues with my AX6000 and attached devices... but want to see if I can observe any differences in overall behavior.
Anything in particular I should keep an eye out for?
Thanks for heads up.
Other than this, no. v32 seems stable while using CTS defaults. I just changed to 40Mhz only channel width as well today and NEST is still connected. No other problems seen thus far.
FURRYe38 wrote:Somenthing that i'm posting to let users know that NG now recommends using the default CTS value of 64 on Orbi AX. I was informed by NG that orbi AX that there are settings and or drivers in the FW that are effected by any CTS changes and they feel that 2347 may cause problems for some. I can attest to this as my 3rd gen NEST would not keep connected to Orbi AX if I set the CTS value to 2347 which does work on other AC model routers. After changing back to 64, the NEST has been connected with out any problems. Over all my Orbi AX on v32 has been up and online and stable with the default CTS value.
So seems the Orbi AX maybe different from all the others in regards to CTS value and usage so even though 2347 works for most other system, Orbi AX seems to be the odd one out for this setting.
I recommend that users first try the default CTS value. If you run into problems first try a factory reset if one hasn't been performed. You can try 2347 and use it if seems to help. Though I would suggest that users having problems with CTS value of 64 please report your problem to NG and let them know so they can review and make changes if they can.
Hope this helps.
I was a value of 500 which seemed to be working fine but then noticed I couldn't get the kids' school supplied Chromebooks (Lenovo) to connect to the Wi-Fi. A quick search yielded this post:
When I changed my CTS value from 500 to 2347, the Chromebooks were able to connect fine, so I left it at 2347.
So what now? Do I change it to 64 because NG says it's the optimal setting for AX?
So do the chrome books not connect with CTS set to 64?
Something to let NG know if about they don't.
dtay wrote:
I was a value of 500 which seemed to be working fine but then noticed I couldn't get the kids' school supplied Chromebooks (Lenovo) to connect to the Wi-Fi. A quick search yielded this post:When I changed my CTS value from 500 to 2347, the Chromebooks were able to connect fine, so I left it at 2347.
So what now? Do I change it to 64 because NG says it's the optimal setting for AX?
One other item I noticed last nite, my 1st gen nest disconnected after setting the RBR to 40Mhz only channel width. I set it back to 20/40Mhz and were back to connected. Something else to keep in mind as a troubleshooting step.
FURRYe38 wrote:So do the chrome books not connect with CTS set to 64?
Something to let NG know if about they don't.
dtay wrote:
I was a value of 500 which seemed to be working fine but then noticed I couldn't get the kids' school supplied Chromebooks (Lenovo) to connect to the Wi-Fi. A quick search yielded this post:When I changed my CTS value from 500 to 2347, the Chromebooks were able to connect fine, so I left it at 2347.
So what now? Do I change it to 64 because NG says it's the optimal setting for AX?
Haven't tried 64 yet to see if it works with the Chromebooks. Will test that once I have the opportunity to schedule an outage with the household. :)
I have v32 on my 753s, and I have CTS set to 2347, and everything works fine, including my Nest thermostat. I have never tried the default value. Also have 20/40 MHz disabled.
Just another data point. Thanks.
What generation is your NEST controller(s)?
I have 1 1st and 1 3rd gen. 3rd gen seems to not like 2347 and the 1st gen doesn't like 40Mhz only. Crazy I know.
Someting to try and see if you notice anything if you set 64 for CTS. IF you do, take notes then change back.
the5rivers wrote:I have v32 on my 753s, and I have CTS set to 2347, and everything works fine, including my Nest thermostat. I have never tried the default value. Also have 20/40 MHz disabled.
Just another data point. Thanks.
Hi. I have a 3rd Gen Nest, and I have had zero problems with it on 2347. I never tried it on 64, but curious to know what the benefits would be if its running fine as it is.
Also had the same CTS setting on my RBK53, with no issues.
Ya I know 2347 works fine on my RBK50 as well. Zero issues with Orbi AC. Not sure why Orbi AX is so different. NG says there are complex settings in the FW that are intricate. They recommended using the default 64. So far with my 1st and 3rd gen NESTs, they are stable, online and no battery drain while using CTS 64 and 20/40Mhz channel width. Though I see others are still seeing problems with battery drain. :smileyfrustrated: Still wonder if part of this is a NEST issue as well.
Ya, been fighting with this for a while now. Had a bug report with NG that we just closed yesterday.
Tried the 64 CTS/RTS threshold as well as 500-played havoc with the PS4 Pro (might be a hardware issue)-when the PS4 Pro is in auto mode (wireless) there would be frequent disconnects-tried 5GHz only mode would not connect-2.4 GHz mode is the only one that would connect at 64 or 500 CTS/RTS threshold. Changed to 2347 and PS4 Pro would connect in all modes (auto, 5GHz, and 2.4 GHz) and no problem with my Nest 3rd gen thermostats. The trials and tribulations of making one solution every one's solution. I don't know if this is necessarily an issue that NG needs to address-when the PS5 comes out this fall we shall see if updated hardware will allow 64 CTS/RTS threshold.
Something to send to NG support. Let them know what your seeing between the CTS values you have tired. If this is NGs recommendations for CTS and users are still having problems when using it, then NG may need to make changes and keep tuning the FW if there wanting users to use CTS 64.
dglsmcd_USMC wrote:Tried the 64 CTS/RTS threshold as well as 500-played havoc with the PS4 Pro (might be a hardware issue)-when the PS4 Pro is in auto mode (wireless) there would be frequent disconnects-tried 5GHz only mode would not connect-2.4 GHz mode is the only one that would connect at 64 or 500 CTS/RTS threshold. Changed to 2347 and PS4 Pro would connect in all modes (auto, 5GHz, and 2.4 GHz) and no problem with my Nest 3rd gen thermostats. The trials and tribulations of making one solution every one's solution. I don't know if this is necessarily an issue that NG needs to address-when the PS5 comes out this fall we shall see if updated hardware will allow 64 CTS/RTS threshold.
dtay wrote:
FURRYe38 wrote:So do the chrome books not connect with CTS set to 64?
Something to let NG know if about they don't.
dtay wrote:
I was a value of 500 which seemed to be working fine but then noticed I couldn't get the kids' school supplied Chromebooks (Lenovo) to connect to the Wi-Fi. A quick search yielded this post:When I changed my CTS value from 500 to 2347, the Chromebooks were able to connect fine, so I left it at 2347.
So what now? Do I change it to 64 because NG says it's the optimal setting for AX?
Haven't tried 64 yet to see if it works with the Chromebooks. Will test that once I have the opportunity to schedule an outage with the household. :)
FURRYe38 - I've changed the RTS/CTS to 64 (from 2347) and the Chromebook seems to be able connect to the Wi-Fi fine. Will have the kids test it when they wake up, but will keep it at 64 for now to see what happens.
Did NG mention specifically why we need to be at 64? Any changelog or technote as to the reasons?
