NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi Firmware Update 2.5.0.40
Does anyone know what's in 2.5.0.40? All I can see from the software release is "Updates the https certificate" - it's described as a Hot Fix, but I would love to see a tad more detail. I had...
I manually updated my firmware from V2.5.0.38 to V2.5.0.40 to see if it would also fix the device naming issue. It did for some devices, but others it will not allow me to change. So the v40 hot fix did not resolve the device naming issue. Note that I did not do a factory reset as it takes me hours to reconfigure the device manually. I did not test v40 for the https issue that it is supposed to address.
tomschmidt wrote:I manually updated my firmware from V2.5.0.38 to V2.5.0.40 to see if it would also fix the device naming issue. It did for some devices, but others it will not allow me to change. So the v40 hot fix did not resolve the device naming issue.
Thank you for giving it a try. If nobody installed firmware updates, those of us who "wait and see" would have no reports to base upgrade decisions on.
- Hi all,
I spoke with NETGEAR support.
Netgear refers to the .30 as “the last stable version” this version does not have the device naming issues. I will not upgrade to .40 seems a very small fix and existing problems still occur.AND WHY DOESN'T NETGEAR POST AN ANNOUNCEMENT ON THESE FORUMS THAT 2.3.5.30 IS "THE LAST STABLE VERSION"?
AND WHY DOESN'T NETGEAR POST AN ANNOUNCEMENT ON THE NETGEAR DOWNLOAD SITE THAT 2.3.5.30 IS "THE LAST STABLE VERSION"?
Whoever is the Program Manager for the Orbi Firmware Development should be fired immediately. After 2 failed firmware releases credibility is gone.
EduardH wrote:
Hi all,
I spoke with NETGEAR support.
Netgear refers to the .30 as “the last stable version” this version does not have the device naming issues. I will not upgrade to .40 seems a very small fix and existing problems still occur.
Here's my thought on the current NG firmware testing/ implementation:
When a firmware is believed to be ready for first time release, it is made available by way of the Orbi login - user manually updates.
This firmware may have 'bugs' which hopefully will be reported, NG responds, fixes, and re-issues (same number?) the firmware, this time as a auto push for it is felt all bugs have been worked out.
Under this process, those that choose to manually upgrade their firmware in essence have become a part of the beta tester group.
I say this for I don't perform manual updates, yet over time (6 months) my firmware is updated with firmware that back 6 months ago was full of problems, yet my network continues to hum along with No changes on my part.
Just my 2 cents. Your mileage may vary.
With the 2.5.0.38 my satelites were obviously connected as the attached devices had internet connection, but in the router web UI they were not appearing, at all. It just said, number of satelites: 0.
So I first manually updated RBR50 to .40 after which the satelites were listed, but with 0 devices shown on them. This at least allowed me to update both satelites manually to .40 just to keep things on the same version.
But I still don't see any devices shown as attached even though they are, since I have internet connection on them. It's a mix of AV receivers, Macbook Pros, iPhones, iPads, Apple TV etc.
Even more ludicrious is the attached screenshot, showing the satelites as disconnected while I'm typing this connected to one of them.
atanvarno , I had something very similar. All satellites and devices appeared when using -.38 firmware, updated firmware to Hotfix -.40 and no satellites/devices appear. I downgraded firmware to -.30 and everything appears again. I was having so many connectivity issues with my Ring Doorbells and version -.38 that I thought I'd go back to older firmware and test that out for a bit.
- Guys, I wrote this earlier. I have spoken with Netgear support and they told me that they see .30 as the last stable firmware version. I downgraded and indeed, issues are gone. I also asked them when a safe, stable release will be announced but he could not reply to this. The .30 version does not have the naming issues etc.
