NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
OrbiOS 2.1.1
The Orbi team at NETGEAR is aware that some users are experiencing higher than expected Orbi Router reboots, special characters in WiFi Passwords and WiFi / Internet disconnects. We believe these issues are related to the OrbiOS 2.1.1 firmware. We are actively working to address these issues, and expect to fix them with a firmware upgrade soon. In the meantime, we’re temporarily suspending auto-upgrading users to OrbiOS 2.1.1.
While we work through some of the issues, we’re releasing a new Beta firmware (2.1.2), which contains:
- Support for LED control & scheduling for Orbi Outdoor Satellite (RBS50Y)
- Fixes high CPU utilization on Orbi Router, which could be causing other issues
- Fixes the Attached Devices UI showing all devices connecting to the Orbi Router
The Beta firmware 2.1.2 files can be obtained from here:
RBR50: http://files.netgear-support.com/go/?a=d&i=n2X2ARvI7o
RBS50: http://files.netgear-support.com/go/?a=d&i=yBsnhHaBiw
RBR40: http://files.netgear-support.com/go/?a=d&i=8xFS1yg8fn
RBS40: http://files.netgear-support.com/go/?a=d&i=Hu3hbx814i
RBW30: http://files.netgear-support.com/go/?a=d&i=PRpkMfJynw
RBS20: http://files.netgear-support.com/go/?a=d&i=OGhLlDB9mQ
Instructions for performing a Manual Upgrade: https://kb.netgear.com/000037217/How-do-I-check-and-manually-upgrade-the-firmware-on-my-Orbi-satellite
If you are having issues with 2.1.1, having higher than normal disconnects or if you have purchased an Outdoor Orbi Satellite (RBS50Y) please upgrade to the new Beta firmware through the manual upgrade process. Feel free contact NETGEAR Support if you’re having issues with MR 2.1.1 (even if you’re outside of the 90 day window).
We apologize for these issues.
Orbi Product Team
Let me give you a quick update on where NETGEAR is with the OrbiOS.
Just before Christmas break, we paused the distribution of OrbiOS 2.1. Very soon, we're about to restart the distribution of a slightly updated version of the beta (2.1.2). In addition to the major new features introduced in 2.1 (e.g. Circle, Ethernet Backhaul), this firmware is expected to address the high CPU issue, as well as the special character in PSK issue as well as support for the Outdoor Orbi. Check Release Notes for complete list.
We are continuing to work on the issues with Google devices that have been documented in the press (several users have provided links here).
My recommendation is that you should either use the Orbi Mobile App (if you haven't seen it recently, check it out, we've made some major improvements) or the Web UI to check for new firmware or wait until your system gets auto-upgraded.
To answer your question, Stars_fan. When Orbi are connected over Ethernet backhaul, the 5GHz band becomes hot standby.
Orbi Product Management
371 Replies
Replies have been turned off for this discussion
Yep, I'll take it. Thanks for the update - and keeping in mind this is a beta, I hope everyone on here will take that in good faith.
I'm so desparate i may just do this upgrade. But only out of desparation.
What if i end up bricking them? Will Netgear replace them, even if out of warranty period?
Just upgraded to the beta firmware, crossing my fingers this fixes the constant wifi disconnects/reboots. I still have the wifi on my Google Pixel 2 XL running Android 8.1 turned off to prevent reboots, is this firmware beta supposed to fix this? There's no reason a client device should be able to reboot the entire system.
sandaboy wrote:... is this firmware beta supposed to fix this? There's no reason a client device should be able to reboot the entire system.
I'm pretty sure that the issue for Android 8 reboots is not fixed in this release, though by fixing some of the high CPU utilization the hope was that would have a positive effect on stability.
Thanks Amrit - 2.1.1 was fine for me for about a week then fell into a pattern of reboots & total loss of wireless. I reverted to 2.0.0.74 and sanity was restored and the family were happy again.
I will probably give the beta a try over the next few days.
I am using daisy chain. When installing the beta which sat should I do first? The one furthest from the router or the one nearest that does the transfer to the distant sat. Backhaul is 5g.
Well, I am hoping the Beta pans out, because I am getting to the point of dumping the entire setup.. Router & 2 Satallites.
>>Fixes high CPU utilization on Orbi Router, which could be causing other issues
I have a questions, how does one find the CPU Utilization? The UI/Interface for the RBR & RBS's really don't give anyone the ability to measure anything. I can have it count packets sent & recieved, and reset once a month, but I can't find any other monitor points in the system at all.
I also rolled back all my Orbis to the .74 version... its better, but not what it needs to be.
Installed the beta and will report. I was having issues with random reboots (vaired from 12 hours to 3-4 days, but would eventually reboot for no reason). Other than that, everything else was good. Connection to the web, speed tests via LAN or Wi-Fi, Circle, satelite connections, devices on the correct band, all were perfect. No Android devices in the household, mostly Apple products (do have 1 Chromecast & 1 Nest Cam though).
Well, I'm at work and just got an email that my Nest Camera is down. Tried to log in remotely and can't. Took like 20 minutes until I could get back in my network remotely, so the reboots are still there.
Greystorm64 wrote:I have a questions, how does one find the CPU Utilization?
If you go to /debug.htm (i.e. 192.168.1.1/debug.htm) then you will see the CPU utilization near the top of the page
Ironic you're refering to this latest firmware release as a "beta" given how many problems the last "non-beta" release created.
I rolled back to a stable version and will wait to see if you guys actually tested this one before I install it.
>> I have a questions, how does one find the CPU Utilization?
http://<router_ip_address>/debug.htm
Why do I hear theme from Jaws in my head while reading this? :-)
Will install this when I get home tonight and see how things go.
AmitR wrote:The Orbi team at NETGEAR is aware that some users are experiencing higher than expected Orbi Router reboots, special characters in WiFi Passwords and WiFi / Internet disconnects. We believe these issues are related to the OrbiOS 2.1.1 firmware. We are actively working to address these issues, and expect to fix them with a firmware upgrade soon. In the meantime, we’re temporarily suspending auto-upgrading users to OrbiOS 2.1.1.
While we work through some of the issues, we’re releasing a new Beta firmware (2.1.2), which contains:
- Support for LED control & scheduling for Orbi Outdoor Satellite (RBS50Y)
- Fixes high CPU utilization on Orbi Router, which could be causing other issues
- Fixes the Attached Devices UI showing all devices connecting to the Orbi Router
The Beta firmware 2.1.2 files can be obtained from here:
RBR50: http://files.netgear-support.com/go/?a=d&i=n2X2ARvI7o
RBS50: http://files.netgear-support.com/go/?a=d&i=yBsnhHaBiw
RBR40: http://files.netgear-support.com/go/?a=d&i=8xFS1yg8fn
RBS40: http://files.netgear-support.com/go/?a=d&i=Hu3hbx814i
RBW30: http://files.netgear-support.com/go/?a=d&i=PRpkMfJynw
Instructions for performing a Manual Upgrade: https://kb.netgear.com/000037217/How-do-I-check-and-manually-upgrade-the-firmware-on-my-Orbi-satellite
If you are having issues with 2.1.1, having higher than normal disconnects or if you have purchased an Outdoor Orbi Satellite (RBS50Y) please upgrade to the new Beta firmware through the manual upgrade process. Feel free contact NETGEAR Support if you’re having issues with MR 2.1.1 (even if you’re outside of the 90 day window).
We apologize for these issues.
Orbi Product Team
RBW30 link is broken
mkenny28 wrote:
AmitR wrote:The Orbi team at NETGEAR is aware that some users are experiencing higher than expected Orbi Router reboots, special characters in WiFi Passwords and WiFi / Internet disconnects. We believe these issues are related to the OrbiOS 2.1.1 firmware. We are actively working to address these issues, and expect to fix them with a firmware upgrade soon. In the meantime, we’re temporarily suspending auto-upgrading users to OrbiOS 2.1.1.
While we work through some of the issues, we’re releasing a new Beta firmware (2.1.2), which contains:
- Support for LED control & scheduling for Orbi Outdoor Satellite (RBS50Y)
- Fixes high CPU utilization on Orbi Router, which could be causing other issues
- Fixes the Attached Devices UI showing all devices connecting to the Orbi Router
The Beta firmware 2.1.2 files can be obtained from here:
RBR50: http://files.netgear-support.com/go/?a=d&i=n2X2ARvI7o
RBS50: http://files.netgear-support.com/go/?a=d&i=yBsnhHaBiw
RBR40: http://files.netgear-support.com/go/?a=d&i=8xFS1yg8fn
RBS40: http://files.netgear-support.com/go/?a=d&i=Hu3hbx814i
RBW30: http://files.netgear-support.com/go/?a=d&i=PRpkMfJynw
Instructions for performing a Manual Upgrade: https://kb.netgear.com/000037217/How-do-I-check-and-manually-upgrade-the-firmware-on-my-Orbi-satellite
If you are having issues with 2.1.1, having higher than normal disconnects or if you have purchased an Outdoor Orbi Satellite (RBS50Y) please upgrade to the new Beta firmware through the manual upgrade process. Feel free contact NETGEAR Support if you’re having issues with MR 2.1.1 (even if you’re outside of the 90 day window).
We apologize for these issues.
Orbi Product Team
RBW30 link is broken
Maybe they are hosting that link using an orbi? ;-)
RBW30:
http:/files.netgear-support.com/go/?a=d&i=PRpkMfJynw
Thank you for finally acknowledging the issues, and suspending the auto upgrades. To me it's the first time it seems like you care and it makes me hopeful.
I'm going to unhook my Eero's tonight and put the Orbi's back in with the beta firmware. Here's hoping it takes care of the disconnects I was dealing with. If so, I can return the Eero's and save myself $500.
I'll report on my progress, fingers crossed.
-Grey
Files are corrupted. Can't download.
Been checking on things remotely, I know that the system uptime has reset at least 3 times in 8 hours. I'm reverting back to 2.1.1.16.
Are you saying that .16 was more stable for you? I doubt there is any basis for that from what was done in this update. I would try to re-appy the updates of the 2.1.2.10 beta again overtop of the existing and see if you get more stability that way.
Also maybe try unchecking UPNP as I found previously that has helped my Orbi stability.
I'm not having any reboots - but then again I never had any with 2.1.1.16 either - what I did have with .16 was internet disconnects on Wifi devices. Too early to tell if that's been solved as that usually happens after a few days of running.
Where are the LED controls?
2.0.0.74 has been functioning well but I'll give this a go. I'm just going to update over 2.0.0.74. I won't reset my Orbi to default and start over. I've just updaed the satellite and then the the router and I'll monitor uptime with debug.htm
