NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
FURRYe38
Sep 17, 2020Guru - Experienced User
New - RBR50 / RBS50 Firmware Version 2.7.0.70 Officially Released
New Features and Enhancements: Supports Smart Parental Control Supports forcing HTTPS for the web GUI management Bug Fixes: Fixes the issue where Option 61 could not use the “@” character in t...
BrianRL
Oct 21, 2020Tutor
Another update...
Against my better judgement (and following the advice of some of the more forceful voices here) I attempted the 2.7.0.70 again.
This time I did it as recommended: Update the satellites first using RBS50-V2.7.0.70, then the router with RBR50-V2.7.0.70, triple-checking along the way.
Both satellites updated, and were reporting back into the base without issue. Seemingly. I let them rest a bit and when I came back I noticed that no devices had connected to the satellites.
Figuring this to be due to the firmware mismatch I went ahead and upgraded the base to 2.7. Upon finishing devices immediately began to reconnect to it, but the satellites were now showing "disconnected". Rebooted the router and satellites and then waited. Devices connected to the router once again, but both satellites continuously reported "disconnected". Re-flashed 2.7 on to the router, waited. Rebooted, waited. "Disconnected."
As aside, the Android Orbi app also refused to detect the network, despite being connected to the router.
Reverted router back to 2.5, out of order I know but it's what I could access. It forced me to walk through setup again, so I entered all previously configured data (it remembered all advanced settings), but afterwards devices began to immediately connect again. So did my Android app. So did the satellites. However, the satellites would not accept any devices. Reverted them back to 2.5, and voila, everything's working again.
Sorry, everyone. 2.7.0.70 is not baked enough for full release. And before anyone starts suggesting that something else is wrong, I'll point out that after the revert both times things are fine, meaning the hardware is capable of working correctly. If a firmware is not working for a selection of the population, then that firmware is not ready for an engineering reason. Some variable isn't being accounted for. And for the RBR/RBS series you cannot expect active technical support, either. Let's just be grateful that we can downgrade firmware on these so our multi-hundred dollar investments don't rot in a box.
FURRYe38
Oct 21, 2020Guru - Experienced User
Next time, try a full power OFF of the RBS and RBR after FW is loaded. A reboot may not be enough. Last resort would be a factory reset after applying the FW files and setup from scratch...
v16 seems to be the most stable though.