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
Well, I'm not going to say things are fixed yet. However, after updating to 2.1.2.18 I'm able to turn on the satellite, and connect my Pixel 2 to wifi, with all my other Google devices connected, and haven't had a reboot since updating. I'll see what happens over the next day or two, but this is more than I've been able to do since installing the system.
CPU usage is still sitting at ~35% on the router, however. Guest mode is enabled, and the router is in AP mode.
I don't think Google has fixed this yet and this firmware doesn't have the fixes. However I if the cpu is not being as taxed, it may be somewhat more resilient to the android bug
I appreciate the work Netgear is doing here. But, I really wish they would stop pushing out these releases before either a) a more drawn-out testing, and/or b) a user-driven (not auto) beta period. Just because 2.1.2.10 has some people stable doesn't mean all of us are, or especially that a new version based on that will be production ready (for autoupdate).
Personally, I went back to 2.0.0.76 due to some very unstable ping times on my LAN, which aren't nearly so bad in the older rev. Been toying with regressing further to 1.11.0.20 even.
I feel a little uncomfortable about having been implicitly enrolled in a beta test program just because I bought an Orbi.
It was my understanding that there was no automatic update to 2.1.2.10 unless manually installed, nor an auto update to 2.1.2.18 unless you'd installed 2.1.2.10. Was your kit automatically updated from 2.1.1.x?