Orbi Firmware Update 2.5.0.38

I saw not speed issues or slower operation with v38 loaded. Though I and others do factory resets. v38 works. 

Something to at least try as maybe the next FW update will not fix your experiences. Reset maybe needed. Works for others.

https://community.netgear.com/t5/Orbi/ORBI-RBK50-RBS50-Tips-Tricks-Hidden-Secrets-etc/m-p/1820500/highlight/true#M74929
https://community.netgear.com/t5/Orbi/ORBI-RBK50-RBS50-Tips-Tricks-Hidden-Secrets-etc/m-p/1820477/highlight/true#M74918
https://community.netgear.com/t5/Orbi/Speeds-have-plummeted-after-latest-update/m-p/1819282/highlight/true#M74655

Good Luck. 

---

wchp wrote:

Without getting into all the things to try I am just posting this an observed performance change.

On a 2018 Macbook Pro on Firmware V 2.5.0.38 I am experiencing ½ to ¼(or less) the 802.11AC throughput vs. the previous version of firmware.

460-585 mps on 2.3.5.30 from Mac OS wifi details and 520/41.2 from Speedtest app

40-180 mbps on 2.5.0.38from Mac OS wifi details and 86/23.9 from Speedtest app

Observed using WiFi details AND WiFi explorer.

Both observations on WiFi Explorer show Chan 48, 90% signal strength, SNR 54dB readings with both versions of firmware.

Laptop and Router locations unchanged.

Tried everything except factory reset/paper clip simply because I dont want to and dont feel I should need to with a public firmware release (with beta firmware versions this is a given that a factory reset is done)

Of note (if it makes any difference) I am running the Armor protection on the RBR (for both tests).

Have reverted back to 2.3.5.30 and will wait for next rev of FW.

 

---

---

FURRYe38 wrote:

 

 

---

 v38 works. ....

 

 

why do you keep saying this?

---

---

Retired_Member wrote:

---

FURRYe38 wrote:

 

 

---

 v38 works. ....

 

 

why do you keep saying this?

---

 

---

Probably because it does with the exception of a couple of minor glitches.

---

MikeG63 wrote:

---

---

Probably because it does with the exception of a couple of minor glitches.

---

My search results prove otherwise....a glitch is a non-necessary glitch to a working network

Only glitch being the device naming problem. Otherwise, v38 works very well for me. And others. 

---

MikeG63 wrote:

Probably because it does with the exception of a couple of minor glitches.

---

---

FURRYe38 wrote:

Only glitch being the device naming problem. Otherwise, v38 works very well for me. And others. 

---

---

and others....?  Who are these others????

---

Retired_Member wrote:

---

FURRYe38 wrote:

Only glitch being the device naming problem. Otherwise, v38 works very well for me. And others. 

---

---

and others....?  Who are these others????

---

I was trying to thread the middle here. I am a beta tester for netgear products and a hard reset between firmware revs is expected and required to fully test each rev as it is introduced. I consider the RBK53 system I use to be the consumer standard that is a great compromise between throughput and coverage. This is the first time in over a year that any of the Orbi public firmware updates have introduced an actual performance issue and not just a GUI or convience/feature issue. It is NOT that I cant do a factory reset, I just dont want to and dont think a public consumer should be expected to. Never mind how many people actually notice, and then know enough to come to the forums to research it and then read all the posts and seperate the salt from the boiling water. Most people here come becuase they 1) realize they have an issue 2) know enough to read the forums 3) take the time to read through a thread like this in its entirety  4) are willing to put in the work to correct a potential issue that a avg. user would not have any inclination or interest in performing. 

