NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
AmitR
Jan 04, 2018NETGEAR Employee Retired
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...
- Jan 17, 2018
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
rce3
Jan 08, 2018Guide
My setup is one RBR50 and two RBS50 all running in AP mode. Network has been stable and working fine except that satellites show up in attached device area of the router webpage rather than the satellite section. I am able to confirm that satellites are working and have devices connecting to them by visiting the satellite webpages and viewing the connected devices.
Today I updated firmware to v2.1.2.10 by updating satellites first and then router.
Immediately after upate my wifi network stopped working. It appeared that the router decided to set up a new network at 10.0.0.1 rather than continue to operate on the 192.168.x.x network I am running. Multiple reboots of multiple components eventually sovled the problem, can't say which action made the difference.
Network now appears to be operating normally, but satellites are still showing up as attached devices rather than as satellites. (During the update process one satellite showed up for a while in the "connected satellite" section with a "poor connection" warning, but it has stabilized to showing up as an attached device.) It also appears that none of the devices connected to the satellites are showing up on the attached device list.
Your mileage may vary...