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 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.
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.
This beta firmware only fixes the issues that amit posted in bullet points all other issues are still being debugged and worked on to be fixed in upcoming betas and firmware releases.
DarrenM
DarrenM wrote:This beta firmware only fixes the issues that amit posted in bullet points all other issues are still being debugged and worked on to be fixed in upcoming betas and firmware releases.
DarrenM
Thanks Darren. When you say only fixes those issues, can I assume KRACK is also considered an "issue" (by your definition) as well, meaning the beta does not include the KRACK patch that 2.1.x.x do, correct?
For my part I think it works well, I just installed the beta version and the problem of connection to the router when we are close to the stellite is fixed.
How long have you been running it for? It would take a solid week of stability for someone to convince me to attempt to upgrade.
