NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Does anyone know what actually triggers an automatic update?
Title says it all.
2 Replies
So, I did an experiment. My system had been up fo 91 days (time since I manually uodated to the x.18 software.) In all that uptime the router never had to be rebooted. However one of my two satellites had to be powered off and on at least weekly, and I also saw momentarily drop outs of the WAN every day or two. I don't know if the Dropouts were due to Orbi or my ISP, but they never affected the system's uptime.
When the last release was announced, I logged into the web browser several times a day to see if Orbi had learned about it on its own. It never did. After a few days I told Orbi to check for new firmware. It did and told me about the new release and asked if I wanted to update. I logged out without replying and waited two days to see it would auto update on its own. It did not. Finally, today, I told it to Update All which it did and in about five minutes I was running on the new firmware.
Because I've been hearing about updates being 'pushed' to the Orbi, I was initially under the impression that somehow Netgear knew the whereabouts of my Orbi and could magically push updates to it. Then, after thinking about it and realizing how unreasonable that would be, I decided the request for an auto update must be initiated from the Orbi itself - either from me telling it to do so or else maybe when the system reboots on its own on or because the user manually restarted it. Maybe when others have seen their system 'auto update' it was because their system failed and rebooted itself and pulled down the update on its own in the process.
Mayhugh1 wrote:
So, I did an experiment. My system had been up fo 91 days (time since I manually uodated to the x.18 software.) In all that uptime the router never had to be rebooted. However one of my two satellites had to be powered off and on at least weekly, and I also saw momentarily drop outs of the WAN every day or two. I don't know if the Dropouts were due to Orbi or my ISP, but they never affected the system's uptime.
When the last release was announced, I logged into the web browser several times a day to see if Orbi had learned about it on its own. It never did. After a few days I told Orbi to check for new firmware. It did and told me about the new release and asked if I wanted to update. I logged out without replying and waited two days to see it would auto update on its own. It did not. Finally, today, I told it to Update All which it did and in about five minutes I was running on the new firmware.
Because I've been hearing about updates being 'pushed' to the Orbi, I was initially under the impression that somehow Netgear knew the whereabouts of my Orbi and could magically push updates to it. Then, after thinking about it and realizing how unreasonable that would be, I decided the request for an auto update must be initiated from the Orbi itself - either from me telling it to do so or else maybe when the system reboots on its own on or because the user manually restarted it. Maybe when others have seen their system 'auto update' it was because their system failed and rebooted itself and pulled down the update on its own in the process.
I have been wondering the same thing. I have 2.1.3.4 that was manually installed to my RBK53 when it was released as beta a while ago. About 3 days ago, I got notification of new firmware 2.1.4.10 in the web interface and also in the app. I did not choose to install the new firmware and it has stayed at 2.1.3.4 after at least 2 overnights. It is still at 2.1.3.4.
My theory is one of the following 3 has happened.
(1) my last manual installation of firmware stopped the auto update life cycle
(2) the designated "beta" status of the last firmware lives outside of the auto update life cycle
(3) Netgear has proactively turned off auto pushing out new firmware from their end due to people's complaints