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.
FURRYe38 wrote:Thanks for letting us know results of powering the system off for a extended period of time. Seems that maybe a hour is a good point. Again, only seems to be happening on v4. Hoping that NG will get this mess fixed soon so extended power downs are not needed. At least for now it's a option to try.
Keep monitoring. Hopefully you'll be ok till next update. :smileyfrustrated:
I find it interesting the range of and type of issues everyone is experiencing and the odd workarounds that work for some and not others. There must be some other interactions going on like switches or connected devices. FWIW, I have almost always had to power cycle / rest my setup after changing the firmware - especially the RBS. And it usually takes a few tries to get things sorted out. Part of that may be getting the WAN Aggregation sync'd with the router and modem and most times I must disable the WAN Aggregation, then re-enable it after the system is up. It's also strange how "unstable" it seems right after updating firmware and how it becomes stable some time afterwards. For example, I could reboot or power cycle everything now and it will come right back up no problem, but immediately after new firmware, it takes a bit of coddling to get it working.
I agreee. Over the past year seems that Orbi AX has been getting more odd behaviors in FW and in operation. I normally just power OFF the RBS and RBR for 1 minute after FW updates I I wanted to help check everyones complaints about having to do factory resets after FW updates. Seems it worked for a while, then a reset happened and now we have to power OFF for a longer period of time. Normally i set up my RBR first, no ISP connection and get it running. Sync up the RBS. Then go for ISP connection. I usually enable LAG after I know the RBR is online and working ok. I haven't done that during initial install of the RBR.
bullm00n wrote:
FURRYe38 wrote:
Thanks for letting us know results of powering the system off for a extended period of time. Seems that maybe a hour is a good point. Again, only seems to be happening on v4. Hoping that NG will get this mess fixed soon so extended power downs are not needed. At least for now it's a option to try.
Keep monitoring. Hopefully you'll be ok till next update. :smileyfrustrated:
I find it interesting the range of and type of issues everyone is experiencing and the odd workarounds that work for some and not others. There must be some other interactions going on like switches or connected devices. FWIW, I have almost always had to power cycle / rest my setup after changing the firmware - especially the RBS. And it usually takes a few tries to get things sorted out. Part of that may be getting the WAN Aggregation sync'd with the router and modem and most times I must disable the WAN Aggregation, then re-enable it after the system is up. It's also strange how "unstable" it seems right after updating firmware and how it becomes stable some time afterwards. For example, I could reboot or power cycle everything now and it will come right back up no problem, but immediately after new firmware, it takes a bit of coddling to get it working.