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.
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.
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.
FURRYe38 wrote: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.
I did a dirty install and only powered everything down for 30 minutes...maybe an hour, tops.
This has been the most stable my setup has been in quite a while. My 60+ devices: Servers, PCs, iPhones, tablets, IoT devices, cameras, Sonos system, etc., have all been very solid with excellent performance. Issues I had with the RBS Admin WEB interface getting hung up have also been resolved as best I can tell. Figures crossed it stays that way.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:
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.
FURRYe38 wrote: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...
In my case my satellite was off for seven, eight hours max overnight. But it definitely seemed to resolve problems that a shorter shutdown (5 minutes or so) had not. It still makes no sense to me.
Well i tried all that is suggested here (barring the downgrades) and it made no difference. I had them unplugged for a day or more, reconnected them, it worked fine for a few hours and back to reboots.
This same exact hardware was fine before 4.6.3.16 was rolled out. Another thing i noticed... its completely ruined the backhaul. The earlier setup was my satellites could connect to each other fine and i had EXCELLENT coverage with them. Now? They only insist on connecting with the main router (and completely fail).I am giving up for now. I will check back later if netgear does anything to fix this bull**bleep**.
- I have enough of trying to make their **bleep**ty firmware work! Cant they not just fix it? Also, I hope they dont expect me to buy a NG product ever again!
I now switched the satellite off and will try the 30mins-1 hour option and if that doesnt work, when I go to bed will switch both off for 7-8 hours, lets see, this is my last try before I throw these in the bir or try to sell them. Everyone is raving about Linksys and Ubiquiti.
