RBK50 Firmware Version 2.5.2.4?

[DatabaseJase]

Release notes finally now available for 2.5.2.4 here:

RBR50 / RBS50 Firmware Version 2.5.2.4 | Answer | NETGEAR Support

• Fixes the issue where the Nintendo switch failed to connect to the Internet after the Orbi installation due to IP conflicts.
• Fixes the system stability issues that occurred after the firmware updated to v2.5.1.32.

[jijun1964]

I just update firmware 2.5.2.4 foe RBS50 and RBR50. Smoothly update and running. Stable, and all device connected has been show properly. It so long long waiting for firmware running as expected.

[FURRYe38]

Good to hear. Thank you for letting us know. 

Enjoy. 

---

@jijun1964 wrote:
I just update firmware 2.5.2.4 foe RBS50 and RBR50. Smoothly update and running. Stable, and all device connected has been show properly. It so long long waiting for firmware running as expected.

---

[Almighty]

I installed 2.5.2.4 yesterday and have had some wifi drops and a lot of connected devices are not showing as connected.

Also tmy satellite doesn't show device name just "unknown"

Any one else having these issues?

[FURRYe38]

Has a power off for 1 minute then back on been performed since last update?

---

@Almighty wrote:

I installed 2.5.2.4 yesterday and have had some wifi drops and a lot of connected devices are not showing as connected.

Also tmy satellite doesn't show device name just "unknown"

Any one else having these issues?

---

[Almighty]

Yes. Powered it down for approx 5 min.

Still missing a lot of devices and all devices on the satellite are "Unknown"

[Mstrbig]

---

@Almighty wrote:

Yes. Powered it down for approx 5 min.

Still missing a lot of devices and all devices on the satellite are "Unknown"

---

Those are the ones that you will probably have to go to directly and forget the network and re-join, then reboot 

[Mstrbig]

Also update the firmware to the latest 2.7.0.70

[Almighty]

I have restarted a couple of devices but they are not shown in connected list.

Also none of the wires devices are showing either.

A lot of wifi devices are dropping connection.

The firmware updates of Orbi RBR50 is really bad.

It shouldn't be this many issues every time a new FW is released.

[mrfranc]

Update the firmware to the latest 2.7.0.70

[FURRYe38]

Be sure to power OFF the ISP modem, RBR and RBS for 1 minute then back ON after a FW update. If problems still crop up, a factory reset and setup from scratch maybe needed. 

---

@Almighty wrote:

I have restarted a couple of devices but they are not shown in connected list.

Also none of the wires devices are showing either.

A lot of wifi devices are dropping connection.

The firmware updates of Orbi RBR50 is really bad.

It shouldn't be this many issues every time a new FW is released.

---

[Almighty]

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.

[FURRYe38]

Let us know how it goes. 

[Almighty]

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.

[mrfranc]

Update the firmware to the latest 2.7.0.70

[FURRYe38]

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.

---

[Almighty]

Downgraded to .16 and it looks much better.

So once again Netgear has released.a crap FW version.

[mixia]

Same here the solution is downgrade firmware

[COMountainGoat]

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.

[Mstrbig]

---

@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.

[Almighty]

I waited three days and it didn't get better.

Downgrade is the only solution that has worked for me.

[argold]

https://kb.netgear.com/000062319/RBR50-RBS50-Firmware-Version-2-5-2-4

[FURRYe38]

I found same thing happens with v4 as well as v70:

https://community.netgear.com/t5/Orbi/New-RBR50-RBS50-Firmware-Version-2-7-0-70-Officially-Released/...

v16 seems to work the best. 

[COMountainGoat]

Even 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.

[FURRYe38]

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/1883...
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 Luck