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
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...
My mileage varied...
Came back home from work the next day to family complaints that wifi wasn't working. Examined system and found the following symptoms:
1. Both satellites were now showing up as satelllites rather than as attached devices.
2. Internet connectivity was extremely slow and unreliable. As an example, would take several minutes to load the google home page and would fail to load even that perhaps half the time. Same applied to any website. This was true for computers connected to Orbi by WiFi and for computers connected to Orbi by ethernet.
3. Could not print wirelessly to wifi printer. Succeeded in printing only after connecting both computer and printer to orbi router via ethernet.
That third point convinced me it was my internal network having problems rather than any problem with my broadband connection. Rebooted a few things without success. Then reverted to 2.1.1.16 and performance immediately returned to normal.
It's been my experience that it takes a long time for all devices to properly display in the attached device screen. As an example, I reverted the firmware last night and as of this morning 16 of my ~30 network devices are showing up in the display with the satellites showing up as attached devices. Everything seems to work regardless of display, so I've never worried about it much. As mentioned in prior post after the 2.1.1 upgrade my satellites initially showed up in the attached device section of the web display and my network performance was fine. I speculate that my network performance problems began some hours later when the satellites registered as satellites rather than attached devices.
Well, my satellite did show up as one right from the start, but after hooking it up to the LAN and thus creating a networked backhaul, the devices list was just nonsense, as it reports all devices as being located on the router, which may make kind of sense, depending on how the MACs are matched to the router or sat.
The router can of course see all the MACs from the wireliess clients on it's own LAN interface, and each MAC would be needed to be examined, if it also is present or local to the bridge on any satellite. Other than that, my combo has been solid for two days, no glitches, no reboots… however, no Android devices for that matter, so I can't comment on that issue. I will have to grab a Android device from the office tomorrow and see, if it crashes the router, if it connects to the wifi. Any particular version of Android needed to force a crash?
I have an Android v7.x and and Android v8.x that both seem to cause the router to reboot after I wake them. Because both devices are affected, I don't think the version of Android is the real cause. Instead, I think it might have something to do with a Wifi update to Android possibly to fix the KRACK vulnerability.
robertcdh wrote:I have an Android v7.x and and Android v8.x that both seem to cause the router to reboot after I wake them. Because both devices are affected, I don't think the version of Android is the real cause. Instead, I think it might have something to do with a Wifi update to Android possibly to fix the KRACK vulnerability.
I have 6 android devices, 2 Samsung 7 phones with 7.01 and 4 tablets running 7.01 and none of them no matter what reset my router or satellite and they have never acted up at any time.
