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
Cotedan
Jan 07, 2018Apprentice
Didn’t have any issues with any Mac devices either. Worked perfectly with 3 Orbis wired.
Nest cams are more stable under the Orbi 2.1.2.10 beta. Where the problem lies, however, is the main router itself - I had random disconnects that killed the entire home network of 45 devices. Thus going back to Google Wifi. Will be trying Eero Pro 3 pack wired in coming days.
fitsnugly
Jan 07, 2018Star
DarrenM Do you have any insights into the firmware file system and whether it includes something like kdump or linux-crashdump to grab kernel panic crash dumps? I poked around via telnet and could not see anything on my end. I looked at the sysctl.conf and such for any clues but alas... It's going to be difficult for us to help diagnose on our end (and help your end fix these issues) without crash dump tools.