NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
New RBR750 / RBS750 Firmware Version 4.6.3.16 Released
Security Fixes:
Fixes security vulnerabilities.
For more information about security vulnerabilities, visit https://www.netgear.com/about/security.
Bug Fixes:
Fixes the issue where the s...
What Firmware version is currently loaded?
Is the RBS directly connected to the back of the RBR or is there a LAN switch in between the RBR and RBS? If so, brand and model please.
Has a power off for 1 minute then back ON with the ISP modem and Orbi system been performed since last update?
Jeffoz wrote:
What a mess. Never issues anymore lately after a rough start straight after release. Now in the morning suddenly instead of my own SSID I was on Ori13. Guess that's the back haul or something? My satellite is connected wired but it shows up as a client now, not a satellite anymore.
Internet works again but all this stuff started after this bad updates I guess.
Latets one. 4.6.3.16. No switch between. Powered off everything, reboots, all doesn't matter. This FW is just bad and we will have to wait until there is a new one. It's just sad you can't deactivate automated updates.
Be sure the RBS updated to v16 as well.
Are you using in wall LAN cableing?
Try taking the RBS to same room as the RBR and connect it to the back to check using a good quality LAN cable. CAT is is recommended.
Remove the RBS from the RBRs web page then try the connection.
Jeffoz wrote:
Latets one. 4.6.3.16. No switch between. Powered off everything, reboots, all doesn't matter. This FW is just bad and we will have to wait until there is a new one. It's just sad you can't deactivate automated updates.
- I use yes. Just patch panels basically extending cabling. I will just wait Fury as it's clearly firmware related, don't want to do a lot of changes while it's firmware related. I just wanted to post so it adds up to the rest of the messages so it's clear for Netgear there is an issue. I send the same to Darren alresdy as well. Appreciate your help and dedication always though!
Ok, was just wondering if the RBS would sync up right with it connected while near the RBR. Rule out in wall cabling.
Hoping NG will get this fixed soon.
Good Luck.
Jeffoz wrote:
I use yes. Just patch panels basically extending cabling. I will just wait Fury as it's clearly firmware related, don't want to do a lot of changes while it's firmware related. I just wanted to post so it adds up to the rest of the messages so it's clear for Netgear there is an issue. I send the same to Darren alresdy as well. Appreciate your help and dedication always though!This is a sublte issue that I think was also introduced in the v4 firmware. My original setup (v3) allowed for a wired backhaul through an unmanaged switch, which stopped working upon the update. To date, wireless backhaul is buggy, saying that it is connected sometimes by 2.4GHz and 5 GHz randomly, and even though showing connected, I'll catch the satellite blinking with white LED as if it has just rebooted. Doing a factory reset with the router and the satellite in the same room and about 15 ft. apart, I'll get a "Poor" 5 GHz status - WTF? The only thing that has worked consistently is a CAT5e cable directly between. I'm sharing all of this so other users aren't surprised when they try and get poor results...
FURRYe38 wrote:Ok, was just wondering if the RBS would sync up right with it connected while near the RBR. Rule out in wall cabling.
Hoping NG will get this fixed soon.
Good Luck.
Jeffoz wrote:
I use yes. Just patch panels basically extending cabling. I will just wait Fury as it's clearly firmware related, don't want to do a lot of changes while it's firmware related. I just wanted to post so it adds up to the rest of the messages so it's clear for Netgear there is an issue. I send the same to Darren alresdy as well. Appreciate your help and dedication always though!2 firmware updates, 1 RMA, 3 months, and multiple interrupted Zoom sessions later, I'm still faced with recurrent disconnections and flashing white/blue lights. This is incredible. Honestly, how am I supposed to retain my trust in Netgear's products?
Stupid garbage Netgear! Once again in the middle of a work call the router decides to reboot itself. Netgear needs to fix this garbage now. MONTHS and it is still not fixed.
I have the RBR750 running firmware V4.6.3.16_2.0.51. Within the last two weeks or so, I have been experiencing high packet loss making Microsoft Teams meeting quite frustrating.
If I run a "ping -t 8.8.8.8", I can often see >1% packet loss. Teams often reports >40% packet loss (it has a "Call Health" feature).
I sit about 20 feet from the main router with no obstructions in the way. I don't know if it is this last firmware or not, but for roughly the last 10 months, my system had been rock solid.
Edit: I should note I also have a "ping -t 192.168.1.254" (my router) that also is experiencing the same packet loss. Additionally, I have a wired device bypassing my Orbi (connected directly to my router) with 0% packet loss to 8.8.8.8.
Also note: my Orbi is running in AP mode.I'm also affected with random diconnects since the new v4 firmware was 'released'. And yes, I did the reset stuff and everything. Read through all of this, nothing helped.
To be honest, the whole thing just shows how unprofessional Netgear (or at least the responsible product team) works. With not being able to provide a stability for standard function (no fancy setup), I have serious doubts that complicated things like security are covered reliably.
As others are so kind and already invest a lot of time supporting with troubleshooting and debugging (resets, downgrade, switching things on/off), I can also provide my help with some advices to Netgear on how these issues can be solved ;)
- Distrubute a new FW update that reverts to an older (working?!) version asap, if there is any.
- Fire the whole FW development team application team. Not only the developers, also product managers and especially testers.
- Get a new team with skilled people to reimplement the Firmware from scratch.
Unfortunatly we would get rid of the late 90's looking web user interface but I could live with that. - Force the (new) Netgear team to use the product they build.
You guys can go back to v3x10 if your systems are working badly.
Revert to v10 on the RBS first then on the RBR lastly using this:
You'll need to block the v4 updates using this:
If not, you'll need to contact NG support directly and let them know whats going on.
Were also seeing better operation with RBS and RBR being fully unplugged from power for 24hours with v16 loaded. If someone was to try something say over night before you go to bed, then when you get up in the morning and power them ON and see the behaviors.
I've also been experiencing this disconnect issue for quite some time now with the v4 firmware. The new update has been better but the issue persists. I recently turned off AX mode in 5G and it seems to improve things a bit..
NG support has been kicking the can down the road for me unfortunately. They just reply back in 2 weeks asking for the log files and after I don't hear back. The case has been open since August. I'm now out of the 90 day support window so I'm not sure what to do once this window is over but the same issue lingers. Well, I guess I know which mesh router not to recommend to friends and family...
