NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Disabling Auto Update (Force Update) firmware version 2.7.3.22 for Orbi 3000 (RBR, RBS and RBK 50)
Hi,
It seems like Netgear now forces a new EULA requiring Auto Firmware Upgrade for all Orbi Routers, unfortunately for our RBR/S/K 50, the new 2.7.3.22 is buggy, and sometimes drop connections between satellite and router out of the blue.
I have followed this instruction many times: https://community.netgear.com/t5/Orbi/Disable-auto-update-of-orbi-firmware-additional-steps-needed/td-p/1575772 , by the way you need to downgrade to stable firmware (for me it's 2.3.5.34) first, to enable Telnet portion.
But after a while it still gets updated. So i am trying a new trick, basically using DNS to block, see the addition to /etc/hosts below.
Does anyone have same issues ?
127.0.0.1 localhost update.netgear.com updates1.netgear.com updates2.netgear.com updates3.netgear.com http.fw.updates1.netgear.com readycloud.netgear.com peernetwork.netgear.com readyshare.netgear.com
And by the way, do above steps on every devices (routers and satellites too).
Remember after enable root, you can telnet using 'root' account without password. Highly advice, to change the root password immediately. Also once you are done, please ensure you disable the telnet access.
Hopefully this works, any ideas, please let me know.
17 Replies
I believe telnet is not supported on v22 FW, you'll need to go back to v104 to get telnet then make changes to block FW updates.
Has a factory reset and set up from scratch after last FW update?
Yes, telnet has been disabled, that's why i mention to downgrade first, before attempting to perform the steps.
The good news is *Nix based, so all the fun stuffs we can do in *Nix, are very applicable....
I didn't do factory reset, but i did backup and restore....
I had to cold reboot, as it wouldn't pickup DHCP from the ISP until i did that....
The EULA has new wording where it required Auto Update
Might try a factory reset next time you update FW IF a problem appears after FW is updated. Seen odd things after a FW update and sometimes, just a reset and setup from scratch is needed.
Good luck.
And by the way, do above steps on every devices (routers and satellites too).
Remember after enable root, you can telnet using 'root' account without password. Highly advice, to change the root password immediately. Also once you are done, please ensure you disable the telnet access.
Hopefully this works, any ideas, please let me know.
