NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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.
RogerSC wrote:I wouldn't waste your time trying to block auto-update, unless you have a lot of time to burn.
The Telnet fix previously referred to does work, although I also changed the auto update settings using the same method in each of my satellites too. When you go into the admin console it says "A new firmware upgrade is available. Click here to get it.", but it doesn't install it automatically. Not so far anyway.
I would urge anyone who is having these problems to ask support for beta version 2.0.1.2, it was provided to me after all the problems with 2.0.0.74 and has been perfect for 2 months. It's the only one that has been able to daisy chain at 5Ghz over the distance between my satellites and it never drops the connection. 2.1.1.16 uses 2.4Ghz for backhaul over the same distance loses its connection every few minutes.
I wish I'd read this before updating from 2.0.0.74 to 2.1.1.16. 2.0.0.74 had been solid for me (with mesh networking disabled). So, I merrily (it is Christmas after all) decided to update. Since then, half the devices (mostly Android) show Wifi connectivity but no Internet. I haven't have a chance to investigate yet but I believe that it is devides attaching to the Sat that can't reach the Internet. Devices close to the main Router can, but, as I say, I haven't had time to check that this is a scientific assertion.
If this were opensource, I'd be happy to investigate. But, this is a commercial offering that I paid a goodly sum for. A reasonable person (I'm from the UK where "reasonable person" has legal meaning) would expect it just "to work" and certainly not faff for hours doing Netgear's system testing and debugging for them. I have all the skills to do these things, but I gave Netgear a large sum of money so that I don't have to.
A disappointed Scrooge.
mossywell wrote:I wish I'd read this before updating from 2.0.0.74 to 2.1.1.16. 2.0.0.74 had been solid for me (with mesh networking disabled). So, I merrily (it is Christmas after all) decided to update.
Unfortunately, unless you jumped through the hoops described elsewhere in this topic, you can't stop it updating. I strongly recommend that you do, though, and save a version of the firmware that works for you for future restores. There are so many variables that there doesn't seem to be a one size fits all release.
got the 2.1.1.1.6 update early this morning via auto-pilot.
When I first tried to open the SlingTV device it said no internet. That turned out to be not true. After a few minutes it was working fine.
The only other thing I've noticed is the wifi signal icon on my laptop seems to fluctulate more than before. Still connected...just noticible. Laptop has not moved.
Currenting experiencing the longest uptime without a self-reboot in the five day that I have owned my Orbi. Two days ago I manually forced the router and the satellite back to 2.0.0.74. I did a factory reset (via a paperclip) on both the router and the satellite as the first step. I did NOT use Telnet to clear NVRAM. The only configuration changes I made was to turn OFF daisy chaining and to turn OFF UPnP. The system ran for 15 hours without a self-reboot on 2.0.0.74 AND all my devices connected to the satellite showed up on the satellite's list.
Yesterday, the Orbi's did a auto-update to 2.1.1.16. (They skipped 2.1.1.12.) That auto-update is what ended the 15 hours of seeming perfect operation. Today, my uptime is over 19 hours and the system seems to be working well, EXCEPT that connected devices are being shown on the satellite's list. Finger's crossed that I make it 24 hours without a self-reboot!
I've attached the statistics page from the router's advanced/internet port page. The statistics show LAN1, LAN2, and LAN3. LAN1 and LAN2 have the same 19 hour uptime, but LAN3 has only 7 hour uptime. I'm assuming LAN1 is 2.4gHz, LAN2 is 5gHz, and LAN3 is the 5gHz backhaul channel. Does that seem correct to you guys?
