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.
This update has been absolutely terrible for me. Devices will not gracefully roam between the router and satelite. Instead, they just drop connection and usually won't automatically reconnect. iPhones rarely stay connected, even when not moving around.
I didn't even want this update. 3.2.18.233 was working perfectly for me, but the system decided to update itself. It should be the user's choice if they want to update, specifically to avoid issues like this.
You can go back to v3:
GoldenRetroGame wrote:
This update has been absolutely terrible for me. Devices will not gracefully roam between the router and satelite. Instead, they just drop connection and usually won't automatically reconnect. iPhones rarely stay connected, even when not moving around.
I didn't even want this update. 3.2.18.233 was working perfectly for me, but the system decided to update itself. It should be the user's choice if they want to update, specifically to avoid issues like this.
A complex series of workarounds to force a firmware downgrade and block automatic updates (both things that Netgear don't officially support) isn't the solution most users are looking for.
In my case, as I am using the Orbi in AP mode and my router doesn't allow individual sites to be blocked at router level, it's not even a workable solution, as the system will simply "upgrade" itself again.
Netgear needs to fix this, urgently.
Since you have a different router and your Orbi is in AP mode you CAN block the update using your other router.
FURRYe38 wrote:You can go back to v3:
That's what I've done. The downgrade did not go smooth though, as the satelite was not registering itself and simply coming up as a regular device on the network. After several resets and reflashing the firmware, it finally started working again.
Garwoofoo wrote:
The old v3 release had major issues too, specifically the DNS lookups intermittently failing when using the Orbi in router mode.
Some of us were on a beta release of v3, which fixed the DNS issue as well as other issues with that branch.
So your back on v223?
GoldenRetroGame wrote:
FURRYe38 wrote:
You can go back to v3:
That's what I've done. The downgrade did not go smooth though, as the satelite was not registering itself and simply coming up as a regular device on the network. After several resets and reflashing the firmware, it finally started working again.
