NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
New - RBK752/753 Firmware Version 4.6.3.7 Released
Security Fixes: Fixes security vulnerabilities. For more information about security vulnerabilities, visit https://www.netgear.com/about/security. New Features and Enhancements: Supports Smart...
***Updated: 9/13/2021 11:50 AM PT
Hello Orbi Community,
Please accept my apologies for any delay in getting this message to you. I have been advised that an official firmware release is in the final stages of internal testing and in the process of being posted to our support site. Likely, within the next 24 hours.
To get this firmware release now please click the link below:
For instructions on how to manually download this firmware please visit:
How do I manually upgrade firmware on my Orbi router using orbilogin.com?
Thank you for your patience,
ChristineT
Thanks for letting us know about this and what you configured.
Keep an eye on this for next few days and let us know how the system works. Hoping this will bring stability to your system.
Curious about changing the router IP to .100. I presume this maybe something you normally do or was this a trobleshooting idea? I normally use .0.1 for the router and .100 to .150 for DHCP IP address pool since I don't have more than 40 devices anyways.
remsreef wrote:
My Orbi RBR750 and RBS750 have been stable and fast with the 4.6.3.7.. here are my settings:
1. Wireless Setup - Enable AX checked
2. LAN setup - I changed my router’s IP address to 192.168.1.100
3. LAN setup - DHCP range from 192.168.1.2 to 192.168.1.254
4. Advanced - Wireless Settings - unchecked “20/40 mhz coexistence”
- Enable WMM for 2.4 and 5ghz both checked
- CTS/RTS threshold to 2347 for both 2.4 and 5g
- Transmit power for 2.4g to 25% and 5g to 100%
That’s pretty much it. I did change the SSID to “test” so nothing could connect to the router and satellite while I was setting everything up. Everything else was on default. After everything was setup, I rebooted the router and satellite, then changed the SSID back to the old name so all the wireless devices could connect. Everything has been rock solid for me, no disconnects and the speeds are fast. Good luck!
I changed it to 192.168.1.100 just for testing purposes and since it’s been stable, I didn’t want to change it back to the defaults 192.168.0.1 or 192.168.1.1.
remsreef wrote:
I changed it to 192.168.1.100 just for testing purposes and since it’s been stable, I didn’t want to change it back to the defaults 192.168.0.1 or 192.168.1.1.I take it you put a DHCP reservation in for 192.168.1.100 then?
You can't use a reservation for 1.100 if it's the router IP address. Next available reservation would be .101.
Sorry please be specific ... so the range you use is
192.168.1.100 to 192.168.1.252? (ie that is the range that the Orbi can assign)?
Or you reduced the range to
192.168.1.2 to 192.168.1.100?
Or you made the router's address 1.192.168.1.1
Thank you
From what I gather, "I changed my router’s IP address to 192.168.1.100" from what the user said.
Thanks. I made all the changes including chaning my IP address to .100
If this doesn't get fixed soon, my next change will be returning this POS Netgear product to Costco and getting something more stable. Beyond furious that Netgear would push this and then not have a way to downgrade without being forced to auto update. If they know there is a problem, they should put out a temporary fix. Eveyrone is working from home and having your network crash 5x a day in the middle of zoom calls is NOT acceptable for a $400 router. I get that things go wrong. All companies have these issues. Not providing a temporary fix OR allowing for a rollback (or an auto rollback) - well, I guess the lawyers can figure that one out.
