NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Armor is a Bummer
Netgear... I've loved your products for years, but you should BE ASHAMED to have released Netgear Armor in this state. I am an executive for a fortune 5 company and have been responsible for the deve...
Hi again BinkyTheClown .
I'm not sure the a factory reset will do much more than just disabling Armor with the app. As long as you keep your Orbi software up-to-date, I'm afraid that Netgear Armor, hereafter, will always be on the router, in either Enabled or Disabled state. So yes, a factory reset will work momentarily; but as soon as you bring the Orbi software up-to-date (and it wouldn't be wise to do otherwise), Armor will be right back in, awaiting activation.
Thanks for the reply. So my home automation is no longer working (e.g. IFTTT recipies controlling Hue lighting) and I'm getting DOS attack notices in my router log. This is all new shortly after enabling Armor and continues after disabling Armor. It took 15 minutes to setup Armor now it is taking 15+ days to recover from that mistake.
So, I downgraded my firmware from 2.3.1.60 to 2.3.1.44
- Router Internet Status is now Good vs. Waiting
- Home automation is now working again
- No more DOS attack messages in log
Not sure if the downgrade fully disabled Armor or if the problem was related to 2.3.1.60. Either way, the router appears to be operating properly now. I'll wait before attempting an upgrade and will post results here in the next day or so.
This is exactly why I havent enabled it even if its just to evaluate the service. Sorry you had these issues. My guess is the .60 has nothing to do with it and more related to the armor software not completely uninstalling.
Agreed. However, apart from factory resetting my router and reconfiguring, I opted to see if a firmware downgrade would at least get me to some sort of stable state. I didn't want to save config and restore as I assumed that would re-enable Armor. Everything seems to be stable now so I will attempt a firmware upgrade back to .60 in the next few days and see if everything is still good.