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 a...
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:
Here is the certifcate error shown on Firefox 70.0.1 for the V2.3.5.34 firmware:
orbilogin.net uses an invalid security certificate.
The certificate is not trusted because it is self-signed.
Error code: MOZILLA_PKIX_ERROR_SELF_SIGNED_CERT
Did you clear all browser caches in your browsers after you updated FW?
It's working for me in IE11 and Opera.
tomschmidt wrote: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.
I was told today that NG pulled v30 and v40 from there Orbi update servers. So users shouldn't see this on there FW update page on the RBR. Yes there available via the download site.
They confirmed that v34 is the standing latest version that they recommend upgrading to. You can upgrade to v34 which has the web page certificate fix or downgrade to v30 or last working version of FW. A factory reset is the last resort if users can't get there systems working normally. Those of us who do resets and manual upgrades, this seems to avoid issues seen by those of you who do see issues and choose not to do a reset. It's up to you. NG said it was coming out with a new FW udpate to fix the device naming issue found in v38. For those of you who can't get there systems working, with or with out a factory reset, revert back to something that works for you and wait for the next update to arrive. No date was given when the next FW upate will be released.
Good Luck.
