NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RBR/RBS 50 firmware 2.7.3.22
New firmware is incoming this week I have been told. No release notes details yet but may fix either device list issues or link rate issue. Keep an eye on https://www.netgear.com/support/product/RBK50...
RBR50 + 2 x RBS 50 firmware just upgraded from 2.7.2.104 to 2.7.3.22
Seems it broke my setup without me clicking to update (I read in another thread that Netgear forced an update - seriously??? WTF??? Is that serious? In the middle of a pandemic, break everyone's wifi while they are working from home?)
Issues found:
* wired backhaul no longer working, only connects using wirelsss (which is poor quality, thus the reason for the wired backhaul). MAJOR ISSUE
* using Android "Netgear Orbi - WiFi System App" version 2.10.6.1635 (the latest, released 23 July 2021) shows both RBS50 as disconnected (red lines), whereas logging into the router itself shows both RBS50 connected using wireless backhaul.
* [subjective] wireless connectivity is poor when via the RBS50 now, previously it was rock solid using v2.7.2.104 with wired backhaul.
* no "enable telnet" option, so no way to properly diagnose or fix
Can I revert to the 2.7.2.104 ? How? Will it "auto-upgrade" itself again? And can I avoid an auto-upgrade by blocking some particular DNS addresses? (Orbi is inside another network).
Try to power OFF the RBR and RBS for 1 minute. Pull the power cord as well. Turn back ON. Factory reset the RBR and RBS and setup from scratch. Let us know if this bridges back wired back haul.
Is the RBS directly connected to the back of the RBR or is there a switch in between?
scubabuddy wrote:RBR50 + 2 x RBS 50 firmware just upgraded from 2.7.2.104 to 2.7.3.22
Seems it broke my setup without me clicking to update (I read in another thread that Netgear forced an update - seriously??? WTF??? Is that serious? In the middle of a pandemic, break everyone's wifi while they are working from home?)
Issues found:
* wired backhaul no longer working, only connects using wirelsss (which is poor quality, thus the reason for the wired backhaul). MAJOR ISSUE
* using Android "Netgear Orbi - WiFi System App" version 2.10.6.1635 (the latest, released 23 July 2021) shows both RBS50 as disconnected (red lines), whereas logging into the router itself shows both RBS50 connected using wireless backhaul.
* [subjective] wireless connectivity is poor when via the RBS50 now, previously it was rock solid using v2.7.2.104 with wired backhaul.
* no "enable telnet" option, so no way to properly diagnose or fix
Can I revert to the 2.7.2.104 ? How? Will it "auto-upgrade" itself again? And can I avoid an auto-upgrade by blocking some particular DNS addresses? (Orbi is inside another network).
Doing the full power off for some time (multiple times, I'd already tried it when I posted) eventually got me to something that recognised the Ethernet backhaul. Awaiting feedback on acceptance factor in the household, with 4~5 simultaneous wireless video conferences at any one time during the week with everyone working and schooling from home, it should become evident soon...
Is the RBS directly connected to the back of the RBR or is there a switch in between?
scubabuddy wrote:
Doing the full power off for some time (multiple times, I'd already tried it when I posted) eventually got me to something that recognised the Ethernet backhaul. Awaiting feedback on acceptance factor in the household, with 4~5 simultaneous wireless video conferences at any one time during the week with everyone working and schooling from home, it should become evident soon...
- There is a switch in between. The only other point of interest is that I have some (up to date) v1 SONOS equipment that I disconnected as well this time, because I had horrible problems with what I think was some spanning tree conflicts about a year ago. SONOS all set to Ethernet only in case you're wondering. Not sure if that was related or not, but with everyone highly reliant on the internet, now is not the time to experiment.
Oh and it is a "dumb switch, unmanaged, and I had also tried power cycling it both the first times when it all failed, and this time that it worked too.