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
dsegel wrote:Unless you turn on Daisychaining, in which case it *IS* a mesh system.
Good point. I don't think that's been identified as contributing factor, though (i.e. reboots happen whether daisychain is enabled or not).
I don't have Android in my eco-system at all, and I was still getting tons of router/satellite reboots and disconnects, so while Android does contribute, Orbi still crashes without that in the mix.
That said, I've been up without a reboot or disconnect since Saturday morning on the new beta.
The changes in my environ were the beta software and not hardwiring much to the the Orbi's themselves, where before every port was full.
So right now:
AP Mode
Beta Software
1 printer plugged into the router
1 Hue bridge plugged into the satellite
Beamforming and MU-MIMO left on
Fastroaming off
Everything has been solid, which it hadn't been for months. Today is my last day to return the eero pro (which was flawless) so I think I will in order to get $500 back.
Here's hoping it stays solid.
First, Eero's forum isn't a very active one, so that doesnt make it a really good reference point. Second, I HAVE gotten my Eero 2nd generations to reboot with a Pixel XL 2. Third, Eero's techsupport, if you were to actually CONTYACT them, would confirm what Google said, as did the Linksys Velop Team and the Amplifi tech support team. I have all three systems plus Orbi, and ALL reboot randomly when my Pixel is connected. The reboots vanish when the Pixel is NOT conneted, which means Pixel and Android are at least contributing factors.
Two things I did on my Orbi which appear to have greatly reduced the random reboots was disabling daisy chain in the firmware and then going into the debug menu and enabling Jumbo Frame support for traffic between LAN ports. Then I rebooted my Orbi. CPU load has since held steady BELOW 10% and memory usage below 200 MB for more than 16 hours now, with NO random reboots or kernel panics by Orbi. Connected Pixel, and the Orbi rebooted within 15 moinutes of Pixel connecting. No Pixel, no reboots.
the eero forum isnt active because there arent as many issues as there are with the Orbi; people only post to complain, not compliment
wase4711 wrote:the eero forum isnt active because there arent as many issues as there are with the Orbi; people only post to complain, not compliment
No, most don't use the Eero forum because most Eero users DON'T KNOW IT EXISTS! It also isn't monitored by their tech support team; if you read the posts there, you'd see that mentioned many times by their SINGLE employee who moderates the page. Eero also never really answers any questions posed there by customers either. Anyone with issues is told to CALL THEIR TECHICAL SUPPORT. I've used Eero since it first came out, and it is not perfect, nor is any networking device. I've been on their forum since that was launched too, and I would not recommend it to anyone looking for help.
Oh, and you can' just go by post titles on Eero's forum to tell if Android issues are there or not, you have to actually read them; thee are more than 300 posts under various titles about users having issues with Android and Eero, and none mention Android in the post titles.
An article mentioning Android 8 causing wifi issues, and mentioning that Google is working on the issue. Samsung, LG, Motorola, and LG all have have similar complaints on their forums.
The issue seems to be quite widespread, with reports on Google's Pixel Phone Help forum , reddit , and Netgear's forums . Most accounts of problems seem to be coming from people using Netgear's Orbi routers, but other reports are trickling in from those with other mesh systems, including routers by Cisco and eero, with a small number people using non-mesh access points affected as well.
https://hk.saowen.com/a/3850999a52d59ad1b0ac031e5e28204a04a70287a131c8f909e370643bb2a674
Here is the original article link without the dodgy saowen.com links:
That said, I've had 0 reboot issues on my RBK50 kit and my Pixel XL running 8.0 or 8.1
- I found a few article this morning where it looks as if there is a problem with the Google Cast protocol and android devices waking from sleep mode across multiple router vendors. The longer a device is in sleep, the more discovery packets it sends when it wakes up, into the 100,000s.
Here is the article that I found that seems to tie it together: https://www.myce.com/news/confirmed-issue-google-cast-causes-temporarily-wifi-drops-around-world-834....
It looks like there might be other issues with Google cast devices and MDNS packets as well like: http://www.androidpolice.com/2018/01/12/google-home-max-appears-killing-wifi-networks/.
I do have a Chromecast on my network, but I so I might unbox my Orbi again and see if that is the culprit... Anyone aware if a new Beta is going to be released so we can test it if better than the current ?
I had one of these Google devices on my network in November with no noticeable reboots. However, I added 3 more devices on my network at about the time the reboots became a problem. TP-Link resolved the issue with a router firmware update. Netgear, will you please look into this?
I'm going to see if there's a workaround other than removing the devices from the network.
Thanks newbeb!
