NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
New - RBR850/RBS850 Firmware Version 4.6.9.11 Released
RBR850/RBS850 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/000038662/How-do-I-enable-disable-auto-firmware-update
- Adds support for IGMPv2 and IGMPv3
- Adds support for PCCW IGMP proxying
- Adds PPPoE passthrough option
- Adds Automatic Private IP Addressing (APIPA)
- Adds an Intranet IP option
Enhancements:
- Improves reliability of Ookla Speedtest results from the Orbi app and device UI
- Improves reliability of the Armor device scan and associated device notifications
Security Fixes:
- Fixes security vulnerabilities.
For more information about security vulnerabilities, visit https://www.netgear.com/about/security.
Bug Fixes:
- Fixes an issue where the incorrect model name displays on the RBS850 debug page
- Various other minor bug fixes
Download Link:
RBR850: https://www.downloads.netgear.com/files/GDC/RBK852/RBR850-V4.6.9.11.zip
RBS850: https://www.downloads.netgear.com/files/GDC/RBK852/RBS850-V4.6.9.11.zip
Please navigate to the link below for step-by-step instructions on how to update your RBR850/RBS850:
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.
NOTE: The Disable Auto Update feature only prevents ANY new FW from being installed if available. This does NOT prevent the system from checking NG services to see if new FW is available. If new FW is available, this will be displayed as a notification to the user on the RBRs web page only. It will be up to the user to upgrade FW or not.
A factory reset maybe needed if problems are encountered after the FW update:
https://kb.netgear.com/31486/How-do-I-reset-my-Orbi-system-to-factory-default-settings
Best
Kevin
Community Team
164 Replies
What would cause a rogue IP address after the update to firmware v4.6.9.11 All my IP are 192.168.1.X and I have one with a 169.254.80.180
A device that isn't getting the normal IP address from the RBR. Look at the MAC address seen at the 169 address and then review the devices you have to see which device has this MAC address.
Any Apple devices? Be sure to disable Wifi Private Address on Apple devices.
out2pgh wrote:
What would cause a rogue IP address after the update to firmware v4.6.9.11 All my IP are 192.168.1.X and I have one with a 169.254.80.180
out2pgh wrote:What would cause a rogue IP address after the update to firmware v4.6.9.11 All my IP are 192.168.1.X and I have one with a 169.254.80.180
One of the additions in this firmware (v4.6.9.11) is "Adds Automatic Private IP Addressing (APIPA)" which is the address3es 169.254.x.x. 🙂
A device will get such address if it can't get an IP address from the DHCP server. What DHCP settings do you have? Is Orbi in Router or AP Mode?
I do not have APIPA turned on
There seems to be a bug with the "Automatically adjust for daylight savings time" on NTP Settings?
In New Zealand it's currently +1 hour for daylight savings, but the time mentioned on the router admin there and under the logs is still back by an hour. Saying it's 10:30am rather than 11:30am. Currently using the default NETGEAR NTP server, might test another.
Let us know what happens with a custom server...
Please post a screen capture of what it looks like on the Admin/NTP Settings page.
Validus wrote:
There seems to be a bug with the "Automatically adjust for daylight savings time" on NTP Settings?
In New Zealand it's currently +1 hour for daylight savings, but the time mentioned on the router admin there and under the logs is still back by an hour. Saying it's 10:30am rather than 11:30am. Currently using the default NETGEAR NTP server, might test another.
Originally set to the default Netgear NTP. I had tried to set the NTP to nz.pool.ntp.org today for testing, same results.
Rebooted when the time was 12:01pm.
Yet under the router logs: [Time synchronized with NTP server] Thursday, Sep 29,2022 11:01:32
All of the router log being off by an hour.
Screenshot shows time as 3:39pm, when it's currently 4:39pm.
I'm assuming that NTP servers don't do the daylight saving itself, it would just be the router setting adjusting it for the log files, etc? It won't affect anything on the Internet or within the Network itself, right since it's using UTC?
What a poorly managed update.
Netgear auto updated my RBR but did not auto update my RBSs. Now I have a satellite that is not connecting to the network and two other satellites connected but do not show an update available - they actually don't show anything other than "Please wait a moment..." in the firmware update screen.
It is unclear to me how a technology company can be this incompetent when rolling out a firmware update.
Hello skeelo,
I understand that your RBR850 was updated and your satellites did not update. You do have the option to manually update your RBS850s.
Please navigate to the link below for instructions and video reference on how to update your RBR850:
Please navigate to the link below for the firmware version 4.6.9.11 for your satellite:
https://www.netgear.com/support/product/rbs850.aspx#download
Best,
Kevin
Community Team
Thanks for your note, Kevin.
I wish I could say I the info provided was new to me and helpful. Unfortunately, given my past experience with this setup I am all too familiar with how to update, reboot, factory reset, etc. my RBR and RBSs.
Thanks to an ongoing issue after an early firmware update (I was an early adopter post launch) that forces my system to effectively shut off (drops all wired and wifi routing capabilities) the solution I have found that works best is to reboot everything once a month (almost to the day). I came to this solution after loading prior FW versions to my RBR and RBSs repeatedly which is when and how I learned to manually update firmware.
All of that said, the Netgear Nighthawk running in my cabin has never skipped a beat and only gets reset when there is a power outage. I expected at least similar reliability from this system since it comes from Netgear (not to mention it costed me 8-10x) and I am now too invested to move onto another manufacturer.
Rest assured, when the next great Wifi hardware update comes or this equipment eventually bricks I will be buying from another company. I would run cat6 in the hallways of my house to my ISPs modem before buying another Netgear Wifi product after this ongoing debacle.
/rant.
skeelo wrote:What a poorly managed update.
Netgear auto updated my RBR but did not auto update my RBSs. Now I have a satellite that is not connecting to the network and two other satellites connected but do not show an update available - they actually don't show anything other than "Please wait a moment..." in the firmware update screen.
It is unclear to me how a technology company can be this incompetent when rolling out a firmware update.
Again, this is not how auto updates work. Companies regularly delay auto-updating everyone to reduce risk. Instead they make the new firmware manually available first and then after a short time and if no issues reported, slowly rollout the update. This is the correct and industry standard way to manage firmware updates.
For most Orbi customers who do not read the forum and who do not immediately install new firmware updates, their devices will *eventually* update. They don't care if their base vs. satellite are temporarily mismatched, as long as they continue to work. They also do not want the extra risk of installing something new, so they instead wait for the company to take responsibility for the update (after the early adopters add greater confidence that it is fine).
Mikey94025 wrote:
skeelo wrote:What a poorly managed update.
Netgear auto updated my RBR but did not auto update my RBSs. Now I have a satellite that is not connecting to the network and two other satellites connected but do not show an update available - they actually don't show anything other than "Please wait a moment..." in the firmware update screen.
It is unclear to me how a technology company can be this incompetent when rolling out a firmware update.
Again, this is not how auto updates work. Companies regularly delay auto-updating everyone to reduce risk. Instead they make the new firmware manually available first and then after a short time and if no issues reported, slowly rollout the update. This is the correct and industry standard way to manage firmware updates.
For most Orbi customers who do not read the forum and who do not immediately install new firmware updates, their devices will *eventually* update. They don't care if their base vs. satellite are temporarily mismatched, as long as they continue to work. They also do not want the extra risk of installing something new, so they instead wait for the company to take responsibility for the update (after the early adopters add greater confidence that it is fine).
Uh... what? My system had issues which is why I posted to begin with.
Aside from the fact there are now 6 pages in this thread in which users highlighted firmware update issues from early adopters of this version, which would/ should delay the auto update process per your diatribe, my system was automatically updated, updated only the RBR, and in doing so had a negative impact on my RBS connectivity.
Had I not had connection issues due to the mismatched firmware loaded in with the auto update I would not have made my original post in this thread.
Every firmware update thread ever posted here that I have seen explicitly states that RBSs should be updated prior to updating the RBR and in this case, Netgear's auto update does not follow the its own best practice. As a result, I had to step in and manually update my system after however many successful firmware auto updates prior to this.
So again, this was a poorly managed update and it is unclear to me how a technology company can be this incompetent when rolling out an auto firmware update.
Edit: Step two in the install FAQ in the first post of this thread states "Updated the firmware on your Orbi satellite" before step three "Update the firmware on your Orbi router".
- Download the firmware for both your Orbi router and satellite.
- Update the firmware on your Orbi satellite.
- Update the firmware on your Orbi router.
I am seeing the guest network appear as well, seem to have disabled it (for now) by changing the name, turning it on and then turning it off again.
Also, I am seeing horrendous wifi performance since I updated about a week ago. My Ring cameras and Yale bridge are reporting poor signal quality, which was not the case with the previous firmware, and some older iPads are having issues connecting and holding a connection while streaming music to AirPlay 2 speakers, which also has not been an issue before. Newer devices are showing less than a full number of wifi bars, which is a new development as well.
Has a factory reset and setup from scratch been performed since last FW update?
- No, I have done that enough times before with zero effect, I am not going that route without a really good reason to do so.
The guest network which had been manually turned off is automagically on again, without any configuration changes or reboots.
Arter v.11 was loaded on the system, did you power OFF the system for 1 minute then back ON and continue to use the system or have you done a full on factory reset and setup from scratch since v.11 was applied?
We have seen the GN being seen during the boot up and ready sequence then it has turned back OFF.
Try this, enable the GN network and changd the SSID Name to something else. once the GN is enabled for a few minutes, re-disable it on the RBRs web page.
Mooose wrote:
The guest network which had been manually turned off is automagically on again, without any configuration changes or reboots.
