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.14.3 Released
Security Fixes: 12/01/2022
Addresses security vulnerabilities.
For more information about security vulnerabilities, visit https://www.netgear.com/about/security.
Bug Fixes:
Moves th...
Upgraded today, no issues.
Saved old config, followed standard upgrade process listed in first post. Also switched over DHCP to limit to 100-200 range. Curious if this will make any difference in stability/performance.
It's nice to see regular, incremental improvements coming from NG!
Saved old config, followed standard upgrade process listed in first post. Also switched over DHCP to limit to 100-200 range. Curious if this will make any difference in stability/performance.
It's nice to see regular, incremental improvements coming from NG!
Updated my RBK752 today as well. Just a power cycle after the FW was processed.
Using .100 to .200 DHCP IP address pool range.
If I update the firm ware via the Orbi app will it do the satellites first or just do the router??? or everything all at once??
Is it advisable to update the firm ware via the app or web interface? is there a better way????
Cine
I highly recommend using the Web UI on the RBS first. Then update the RBR lastly using it's Web UI with a wired PC and web browser.
Cinemagic310 wrote:
If I update the firm ware via the Orbi app will it do the satellites first or just do the router??? or everything all at once??
Is it advisable to update the firm ware via the app or web interface? is there a better way????
Cine
Setting DHCP limit between 2-200 ranges can help with stability in some cases, especially with FW upgrade. For example, if one of the devices on the network grabs the Orbi internal IP address, 192.168.1.250, the Satellite won't come online, reboot randomly, or hang. This is important during firmware upgrade because Orbi Satellite expects 192.168.1.250 to be available and exclusive to itself.
I've see best stability with .100 to .200. I personally use .100 to .150 since I don't have more than 40 devices online currently. Also gives room for static IP assigned devices on either side of this pool.
Looking for advice:
- Have been on Firmware Version: V4.6.9.11_2.3.5 and have not had a reboot since installation.
- System Uptime: 88 days 02:03:48
- Only issue we've seen is occasional hardwired lockup on my wife's laptop/hub...but I think its the hub.
- I see this latest firmware 4.6.14.3 seems to include many updates since our last update.
- I have never reset/wiped the router set since original purchase, only layered firmware updates on top of next.
I have early RBK753 set from Costco, enjoyed over a year of trouble free service before going through a year of constant rebooting that lasted until 4.6.9.11_2.3.5...so with 90 days of uptime, I'm really cautious of moving to new firmware.
My questions:
- How's this latest fw for rebooting? Is it stable, good uptime?
- If I save off my cfg file and do reset, will I get all my custom names I've created for various devices (I assume its tied to MAC address).
- What does narrowing the IP range to 100-200 do (other than limiting number of devices)
- Are the security fixes addressing minor things or major vulnerabilities?
Trying to decide: Is it worth updating? If so, should I do a full wipe/reset then apply cfg file?
SW_ wrote:Setting DHCP limit between 2-200 ranges can help with stability in some cases, especially with FW upgrade. For example, if one of the devices on the network grabs the Orbi internal IP address, 192.168.1.250, the Satellite won't come online, reboot randomly, or hang. This is important during firmware upgrade because Orbi Satellite expects 192.168.1.250 to be available and exclusive to itself.
Not following the logic here... I restricted my DHCP range between .100 and .200, and my Satellites are both showing up within that range: One has .121 and the other has .122.
As it should.
