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.9.11 Released
RBR750/RBS750 Firmware Version 4.6.9.11 Released
New Features:
Adds an auto-firmware upgrade enable/disable option <Long awaited feature is FINALLY HERE!
https://kb.netgear.com/...
Possible something on the AU side hasn't been cleared out. Seen this before with other users posting getting older FW notifications when newer is already onboard. You can ignore that.
Be sure that you set your RBR to disable auto updates under the Manual Tab.
EdFerreira wrote:
Strangely enough i'm being offered the
V4.6.3.16 in my RBS750 in autoupdate after the 4.6.9.11 upgrade. What can it be?
So I've had mine running for about 1.5 wks on the new firmware. No major issues so far. I did a manual update of the satellites then router, followed by a reset. Email alerts and auto update have been disabled. I haven't had any random reboots. The only thing I've noticed is that devices connected to my guest network seem to be renewing/refreshing their IP every few mins according to the logs, they seem to function fine but there are a lot of logged events.
Ya we know about the GN DHCP refreshing. Will be sure to pass this on to NG.
Be sure to save off a back up configuration to file for safe keeping. Saves time if a reset is needed.
https://kb.netgear.com/000062080/How-do-I-back-up-the-configuration-settings-on-my-Orbi-WiFi-System
InitialG wrote:
So I've had mine running for about 1.5 wks on the new firmware. No major issues so far. I did a manual update of the satellites then router, followed by a reset. Email alerts and auto update have been disabled. I haven't had any random reboots. The only thing I've noticed is that devices connected to my guest network seem to be renewing/refreshing their IP every few mins according to the logs, they seem to function fine but there are a lot of logged events.
Finally! A Netgear firmware update that I didn't have to simultaneously rub my tummy and pat my head to get it to run–then find out it created other issues! I've been running 4.6.9.11 for 7 days with no major issues.
I did a manual install (RBS's first) with no factory reset afterwards (I prefer to start there as the reconfiguration process is lengthy in my environment.). So far–right after the install–I've only had the Guest Network start broadcasting on its own. (I don't normally run the GN.) That was easily fixed by going into the Web UI and enabling the GN, waiting for it to reset, then disabling it. I also disabled email logging.
WiFi speeds are slightly slower at longer distances from the RBR and RBS (maybe 10% less). This is an acceptable trade to not have any random reboots, flashing lights, and email logging nonsense.
Also very happy NG finally listened to the owners and allowed us to turn off firmware auto-updates. Fairly happy camper for now!
To revive this old thread, yesterday, Netgear released v4.6.9.11 via the Upgrade button on the Orbi iOS app. I selected that and the router did appear to update successfully. However, none of the satellites updated and there's no way through the app to trigger that.
So I logged into the router's web page (advanced -> online update), and it confirms that the router is running V4.6.9.11 and the satellites are all running V4.6.8.2. The router status says No New Firmware Available, and all the satellites offer V4.6.3.16, which doesn't make sense to me. By version number those all look like downgrades!
Further, selecting UpdateAll, I see the satellite statuses turn to "Upgrading..." but then nothing happens, as I kind of would expect given they're actually offering to downgrade.
Is there an upgrade available for the satellites, and how would I get them to install it?
If the RBS are still connected and synced, manually update the RBS using there web pages ON the RBS themselves. Find the IP address of the RBS on the RBRs web page and use this in a web browser after manually downloading the RBS FW file:
I recommend using this method to update the RBS FIRST, then the RBR lastly, using a wired PC and web browser. I would avoid using Orbi app as you can see, that may not work correctly.
pumpichank wrote:
To revive this old thread, yesterday, Netgear released v4.6.9.11 via the Upgrade button on the Orbi iOS app. I selected that and the router did appear to update successfully. However, none of the satellites updated and there's no way through the app to trigger that.
So I logged into the router's web page (advanced -> online update), and it confirms that the router is running V4.6.9.11 and the satellites are all running V4.6.8.2. The router status says No New Firmware Available, and all the satellites offer V4.6.3.16, which doesn't make sense to me. By version number those all look like downgrades!
Further, selecting UpdateAll, I see the satellite statuses turn to "Upgrading..." but then nothing happens, as I kind of would expect given they're actually offering to downgrade.
Is there an upgrade available for the satellites, and how would I get them to install it?
Thank you! I've done exactly this and have upgraded all satellites and the router. I've turned on automatic updates from here on.
Glad you got it working.
Were hoping that AU will be tested more before being used. Hopefully next FW update will work properly and RBS set updated first then the RBR all in one shot. We just don't know at this point in time.
Be sure to save off a back up configuration to file for safe keeping. Saves time if a reset is needed.
https://kb.netgear.com/000062080/How-do-I-back-up-the-configuration-settings-on-my-Orbi-WiFi-System
Enjoy. 📡
pumpichank wrote:
Thank you! I've done exactly this and have upgraded all satellites and the router. I've turned on automatic updates from here on.
Looking forward to seeing how auto update works. Thanks for the recommendation to backup the config. I just saved the router's config. Do I need to save a config from each satellite too?
We'll see.
Nope.
Manually saw and got the updated firmwares via 753 router's internal updater this early afternoon PDT. So far, so good. I did have one cheap streaming video box that couldn't access to the Internet even though connected to a wifi guest RBS strongly. I made it forget and reconnect it. Weird/Odd. Hopefully, this version is good! Oh, and I disabled the firmware autoupdater. I'll check and update manually!
InitialG wrote:So I've had mine running for about 1.5 wks on the new firmware. No major issues so far. I did a manual update of the satellites then router, followed by a reset. Email alerts and auto update have been disabled. I haven't had any random reboots. The only thing I've noticed is that devices connected to my guest network seem to be renewing/refreshing their IP every few mins according to the logs, they seem to function fine but there are a lot of logged events.
Hmm, maybe that is why my streaming box told me no Internet connection. I had to manually forget and reconnect to it after the firmware updates.
InitialG wrote:
The only thing I've noticed is that devices connected to my guest network seem to be renewing/refreshing their IP every few mins according to the logs, they seem to function fine but there are a lot of logged events.
It has been reported that whereas the primary network typically issues DHCP leases for 1 day (86,400 seconds), the guest network issues leases for a much shorter time. The assumption being that "guests" are likely to be transitory and there is no point in keeping an IP address in limbo when the device has departed and may never return.
Would it be convenient to discover the length of the guest DHCP lease on your network?
(On a Windows computer this is easily done by opening a command window and running ipconfig /all.
This will display when the lease was issued and when it expires.)
CrimpOn wrote:
InitialG wrote:The only thing I've noticed is that devices connected to my guest network seem to be renewing/refreshing their IP every few mins according to the logs, they seem to function fine but there are a lot of logged events.
It has been reported that whereas the primary network typically issues DHCP leases for 1 day (86,400 seconds), the guest network issues leases for a much shorter time. The assumption being that "guests" are likely to be transitory and there is no point in keeping an IP address in limbo when the device has departed and may never return.
Would it be convenient to discover the length of the guest DHCP lease on your network?
(On a Windows computer this is easily done by opening a command window and running ipconfig /all.
This will display when the lease was issued and when it expires.)
My desktops don't have wireless. Is there a way to check in an iPhone with iOS v15.7?
CrimpOn wrote:
InitialG wrote:
The only thing I've noticed is that devices connected to my guest network seem to be renewing/refreshing their IP every few mins according to the logs, they seem to function fine but there are a lot of logged events.
It has been reported that whereas the primary network typically issues DHCP leases for 1 day (86,400 seconds), the guest network issues leases for a much shorter time. The assumption being that "guests" are likely to be transitory and there is no point in keeping an IP address in limbo when the device has departed and may never return.
Would it be convenient to discover the length of the guest DHCP lease on your network?
(On a Windows computer this is easily done by opening a command window and running ipconfig /all.
This will display when the lease was issued and when it expires.)
The Lease Time for the Guest Network devices is set to 15 minutes by Netgear.
This is probably great for those who actually use the Guest Network for GUESTS, but many users are now using the Guest Network for IoT devices to provide network segregation from the main network devices as the security is not always the greatest on some IoT devices.
It would be great if this was user configurable and I believe some router manufacturers allow the user to set this time.
TC_in_Montana wrote:
CrimpOn wrote:
InitialG wrote:The only thing I've noticed is that devices connected to my guest network seem to be renewing/refreshing their IP every few mins according to the logs, they seem to function fine but there are a lot of logged events.
It has been reported that whereas the primary network typically issues DHCP leases for 1 day (86,400 seconds), the guest network issues leases for a much shorter time. The assumption being that "guests" are likely to be transitory and there is no point in keeping an IP address in limbo when the device has departed and may never return.
Would it be convenient to discover the length of the guest DHCP lease on your network?
(On a Windows computer this is easily done by opening a command window and running ipconfig /all.
This will display when the lease was issued and when it expires.)
The Lease Time for the Guest Network devices is set to 15 minutes by Netgear.
This is probably great for those who actually use the Guest Network for GUESTS, but many users are now using the Guest Network for IoT devices to provide network segregation from the main network devices as the security is not always the greatest on some IoT devices.
It would be great if this was user configurable and I believe some router manufacturers allow the user to set this time.
Ditto. Is this issue new in this firmware version or did it exist in earlier versions as well?
ant wrote:
Ditto. Is this issue new in this firmware version or did it exist in earlier versions as well?
15 minute Lease Time on Guest Network is not new. It's been that way for a long time.
TC_in_Montana wrote:
ant wrote:Ditto. Is this issue new in this firmware version or did it exist in earlier versions as well?
15 minute Lease Time on Guest Network is not new. It's been that way for a long time.
Thanks.
The entries are indeed related to mobile/tablet devices (IoT etc) and I'm not sure of the lease times (from the devices)
I can confirm that the log entries I have (for 5 devices) were roughly at 15min intervals.
I didn't realise about the default 15mins. Thx for that bit of information.
You have guessed correctly that I use Guest Network for IoT devices and simple network segregation.
Just for info, the update went smooth when followed the instructions in the community. Have set the auto update to disabled.
Now we see how it performs in the upcoming weeks.
