NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
SW_
Mar 22, 2019Prodigy
New Orbi RBR50/RBS50 Firmware Version 2.3.1.44
Netgear is pushing out yet another a new Orbi firmware update.
Hopefully it's better than the last version v32.
Please share your experience.
Firmware Update
...
Joboo7777
Apr 06, 2019Apprentice
I'm running a default config of .44 on RBR50/RBS50 setup. Only settings I changed were enabling MU-MIMO and Implicit Beamforming. I have not see any decrease in speed from my iPhone 8(or any other devices for that matter). I'm wondering if the issues people are seeing are more related to the state of wireless after the reboot required to install firmware vs the actual firmware itself. Being in the IT field, I've seen upgrades and/or patches blamed for issues when the reboot required to apply the patch/upgrade has been the root cause. From what I understand everytime you reboot your wireless there is a potential for the channles used to change which could create variations in performance. Maybe this could be the issue.
FURRYe38
Apr 06, 2019Guru - Experienced User
Seen many issues with Orbi. Some has been FW. Mostly other issues are mis-configurations. Yes, Beamforming and MIMO should be enabled along with WMM. Seen it were somehow WMM gets disabled. WMM should always be enabled. MIMO is not as important due to some users ma not have MIMO supporting devices. Beamforming is always good to have on.
Also FW updates seem to go back on auto updates and continuing rather than doing a factory reset and setup from scratch. Seems that lingering old code and configurations seems to not migrate well into newer FW. Factory resets and setup from scratch clears this up in most cases.
Joboo7777 wrote:
I'm running a default config of .44 on RBR50/RBS50 setup. Only settings I changed were enabling MU-MIMO and Implicit Beamforming. I have not see any decrease in speed from my iPhone 8(or any other devices for that matter). I'm wondering if the issues people are seeing are more related to the state of wireless after the reboot required to install firmware vs the actual firmware itself. Being in the IT field, I've seen upgrades and/or patches blamed for issues when the reboot required to apply the patch/upgrade has been the root cause. From what I understand everytime you reboot your wireless there is a potential for the channles used to change which could create variations in performance. Maybe this could be the issue.