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.
So the actual RBS is a 850? Log into the RBS web page and confirm it's a 850...
What is the distance you have the RBS place from the RBR? Try moving the RBS closer to the RBR, maybe on a edge of wifi signal is at Poor and Good and moving it closer may fully get it into good.
You might do a reset on the RBR and RBS as well...
N3tworkDud3 wrote:
Update on my situation - the status of the Backhaul was poor. I have never seen a status other than good in the time I've had this system installed (over a year).
I decided to go ahead and reset the satellite and re-pair it to the RBR. Just in case it had a problem like the RBR did. I reset and re-paired the RBS to RBR. Seemed to fix it, but I'm noticing the Backhaul status is actually changing from Poor to Good and back. I see Poor more than Good.
Went to the RBS to see if I could reboot it remotely, just to see if after the process yesterday, it needed to reboot again. Nothing was connected to it. No option on its web page. Went to the debug page. Strange thing - it reported the device as an RBS 750, not 850. The main page does state it's an RBS850. Wonder if this is an indication of our issues with satellites - the firmware doesn't identify the hardware correctly?
I checked the debug page of the RBR and it does identify as the RBR850 correctly.
Furrye38 - I appreciate the input but this thread is about the firmware update and issues with it. I can assure you the RBS is an 850. I bought the RBK850 with one RBR850 and one RBS850. When I said "The main page does state it's an RBS850" right after saying the Debug page said RBS750 - it meant I went to the RBS web page for crying out loud.
Also - the distance has NOT changed at all in the time I've had this system. The ENTIRE time the backhaul reported Good.
Please - whatever Netgear did to the firmware was negligant. Maybe take a breath and consider what people are saying - read to understand - and consider the link back to the firmware update the night before.
Thanks.
Try this as this seem to help this user out:
If not, You'll need to contact NG support and open a support ticket then and get there help and information regarding your system if your having problems with it.
Good Luck
N3tworkDud3 wrote:
Furrye38 - I appreciate the input but this thread is about the firmware update and issues with it. I can assure you the RBS is an 850. I bought the RBK850 with one RBR850 and one RBS850. When I said "The main page does state it's an RBS850" right after saying the Debug page said RBS750 - it meant I went to the RBS web page for crying out loud.
Also - the distance has NOT changed at all in the time I've had this system. The ENTIRE time the backhaul reported Good.
Please - whatever Netgear did to the firmware was negligant. Maybe take a breath and consider what people are saying - read to understand - and consider the link back to the firmware update the night before.
Thanks.This update has definitely caused issues for me.
I've got two satellites and previously they each connected directly to the router with a really strong signal.
Since this update was automatically applied (which I am very cross about), Satellite 2 insists on connecting to Satellite 1 rather than the router, so I now have a daisy-chain topology. The signal on Satellite 2 is now not as strong as it was.
If I disconnect Satellite 1 completely, Satellite 2 WILL connect to the router, but the connection is now very poor whereas previously it was very strong. I have no idea why this would be and nothing else has changed apart from the firmware update.
I've switched off everything for ten minutes and reconnected it all and this behaviour is consistent. It's not a major problem I guess but it's notably worse than it was on the old firmware and I have no idea why it is exhibiting this behaviour now.
Forcing firmware updates on equipment that people are relying on to be able to work effectively from home is extremely poor behaviour, in my opinion. My system was perfect before... now, not so much.
Try this as this seem to help this user out:
Garwoofoo wrote:
This update has definitely caused issues for me.
I've got two satellites and previously they each connected directly to the router with a really strong signal.
Since this update was automatically applied (which I am very cross about), Satellite 2 insists on connecting to Satellite 1 rather than the router, so I now have a daisy-chain topology. The signal on Satellite 2 is now not as strong as it was.
If I disconnect Satellite 1 completely, Satellite 2 WILL connect to the router, but the connection is now very poor whereas previously it was very strong. I have no idea why this would be and nothing else has changed apart from the firmware update.
I've switched off everything for ten minutes and reconnected it all and this behaviour is consistent. It's not a major problem I guess but it's notably worse than it was on the old firmware and I have no idea why it is exhibiting this behaviour now.
Forcing firmware updates on equipment that people are relying on to be able to work effectively from home is extremely poor behaviour, in my opinion. My system was perfect before... now, not so much.