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
As regards the update order for a new firmware update, I understand to update the satellites first, then the router last for a manual update. And when I did an online update during my initial setup to update from the factory installed 1.12.0.18 to 2.0.0.74, I did the satellites first, then the router, iirc. Then I was able to manually update from 2.0.0.74 to 2.1.1.16 in the proper order. But I could not manually update straight from 1.12 to 2.1. I had to online update to 2.0 first.
But I'm curious, how does the auto-update process work in that same regard? Does the push update do the satellites first, then the router last?
This latest beta update (2.1.2.10) has resolved all of the issues I was having with disconnects and with not showing devices connected to my 2 satellites.
Im re-reading the original message and I just want to confirm this beta does NOT address the bug where orbi wont save special characters in password, correct?
lowepg wrote:Im re-reading the original message and I just want to confirm this beta does NOT address the bug where orbi wont save special characters in password, correct?
That appears to be the case from the message, but if you are on 2.1.1.12 or 2.1.1.16, you don't have anything to lose by trying this one. I tried adding a $ in my guest password and that worked, but I have seen another user has trouble with extremely long passwords still.
Unfortunately my experience with the Netgear Orbi will contradict to end tonight.
I installed the latest beta software on the router and the two satellites that I have. It’s seemed to be working mostly well. Tonight I got a child fork error as I tried to open the web browser. Also got the same error when I tride to open it from another laptop and on my iPad.
From that point, Things were disconnecting, wired things were showing up as wireless and vice versa etc. Did a factory reset on all three units. Difficulties continued afterwards.
I had one restart at 2 hours. Debug shows system uptime of two hours but it definitely bumped some devices off because their addresses changed.
I'm thinking of a reset. in real world shouldn't have to do this but since Netgear released a buggy update and we here are savvy enough I'll try it. Then it's back to .74. Even .74 improved with a reset.
Update: one of my satellites keeps showing a blue ring. Diagnosing.
dpaugro wrote:Update: one of my satellites keeps showing a blue ring. Diagnosing.
I unplugged and replugged it. Blue light went away after a minute or two, which is longer than the stated 10 seconds on the KB site. I'm watching uptime on that satellite. The other satellite has not exhibited problems and uptime indicates no restarts since I upgraded firmware.
Router rebooted after 3 hours. Back to .74. So frustrating
Updated rotuer and satellite with great results!
Everything running smooth and attached devices now display correctly.
Thanks for this beta firmware.
I gave it a shot because I add some random reboots (not much) and because the attached device list was wrong.
Updated to 2.1.2 one hour ago 2xRBS50 + 1xRBS40 + RBR50. Everything running smooth. So far so good. Attached device list is correct. I'll update my feedback after few days.
One of the less painful upgrades, everything went smooth. Devices connected right up the Sat and Router and information on connections are correct Will monitor
PyroDog wrote:Updated rotuer and satellite with great results!
Everything running smooth and attached devices now display correctly.
I take back what I said. Still having issues:
https://community.netgear.com/t5/Orbi/Packet-loss-pattern/m-p/1479220#M20248
The issue seemingly related to Android phones is still present. I installed the beta late last night and this morning the router rebooted when my Android phone alarm went off.
Good until I used my Android phone and the system rebooted. Android reboot issue is not fixed.
this has been worse than 2.1.1.16 in my case. Since updating last night, I've had 2 or 3 router reboots, 1 satellite reboot, and 1 maybe two dropping all wifi connections.
I did not reset the router after updating. I just updated and ran it. Need to work at home today so going back to 2.0.0.74
Blcklab wrote:this has been worse than 2.1.1.16 in my case. Since updating last night, I've had 2 or 3 router reboots, 1 satellite reboot, and 1 maybe two dropping all wifi connections.
I had a mod PM me about having any Android 8.0 devices in my household because that fix is NOT in this beta, closest thing I have to an Android device is a Chromecast which wasn't turned on during my testing.
I do. However I haven't noticed getting "kicked off" when that device connects or wakes. Sometimes it runs fine. Sometimes not. Either way I need to use my phone at wifi where I live.
Had all the reported problems with 2.1.1.16 with a barely functinoal system. Kids all switched to Verizon LTE. It was awful. Had to manually reboot system several times a day just to be able to watch streaming TV and browse on Apple devices. Hardwired devices were ok.
Updated to 2.1.2 beta and it is much better. Still getting occasional connection problems where device stays connected, but unable to get through to Internet. Have not had to reboot router system since going to 2.1.2 though. The connection problems recover after about a minute or two. Devices are now connecting to satellites while the 2.1.1.16 almost everything connected to base router unless it was literally next to a satellite.
Summary - 2.1.2 is definitively better than 2.1.1.16 but still not a true fix
Does the beta have the KRACK patch?
Despite intially having a decent experience with 2.1.1.16, I eventually downgraded to 2.0.0.74 after some stability issues with 2.1.1.16
I am happy to stay with 2.0.0.74 for the now so long as the beta does not give me anything urgent / beneficial above 2.0.0.74. I know the connected 'devices list' is fixed in the beta, but anything else compelling that the beta includes above 2.0.0.74?
I would say just Disney Circle if you wanted to use that...and wired backhaul if you can get it to work
Found a bug with firmware V2.1.2.10. None of my port forwarding seems to be working after the update.
I tried removing and re-adding but no joy. :-/
- "Found a bug with firmware V2.1.2.10. None of my port forwarding seems to be working after the update.
I tried removing and re-adding but no joy. "
This is the kind of thing (if validated and no very very odd setup) that drives us a little nuts. What sort of testing process doesn't check core functionality like this? I hope it's a one off config issue and not broken across the board. My setup seems pretty stable and it is nice to see what's REALLY connected to each router/satellite.I just checked mine...all 3 of mine ARE working with the beta. i will also add that mine are working with NO-IP dynamic dns service.
