NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
New - Orbi RBR50 Router Firmware Version V2.7.2.104 Released
Security Fixes:
- Fixes security issues
This firmware addresses security vulnerabilities. For more information about security vulnerabilities, visit https://www.netgear.com/about/security.
Download Link:.
RBR50 - https://www.downloads.netgear.com/files/GDC/RBK50/RBR50-V2.7.2.104.zip
RBS50 - https://www.downloads.netgear.com/files/GDC/RBK50/RBS50-V2.7.2.104.zip
IF this doesn't appear in the RBRs FW upate web page as being available, you can manually install and apply:
https://kb.netgear.com/31573/How-do-I-manually-upgrade-firmware-on-my-Orbi-router-using-orbilogin-com
https://kb.netgear.com/000037217/How-do-I-check-and-manually-upgrade-the-firmware-on-my-Orbi-satellite
Update the RBS first, then RBR lastly.
Let us know how it works for you.
Good Luck.
- I became aware of the latest firmware while browsing this forum. Neither the app nor the web interface indicated an available update. I downloaded the files via my computer and performed a manual update via the web interface -- one satellite first, then the other, then on to the router. (RBK50) In the past, I have had updates pushed out (only once); notices both on the web and app of firmware updates available; and updates that I found were released via this forum which I've manually installed (the latter seems to be the most frequent way I have updated firmware). Through all ways, I have never had the slightest issue with downloading and installing updated firmware.
183 Replies
Thanks for your recommendation, however when I do manual updates, works just fine.
Is this update US-only (as was the last in the 2.7 series)?
defjaf wrote:Is this update US-only (as was the last in the 2.7 series)?
Doesn't say so anywhere.
I would not assume that v104 isn't for all regions, this version still follows the v2.7 version line thus may still be considered a continuation fix from the v2.7 line and thus maybe a security fix for what may have been missing in v102 which I is still a US region only version.
This article applies to:
defjaf wrote:Is this update US-only (as was the last in the 2.7 series)?
I am in the UK and currently on 2.6.1.40.
Interestingly. the product/download page shows both 2.7.2.104 and 2.6.1.40, but neither seems to be marked as region-specific (IIRC the previous 2.7.* was marked US-only on this page).
Moreover, 2.7.2.104 is now being shown as available on both the iOS Orbi app and the orbilogin web page. (If I update I probably can't do it until later.)
It lists only the following as affected by it:
RBR750
RBR850
RBS40V
RBS750
RBS850
Possible that NG is making v2.7_v104 line available for all regions if your seeing this on the Orbi app and on the RBRs web page if your in the UK. This is good info.
defjaf wrote:I am in the UK and currently on 2.6.1.40.
Interestingly. the product/download page shows both 2.7.2.104 and 2.6.1.40, but neither seems to be marked as region-specific (IIRC the previous 2.7.* was marked US-only on this page).
Moreover, 2.7.2.104 is now being shown as available on both the iOS Orbi app and the orbilogin web page. (If I update I probably can't do it until later.)
I upgraded from 2.5.1.16 to 2.7.2.104 yesterday. So far no issues.
In the past I tried several versions after 2.5.1.6 and had issues with all of them within a short time after upgrade.
So I went back to 2.5.1.16 all the time. I also had "minor" issues with 2.5.1.16, mainly after power outage with the satellites not getting stable connecction to the router. So I had always to power off the whole system (1xRBR50, 2xRBS50 via WiFi, 1xRBS50 over LAN, behind a switch) and power on first the router and then one satellite after the another.This time, I just upgraded the satellites manually, one by one. And finally the router. No need to power cycle the satellites again. They all conneccted to the router and remain stable until now. Also the clients are connected without any intervention.
So it looks like we have finally a stable firmware.
Btw, I'm using the Orbi with these "features" enabled:
- Router mode (for me there is no option to use the Orbi only in AP mode)
- Enabled "Access Control"
- Defined some "Port Forwarding"
- using "Dynamic DNS"
- using "VPN Service"
- using "LAN Address reservation" (bind MAC to a fix IP address)
Please keep us posted
I hope it works well for you
thanks for the informative post
Be sure to make a new backup configuration to file for safe keeping.
Ha_Ku_Na wrote:I upgraded from 2.5.1.16 to 2.7.2.104 yesterday. So far no issues.
In the past I tried several versions after 2.5.1.6 and had issues with all of them within a short time after upgrade.
So I went back to 2.5.1.16 all the time. I also had "minor" issues with 2.5.1.16, mainly after power outage with the satellites not getting stable connecction to the router. So I had always to power off the whole system (1xRBR50, 2xRBS50 via WiFi, 1xRBS50 over LAN, behind a switch) and power on first the router and then one satellite after the another.This time, I just upgraded the satellites manually, one by one. And finally the router. No need to power cycle the satellites again. They all conneccted to the router and remain stable until now. Also the clients are connected without any intervention.
So it looks like we have finally a stable firmware.
Btw, I'm using the Orbi with these "features" enabled:
- Router mode (for me there is no option to use the Orbi only in AP mode)
- Enabled "Access Control"
- Defined some "Port Forwarding"
- using "Dynamic DNS"
- using "VPN Service"
- using "LAN Address reservation" (bind MAC to a fix IP address)
Sidebar question:
- Is restoring settings from a backup a reliable way to set up the system?
- Especially when changing the firmware?
- or after resetting the devices to factory condition?
The conventional wisdom is to reset to factory settings and re-enter the configuration.That clears out any remenants and provides a fresh start. Is that equivalent to restoring settings from the .cfg backup file?
Ha_Ku_Na wrote:
I upgraded from 2.5.1.16 to 2.7.2.104 yesterday. So far no issues.
In the past I tried several versions after 2.5.1.6 and had issues with all of them within a short time after upgrade.
...- using "VPN Service"
- using "LAN Address reservation" (bind MAC to a fix IP address)
Just to have you updated. After nearly 5 days on 2.7.2.104 -> NO issues at all !
Looks like I do not have to look for (mesh) alternatives (non Netgear).
Be sure to make a new back up configuration to file for safe keeping.
Enjoy. :smileywink:
Ha_Ku_Na wrote:Ha_Ku_Na wrote:
I upgraded from 2.5.1.16 to 2.7.2.104 yesterday. So far no issues.
In the past I tried several versions after 2.5.1.6 and had issues with all of them within a short time after upgrade.
...- using "VPN Service"
- using "LAN Address reservation" (bind MAC to a fix IP address)
Just to have you updated. After nearly 5 days on 2.7.2.104 -> NO issues at all !
Looks like I do not have to look for (mesh) alternatives (non Netgear).
Downloaded the firmware update from the phone app. Router stopped working. Despite multiple factory resets, can't reinstall it. Can't even get either the browser portal or phone app to communicate with the router – or see the Orbi Wifi net, which it needs to do to reinstall.
Talked to an Orbi tech who said, in effect, that it was my mistake for having upgraded – and that (at a price) they'd help me revert to the old firmware.
TedNemo wrote:Downloaded the firmware update from the phone app. Router stopped working. Despite multiple factory resets, can't reinstall it. Can't even get either the browser portal or phone app to communicate with the router – or see the Orbi Wifi net, which it needs to do to reinstall.
Talked to an Orbi tech who said, in effect, that it was my mistake for having upgraded – and that (at a price) they'd help me revert to the old firmware.
wow....Router stopped working.....(we'll save that for another discussion)
you may need to perform a factory reset and start over. Next time dump the app
https://kb.netgear.com/31486/How-do-I-reset-my-Orbi-system-to-factory-default-settings
Thanks for replying. Already did (several) factory resets. But the Orbi Wifi ID (network) doesn't appear (only something called DNIWIFI), so there's no way I can make the reinstallation work via either the app or the web portal. Have ordered an ethernet cable and guess I'll try to connect to the Orbi router directly and cross my fingers.
Is there an easy way to just revert to the old firmware? I assume that even after the reset, the updated firmware will still be there, right?
Thanks again
I did the update this morning, something went wrong and now the wireless network is not working. I went into the Telnet port (enabled via the debug.htm) and I found out that when the orbi is starting up there is a kernel bug error and it unloads all the Atheros kernel drivers.
this is the error I see in the boot log:
kernel BUG at /home/release/orbi-maintrunk-buildroot-20191028125258.git/build_dir/target-arm_cortex-a7_uClibc-1.0.14_eabi/linux-ipq806x/qca-wifi_dni-10.4-g0.1.453.110-unified-profile/qca-wifi_dni-10.4-g0.1.453.110/os/linux/../../qca_ol/../cmn_dev/htc/htc_recv.c:620!
Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARMThen a lot of debug lines, then:
ath_dev: driver unloaded
ath_tx99: driver unloaded
ath_rate_atheros: driver unloaded
ath_hal: driver unloadedI have a RBR50, and now I don't have anything to replace it quickly!
Please help!
lcba813 wrote:I did the update this morning, something went wrong and now the wireless network is not working. I went into the Telnet port (enabled via the debug.htm) and I found out that when the orbi is starting up there is a kernel bug error and it unloads all the Atheros kernel drivers.
this is the error I see in the boot log:
kernel BUG at /home/release/orbi-maintrunk-buildroot-20191028125258.git/build_dir/target-arm_cortex-a7_uClibc-1.0.14_eabi/linux-ipq806x/qca-wifi_dni-10.4-g0.1.453.110-unified-profile/qca-wifi_dni-10.4-g0.1.453.110/os/linux/../../qca_ol/../cmn_dev/htc/htc_recv.c:620!
Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARMThen a lot of debug lines, then:
ath_dev: driver unloaded
ath_tx99: driver unloaded
ath_rate_atheros: driver unloaded
ath_hal: driver unloadedI have a RBR50, and now I don't have anything to replace it quickly!
Please help!
Factory reset?
and we'll file this away in the I shouldn't have upgraded file
vajim wrote:
Factory reset?and we'll file this away in the I shouldn't have upgraded file
I did the 30-30-30 reset, and loaded the latest firmware via TFTP. same issue.
Then did it with the latest 2.6 firmware, and the same happened... I'm guessing something bogus on the latest 2.7 trashed the network hardware?
Is there a way to do another kind of factory reset? a lower level one?
Hi
Got RBR50 router, and 2 Satellits RBS50Y+RBS50. After the new update, there is no connection to the satellits. No able to manuel update, because there is no connection. See picture.
What to do??
Pictures placed in-line takes time to be available. Attach it (at the bottom of the msg compose window).
First, don't use amy Orbi mobile app for anything important. The idea if using a tool that depends on Wifi to set up or troubleshoot WiFi is nuts!
Power off the satellites. Connect to the router with an ethernet cable and use the Orbi's web interface at orbilogin.net or 192.168.1.1 (it is documented in the manual and many places how to do this).
Check functionality of the router, its firmware version, connected devices.There is no point in proceeding until the router works correctly at its ethernet and wifi functions.
If the satellite(s) are not showing up in the Orbi router web interface, power them on one at ta time and see if they get connected. If not, factory reset the satellite and see if it connects to the router.
Thanks very uch for this. Problem is that I simply can't get into the router – even by ethernet. So have pretty much run out of options. I will give the ethernet one more try, fingers crossed.
- Update Friday last via App. Unstable and network drops/ fails randomly. What can I do to correct?
Cubuff wrote:
Update Friday last via App. Unstable and network drops/ fails randomly. What can I do to correct?If doing a Factory Reset and reconfiguring does not help, the only other option is to download a previous firmware and install it manually.
https://www.youtube.com/watch?v=cMw4ePACgc4
There seem to be a lot of posts that start out: "I updated firmware using the app, and.... (something bad happened)"
I have wired backhaul. After attempting 2.7.2.104 update, both of my satellites appeared at the same IP address (192.168.1.250) in the Orbi router "connected devices", under connected satellites. (problem right there..) However, none of my devices would connect to any Sat via WiFi. (Everything within range was connected directly to the router). The router itself appears to work. But the satellites went to the slow white pulsing ring and stay there forever.
Attempting a direct web connection to 250 results in "refused connection". Even after turning off one of the satellites (conflicting IP address).
So next I tried the TFTP update method on one of the Sats. Isolated on a dedicated PC ethernet connection with manual IP. TFTP would not work, no blocks were transmitted. The sat would configure itself to IP address 250. I could PING it from the PC. But I could not open it's web pages, and I could not upload the FW file via TFTP. Tried resetting the sat numerous times and no dice.
So both satellites are "stuck" with the slow pulsing white ring. I ran a WiFi scan utility on my phone, and I don't even see any WiFi at all coming from the satellite. So whatever the FW is doing, it hasn't gotten to the point where it enables WiFi yet.
Any suggestions for the next step, now that Netgear has broken my network?
I bought the router and it came with FW version v.2.0.0.74. The router / APP is not detecting any updates as available in web interface. Its been just a day with the mesh setup. So far its ok. Is there anything I am missing out without the latest updates. I read somewhere in the forum that we have to go through sequentially for the updates which seems to be a lot and time consuming. If I try updating directly to the latest version, will it fail due to some file size limit or so?
You should be able use v2.2.1.212 on the RBS first then on the RBR. I would then try v2.3.5.30 on the RBS then RBR lastly.
Then you should be able to go to v104 on the RBS first then on the RBR lastly.
You'll need to use a wired PC or laptop and web browser. IE11, Edge or Firefox.
Download the FW files here before starting:
https://www.netgear.com/support/product/RBK50.aspx#download
You can connect to the RBSs web page and send the FW files directly to the RBS.
arunprasanth wrote:I bought the router and it came with FW version v.2.0.0.74. The router / APP is not detecting any updates as available in web interface. Its been just a day with the mesh setup. So far its ok. Is there anything I am missing out without the latest updates. I read somewhere in the forum that we have to go through sequentially for the updates which seems to be a lot and time consuming. If I try updating directly to the latest version, will it fail due to some file size limit or so?
FURRYe38 wrote:You should be able use v2.2.1.212 on the RBS first then on the RBR. I would then try v2.3.5.30 on the RBS then RBR lastly.
Then you should be able to go to v104 on the RBS first then on the RBR lastly.
You'll need to use a wired PC or laptop and web browser. IE11, Edge or Firefox.
Download the FW files here before starting:
https://www.netgear.com/support/product/RBK50.aspx#download
You can connect to the RBSs web page and send the FW files directly to the RBS.
arunprasanth wrote:I bought the router and it came with FW version v.2.0.0.74. The router / APP is not detecting any updates as available in web interface. Its been just a day with the mesh setup. So far its ok. Is there anything I am missing out without the latest updates. I read somewhere in the forum that we have to go through sequentially for the updates which seems to be a lot and time consuming. If I try updating directly to the latest version, will it fail due to some file size limit or so?
Posts like this advising people to upgrade firmware should be viewed with caution. Lots of firmware problems reported here every day
Thanks everyone for your great feedback, in as much as I love Netgear this issue with upgrading there devices is a common one. Sadly they really don't have any solid competition to light a fire under them to get it right the first time.
I run a small successful busines from my home that relies 99% on my internet connectivity my orbi is still on V2.5.1.16 its super stable and until I can confirm that this new firmware is not going to put me out of business, I'll stay on V2.5.1.16
