NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
JMU1998
Dec 19, 2017Luminary
Orbi firmware v2.1.1.16 discussion
do we need to do nvram wipe for this 2.1.1.16 Firmware just released today? noticed it downloaded automatically.
robertcdh
Dec 25, 2017Apprentice
I'm also having random reboots since the 2.1.1.16 update.
I found this article while browsing Reddit. What are your thoughts on this?
orbirick
Dec 25, 2017Apprentice
robertcdh wrote:I'm also having random reboots since the 2.1.1.16 update.
I found this article while browsing Reddit. What are your thoughts on this?
All I can say is that I'm running Oreo (8.0) on my OnePlus3. I installed the Orbi system about 24 hours ago and upgraded to v2.1.1.16. After futzing around with a router I used as a switch and having some connectivity issues, I replaced the router with a Gb switch, disabled UPnP, enabled MU-MIMO and beamforming as well as fast routing.
The debug page shows I've been up for 13+ hours now. I've not noticed any reboots other than the ones I forced. AFAIK, the system is running normally on 2.1.1.16 for me. So far.
- ratickleDec 25, 2017Apprentice
orbirick wrote:
robertcdh wrote:I'm also having random reboots since the 2.1.1.16 update.
I found this article while browsing Reddit. What are your thoughts on this?
All I can say is that I'm running Oreo (8.0) on my OnePlus3. I installed the Orbi system about 24 hours ago and upgraded to v2.1.1.16. After futzing around with a router I used as a switch and having some connectivity issues, I replaced the router with a Gb switch, disabled UPnP, enabled MU-MIMO and beamforming as well as fast routing.
The debug page shows I've been up for 13+ hours now. I've not noticed any reboots other than the ones I forced. AFAIK, the system is running normally on 2.1.1.16 for me. So far.
I have 27 devices connected to the network, including Android, Apple, and Windows based products. None of my Android devices are running Oreo.
Four days ago I did factory resets on router and satellite and manually loaded 2.1.1.16. Disabled UPnP, but did not enable any "advanced features". Stability is much better than before the factory reset and reload, but on average I still get random self-reboots on both the router and the satellite. I have had uptimes of more than one day, but never more than a day and a half. Also had self-reboots in as little as four hours.
This morning right before the router self-rebooted, I was looking at the uptime via debug and I noticed that the CPU utilization was around 75%. This seems very high for a router where no one was using any connected devices except me and I was just reading email. A few minutes later, the router self-rebooted. So frustrating.
- orbirickDec 25, 2017Apprentice
Checking the debug page this morning (Merry Christmas!), I see one of the satellites rebooted about 4AM this morning. Otherwise, the router has been up over 21 hours and the other satellite about 9 hours since I unplugged it to install a Chromecast Ultra about midnight last night.
I'm in a 'trust but verify' mode right now.
- morrisseysbDec 25, 2017Apprentice
Nothing was connecting to my satelite. I tried turning UPNP off and fast roaming and various other things off and on. I have gone back to 2.0.0.74 and back to normal...devices are connecting to the sat again. I wanted to use Disney Circle but what's the point if half the devices in the house can't connect to the sat after that and they have very poor signal just connected to the router?