It is not that I cant do a factory reset to see if it corrects the issues I am seeing (which includes device lists and other niggly's) It is just that I treat this system as if I was a oblivious consumer that just thinks and expects it to work. So... I wont do a factory reset. The new firmware release notes do not specifically list any serious vunerabilities or performance issues that effect my specific implimentation. User defined channels, annotated devices list or actual MU-MIMO reality that most household clients are oblivious of the standard, etc. I respect that a hard factory reset and manual reconfiguration from scratch MAY fix my observed issues, but dont think I should need to (in the role of a new user). I honestly think that those of us that post here are the exceptions rather than the norm and I simply choose to report what I am experiencing with my hardware in hopes that Netgear follows these threads to a degree to help ID issues and improve their product. Doubtful many if almost any know how to find hidden pages in firmware and play with settings Netgear did not make public and may or may not work. So, Fury, glad you have things sorted and thanks for presenting a potential resolution, Netgear, hope you read this, Others, revert to prev version (2.3.5.30?) and you can find it on the RBK50 support page (https://www.netgear.com/support/product/RBK50.aspx#download under "Previous Versions" and plug along like most of the folks that dont know this forum exists. 

---

Retired_Member wrote:
And stop performing manual firmware updates

---

VAJim,

I tried updating to the newest rev both using the "automagical" auto update button and then reverted and then tried updating manually by downloading the newest firmware and doing the Satalites first and then the Router. I expected no difference and found none, but just tried it anyway for the sake of giggles.

After the updates I did do a hard power off/on after they came up with .38 but that was the extent of the effort I was willing to put forth. 

Most settings in my config are manual and customized and I have a very eclectic mix of IoT devices to go along with my peak of 67 devices.

Even if I do a hard reset it may or may not resolve the issue I am observing on my hardware in my environment. 

p.s. AND I should have tested on both a wired and wireless connection to the router and substituted a different cable modem to rule out those variables, but again, I am pretending I am a happy homeowner user so only reporting and testing as such.

---

wchp wrote:

---

Retired_Member wrote:
And stop performing manual firmware updates

---

VAJim,

I tried updating to the newest rev both using the "automagical" auto update button and then reverted and then tried updating manually by downloading the newest firmware and doing the Satalites first and then the Router.

 

Here's what I have in mind:

 

Manual updates = user does it.  Either by 'clicking' on the update at the router loging screen (after seeing that there is an update)...or.....downloading from the 'download' area of the NG website, usually in an effort to fix a problem (how did that happen).

 

Automaticallly = user does nothing.  NG pushes the firmware.  Usually in the case of a major revision.  I suspect this would also include security issues that I keep hearing a frantic call about from posts here.

 

Bottom line...once your network is running, leave it alone.  

You should try a factory reset and setup from scratch. Some as a last resort. Some of us don't see problems like you do. 

---

wchp wrote:

---

I tried updating to the newest rev both using the "automagical" auto update button and then reverted and then tried updating manually by downloading the newest firmware and doing the Satalites first and then the Router. I expected no difference and found none, but just tried it anyway for the sake of giggles.

After the updates I did do a hard power off/on after they came up with .38 but that was the extent of the effort I was willing to put forth. 

Most settings in my config are manual and customized and I have a very eclectic mix of IoT devices to go along with my peak of 67 devices.

Even if I do a hard reset it may or may not resolve the issue I am observing on my hardware in my environment. 

p.s. AND I should have tested on both a wired and wireless connection to the router and substituted a different cable modem to rule out those variables, but again, I am pretending I am a happy homeowner user so only reporting and testing as such.

---

---

FURRYe38 wrote:

You should try a factory reset and setup from scratch. Some as a last resort. Some of us don't see problems like you do. 

 

 

Factory reset is for lost password

---

Can we all vote to have this FURRYe38 stop posting. 99% of his posts are "I'm not having any problems so you shouldn't either." Quite possibly the most unhelpful person I've ever seen. He's like those people who answer Amazon questions with "I don't know"

Why certainly, you can contact NG and let them know what you feel. I post as I see fit. I report only to them. 

Good Luck. 

---

Gregron wrote:

Can we all vote to have this FURRYe38 stop posting. 99% of his posts are "I'm not having any problems so you shouldn't either." Quite possibly the most unhelpful person I've ever seen. He's like those people who answer Amazon questions with "I don't know"

---

---

Gregron wrote:

Can we all vote to have this FURRYe38 stop posting. 99% of his posts are "I'm not having any problems so you shouldn't either." Quite possibly the most unhelpful person I've ever seen. He's like those people who answer Amazon questions with "I don't know"

---

He lives on the edge.  All others see him as difficult 

---

wchp wrote:

On a 2018 Macbook Pro on Firmware V 2.5.0.38 I am experiencing ½ to ¼(or less) the 802.11AC throughput vs. the previous version of firmware.

460-585 mps on 2.3.5.30 from Mac OS wifi details and 520/41.2 from Speedtest app

40-180 mbps on 2.5.0.38from Mac OS wifi details and 86/23.9 from Speedtest app

Observed using WiFi details AND WiFi explorer.

Both observations on WiFi Explorer show Chan 48, 90% signal strength, SNR 54dB readings with both versions of firmware.

Laptop and Router locations unchanged.

Tried everything except factory reset/paper clip simply because I dont want to and dont feel I should need to with a public firmware release (with beta firmware versions this is a given that a factory reset is done)

Of note (if it makes any difference) I am running the Armor protection on the RBR (for both tests).

Have reverted back to 2.3.5.30 and will wait for next rev of FW.

 

 

---

OK... finally decided to give a hard reset a try.

1) Upgraded from 2.3.5.30 to 2.5.0.38 (Tested and till same speed issue)

