NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
New Online Update 4.6.3.16 (RBR850/RBS850)
Just did a downgrade from 4.6.3.9 to 3.2.18.1, factory resetted and I see Netgear are pushing an update automatically to 4.6.3.16. (see attached screenshot) This firmware is not available as an o...
FURRYe38 wrote:v3.2.11.2 was last version with telnet in the debug.htm UI.
jayeshm wrote:Thanks.
I will throw it up in my guest room and see how it holds up for a few days.
Just for checking, if one has to stick with a 3.xx firmware which one do you personally recommend?
Firstly thanks for all the help furry. You have been patiently helping everyone here, and while i was being sarcastic earlier, your help is much appreciated.
Using PFsense i threw up on an old nuc, i was able to block all updates and manually shift to 3.2.18xx which is the last v3 update. So far it seems to work. Taking your advice i reset them entirely, kept them off for half a day, and then plugged them back in and added them back. I think one of my satellites is a bit wonky, since it oddly loses connection once in a while, but the rest of them seem to be holding up fine.
I have been able to successfully block updates via pfsense, since whenever i check via firmware updates manually, it gives a connection error. I looked up all the names suggested here in the various threads and added all of them to a small blocklist.
If the problem if following the RBS then there maybe a fault in the RBS that v4 is revealing as well. If the other RBS works, then this would not be a FW issue.
Only site you need to block if you revert back to v3 is devcom.up.netgear.com 13.225.0.117 <this one is only needed to block Orbi AX.
I found that blocking other addresses seems to cause the Orbi AX system to stop working and gives a front PINK LED indication.
Thanks @ FURRYe38, You were dead on about having the update1.netgear.com addresses in the rule. When I put the 3.2.18.1 firmware back on and rebooted, I got the pink light. I did the factory reset, went throught the setup process again, and got hung up connecting to the Internet. I removed the update1.netgear.com address and it instantly connected! I am praying it doesn't auto-update with only the devcom.up.netgear.com & 13.225.0.117 address blocked. Everything is back to my preferences now....speed test works and both satellites are wired with consistantcy between the app and the web page. I am only limiting doing another firmware upgrade if there is only a substantial performance increase promised. Thanks again @ FURRYe38 for the help!