So I have an RBR40 with two RBS20 satellites and the 2.7.3.22 firmware just showed up in the app as an update. I’m currently on 2.6.2.104.
I’ve seen some threads here with bricked main routers and other issues. I was wondering if I could get an informal poll on people’s results here. If you’ve updated to 2.7.3.22, could you post your result here? I’m a little wigged out. We’ve been dealing with major internet problems for months now and just had a solid week or so of no issues after finally switching ISPs. So I don’t want to break the Orbi. But I do like to stay on top of security updates.
Don't do it. Seems like at least every other update causes me issues that are seemingly random. Right now, the network drops internet connection but still broadcasts network and connections appear to be ok. Already spent a week on it without issues. Last time it took me four months to solve a similar problems. Netgear!!!!!?????!!!!!!!
What is that saying? "Fools rush in where angels fear to tread."
If the system is working well, I would feel no urgency to mess with it.
But, do not be surprised when one day the firmware is updated by Netgear. Unless you look at the Orbi management interface every day, it may be some time before you realize this happened. Or... as some have posted, it will become all too apparent.
For what it's worth (knock on wood) my system has been running for a week now on 2.7.3.22 with no issues. I have an RBR50, RBS50, and RBS50Y. I upgraded each satellite manually, waited for them to fully reboot, then upgraded the router. I was a little worried because the last manual upgrade I did caused some issues on the router where the login web page would not load, but I was able to complete the update using the app. No issues at all with the upgrade process this time.
For what it's worth (knock on wood) my system has been running for a week now on 2.7.3.22 with no issues. I have an RBR50, RBS50, and RBS50Y. I upgraded each satellite manually, waited for them to fully reboot, then upgraded the router. I was a little worried because the last manual upgrade I did caused some issues on the router where the login web page would not load, but I was able to complete the update using the app. No issues at all with the upgrade process this time.
Just continued to use the system as-is. I haven't down the full power down with any of the updates I've applied so far, and I haven't noticed any issues.
I should add a disclaimer that I am having some issues with my RBS50Y rebooting, but that was happening prior to the firmware upgrade. I think it's a power issue possibly, but I'm still troubleshooting. The RBS50Y is a recent addtion to my system. The RBR50 and RBS50 have been in operation for about a year now.
I should add a disclaimer that I am having some issues with my RBS50Y rebooting, but that was happening prior to the firmware upgrade. I think it's a power issue possibly, but I'm still troubleshooting. The RBS50Y is a recent addtion to my system. The RBR50 and RBS50 have been in operation for about a year now.
Yeah, the RBS50Y is running 2.7.3.22 as well. That's one of the reasons I eventually decided to upgrade, so all components were running the same firmware version. I have a couple of things to try before doing a factory reset, so I'll see how those go first.
Yeah, the RBS50Y is running 2.7.3.22 as well. That's one of the reasons I eventually decided to upgrade, so all components were running the same firmware version. I have a couple of things to try before doing a factory reset, so I'll see how those go first.
I woke up one day and had 2.7.3.22 auto installed on my RBR50 and one RBS50. This was a few weeks ago and I haven’t had any problems. All my settings look the same too.
I found my way to these forums after 2 years because of the 2.7.3.22 firmware.
I'd tell you not to do it. This is the first firmware update where I've had major issues.
My upload speeds dropped to 1 mb, one of my 2 satellites keeps dropping off and reconnecting randomly. After the updated I had about 10 duplicate IP addresses creating conflicts . Devices wouldn't just auto reconnect. On many of them had to forget the network and readd it. And now 50% of my devices in the Orbi app and web based router management tools show offline or not even connected when they actually are connected.
This sucks.
My understanding is that I have perform a factory reset, but that seems like a pain in the butt especially if I have to re-enter the SSID and password for 70 devices and reconfigure the router from scratch.
It's like Netgear didn't test this firmware out at all. It's bad. Really bad. But maybe it's just me.
@Yosmany21 wrote: My understanding is that I have perform a factory reset, but that seems like a pain in the butt especially if I have to re-enter the SSID and password for 70 devices and reconfigure the router from scratch.
Sory you made a beginner mistake. Every time I insall a new WiFi router or Factory Reset the one I'm using now, I put in exactly the same SSID/password . That way, all my devices reconnect automatically. And, if I decide to "go back" to the old WiFi router, it is a simple swap and the devices reconnect again.
Also, when I want to change the Password Recovery security questions, I am required to enter the old password and then new password (two times). I just use the same password for old and new.
If I factory reset the router do I have to factory reset the satellites? Is there a Best practice to follow when doing a reset of your system with two satellites?
If you reset the RBR it's best to reset the RBS as well. Initial steps after a FW update is to power OFF the RBR and RBS and ISP modem.
If this doesn't work to resolve odd isssues, then a reset would be next step.
@Yosmany21 wrote: If I factory reset the router do I have to factory reset the satellites? Is there a Best practice to follow when doing a reset of your system with two satellites?
I thought it did mine too (RBR40). But after being persistent, doing a 7 second reset, 30-30-30 second on off on reset, and then powered off then on again (without reset), it eventually booted back up. But weird thing is that it didn't update to 2.7.3.22 it stayed on 2.6.2.104. Maybe that's a good thing.
I thought it did mine too (RBR40). But after being persistent, doing a 7 second reset, 30-30-30 second on off on reset, and then powered off then on again (without reset), it eventually booted back up. But weird thing is that it didn't update to 2.7.3.22 it stayed on 2.6.2.104. Maybe that's a good thing.
