NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Firmware 2.7.3.22, a poll
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 ...
I don’t know who posted the below message but it’s like I wrote it myself. I am dying every day with all the issues that I am experiencing since I am upgraded to 2.7.3.22.
This is the first time in my life that I am posting anything in any forums, that’s how frustrated and desperate I am for a solution. No, I don’t intend to buy the latest and the greatest from Netgear to solve the problem.
I have an RBR40, no ISP router, with 3 satellites, I am experiencing the same issues described below and what’s worst I don’t know what the solution is. I can’t contact support. have tried everything possible, I have downgraded twice to the previous version and twice it had auto-updated. There is no freaking way to turn-off auto update. I hope someone from Netgear support monitors this forum and acts on this because it’s a horrible horrible experience.
————————————————
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.
This is the first time in my life that I am posting anything in any forums, that’s how frustrated and desperate I am for a solution. No, I don’t intend to buy the latest and the greatest from Netgear to solve the problem.
I have an RBR40, no ISP router, with 3 satellites, I am experiencing the same issues described below and what’s worst I don’t know what the solution is. I can’t contact support. have tried everything possible, I have downgraded twice to the previous version and twice it had auto-updated. There is no freaking way to turn-off auto update. I hope someone from Netgear support monitors this forum and acts on this because it’s a horrible horrible experience.
————————————————
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.
abacka_08 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.
This is incorrect. A Factory Reset erases all user configurations. But, during the setup, simply set the SSID/password to what it was before the reset and all of those 70 devices will immediately connect.
Since I have done a huge amount of 'tinkering' with my Orbi, the process I follow is to:
- Save a copy of the configuration to my PC (Mac, laptop, whatever).
This is found on the Orbi web interface (http://orbilogin.net), on the Advanced Tab, Administration Menu, Backup Settings. - Perform the Factory Reset.
- Connect to the router again, and it will begin the setup process.
- Enter the bare minimum of information until you get to a page that offers the option to "Load a saved configuration."
- Doing this will restore all user settings, including the previous SSID/password.
- The router will reboot and everything will reconnecct.
- Takes about 15 minutes
I am at a loss to explain how some customers experience nine kinds of hell with firmware V2.7.3.22 whereas my Orbi has been on this firmware since Sept 22 and works the same as always.
I am at a loss to explain how some customers experience nine kinds of hell with firmware V2.7.3.22 whereas my Orbi has been on this firmware since Sept 22 and works the same as always.
Same here. Aside from the issue I'm having with the traffic meter not resetting at the first of the month and the device manager list not correctly showing active devices (I've experienced this issue starting with firmware version 2.7.0.70 I believe) I have not had any stability or connection speed issues with my system. My system consists of an RBR50, RBS50, and RBS50Y.
There must be a common bond somewhere between the people having issues. Maybe a defective run of hardware since a factory reset doesn't resolve the issues? I'm at a loss as well.
I just use Voxel's firmwares. Improves the stock firmware without changing the interface and only has stable releases. Also changes the firmware numbering so Netgear can't auto update your router. It's not hard to revert back to stick should you want to either
May be firmware related. Every morning wired speed drops to 50mbps or so. Reboot and it goes back to 900 (gigabit service.) does this sound like a hardware or software issue?
