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
I had issues even with the beta. I've rolled back to 1.x acted having issues with .74. Admittedly I did not fully power cycle my whole system when I rolled back to .74 although I don't think that was the cause of the reboots. However I was having issues where my device would show connected no internet.
Anyhow there is now peace in my family with the following changes I made. Should not have to do this with orbi though.
I'm not sure if only one of these was an issue or cumulative effect.
Telnet disable auto update
Rollback router and satellite to 1.11.0 .20
Reset nvram
Reset router and satellite to default with Paperclip then turn off and unplug
Turn off cable modem and switch and unplug
Wait a minute or two
Turn modem and switch back on
Turn satellite and router back on
Setup as new system
I used my original network name and password so my devices would reconnect without reconfiguring. This was a big deal because I have bows and ring doorbell and those are a process to entered WiFi username and passwords
My system has been up over 24 hours with 0 reboots. Additionally I can tell that the Wi-Fi connections to my devices have not been dropped.
For the time being I will stick with this firmware. It meets my needs. I reckon I'm slightly vulnerable to the krack exploit
I will monitor this forum to see when a working firmware update comes out
Anyhow there is now peace in my family with the following changes I made. Should not have to do this with orbi though.
I'm not sure if only one of these was an issue or cumulative effect.
Telnet disable auto update
Rollback router and satellite to 1.11.0 .20
Reset nvram
Reset router and satellite to default with Paperclip then turn off and unplug
Turn off cable modem and switch and unplug
Wait a minute or two
Turn modem and switch back on
Turn satellite and router back on
Setup as new system
I used my original network name and password so my devices would reconnect without reconfiguring. This was a big deal because I have bows and ring doorbell and those are a process to entered WiFi username and passwords
My system has been up over 24 hours with 0 reboots. Additionally I can tell that the Wi-Fi connections to my devices have not been dropped.
For the time being I will stick with this firmware. It meets my needs. I reckon I'm slightly vulnerable to the krack exploit
I will monitor this forum to see when a working firmware update comes out
FWIW I have Android 8.1 (Pixel XL2), 2 google home and a chromecast on 1.11.0 .20 with no current issues. My perception is if Android OS and home devices are causing issues it's still related to 2.x firmware