NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi firmware update v2.1.4.16 availability
We’ve been monitoring issues that some customers have experienced in OrbiOS 2.1.4. In response, we’re releasing firmware that provides a permanent fix for the homekit issue along with various other f...
Dlink used to lock the saved config to a particular version of firmware so users won't restore a given backup of the config (old to new, new to old), i thought it was annoying at first, but now i think its brilliant.
on the side note, netgear should, on any firmware upgrade (or downgrade) create a soft trigger (built in) to restore to factory default after each upgrade/downgrade, but they first need to show a banner warning users to save a backup (for same compatible version of the firmware) or start from scratch for incompatible backup (based on firmware versioning).
it seems the netgear eng are not users of their own product, they probably use Asus, Meraki's, Ubi's or Cisco.
olf wrote:
Dlink used to lock the saved config to a particular version of firmware so users won't restore a given backup of the config (old to new, new to old), i thought it was annoying at first, but now i think its brilliant.
on the side note, netgear should, on any firmware upgrade (or downgrade) create a soft trigger (built in) to restore to factory default after each upgrade/downgrade, but they first need to show a banner warning users to save a backup (for same compatible version of the firmware) or start from scratch for incompatible backup (based on firmware versioning).
it seems the netgear eng are not users of their own product, they probably use Asus, Meraki's, Ubi's or Cisco.
You know, the method that I usually use is to see if the mfr. suggests resetting and manually restoring configuration in the release notes for the new version. If not, then just upgrade (or be auto-upgraded), and if problems are encountered, then do the reset procedure. A lot of times, no problems come up if a reset isn't done. When problems do come up, my go-to things to try are power-cycling first, then if that doesn't help, full factory reset and manually reconfigure.
It seems like, with the kind of problems that I read about here, that Netgear should note this in the release notes, even if a reset isn't required by the changes between versions. That if problems come up, how to reset and manually restore the configuration. I just checked and this isn't in the standard Netgear release notes...they do tell you to write down your current configuration settings before flashing, but not what to do if problems occur after flashing. Just doing this might decrease the number of support calls that they get, and save them money. And help their users *smile*.
By the way, this latest version is working well for me, no resets required this time. Although I have had to do a full factory reset or two along the way (over a year and a half of ownership). I do have the Orbi in AP mode, though, so I'm using a more limited subset of the product functionality.
This constant factory reset requirement is unacceptable.... Orbi is aimed at consumers who want a wifi system you don't always have to think about & just works. I personally have the outdoor orbi satellite & it is mounted so the back panel isn't accessible making a factory reset extremely inconvenient on this type of setup. I am glad it is helping some users but I do hope that Netgear comes up with a much better solution. Factory reset should only be used as a last troubleshooting resort.
- It isn’t to obvious if that’s what’s being required every firmware update 😂
computersteve wrote:
This constant factory reset requirement is unacceptable.... Orbi is aimed at consumers who want a wifi system you don't always have to think about & just works. I personally have the outdoor orbi satellite & it is mounted so the back panel isn't accessible making a factory reset extremely inconvenient on this type of setup. I am glad it is helping some users but I do hope that Netgear comes up with a much better solution. Factory reset should only be used as a last troubleshooting resort.
I agree...I mentioned factory reset as what I do when I have the rare problems that I've had, and power-cycling the units doesn't take care of it. That's unusual, but you won't find a router/wireless system out there where problems don't come up very occasionally, usually after an upgrade, which makes them even rarer. A reset isn't something that you have to do every day, you may never have to do one. But if problems do come up due to something bad happening while flashing a new version, or a power line surge/brownout or whatever, it is good to know about it and be okay with it. Not something that you should be doing very much, or expect to do, but it happens. If you find yourself doing that a lot, then you may have bad hardware, a misbehaving client device, etc.
I agree that factory resets should be a last resort. What no one has mentioned is that factory resets destroy customisation.
Under the Orbi router’s Attached Devices list I always name and describe each device in my household that is attached to the Orbi system. A factory reset means rebuilding this list.
I know we can backup settings, which includes attached device names, then restore the backup after a reset, but then the fear is that the restore inadvertently reintroduces the very problem that lead to the factory reset in the first place.
There must be a better way, like a warm restart. My modem/router has the ability to restart with current settings or restart with factory settings.