2) Applied Hotfix 2.5.0.40 (tested and still same speed issue)

AND STILL exactly the same problem.

3) Paperclip reset the router and both Satallites from scratch

Exact same problem still as listed above making NO changes to the factory config other than the firmware rev.

4) Manually entered my standard config.

Still:

"460-585 mps on 2.3.5.30 from Mac OS wifi details and 520/41.2 from Speedtest app

40-180 mbps on 2.5.0.38from Mac OS wifi details and 86/23.9 from Speedtest app"

SO... went to Costco and purchased a brand new RBK53S system

1) Upgraded from 2.3.5.xx (firmware it shipped with) to 2.5.0.38

2) Applied Hotfix 2.5.0.40

3) Tested WiFi speed and same poor performance on new system as my old one.

3) Downgraded the NEW RBK53S system to 2.3.5.30 AND... silly thing, WiFi speeds and connectivity back to normal.

I dont see a hard reset resolving the performance issues that are presenting themselves in my environment (CM-1100 --> RBK53)

with either my 1 year old RBK53 or a brand new RBK53S

I dont have PC or Android devices to test with but the WiFi slowdown is significant on my 2018 Mackbook Pro and iPhone Xs.

Thanks for trying the reset and letting us know. 

Keep what works for you loaded. 

---

wchp wrote:

---

wchp wrote:

On a 2018 Macbook Pro on Firmware V 2.5.0.38 I am experiencing ½ to ¼(or less) the 802.11AC throughput vs. the previous version of firmware.

460-585 mps on 2.3.5.30 from Mac OS wifi details and 520/41.2 from Speedtest app

40-180 mbps on 2.5.0.38from Mac OS wifi details and 86/23.9 from Speedtest app

Observed using WiFi details AND WiFi explorer.

Both observations on WiFi Explorer show Chan 48, 90% signal strength, SNR 54dB readings with both versions of firmware.

Laptop and Router locations unchanged.

Tried everything except factory reset/paper clip simply because I dont want to and dont feel I should need to with a public firmware release (with beta firmware versions this is a given that a factory reset is done)

Of note (if it makes any difference) I am running the Armor protection on the RBR (for both tests).

Have reverted back to 2.3.5.30 and will wait for next rev of FW.

 

 

---

OK... finally decided to give a hard reset a try.

1) Upgraded from 2.3.5.30 to 2.5.0.38 (Tested and till same speed issue)

2) Applied Hotfix 2.5.0.40 (tested and still same speed issue)

AND STILL exactly the same problem.

3) Paperclip reset the router and both Satallites from scratch

Exact same problem still as listed above making NO changes to the factory config other than the firmware rev.

4) Manually entered my standard config.

Still:

"460-585 mps on 2.3.5.30 from Mac OS wifi details and 520/41.2 from Speedtest app

40-180 mbps on 2.5.0.38from Mac OS wifi details and 86/23.9 from Speedtest app"

 

SO... went to Costco and purchased a brand new RBK53S system

1) Upgraded from 2.3.5.xx (firmware it shipped with) to 2.5.0.38

2) Applied Hotfix 2.5.0.40

3) Tested WiFi speed and same poor performance on new system as my old one.

3) Downgraded the NEW RBK53S system to 2.3.5.30 AND... silly thing, WiFi speeds and connectivity back to normal.

 

I dont see a hard reset resolving the performance issues that are presenting themselves in my environment (CM-1100 --> RBK53)

with either my 1 year old RBK53 or a brand new RBK53S

I dont have PC or Android devices to test with but the WiFi slowdown is significant on my 2018 Mackbook Pro and iPhone Xs.

---