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...
Did anyone else get an private message from NetGear support to help work with their L2 Support team? It was from DarrynM
I got a PM to work with support last week. They contacted me and the tech tried replicating the problem on their lab system (reboot loop on wired backhaul). They suggested a factory reset which has fixed my problem.
So it’s just an attempt to fix your problem, not an attempt by the developers to understand what is going on.
I’d recommend doing a factory reset (not that painful) and if problems persist, respond to the PM that you want to work with them.
So it’s just an attempt to fix your problem, not an attempt by the developers to understand what is going on.
I’d recommend doing a factory reset (not that painful) and if problems persist, respond to the PM that you want to work with them.
Glad the factory reset helped with yours. Been asking users to do this. Ya I know it's pain however seems that each FW that gets released is different and for some reason the configuration persistence is getting in the way or not being correctly re-applied after a auto update. I've posted this behavior to NG. Not sure why they can't seem to get a seemless update to work with out users having to resort to a full factory reset and set up from scratch. Hopefully they will figure it out. Ive had no issues after donig a factory reset and setting up from scratch. Then do a save configuration to file. Keep this for the current version of FW that it was saved for.
jeblis wrote:
I got a PM to work with support last week. They contacted me and the tech tried replicating the problem on their lab system (reboot loop on wired backhaul). They suggested a factory reset which has fixed my problem.
So it’s just an attempt to fix your problem, not an attempt by the developers to understand what is going on.
I’d recommend doing a factory reset (not that painful) and if problems persist, respond to the PM that you want to work with them.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.
