NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
New - RBR350 / RBS350 Firmware Version 4.4.1.29 Released
New Features and Enhancements: 08/09/2022
- IPv6 DS-Lite, MAP-E support
- Analytics opt-in/opt-out for EU region
- VLAN ID and DHCP options 60/61 support
- Admin password strength enforcement
- Admin password brute force attack prevention
Bug Fixes:
- Fixes issue where the router’s LAN ports are not accessible to the Internet when PPPOE is enabled on the VLAN
- Fixes issue where changing the country/region in the router device UI can prevent the satellite from connecting to the router
Security Fixes:
- Fixes security vulnerabilities.
- For more information about security vulnerabilities, visit https://www.netgear.com/about/security
Download Link:
https://www.netgear.com/support/product/rbk352.aspx#download
Firmware Update Instructions:
To update your product’s firmware, follow the instructions in your product’s user manual.
To find your user manual, visit https://www.netgear.com/support/
enter your model number in the search box, and click the Documentation button on the product
NOTE: Orbi app or the routers web page may not report seeing new FW updates. NG may not push this to there auto update services immediately and may activate the newer FW update being seen on there auto update services at a later time. User will have the choice to manually update if you want too.
If you manually update, be sure to update the RBS first, then RBR lastly.
NOTE: Update the RBS first, then the RBR lastly. I recommend doing a full on factory reset after the FW loads, system is back to ready and a power OFF for 1 minute then back ON has been performed. Use a wired PC and web browser for this. Load the FW on to each RBS web page using the RBS web page, not thru the RBRs web page. Then load the FW lastly on the RBRs web page. Walk thru the setup wizard. You can manually setup the system as well for those who are more experienced with this.
A factory reset maybe needed if problems are encountered:
https://kb.netgear.com/31486/How-do-I-reset-my-Orbi-system-to-factory-default-settings
NOTICE: All users are advised to not downgrade FW on Orbi systems to older versions of FW. Downgrading FW may cause problems on the system and or cause units to no longer function. If you experience a problems after FW updating your Orbi system, please post in this thread or create a new post and give details to what your experiencing and we'll help you troubleshoot the problem.
This article applies to:
Let us know how it works for you in this thread please.
70 Replies
No firmware update since September 2022. Where is the support of Netgear????
I have encountered a similar issue with my RBR750 seeing my RBS350 satellite. Quick synopsis: Earlier today I noticed my router had not automatically updated the latest firmware even though it was set to automatically update. I realized I was actually a few versions behind. However, when checking updates for the satellite, it said that the update check failed. I updated the router without any issues, however, nothing would get the satellite to see an update.
Through my troubleshooting steps, I tried to factory reset the satellite numerous times and even factory reset the router as well. Through those processes though, the satellite now cannot be seen by the router nor can it be synced.
UPDATE: I was able to successfully manually update the satellite to 4.4.1.29 by directly connecting it to the router using the guide linked by FURRYe38. Unfortunately that had the same results. So right now I have:
- RBR750 (v7.2.6.31 5.0.24)
- RBS350 (v4.4.1.29)
It would be very much appreciated if there were any other ideas out there that I could try. Thanks in advance.
Need to downgrade the RBR750 back to v4 FW. The v7x FW is not compatible with 350 RBS.
FURRYe38 ....thank you! I was just about to update my post as I found this thread where you were able to help out and let folks they need to downgrade. Apologies for a duplicate post and for not finding it sooner, but thank you for your prompt reply. I realized my blocker was made more confusing since "RBK653" is not a product model that I recalled purchasing....instead opting to focus on just searching for RBS350 and RBR750 and not connecting those dots! 🙂
You mentioned v4, but not any specific version, so I would assume the latest (v4.6.14.3) would be the best one and not the one in this thread (v.4.4.1.29)?
As an aside, do you think there is a chance that the next RBR750 update would have compatibility for RBS350s? Since they were sold together in RBK653, I would hope that NG would keep them compatible so owners can stay both current and secure while maintaining their intended functionality?
unfortunately I have the "loser" series RBK350.. although it is a new product, it has no longer had software support for 1 and a half years..
I don't understand why a new firmware hasn't been released after more than a year..
Im sure theres one in the line.
The RBR350 has 3 big issues, very annoying at any system
Finally decide to go for another systems.
1) FireStick didn't connect well in many cases. In Spain, RBR350 choose DFS Channel 108, which is not accepted by FireStick.
FireStick not connects to middle–range DFS channels (52–144) in the 5GHz band, only connecting to channels on either ends (36–48 and 149–161) of the spectrum.
And I CANNOT CHANGE to another Channel in RBR350.
2) Wifi 2.4 and 5GHz SSID cannot be split in 2, to force connections.
3) You cannot choose which satellites are connected all devices. Then, sometimes, devices decide to connect to lowest power signal or signal far away, because it detects first. You cannot change it manually.
This are typical problems in a house.
Perhaps not so technical, but very annoying for the normal user.
I think ORBI should be more flexible with the setting options.
Regards,
Jose
Jose_394 wrote:
The RBR350 has 3 big issues, very annoying at any system
Finally decide to go for another systems.
1) FireStick didn't connect well in many cases. In Spain, RBR350 choose DFS Channel 108, which is not accepted by FireStick.
FireStick not connects to middle–range DFS channels (52–144) in the 5GHz band, only connecting to channels on either ends (36–48 and 149–161) of the spectrum.
And I CANNOT CHANGE to another Channel in RBR350.
Orbi AX systems only support front haul 5Ghz channel changes 36 thru 48. All other higher channels are used for the wifi BACKHAUL connection between the RBR and RBS. THis is how MESH systems work. Not user changable. I use 40 all the time and works well.
2) Wifi 2.4 and 5GHz SSID cannot be split in 2, to force connections.
Orbi systems have never allowed the SSID to be split. Due to complexitity of the system and wifi, this remains a closed featured. Keep an eye on future FW updates however.
3) You cannot choose which satellites are connected all devices. Then, sometimes, devices decide to connect to lowest power signal or signal far away, because it detects first. You cannot change it manually.
Due to how client devices work and operation. They choose where to connect based on signal level, noise and interference. Placement of RBR and RBS and distances is very important. You can adjust the power level on the system to help steer devices from say the RBR to the nearest RBS.
This are typical problems in a house.
Perhaps not so technical, but very annoying for the normal user.
I think ORBI should be more flexible with the setting options.
Technology can only do so much. Many factors and varioables surround wifi and wifi MESH systems.
FURRYe38 wrote:New Features and Enhancements: 08/09/2022
- ...
- Admin password strength enforcement
- Admin password brute force attack prevention
How is this possible that "Admin password strength enforcement" if I can only log on m RBS350 using the standard user/password (admin/password). It does not take over the password from RBR and its web interface does not offer an option to change this default password.
Please od make change in this area asap!!!
That's be cause the RBS hasn't properly synced to the RBR and hasn't got the log in information change from the RBR. You'll need to troubleshoot that to resolve what your seeing.
"Please od make" ? Huh?
No change in FW needed.
alternet wrote:
How is this possible that "Admin password strength enforcement" if I can only log on m RBS350 using the standard user/password (admin/password). It does not take over the password from RBR and its web interface does not offer an option to change this default password.Please od make change in this area asap!!!
Hi,
Did the update (first satelites, second router including factory reset after updates) but have some problems. Configuration is RBR350 (AP mode) and 2 RBS350 satelites behind a Fritzbox 7590 modem. Everything works for the "normal" network both with wireless and wired backhaul. The guest network only works with the wireless backhaul. When I connect the cables to the satelites the guest network is up and config pages show normal status but connected devices loses internet connection.
With the previous firmware version the guest network also worked with the wired backhaul. Is this a bug? Or did I miss something and are other changes required to get this working with this firmware version?
Are the RBS connected to the RBR? In back of the RBR or is there a network switch in between?
What CAT# lan cables are you using? CAT6 is recommended.
Did you sync the RBS first to the RBS wirelessly then after the BLUE LED appears, then connect the RBS to the RBR via ethernet?
Give several minutes for the RBS to sync fully and the front LED to turn OFF.
Supersjel wrote:
Hi,
Did the update (first satelites, second router including factory reset after updates) but have some problems. Configuration is RBR350 (AP mode) and 2 RBS350 satelites behind a Fritzbox 7590 modem. Everything works for the "normal" network both with wireless and wired backhaul. The guest network only works with the wireless backhaul. When I connect the cables to the satelites the guest network is up and config pages show normal status but connected devices loses internet connection.
With the previous firmware version the guest network also worked with the wired backhaul. Is this a bug? Or did I miss something and are other changes required to get this working with this firmware version?
Thanx for the reply! I'll try to answer the questions
FURRYe38 wrote:What CAT# lan cables are you using? CAT6 is recommended.
It's (unshielded) CAT6 cables. But I can't imagine the cable is the problem. Because if it was ... (my logic) ... I would think both the normal and guest network wifi would fail. But the outcome for the cabled setup is only the guest network is not working.
FURRYe38 wrote:Did you sync the RBS first to the RBS wirelessly then after the BLUE LED appears, then connect the RBS to the RBR via ethernet?
Yes, found on this community in a post this is important so I did. Even let it run for 10 minutes with some tests on the clients to see if it was stable.
FURRYe38 wrote:Are the RBS connected to the RBR? In back of the RBR or is there a network switch in between?
Last but not least the most interesting question, read a lot about this after the purchase six months ago. The manual of the Orbi's misses good documentation on wired setups. I have a netgear gigabit switch and read some contradicting information. So with the old firmware I just tested a few setups.
- modem -> orbi router -> orbi satelites (i.e. connecting satelites through router): worked
- modem -> switch -> orbi router -> orbi satelites (i.e. connecting satelites through router): worked
- modem -> orbi router & orbi satelites (i.e. connecting both router & satelites on modem): worked
- modem -> switch -> orbi router & orbi satelites (i.e. connecting both router & satelites on switch): worked
- modem -> orbi router -> switch -> satelites : instable (and undesired because the Orbi doesn't support IP-TV over network).
With some variations:
- Connecting the orbi router (in AP mode) through WAN or LAN did make no difference (except for blinking led if LAN is used)
- Connecting the satelites made difference, I read somewhere the LAN port on the right/most distance to power connection must be used.
I think 1/2 are the official ones (the "downstream option"). But since 4 lead to the optimal placement (best coverage) so I chose that. And used that until the firmware upgrade.
So this question reminds me of something. Don't remember which LAN port on the satelite I used yesterday. Double check that. And maybe this working setups changed with the new version and I should revisit option 1/2? Or is there another setup that I missed?
Hello,
can someone say if the loopback bug is fixed in this firmware version? There should be something like
echo 0 > /proc/sys/net/bridge/bridge-nf-call-iptables
According to my experience the bug is still there. It's really annoying if you want to use the satellites with a wired backhaul.
Kind regards
Hello Raj012,
Welcome to the NETGEAR Community!
I understand that you are having stability issues with your LAN connection. Factory reset has been proven to help re-establish the connection to your RBR350 via LAN.
Please perform a factory reset then check your ethernet connection for stability.
Best,
Kevin
Community Team
My RBS350 says that it now has the firmaware v4.6.9.11 (please see screenshot below), but I still don't see any reference for this version for RBS350?
v.29 is posted on NG download site for manual download. It may not be seen on the RBRs FW update web page as NG may not be giving notifications for it yet. If you want v.29, you'll need to manually apply this version.
- I still have issues with wired Ethernet connection even after this upgrade.
- I have the same issue. I have recently purchased this system. It works perfectly until i plug a ethernet cable in. Then it turns magenta and disconnects. For reference, only one device (satellite tv) into a rbs350 satellite.
What ethernet cable are you plugging and where are you connecting this cable at?
Gider1989 wrote:
I have the same issue. I have recently purchased this system. It works perfectly until i plug a ethernet cable in. Then it turns magenta and disconnects. For reference, only one device (satellite tv) into a rbs350 satellite.
