RBR50 AP Mode / FW Update 2.7.3.22

---

markcdaniel wrote:

Currently running 1 x RBR50 + 4 x RBS50 (2 wired backhaul, 2 wireless backhaul) in AP mode and all on FW 2.5.1.16.  Two questions:

 

1) Is there any reason that anyone knows of to update to FW 2.7.3.22 in this configuration? I have read through the poorly documented changlogs for all FW releases between my current version and the latest version and didn't see anything compelling for an AP configuration, but wanted to see if the community had any additional input.  There is 0% chance I will ever use it in router mode, which is where all of the FW attention seems to be focused.

If your system works then you don't have to update it. 

 

2) The autoupdate detects 2.7.2.104 as the most recent version while netgear.com has 2.7.3.22.  Does this mean that I have to upgrade 2.5.1.16 --> 2.7.2.104 --> 2.7.3.22 and can't go directly to 2.7.3.22.  The release notes for 2.7.3.22 don't say anything about a prior version limitation requiring a multi-step upgrade.  So, wondering if it is a multi-step upgrade that hasn't been documented properly or if the autoupdate logic just hasn't been updated yet. I don't want to manually update to 2.7.3.22 only to find that I have bricked my AP because I missed an interim step.

 

IF v16 or v104 is already loaded you can go directly to v22 if you want to. You can manually apply the v22 FW files yourself. 

https://kb.netgear.com/31573/How-do-I-manually-upgrade-firmware-on-my-Orbi-router-using-orbilogin-com
https://kb.netgear.com/000037217/How-do-I-check-and-manually-upgrade-the-firmware-on-my-Orbi-satellite

 

If you do, update the RBS first, then RBR lastly. 

 

---

---

markcdaniel wrote:

1) Is there any reason that anyone knows of to update to FW 2.7.3.22 in this configuration?

 

Not that I can see.  I saw a comment that this new firmware correctly reports "Link Rate" for devices connected to satellites.  If this is a BIG DEAL for you, then an update may fix that problem.  My practice is to wait until early adopters have discovered any "gotcha's" in new firmware before installing it myself.

 

2) The autoupdate detects 2.7.2.104 as the most recent version while netgear.com has 2.7.3.22.  Does this mean that I have to upgrade 2.5.1.16 --> 2.7.2.104 --> 2.7.3.22 and can't go directly to 2.7.3.22.

 

No.  It just means that the Firmware Update mechanism in the Orbi has not been modified to recognize this new firmware version.  Netgear often waits to "see what happens" before recommending people update.

 

The original Orbi firmware was created with a maximum size that the image could be and eventually the image got larger than that. So Netgear created firmware specifically to allow firmware updates with a larger size.  Since then, any version can be manually loaded.  (If, that is, there is any reason to do so at all.)

---