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.
My Orbi and 2 satellites had all been previously updated manually, but still did an auto update to the new release without prompting, so the suggestion that this switches it off is not correct. I was left with a completely unusable system this morning. The information here seems to be the best advice to disable it: https://community.netgear.com/t5/Orbi/Firmware-V1-12-0-18-Discussion/td-p/1320421/page/5
I rolled back to beta V2.0.1.2, which has been rock solid for a couple of months.
NickC4555 wrote:My Orbi and 2 satellites had all been previously updated manually, but still did an auto update to the new release without prompting, so the suggestion that this switches it off is not correct. I was left with a completely unusable system this morning. The information here seems to be the best advice to disable it: https://community.netgear.com/t5/Orbi/Firmware-V1-12-0-18-Discussion/td-p/1320421/page/5
I rolled back to beta V2.0.1.2, which has been rock solid for a couple of months.
I wouldn't waste your time trying to block auto-update, unless you have a lot of time to burn. I've tried everything mentioned in this forum to block auto-update, including using dd-wrt on my R7800 (Orbi is in AP mode) and restricting access to "netgear.downloads.com" and "netgear.download.com" as well as all the telnet stuff on both the router and satellite. The dd-wrt dodge that I had high hopes for doesn't seem to have worked. When 2.1.1.16 went out, my Orbi said that there was new firmware available from Netgear, a bad sign for blocking auto-update. While I didn't wait to see if the Orbi could download it or not, I sort of assumed that the path that the Orbi uses to check for new firmware is the same path that it would use to download it. Once I find out what that path is, I can block it until Netgear changes it, but not there yet.
Sometimes it takes days for auto-update to catch up to you, but you can just assume that it will sooner or later *smile*.
Has anyone recently tried using telnet to change the nvram parameters as described it this link?
https://community.netgear.com/t5/Orbi/Firmware-V1-12-0-18-Discussion/td-p/1320421/page/5
I was going to try that to stop auto-update, but if it doesn't work, I won't waste my time.
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.