NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Blocking auto update
Anyone successfully able to block auto upgrade to .18? Downgraded to .74 fw. Block ftp and auto_upg flag to 0 in the config. Today it auto upgraded back to latest .18 code. It is piece of **bleep*...
Why come on here to whine about it? Just return it and get on with your life. Geez.
wrote:Why come on here to whine about it? Just return it and get on with your life. Geez.
You seem to be the one spamming everyone's posts with your whining.
Civility please, all.
My experience, the Telnet method doesn't always work (maybe it sometimes works).
Current thing I'm using is an upstream firewall block - since my Orbi is running in AP mode, I've added a couple of rules to my upstream Linux router/firewall to reject all traffic initiated by the Orbi's IP addresses. Set a DHCP static lease to set the Orbi's IP addresses. When I do a firmware check on the router, all it can say is "service unavailable."
Wish there was an easier way, but I don't think so. The block doesn't affect LAN traffic, only the Orbi's ability to get to the Internet at all.
FWIW, I have also been testing alternatives to Orbi. Velop, Eero. Those both have their own set of problems...
wrote:Civility please, all.
My experience, the Telnet method doesn't always work (maybe it sometimes works).
Current thing I'm using is an upstream firewall block - since my Orbi is running in AP mode, I've added a couple of rules to my upstream Linux router/firewall to reject all traffic initiated by the Orbi's IP addresses. Set a DHCP static lease to set the Orbi's IP addresses. When I do a firmware check on the router, all it can say is "service unavailable."
Wish there was an easier way, but I don't think so. The block doesn't affect LAN traffic, only the Orbi's ability to get to the Internet at all.
FWIW, I have also been testing alternatives to Orbi. Velop, Eero. Those both have their own set of problems...
I have checkpoint fw as upstream router/firewall. I added ACL to block all Orbi->FTP WAN traffic. This doesn’t work for fw autoupdate. I can see in the firewall log. Orbi router is making call to AWS IP’s on FTP ports and TCP 8883 port. Then making another call on HTTPS to download firmware.
I haven’t added BLOCK All from Orbi->WAN traffic.
wrote:Civility please, all.
My experience, the Telnet method doesn't always work (maybe it sometimes works).
Current thing I'm using is an upstream firewall block - since my Orbi is running in AP mode, I've added a couple of rules to my upstream Linux router/firewall to reject all traffic initiated by the Orbi's IP addresses. Set a DHCP static lease to set the Orbi's IP addresses. When I do a firmware check on the router, all it can say is "service unavailable."
Wish there was an easier way, but I don't think so. The block doesn't affect LAN traffic, only the Orbi's ability to get to the Internet at all.
FWIW, I have also been testing alternatives to Orbi. Velop, Eero. Those both have their own set of problems...
Block ALL from Orbi Router and Satellite works. Thanks mate!
Hello Everyone
We have a update about the 2.1 firmware you can check it out here
https://community.netgear.com/t5/Orbi/OrbiOS-MR-2-1-issues/m-p/1506307#M23649
DarrenM
wrote:
wrote:Why come on here to whine about it? Just return it and get on with your life. Geez.
You seem to be the one spamming everyone's posts with your whining.
He is a troll. Searched all his posts (tsig). Spamming everyone with the same message as above.
Once again, we need everyone to vote for this:
OK, but click the link below and then vote for the feature request (rather than just kudo the post). Thanks :-)
