Disabling Auto Update (Force Update) firmware version 2.7.3.22 for Orbi 3000 (RBR, RBS and RBK 50)

Try putting on a power plug with a timer built in that offers scheduling. 

---

mbreksop wrote:

Btw, Netgear figured out a way to override my changes, and this morning it came back forced upgraded to 2.7.3.22 again....

The real problem is a random drop connection during heavy load, anywhere from few seconds to a minute or so.

Is there any way to schedule a reboot via cronjob or something on downtime (like Friday Midnight or something) ?

---

As I read through this post, it appears to me that there are several topics mixed together:

• The newest firmware, V2.3.7.22, does not perform correctly.  It randomly drops connection during heavy load.
  It is difficult to diagnose a problem that occurs randomly.  If "heavy load" is definitely the cause, then it should be fairly simple to replicate the issue on demand by generating the required load.
• Attempts to address the issue by manually installing previous firmware are frustrated by the Orbi auto-updating itself to V2.7.3.22.
• There is a desire to force the Orbi to reboot at specified times.

One thing is pretty clear: Any attempt to block the Orbi from auto-updating by modifying parameters through the telnet command line will be erased the next time the Orbi reboots when the entire contents of working memory are replaced by the factory image.  The technique I favor, (which is simply replacing the root file firmware_version with a bigger than possible number) will fail on reboot. So will messing around with the hosts file or setting any parameters.

If a scheduled reboot is intended to address problems with V2.7.3.22 by rebooting the router, then using a timer is the answer. A chron job will disappear upon the first reboot, as will telnet access.  A WiFi smart plug stores the schedule on the plug itself.  (I have tested this.)  It could be told to turn the power off at 1:00AM on Friday and back on at 1:02AM on Friday, and it will do so.  Yes, it will lose WiFi for a couple of minutes, but it will do what it is supposed to do.

If the goal is to absolutely, positively, "no failures" prevent auto-update, then the only solution is to connect the Orbi to another router and use that router to block those Netgear web sites.

It is not clear to me when Netgear's EULA first mentioned allowing Netgear to update firmware without notice.  3-4 years ago, Netgear regularly 'pushed' firmware updates to Orbi and appeared to pause the practice after angry reactions from users.  The only way to check that would be to deliberately load some old firmware and look very closely at the EULA.