NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RBK50 Firmware Version 2.5.2.4?
Hi all, I woke up this morning with a notification from the Orbi app that the firmware on my RBK50 had been automatically updated to 2.5.2.4 (screenshot attached). There doesn't seem to be any ment...
How the hell can a restart of my fiber switch have anything to do with my Orbi not showing my connected devices?
If I reboot/shutdown the Orbi units all connections are dropped and the Orbi router has no idea if any other node has been restarted.
But just for taking your advise I will do as you what you say.
Let us know how it goes.
Users can revert to v16. v16 seems to work well for stock FW. Havn't had any problems using this version.
User can also use Voxe's 3rd party FW as well:https://community.netgear.com/t5/Orbi/Voxels-FW-available-for-50-series-Orbi-only-available/m-p/1883615#
https://www.snbforums.com/threads/custom-firmware-build-for-orbi-a-la-faq.65224/
You can revert back to stock FW if it doesn't work out for you.
Good LuckEven if waiting worked (which from other reports, it doesn't), waiting hours or days for a network appliance to correctly report attached devices isn't acceptable. Full Stop.
It appears that the SDLC for Orbi Firmware consists of:
1) Does it compile? Yes -> Ship it
With little to no QA or regression testing. Seriously, something as basic as attached devices breaking wasn't caught?
If the radio's weren't so darn good, I'd dump the system. As it is I'm very tempted to blackhole the Netgear update servers so it can't ever auto-update.
I waited three days and it didn't get better.
Downgrade is the only solution that has worked for me.
COMountainGoat wrote:Yup, badly borked - the connected device page is completely inaccurate. Logging into the satellites shows local connections, but even those are incomplete.
Downgrading to 2.5.1.16 is the answer.
Netgear *really* needs to give us a UI option to disable firmware updates that persists across reboots.
Actualy if you wait 24 to 48 hours, the system seems to stablize and everything seems to correct itself in the app and GUI, with the exception of maybe a cellphone and camera or 2, which just needs to have the network forget and rejoin routine.
Problem is everyone is impatient and downgrades too quickly.
The better solution would be to manually upgrade to V2.7.0.77. Just remember to update the satellites first, then the router. I upgraded 3 RBK53 systems this morning to 2.7.0.77, with no issues.
I find, after updating, I see better speeds on any ISP over 350Mbps and smoother and faster connections.
Yup, badly borked - the connected device page is completely inaccurate. Logging into the satellites shows local connections, but even those are incomplete.
Downgrading to 2.5.1.16 is the answer.
Netgear *really* needs to give us a UI option to disable firmware updates that persists across reboots.
Same here the solution is downgrade firmware
Downgraded to .16 and it looks much better.
So once again Netgear has released.a crap FW version.
Downgrade to v16. I haven't had any problems with v16 and wireless connections.
Almighty wrote:Have now shut down evrything. Fiber switch, router, satellite, all switches.
Still having issues with not showing connected devices. But the worst is that devices drop wifi connection.
Really thinking of getting another mesh system. I have never seen a system with this much issues for every FW upgrade.
Update the firmware to the latest 2.7.0.70
Have now shut down evrything. Fiber switch, router, satellite, all switches.
Still having issues with not showing connected devices. But the worst is that devices drop wifi connection.
Really thinking of getting another mesh system. I have never seen a system with this much issues for every FW upgrade.
