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.
Did something interesting. Ran the Enable LAN/WAN Packet Capture on my satellite (ip.addr/debug.htm). Saw manhy calls to http://schemas.xmlsoap.org/soap/encoding/. Also saw:
- Number of hops: 255 (should be 1) With 255, the connection shows "poor"
- Many repeats for a MAC address not resolving to IP.
- Checks for Firmware in the folder for 4.6.3
- Firmware looking to https://http.fw.updates1.netgear.com/rbs850/V4.6.3/us/fileinfo.txt
- Uplink snr = 31 Rate to CAP = 520 Mbps (this one is interesting - the SNR is really low - the cap of 520 Mbps - not sure what radio it's tied to. I've suspected the Orbi has limited the speed I can get per device since installing them)
- Lots of kern.err llines
- Etc. etc etc.
Didn't run the capture that long either. Lots of interesting info. that's going to take a while to get through.
Is this with the RBS in same room as RBR or at the remote RBS location placement?
FURRYe38 wrote:Is this with the RBS in same room as RBR or at the remote RBS location placement?
If you are asking me - it's a few rooms away - don't want them too close and I'm not moving it to troubelshoot - worked great when i first bought them. Firmware updates the past year has made some functionality problematic - but not the connection between the RBR and RBS.
Would be good to place in same room as RBR to check logs. Then move it back. Yes I know, this is only for troubleshooting.
Otherwise, you'll need to contact NG support.
You can also try leaving the system unpowered for a few hours and see if this help. Others are posting that leaving the RBR and RBS unplugged for 24 hours seems to be working for them. I'm curious if leaving it OFF for less than a couple of hours results is any differences.NG will have to fix all this regardless. Either try the suggestions or downgrade the system while you wait for NG to fix this.
- Super curious why you think it’s better to get logs with the RBS and RBR in the same room.