RBR850 / RBS850 Firmware Version 3.2.15.32 - Hot Fix-Firmware Update

[dglsmcd_USMC]

Addresses security issues-get it here:

https://kb.netgear.com/000062077/RBR850-RBS850-Firmware-Version-3-2-15-32-Hot-Fix 

@FURRYe38 

[FURRYe38]

Kewl. Nat Filter for gamers is fixed in this version. Should be at least.

[Chuck_M]

For those that have RBS-50's hard wired to their AX systems -- there is also a corresponding upgrade to the RBS50 firmware found at:

https://www.netgear.com/support/product/RBK50.aspx#download

These potential updates are NOT announced by RBR-850 so you have to get them manually

RBR850, RBS850 and RBR50s took this upgrade very well (albeit manually installed) and are running smooth.

[KMDonlon]

Running smoothly here too. Log entries bug is the only issue I am still seeing

[FURRYe38]

Did you loaded FW and continue or load FW and factory reset? 

---

@KMDonlon wrote:
Running smoothly here too. Log entries bug is the only issue I am still seeing

---

[KMDonlon]

Just loaded firmware and then one final reboot after the router & satellite were updated.

[FURRYe38]

Thanks. 

[Chuck_M]

I personally only loaded firmware in both the RBK852 and the RBS50s ---  no factory reset.  

[the5rivers]

I'm seeing a similar update for the RBR753s:

https://kb.netgear.com/000062075/RBR750-RBS750-Firmware-Version-3-2-15-32-Hot-Fix

I just got mine from Costco a few days ago. It automatically updated to 3.2.15.25 when I installed it. I'll try the newest update and see what happens.

[FURRYe38]

Let us know how it goes. 

[FURRYe38]

I just updated to v32. I factory reset and setup from scratch here. I'm using default wifi CTS settings. 

Port Address Restricted NAT is seen for NAT Filter set to open so I presume the bug that was fixed for me in a different version of FW hasn't made it to release yet. This was a minor hot fix so I'm hoping the NAT Filter fix will be in next major FW update. 

I'm running default CTS values to see if I notice anything. Especially with my 3rd gen NEST. 

[ekhalil]

---

@FURRYe38 wrote:

...... Especially with my 3rd gen NEST.

---

Is this NEST Protect? 😉

[FURRYe38]

Thermostat. 

[KMDonlon]

Just noticed I am getting far more than 7 log entries again and I have changed nothing on my end. How is this changing?

[Chuck_M]

I am not.  Mine is still at about 7

[FURRYe38]

I'm only seeing 8. 

[sl0thk1ng]

Anyone notice that the hotfix number is incorrect?

[FURRYe38]

Is this after you applied v32? 

---

@sl0thk1ng wrote:

Anyone notice that the hotfix number is incorrect?

---

[sl0thk1ng]

Yep, I applied it when it first came out just never notice it until today.

[FURRYe38]

What browser are you using? 

Facfory reset of the RBR after the update? 

Heres mine with Opera browser:

[sl0thk1ng]

Yes, I had to reset it because it was causing my Skype video to lag. Used chrome, Firefox, and edge same result.

[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. 

[FURRYe38]

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. 

[Chuck_M]

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.

[FURRYe38]

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.