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 is...
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
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
Just updated to the beta.
Some dievices are showing on th Sats. I will check later in day for full connections.
CPU loads are
RBR50 13.5%
Near Sat 30.*% 5g connect
Far Sat 21.4 % 5g connect
AP mode
updated manually with no reboot.
So far so good.
Previously I had 15 days on 16 with no issues otehr than lasck of Sat UI info.