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.
You'll need to contact NG support this and let them know what your experiencing then.
Good Luck.
N3tworkDud3 wrote:
New thing for me today - checked the status of my system - now the satellite is out of sync. I rebooted it, showed a poor status. Then - back to out of sync.
What a joy.
Furry - not initerested in what you have to say about this - any reply will be ignored as this is 100% related to the firmware update failure of Netgear. No I'm not going to go down to 3.x firmware and finegeling the router(s) to prevent auto updates at this time. Netgear needs to step up.
Anyone thinking of a class action? I am.
Furry...your suggestion to power down everything for 24 hours seems to have remedied the satellite backhaul oscillating between poor and good that I was experiencing introduced with the 4.6.3.16 fiirmware. It has been 72 hours since power back up and I haven't seen this condition return. Thanks.
I don't fully understand it but I have the same thing to report. I unplugged my misbehaving satellite for several hours overnight (mostly because it kept flashing blue, then white, and waking me up!) Since I plugged it back in the following morning, the system's been stable again as far as I can tell. Speeds are back to normal and I haven't noticed any satellite dropouts. It's been a few days now.
I still don't trust this firmware - I'm not making any changes to the configuration for now, as I'm concerned that any kind of reboot will cause the problems to recur. But at least the system is usable for now.
I genuinely don't understand why unplugging the system for a few hours might resolve problems that unplugging for a few minutes does not.
Garwoofoo wrote:I genuinely don't understand why unplugging the system for a few hours might resolve problems that unplugging for a few minutes does not.
It doesn't. Any processes that run get killed off when you power it down. You don't want to unplug and plug back in immediately, but allow a few minutes to pass - 5-10 should be the most you need.
Edit: Should probably qualify this - if you kill the power to all your devices, 5-10 minutes is all you should need. But - if you only power off a troubling sattelite, keeping it off a period of time may allow the RBR to time out trying to communicate with the satellite which could be part of the issue.
WRSORBI Garwoofoo Thanks for letting us know. Yes I agree this seems odd that 24 hours seems to be key in the system working again. No idea why unless there is something else working behind the scenes that 24 hours seems to get reset somewhere else and then after that all works. I thought that a few minutes would be enough but when I ran out of time troubleshooting this, I just unplugged it all and came back to it the next day, 24 hours and it started working. It's crazy for sure.
Glad it's working now.
- If powering off for an extended period (24 hours) fixes an issue, it would indicate a heat induced problem. For the satellites going through repetitive signal seeking, the transmitter must be cycling into high power mode creating heat soak. Letting it cool, then getting re-synced might be avoiding the overheating.
Everyone should keep track if the problem/resolution repeats itself. I'd probably RMA the units and hope for a more stable replacement.Anything is possible. Why I'm curious if a shorter time frame of being OFF would work as well. Like 30 minutes or 1 hour...
Only reason why I mentioned it in my post was that I had spent enough time trying to figure out what was happening, I had to stop and come back to it. I turned it off and left it, went to work the next day and came home and started fiddling with it again and found everything worked, no reboot loop and I was able to get in to AP mode with v16.