Re: Netgear removed FW 2.5.0.40 + Current 2.3.5.38 "no new fw avail" = Don't upgrade

silpheedc · ‎2019-11-22

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?

FURRYe38 · ‎2019-11-22

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?

@Blanca_O

@Christian_R

sclawrenc · ‎2019-11-22

Which one should we use? The 2.3 or 2.5 versions? It's confusing to say the least.

CrimpOn · ‎2019-11-22

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.

FURRYe38 · ‎2019-11-22

As suggested, it's up to you what you want to do and try. Eitherway, I would as a last resort factory reset your RBR when upgrading or downgrading to check the operation of what your wanting to use. Others have reported doing this has solved there problems they saw:

https://community.netgear.com/t5/Orbi/2-5-0-40-Attached-Devices-Issue-on-RBR50-RBS50/m-p/1827366/hig...

@sclawrenc wrote:
Which one should we use? The 2.3 or 2.5 versions? It's confusing to say the least.

sclawrenc · ‎2019-11-22

Thanks.

Which one is the latest version? I would think the 2.5, but I'm not sure based on the release info.

FURRYe38 · ‎2019-11-22

v2.5.0.40 if your going by numbers. They just posted v2.3.5.34 today if you want to call this the "latest".

silpheedc · ‎2019-11-22

2.5 is latest

FURRYe38 · ‎2019-11-22

Yep.

sclawrenc · ‎2019-11-23

So why did they release another 2.3 if 2.5 is the latest? That doesn’t make sense.

nicktrick92 · ‎2019-11-23

I upgraded to 2.5.0.40 a couple days ago and have had troubles ever since. The network has been literally (No exageration) dropping every 3-5 minutes. I'm going to be reverting back this morning, but I highly suggest not upgrading if you do have the option to go to 2.5.0.40. Not sure if there's an issue with it or what.

tomschmidt · ‎2019-11-23

@nicktrick92 wrote:
I upgraded to 2.5.0.40 a couple days ago and have had troubles ever since. The network has been literally (No exageration) dropping every 3-5 minutes. I'm going to be reverting back this morning, but I highly suggest not upgrading if you do have the option to go to 2.5.0.40. Not sure if there's an issue with it or what.

The last stable release is V2.3.5.30 as reported by most users. NG has recently released a hot fix V2.3.5.34 to fix the expired https certificate. I have reverted my RBR50 router and RBS50 satellites to V2.3.5.30 and my network is more stable and my device names are correct and I can edit them, whereas V2.5.0.38 and .40 device names are completely broken and messed up. NG support has asked me to try the V2.3.5.34 hot fix, but I do not have time currently to try it. I hope to make time in the next 2-3 days to try it, but I would like to see if others have tried V2.3.5.34 without issues. It can be found at https://kb.netgear.com/000061420/RBR50-RBS50-Firmware-Version-2-3-5-34-Hot-Fix

CrimpOn · ‎2019-11-23

@sclawrenc wrote:
So why did they release another 2.3 if 2.5 is the latest? That doesn’t make sense.

It does make sense. Users have been furious with Netgear since August when they let the SSL Certificate expire. (Words like "stupid", "incompetent", etc.) Since the 38 and 40 releases have proved so unpopular that Netgear actually pulled them, the least they could do was to update the damn Certificate. It's a simple file replacement, which they should have done in August. One problem solved. The Cert complaints go away.

FURRYe38 · ‎2019-11-23

Try a factory reset on the RBR and RBS. Factory reset the router using the back push pin button. Hold it in until the top led turns on AMBER then let go. Power OFF the ISP modem for 30 seconds than back on. Wait for the WHITE led to slowly pulsate on top of the RBR, then log in to orbilogin.com using a web browser and walk thru the setup wizard. This time write down all important information for safe keeping later on. I have v40 loaded on my RBR50 and used this method to set up after v40 was loaded. No issues seen like what your describing.

If you continue to have problems after the reset, downgrade to v30 or try v34 if your concerned about the certificate problem.

@nicktrick92 wrote:
I upgraded to 2.5.0.40 a couple days ago and have had troubles ever since. The network has been literally (No exageration) dropping every 3-5 minutes. I'm going to be reverting back this morning, but I highly suggest not upgrading if you do have the option to go to 2.5.0.40. Not sure if there's an issue with it or what.

PapaMike · ‎2019-11-24

I manually upgraded to 2.5.0.40 last night and didn't have any negative experiences. No drops, no slow-downs and all 25 devices connected and properly identified. Currently I get more than I pay for, 117/15.

I've owned Orbi since 2014 and have never experienced more than stellar performance.

What am I doing right?

I realize a few people have firmware issues, but there are many of us who have never been disappointed by Orbi performance.

Wire1852 · ‎2019-11-24

Sorry but at this point the Netgear Orbi firmware development team has burned multiple users & lost all credibility. I'm not going to be a guinea pig with for all practical purposes a hot fix with a single line of documentation. As far as I know it could just be a straight copy of the 40 hot fix.

Staying on the sidelines is the most logical & safest thing to do.

@tomschmidt wrote:
NG support has asked me to try the V2.3.5.34 hot fix, but I do not have time currently to try it. I hope to make time in the next 2-3 days to try it, but I would like to see if others have tried V2.3.5.34 without issues.

pablohoney · ‎2019-11-25

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.

tomschmidt · ‎2019-11-25

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.

CrimpOn · ‎2019-11-25

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:

FURRYe38 · ‎2019-11-25

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.

FURRYe38 · ‎2019-11-25

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.

Voxel · ‎2019-11-26

Interesting... I mean 2.5.x.x vs 2.3.x.x. But I still do not see any logic in this chronological numerations.

If somebody is interested I've released my custom firmware build v. 2.5.0.42SF-HW (2.5.0.40 was used as a basis, "HW" means hrdware acceleration of OpenSSL). List of changes:

https://www.snbforums.com/threads/custom-firmware-build-for-orbi-rbk50-v-2-5-0-42sf-hw.60308/

Voxel.

tomschmidt · ‎2019-11-26

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

Wire1852 · ‎2019-11-26

Translation.... Netgear Orbi Firmware Team = Keystone Cops

It just keeps getting worse & worse. They can't even register a security certificate correctly.

@tomschmidt wrote:
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

FURRYe38 · ‎2019-11-26

Did you clear out all browser caches in FF, exit the browser then restart it?

Does this happen with any other browsers?

I'm not seeing this with v40 loaded.

@tomschmidt wrote:
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