NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
New - RBR50 / RBS50 Firmware Version 2.7.5.4
Bug Fixes: 02/23/2023
This firmware provides the following bug fixes:
Various Armor bug fixes
Various SPC (Smart Parental Control) bug fixes
Security Fixes:
This firmware addresses secu...
I recommend a power OFF the the RBR and RBS for 1 minute then back ON with the RBR first then RBS.
Should be fully synced after this.
Glad you got it working. Please mark your thread as solved so others will know. Be sure to save off a back up configuration to file for safe keeping. Saves time if a reset is needed.
https://kb.netgear.com/000062080/How-do-I-back-up-the-configuration-settings-on-my-Orbi-WiFi-System
Enjoy. 📡
I have no idea why Netgear does what they do. What I have observed over the past six years is that when Netgear posts a firmware update to the support web site, some hardy souls immediately download and install it. Often they file good reports. Occasionally, the forum soon fills with reports of problems. On one occasion, the update was pulled. On another occasion, rather than post firmware, Netgear pushed an update to thousands of routers which locked out the Orbi app and blocked web access as well. Incredible chaos.
I, personally, prefer to wait while other people discover whether the Quality Assurance program was 100% successful (or not). When reports on the forum have been fine for a while, I either update manually or "wait them out" to see how long it will be before Netgear 'pushes' the update to everyone.
Given that the Quality Assurance program cannot possibly examine every possible combination of Internet Service Provider, WiFi environment, and home devices, letting some volunteers "go first" does not appear to be a "horrible practice" to me.
I don't consider a user (novice or expert) who installs a final release software a "volunteer". If the goal is to iron out bugs before releasing it to auto-update, industry standard would dictate you label it as beta and initiate an official beta testing program where users can then actually sign up to volunteer for testing. Anything else is very misleading an amateurish.
Over the history of Orbi, there as been MANY issues surrounding FW and Auto updates. Mostly causing problems over the night after users systems were updated when they had been working well. Been MANY complaints from users about this. Also been MANY requests to stop using Auto Update or allow users to disable this feature. NG finally only relented last year after a major fire storm happened on Orbi AX systems id they finally implement controls to disable AU. Made users happy here.
So NG has been pushing only major versions FW updates and leaving minor versions of FW updates to the user to manually install them if they wish too. NG seems to be relaxing there FW update pushes these days and letting users choose when they want to update. When NG does auto update they do so in small batches. Seems that after having such a bad long time use over the years, maybe NG has learning something.Yes NG internal testing processes are of concern. No idea what they have been doing all these years. Hoping there learning something. Been a slow process for sure.