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.
Had issues with the satellite after the update.
It looks like it did not manage to sync correctly post update.
Tried removing and resetting the satellite, even tried rolling back to v3 which did not last very long since I couldn't block it from updating again - using it in router mode, couldnt telnet in (no option in the debug menu anymore, putty gives me a connection refused error), blocking the update sites in the setting does not do anything really.
Being sick of looking of solutions to try get the downgrade to stick, I tried getting the new firmware to work for me via the usual power cycle + factory reset + sync
At one point, somehow the sync ended up wonky and the wireless password did not manage to get synced - I had to use the password to the default SSID to log into my network.
Kept trying and somehow it finally managed to get going by manually syncing it while having the units side by side sans cable connection to the satellite.
Plugging in the LAN cable to the satellite somehow screwed something up for me.
Even after it synced, once I plugged the cable in, the ip address resolution stopped working.
Keeping it wireless at the moment, though backhaul status remains as poor on the web console despite the satellite itself showing a solid blue when it connected (yes it shows that its a 5G connection).
I'm gonna try plugging in the cable again later when no one else is using the internet, hopefully its just my impatience that the wired connection does not work
I still wish netgear just lets consumers disable the auto update esp when most have to work from home now, any disruption to the internet is so painful.
Its rubbish for such an expensive system to be so limited and disruptive.
Safe to say I doubt I would ever opt for another netgear wifi system while this policy remains unchanged (waiting on more wifi 6e products before a switch but if such issues continue, I might just be forced to jump the gun).
Try downgrading back to v3 on the RBS first then RBR lastly then follow the link to block using telnet:
https://community.netgear.com/t5/Orbi-WiFi-6/RBK750-Series-Firmware-Update-v4-6-3-7/m-p/2130584#M18586
https://community.netgear.com/t5/Orbi-AX/RBK750-Series-Firmware-Update-v4-6-3-7/m-p/2131307/highlight/true#M18670
frostyfly wrote:
Had issues with the satellite after the update.
It looks like it did not manage to sync correctly post update.
Tried removing and resetting the satellite, even tried rolling back to v3 which did not last very long since I couldn't block it from updating again - using it in router mode, couldnt telnet in (no option in the debug menu anymore, putty gives me a connection refused error), blocking the update sites in the setting does not do anything really.
Being sick of looking of solutions to try get the downgrade to stick, I tried getting the new firmware to work for me via the usual power cycle + factory reset + sync
At one point, somehow the sync ended up wonky and the wireless password did not manage to get synced - I had to use the password to the default SSID to log into my network.
Kept trying and somehow it finally managed to get going by manually syncing it while having the units side by side sans cable connection to the satellite.
Plugging in the LAN cable to the satellite somehow screwed something up for me.
Even after it synced, once I plugged the cable in, the ip address resolution stopped working.
Keeping it wireless at the moment, though backhaul status remains as poor on the web console despite the satellite itself showing a solid blue when it connected (yes it shows that its a 5G connection).
I'm gonna try plugging in the cable again later when no one else is using the internet, hopefully its just my impatience that the wired connection does not work
I still wish netgear just lets consumers disable the auto update esp when most have to work from home now, any disruption to the internet is so painful.
Its rubbish for such an expensive system to be so limited and disruptive.
Safe to say I doubt I would ever opt for another netgear wifi system while this policy remains unchanged (waiting on more wifi 6e products before a switch but if such issues continue, I might just be forced to jump the gun).
FURRYe38 wrote:Try downgrading back to v3 on the RBS first then RBR lastly then follow the link to block using telnet:
My system auto updated again. I downgrading back to v3.2.18.233, but I have no way to telnet in to the system. The telnet option doesn't exist on the debug page. Unhiding the enable tenet option using dev tools doesn't seem to help either. Enable the option doesn't do anything.
Is there any other way to enable telnet?
From what the user says, this works:
https://community.netgear.com/t5/Orbi-WiFi-6/RBK750-Series-Firmware-Update-v4-6-3-7/m-p/2130584#M18586
https://community.netgear.com/t5/Orbi-AX/RBK750-Series-Firmware-Update-v4-6-3-7/m-p/2131307/highlight/true#M18670But you have to use the v10 version of FW for now. V3.2.10.10 as this was last version that had working telnet.
GoldenRetroGame wrote:
FURRYe38 wrote:
Try downgrading back to v3 on the RBS first then RBR lastly then follow the link to block using telnet:
My system auto updated again. I downgrading back to v3.2.18.233, but I have no way to telnet in to the system. The telnet option doesn't exist on the debug page. Unhiding the enable tenet option using dev tools doesn't seem to help either. Enable the option doesn't do anything.
Is there any other way to enable telnet?
FURRYe38 wrote:But you have to use the v10 version of FW for now. V3.2.10.10 as this was last version that had working telnet.
The 10 version has broken DNS and other issues, so that doesn't really work.
Welp, I connected the cable back again and it looks like its working now.
Looks like it really was because I was impatient the last time.
I'll observe for now to see how it performs before deciding whether I want to go through the hassle of having to try the downgrade again.
Glad that was wall then...
frostyfly wrote:
Welp, I connected the cable back again and it looks like its working now.
Looks like it really was because I was impatient the last time.
I'll observe for now to see how it performs before deciding whether I want to go through the hassle of having to try the downgrade again.