NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Liquidcore
Aug 11, 2020Star
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...
DatabaseJase
Sep 17, 2020Luminary
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
Sep 21, 2020Guide
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.
- COMountainGoatOct 21, 2020Apprentice
Yeah, having a factory reset be the right answer because of software defects is different from should it be the right answer :-).
And do appreciate the advice and insight. Shame that Netgear can't fix the QA issues after all these years.
- FURRYe38Oct 21, 2020Guru
I totally understand the frustrations. Some of us have been helping out here in the forums for a while now. So we have seen all the experiences and feedback when new FW comes out. Some of us have found solutions and work around to help users get thru the tough times. There are reasons why we ask questions and do have use factory resets. For me and others, it's been experienced that this helps resolve issues seen, before and after FW updates. Seen alot of odd ball problems that seem to stem from using Orbi app updates and when NG pushes FW thru auto update. Works one day then next day we see people posting and talking about problems seen after wards.
Why from personal experiences with Orbi, manual FW updates and factory resets afterwards and setup from scratch has show me over the years, has proven to help keep these things up an running and running pretty well.
Aside the UI issues which have plagued NG since Orbi first came out I believe which is another ball of wax.
I have loaded both v4 and v70 and even after reset, they seem ok. However thre is one bug that will impact maybe only a few users. Seems that if you have an RBS thats ethernet connected to the RBR with two or more daisy chaing switches in between, these FW cause an ARP storm on the network when the RBS is connected to the last switch. I have this configuration in my home and had it for a while now. This ARP storm doesn't happen on v16 FW which I had to revert back to. So NG has done something with v4 and v70 that effects some RBS and switch configurations. I presume since seeing more posts here about v4 and v70 along in the reddit forums, these two version need to be reviewed by NG again and hopefully they can fix the issues at hand. Theres nothing we can do here in the forums to effect any fixes when it comes to FW.
So for those having problems on v4 and v70, revert back to v16. I find it to be the most stable version currently for Orbi 50 series.
Make contact with netgear support for those that are under warranty.For those that are not under warranty, make contact with a forum moderator to let them know what your having problems with and what you have done.
Good Luck.
- COMountainGoatOct 21, 2020Apprentice
Oh I'm sure, but for how long? ;-)
Seriously, I'm just frustrated right now - firmware quality has been a problem for years, and nothings really changed. Bonjour connectivity continues to be a problem (though to be fair, not sure if that's orbi or apple). Orib has hands-down best performance and coverage, so I put up with it, but it's frustrating - like a really nice car that keeps breaking down.
- FURRYe38Oct 21, 2020Guru
Orbi AX is working for me and others...
- COMountainGoatOct 21, 2020Apprentice
Yup, the device-missing bug looks like it's still in .70 too.
I just cancelled my order for a new wifi6 system. If they can't get a years-old system stable, I doubt they can get the new one there anytime soon.
- FURRYe38Oct 21, 2020Guru
You can downgrade to v16 as that seem to be the best version currently:
Andre71 wrote:About a week on release 2.5.2.4.
I noticed these issues:
- Several devices are missing from the list of attached devices (but are connected);
- No log entries in the log anymore, although all options are selected.
- Andre71Oct 21, 2020Aspirant
About a week on release 2.5.2.4.
I noticed these issues:
- Several devices are missing from the list of attached devices (but are connected);
- No log entries in the log anymore, although all options are selected.
- COMountainGoatOct 20, 2020Apprentice
Looks like .70 is pretty bad too. What's going on with QA?
- COMountainGoatOct 19, 2020Apprentice
Doesn't fix it - this is clearly a software defect.
- FURRYe38Oct 19, 2020Guru
Did you first power OFF the RBR/RBS for 1 minute then back on to check to see if devices appeared? This is a first step to try after a FW update.
JP7 wrote:
Installed 2.5.2.4 and about 10% of my devices no longer appeared in the connected devices list. I did several reboots but not all devices would show up. I reverted back to 2.5.1.16 and all devices are now showing up again in list. - JP7Oct 19, 2020AspirantInstalled 2.5.2.4 and about 10% of my devices no longer appeared in the connected devices list. I did several reboots but not all devices would show up. I reverted back to 2.5.1.16 and all devices are now showing up again in list.