NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
chrisuk
Nov 10, 2019Aspirant
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...
Wire1852
Nov 13, 2019Apprentice
What I waiting to hear is if anyone has upgrade to 2.5.0.40 from a version other than 2.5.0.38 without encountering any issues (like 2.3.5.30). I would like the security certificate update of the expired Aug security certificate, but after the issues of 2.5.0.38 no way am I updating first to 2.5.0.38.
They only thing I believe is in the update is the security certificate which should have been updated months ago. Notice the hot fix is a beta indicating this is a new process which Netgear threw together after missing putting the security certificate in 2.5.0.38. How many hot fixes has Netgear done previously on the Orbi?
It's disappointing Netgear provides next to no info (a single line) on what's in the hot fix. It's also disappointing that no one from Netgear will post on this forum on these issues and when they'll be addressed.
tomschmidt
Nov 13, 2019Virtuoso
Wire1852 wrote:It's disappointing Netgear provides next to no info (a single line) on what's in the hot fix. It's also disappointing that no one from Netgear will post on this forum on these issues and when they'll be addressed.
Likewise I am extremely disappointed with the lack of support from NG. I have had multiple tickets opened with them on the Orbi due to firmware bugs. They even replaced my RBR50 under RMA once to try to fix the DNS resolver issues that it had with earlier firmware. All that their support can suggest is resetting back to factory and programming the settings manually. However even with the V2.5.0.38 release, this does not fix the device naming issue.
NG support likewise cannot give the customers any expected timeline for fixes to the firmware. Their regression testing (if they even do regression testing) should have caught the device naming bug before the V2.5.0.38 release. The v40 hot fix does not address this issue either.
I just this week checked these Community Forums for support since NG tech support is extremely lacking even with extended warranty support on my system. I have never had so many issues with any network or computer hardware in my last 35+ years in the tech industry.
- Retired_MemberNov 13, 2019
tomschmidt wrote:
Wire1852 wrote:It's disappointing Netgear provides next to no info (a single line) on what's in the hot fix. It's also disappointing that no one from Netgear will post on this forum on these issues and when they'll be addressed.
Likewise I am extremely disappointed with the lack of support from NG.
Please keep one thing possibly in mind, in the case of firmware glitches, IF you did a manual update, you are partially to blame. I know that's not the 100% solution, but think about it, IF your system was working, why upgrade? On the other hand IF a auto pushed firmware upgrarde sinks your network, you only have NG to blame.