NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Netgear removed FW 2.5.0.40 + Current 2.3.5.38 "no new fw avail" = Don't upgrade
Just noticed that the Netgear Downloads site no longer shows 2.5.0.40. And on my running RBR and RBS 2.3.5.38, they are no longer indicating that an FW upgrade is available. Could it be that someone at Netgear realized that the 2.5.x.x branch is broken? And it begs the question: who exactly is 2.5.x.x even for?
32 Replies
Interesting,
https://kb.netgear.com/000061393/RBR50-RBS50-Firmware-Version-2-5-0-40-Hot-Fix is still available.
However I see https://kb.netgear.com/000061420/RBR50-RBS50-Firmware-Version-2-3-5-34-Hot-Fix as being available now with same release note information as v40.
Security Fixes:
- Updates the https certificate
Seems that they are reverting from v2.5x to v2.3x. No idea why the numbering scheme is different.
Maybe the NG put the HTTPS fix in the v2.3x version so users can get this fix along with Device Naming that seems to be working at this version level?
Maybe one of the forum Moderators can comment?
Which one should we use? The 2.3 or 2.5 versions? It's confusing to say the least.
- My feeling is the prudent thing to do is wait for some people to install 2.3.5.34 and see what they report.2.3.5.30 is "stable", but has that irritating problem with the SSL Certificate having expired last August. If the invalid Cert doesn't bother you, and your Orbi is doing eveything you want, leave it alone.If the invalid Cert does bother you, and people report 2.3.5.34 not causing any problems, then update to it.If you have some issue that 2.5.0.40 appears to have solved and you do not mind the device naming being totally screwed up, then I would read through the entire sequence of posts involving 2.5.0.38 and 2.5.0.40 and make a judgement call. "Is what I stand to gain worth the shortcomings that people have pointed out?"For me, it's simple. I'm staying on 2.3.5.30 until there is a consensus that 2.3.5.34 causes no problem.
Please see my other posts in the other threads. Netgear has acknowledged to me via. email that there are bugs in the current firmware. They have based this on logs I have sent them for my RBR and RBS 50. They are working on a fix to be out in the next few weeks. I have told them that they need to sort out their firmware and ensure proper QA is donew as their last few versions have been buggy. I told them I do not want to keep emailing Patrick Lo (CEO) and Mark Merrill (CTO) with ongoing firmware issues. But at least now they have acknowledged that the issue is their end and not ours which has not happened before.
I updated my firmware from V2.3.5.30 to V2.3.5.34 an hour ago. So far the device naming looks correct as it did with the .30 release. However, there are two issues I see with the .34 hot fix update.
1. The firmware update screen showed that it should take about 3 minutes to update the firmware. This screen did not update, I finally had to open a new window to my router to see that the update completed.
2. Web browsers still do not trust the updated https certificate for the .34 release. The expiration date of the certificate is now for November 2029, but Edge, Internet Explorer and Chrome browsers still do not trust the certificate.
Thanks for sharing this (unexpected) news. Would it be convenient to post the actual certificate information?
Of my many browsers, Firefox seems to do the best job of actually showing the certificate information.
Here is how Firefox displays the certificate that expired in August:
