NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
How to disable auto-update
I prefer to update manually, is there a way to turn that feature off?
Yes I saw many threads on this and never saw anyone that I coould conclude got it to work. Did you by chance also add this option found on page 7 of this thread as well - "orbi_auto_upg=0".
Netgear seems to be determined to lose customers is all I can see, or they just do not care. They act liek these are just beta test systems and have no consideration for their customers. These are very expensive systems and they seem incapable of testing even basic functions. It is like they only test the new features they are deploying and break the stable part of the system. In any case, even thorough testing can't catch every problem on every configuration which is why they should allow the CUSTOMERS WHO OWN THE PRODUCT upgrade and the time of their choosing. If they have urgent security systems, they can be deployed seperately. That is what is done in the business world. I can assure you, our business does not allow vendors to just drop their software in at the time of their choosing. If people are novies and not sure allow them to auto update or allow us to NOT auto update. In any case, I am thinking of just selling mine off in piece parts and going back to my Apple router until I can find a another solution, possibly Linksys. It is a shame as this system works really well once you get it tweaked to your services you are running on it - at least until the next Netgear Seagull droppings come in.
You could contact NG support and ask about there Beta FW if avaiable. Theres been some users to acquire this and has worked for them.
Worth a try before you give up.
My system is working fine for me.
Boomer_1wrote:Yes I saw many threads on this and never saw anyone that I coould conclude got it to work. Did you by chance also add this option found on page 7 of this thread as well - "orbi_auto_upg=0".
Netgear seems to be determined to lose customers is all I can see, or they just do not care. They act liek these are just beta test systems and have no consideration for their customers. These are very expensive systems and they seem incapable of testing even basic functions. It is like they only test the new features they are deploying and break the stable part of the system. In any case, even thorough testing can't catch every problem on every configuration which is why they should allow the CUSTOMERS WHO OWN THE PRODUCT upgrade and the time of their choosing. If they have urgent security systems, they can be deployed seperately. That is what is done in the business world. I can assure you, our business does not allow vendors to just drop their software in at the time of their choosing. If people are novies and not sure allow them to auto update or allow us to NOT auto update. In any case, I am thinking of just selling mine off in piece parts and going back to my Apple router until I can find a another solution, possibly Linksys. It is a shame as this system works really well once you get it tweaked to your services you are running on it - at least until the next Netgear Seagull droppings come in.
How do you go about doing that? I am out of the 90 day period and I am not going to pay for support due to their total lack of support.
Have to get on the phone with them from what others have said.
Ok Thanks.
tried one more time to downgrade to older vesrion,done all on telnet,but still uppgrade itself to V2.0.1.4,netagear please make options to turn of auto uppdate ;)
Try deleting cron job, but it would only work only until reboot.
Are you referring to the /tmp/etc/crontabs/root or /var/spool/cron/crontabs/root. It looks like they rebuild it in the S10boot file on each startup. It looks to me like the /var/spool/cron/crontabs/root is the master. Perhaps instead of deleting it just comment out that line.
However, one might consider if you aren't disrupted to just shutoff your internetlink for a few minutes before 3:49AM and a few minutes after, unless it initiates a some sort of retry.
Primary is /tmp/etc/crontabs, /var/spool/cron/crontabs is symlink to this directory.
crond is started as:
crond -c /tmp/etc/crontabs -T GMT-0
So
crontab -c /tmp/etc/crontabs -d root
could help
Thanks. Yes I saw that. The cron is running against the tmp/cro fn file. I was looking into just commenting out the line with the firmware in it and leaviing the one that emails the logs. That seems to work. However it still gets rebuilt on reboot. It does not get rebuilt from either /var/spool/cron/crontabs/root or /rom/var/spool/cron/crontabs/root. It all gets corrected on a reboot. It looks like they are doing this in the /etc/init.d/boot file. They probably have a hidden slice that it is rebuilt from on reboot or embed it in a command. It could be a simple one line command embedded in an executable to put it in. I am going to look a bit further. Worse case I might just try blocking the internet connection for a few minutes and see if it retrys.
I have just one line in there, thats why I suggested to delete it.
The read-only original file is in /rom/var/spool/cron/crontabs/root
17 04 * * * streamboost update_fmn; streamboost auto_upload; streamboost auto_update && streamboost restart
What we are changing is just overlay. When Orbi boots, / gets restored from /rom.Changing /rom permanently is more complicated and risky for people. So don't do it.
Thanks. I was not going into it any further than the other 2 files. The /rom file may clash with something they are updating so I will either just change the entry you mentioned or go the route of blocking the the connection at the time of execution. Commenting out that enttry should work as well as long as you don't reboot.
