NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Your experience with Firmware 2.2.1.210 released as of 10/3/18
The other long thread on the new firmware is useless and has become a tech support thread. Please only post your experience after upgrading to the new firmware, good or bad. I'd like to see everyone'...
Just curious, when your v210 was applied, did you use the autoupdate feature and continue to use the system or manually load the FW and do a factory reset?
njweb wrote:
Update - I have been on this 2.2.1.210 firmware since October and my wifi connection has been rock solid. I work remotely often and use Citrix Workspace to connect to my virtual work desktop and have not suffered any disconnects in a long time (since getting Orbi firmware 2.2.1.210 in fact).
With one of the PRIOR recent firmwares (do not recall which one) I was having sporadic disconnect issues, but those issues stopped competely after getting 2.2.1.210.
I used the built-in update. I have auto-update disabled and will keep that disabled FOREVER!
Furthermore, I am completely DONE with the Netgear's "doggy doodoo" of "wipe-update-wipe-reconfigure". If they can't push an update that does NOT involve a full reset (seems to be the Netgear response to all problems)...well...they need to rethink thier strategy.
Netgear Orbi Pro needs to be "PRO".
"Pro" needs to have business class features (vLAN, etc, etc)
"Business Class" needs to have abilty to handle a software update that does not disrupt "BUSINESS" and require a full factory reset to resolve.
Happy New Year!!!
I think it's been NGs intent to have autoupate work and not have to factory reset and setup from scratch. Unfortinately, something in there FW development and update process seems to break at this point. Thus factory resets are needed in some cases to clear out prior configurations and FW settings. I've seen this on my system as well. AutoUpdate gets applied however items in the background start to not work right until I factory reset and setup from scratch. One thing I do is do a router config save to file, then if I do need a reset, I can reset then apply the saved config from file for quick setup.
Orbi has a Pro version:
https://community.netgear.com/t5/Orbi-Pro-WiFi-for-Small-Business/bd-p/en-business-orbi-pro
Something to post about if your interested in the Pro version.
Good Luck.
Flash008 wrote:
I used the built-in update. I have auto-update disabled and will keep that disabled FOREVER!
Furthermore, I am completely DONE with the Netgear's "doggy doodoo" of "wipe-update-wipe-reconfigure". If they can't push an update that does NOT involve a full reset (seems to be the Netgear response to all problems)...well...they need to rethink thier strategy.
Netgear Orbi Pro needs to be "PRO".
"Pro" needs to have business class features (vLAN, etc, etc)
"Business Class" needs to have abilty to handle a software update that does not disrupt "BUSINESS" and require a full factory reset to resolve.
Happy New Year!!!
Flash008 wrote:
I used the built-in update. I have auto-update disabled and will keep that disabled FOREVER!
Happy New Year!!!
Flash - can you please detail how you disabled auto-update in such a way that it is actually 'sticking' and not auto-updating? Myself, and several others, used the older telnet instructions and changed the three values etc, but it auto-updated anyway. Do you have a new way of doing it that seems to stick? Thanks!
Jeremyinsf wrote:
Flash - can you please detail how you disabled auto-update in such a way that it is actually 'sticking' and not auto-updating? Myself, and several others, used the older telnet instructions and changed the three values etc, but it auto-updated anyway. Do you have a new way of doing it that seems to stick? Thanks!
I'm not Flash...but there are FOUR settings that need to be adjusted:
- orbi_auto_upgrade
- auto_check_for_upgrade
- auto_update
- orbi_auto_upg
The instructions that are usually referenced omit that last item.
Even then, I had a few issues with getting the settings to stick, since the system kept wanting to start an auto-check/auto-upgrade cycle before I could make the changes. Waiting a day and trying again finally, knock wood, did the trick.