NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RBR/RBS 50 firmware 2.7.3.22
New firmware is incoming this week I have been told. No release notes details yet but may fix either device list issues or link rate issue. Keep an eye on https://www.netgear.com/support/product/RBK50.aspx#download
65 Replies
Replies have been turned off for this discussion
You know pablo,
at this point, I think I will wait this one out. I normally will not wait for the firmware auto update cycle and instead will opt for manual install. Not so anymore. Router and sat. working well.
HELP!, mY RBR50 and 4 RBS50 updated to 2.7.3.22 and now no device will stay on the network. How do I roll back to the previous version 104? It was solid?
The current posting on the web site is incorrect. The zip file for the router RBR50 is fine the file for the RBS50 satellite contains the RBR50 image file as well. The RBS50 image is missing.
I spoke with support and was disconnected during the call and no one has called back so ....
So I am currently half updated. (anyone aware of any pit falls running hybrid on firmware revs until update is posted correctly.
- I have just noticed that too! I have emailed my contact directly in support to make them aware of the issue and asked them to fix it ASAP.
In case anyone else reading this thread is interested:
Bug Fixes:
- Fixes the DNS query failure issue that occurs when traffic meter and daylight saving are enabled
Security Fixes:
- This firmware addresses security vulnerabilities.
RASB pablohoney They fixed the issue with the mismatched firmware. The downloads now contain the correct images. Will probably wait a couple days to install so I can see some feedback on it first, but I've looked in the zip files and they now contain the proper images.
Enable telnet in Debug mode is missing
PCSP wrote:Enable telnet in Debug mode is missing
I think I use correct version (I downloaded 10 July 2021 - and got RBR50-V2.7.3.22.img, RBS50-V2.7.3.22.img) and everything is OK except missing enable telnet in Debug mode.
I will try download it again and test it
$ md5sum *V2.7.3.22*
09a78255fb2ce64d065eb59805ca3750 RBR50-V2.7.3.22-20210710.zip
09a78255fb2ce64d065eb59805ca3750 RBR50-V2.7.3.22-20210805.zip
ad86562c89a82678e366bb28fdec218b RBS50-V2.7.3.22-20210710.zip
ad86562c89a82678e366bb28fdec218b RBS50-V2.7.3.22-20210805.zip
Same in RBR40/RBS20
Please post here for any 20 or 40 series issues:
Please give details.
Thank you.
dburg wrote:
Same in RBR40/RBS20
RBR50 + 2 x RBS 50 firmware just upgraded from 2.7.2.104 to 2.7.3.22
Seems it broke my setup without me clicking to update (I read in another thread that Netgear forced an update - seriously??? WTF??? Is that serious? In the middle of a pandemic, break everyone's wifi while they are working from home?)
Issues found:
* wired backhaul no longer working, only connects using wirelsss (which is poor quality, thus the reason for the wired backhaul). MAJOR ISSUE
* using Android "Netgear Orbi - WiFi System App" version 2.10.6.1635 (the latest, released 23 July 2021) shows both RBS50 as disconnected (red lines), whereas logging into the router itself shows both RBS50 connected using wireless backhaul.
* [subjective] wireless connectivity is poor when via the RBS50 now, previously it was rock solid using v2.7.2.104 with wired backhaul.
* no "enable telnet" option, so no way to properly diagnose or fix
Can I revert to the 2.7.2.104 ? How? Will it "auto-upgrade" itself again? And can I avoid an auto-upgrade by blocking some particular DNS addresses? (Orbi is inside another network).
Try to power OFF the RBR and RBS for 1 minute. Pull the power cord as well. Turn back ON. Factory reset the RBR and RBS and setup from scratch. Let us know if this bridges back wired back haul.
Is the RBS directly connected to the back of the RBR or is there a switch in between?
scubabuddy wrote:RBR50 + 2 x RBS 50 firmware just upgraded from 2.7.2.104 to 2.7.3.22
Seems it broke my setup without me clicking to update (I read in another thread that Netgear forced an update - seriously??? WTF??? Is that serious? In the middle of a pandemic, break everyone's wifi while they are working from home?)
Issues found:
* wired backhaul no longer working, only connects using wirelsss (which is poor quality, thus the reason for the wired backhaul). MAJOR ISSUE
* using Android "Netgear Orbi - WiFi System App" version 2.10.6.1635 (the latest, released 23 July 2021) shows both RBS50 as disconnected (red lines), whereas logging into the router itself shows both RBS50 connected using wireless backhaul.
* [subjective] wireless connectivity is poor when via the RBS50 now, previously it was rock solid using v2.7.2.104 with wired backhaul.
* no "enable telnet" option, so no way to properly diagnose or fix
Can I revert to the 2.7.2.104 ? How? Will it "auto-upgrade" itself again? And can I avoid an auto-upgrade by blocking some particular DNS addresses? (Orbi is inside another network).
Doing the full power off for some time (multiple times, I'd already tried it when I posted) eventually got me to something that recognised the Ethernet backhaul. Awaiting feedback on acceptance factor in the household, with 4~5 simultaneous wireless video conferences at any one time during the week with everyone working and schooling from home, it should become evident soon...
scubabuddy wrote:RBR50 + 2 x RBS 50 firmware just upgraded from 2.7.2.104 to 2.7.3.22
* no "enable telnet" option, so no way to properly diagnose or fix
Hi there,
Facing the same issue, I could restore telnet access using the updated version of telnet-enable2.py, enabling back Telnet using V2.7.3.22: https://github.com/bkerler/netgear_telnet
I could push all my existing custom configuration (upnpc, automation, etc.) from here.
Hope this will help you as well...
mmz06 wrote:
scubabuddy wrote:RBR50 + 2 x RBS 50 firmware just upgraded from 2.7.2.104 to 2.7.3.22
* no "enable telnet" option, so no way to properly diagnose or fix
Hi there,
Facing the same issue, I could restore telnet access using the updated version of telnet-enable2.py, enabling back Telnet using V2.7.3.22: https://github.com/bkerler/netgear_telnet
I could push all my existing custom configuration (upnpc, automation, etc.) from here.
Hope this will help you as well...
Hi,
The tool sounds promising. However I wonder if you can clarify
- How do you find the MAC address of br0 interface?
- It says the tool is for Netgear Orbi LBR20. Are you using LBR20? If not, did you need to make any changes to get it working with your Orbi router?
Thank you very much .
Joseph
Well in case anyone was wondering how I just recently (Christmas 2021) solved the problem of my Orbi updating to 2.7.3.22 and thus breaking wired backhaul and having various ongoing app issues...
Firstly a recap:
- wired backhaul became unreliable at best after Netgear forcibly updated my stable 2.7.2.104 Orbis to the crappy 2.7.3.22 firmware.
- The auto-update happened without my approval, and doesn't have any way of being stopped.
- The Orbi App kept reporting only one Satellite connected, but showed devices (that were working, albeit unreliably) connected to the other Satellite when you clicked into that Satellite (i.e. the app was broken too)
- No "enable telnet" option so the ability to diagnose & fix has been removed.
So in summary, Netgear forcibly updated to unreliable software, with no way back (just auto-updates again) and destroyed a previously functional network.
Now the solution:
- Get Officeworks to pricematch (and minus 5%) Bing Lee's current $329 offer on a Google Nest Wifi 3 Pack (router + 2 points). https://www.officeworks.com.au/shop/officeworks/p/google-nest-wifi-3-pack-1-router-and-2-points-sygg1m2v3 and https://www.binglee.com.au/products/google-ga00823-nest-wifi-3-pack-one-router-and-two-points (valid to end of 2021)
- Rock solid performance, zero dropouts. I bought 2 of these 3-packs and also used the second Google Nest Router as a "point" (wired backhaul between the second Nest WAN to the "main" Nest LAN and it "just works")
- The SONOS (4 units all latest firmware with their wireless disabled, connected via a switch to the LAN of the Google Nest Wifi) also now just works consistently, instead of fighting with the Orbit and going randomly offline (suspect something to do with Spanning Tree Protocol, worked with 2.7.2.104 but another thing that the Netgear auto-update broke)
- WAF has moved to 100% and the kids have STFU about dropouts. So Netgear and their forcibly-updating Orbis can GaGF.
Worth every cent (the Google Nest Wifi that is). Yeah, there is nothing to configure, no knobs to play with, no telnet console (to my knowledge) etc etc. But unlike the Orbi with the 2.7.3.22 firmware, the Google equipment actually just works, so no real need.
- I just want to confirm because I've been racking my brain on this...half my devices on the attached devices list and the Orbi app show "offline" even though they are NOT offline.
This is a known issue on V2.7.3.22?I don't believe it's an issue exclusive to 2.7.3.22 as I had the same problem with previous firmware versions. I suppose a factory reset might resolve the issue, but it's more of an annoyance for me more than anything so I haven't bothered.
Yosmany21 wrote:
I just want to confirm because I've been racking my brain on this...half my devices on the attached devices list and the Orbi app show "offline" even though they are NOT offline.
This is a known issue on V2.7.3.22?- It may have been there before the update to 2.7.3.22, I didn't notice it until after I updated.
This update gave me more issues than any I've ever had. Duplicate IPs creating conflicts. One the saltellites randomly disconnects and reconnects, reduced internet upload speeds.
I figured having 50% of my devices showing as "offline" or not present on the network at all even though the are online or connected was just a side effect of a really bad firmware update.
Has anyone confirmed that a full factory reset fixes the issue?
The current posting on the web site is incorrect. The zip file for the router RBR50 is fine the file for the RBS50 satellite contains the RBR50 image file as well. The RBS50 image is missing. I spoke with support and was disconnected during the call and no one has called back so . So I am currently half updated. (anyone aware of any pit falls running hybrid on firmware revs until update is posted correctly.
Strange. The *.img file inside the *.zip has the correct name for a satellite (RBS50...) Are you saying that the Orbi satellite refuses this file?
The new firmware has come out and again we are having intermittent dropping issues. I have tried to revert to an older code and set the autoupgrade parameters to 0 but the router still upgrades during the night. This upgrade also takes away the telnet option from the debug menu. I am not happy with having to work on this issue about every other firmware update. Netgear can you help your user community out and get this issue fixed.
What do you mean by "intermittent dropping issues"? What is happening?
Top ring LED turn ON? if so, color of LED?
What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?
Has a power off for 1 minute then back ON with the ISP modem and router been performed since last update?
Be sure to restart your network in this sequence:
Turn off and unplug modem.
Turn off router and computers.
Plug in and turn on modem. Wait 2 minutes for it to connect.
Turn on the router and wait 2 minutes for it to connect.
Turn on computers and rest of network.
Try this version of FW?https://community.netgear.com/t5/Orbi/Missing-Connected-Devices/m-p/2142349/highlight/true#M126110
JusttestFW wrote:
The new firmware has come out and again we are having intermittent dropping issues. I have tried to revert to an older code and set the autoupgrade parameters to 0 but the router still upgrades during the night. This upgrade also takes away the telnet option from the debug menu. I am not happy with having to work on this issue about every other firmware update. Netgear can you help your user community out and get this issue fixed.
The connectivity drops out and the light on the router goes white and strobes for about 2 min then it picks back up again. I have tried everything in your list multiple times. The ISP is directly connected to the ORBI and receives the IP address from the ISP. I use pingplotter to watch when it drops and to see how long it stays down. I have had several different versions of firmware that have worked just fine and several versions that have the intermittent drop issue. This last update looks like they are trying to cut out our ability to downgrade and turn off auto update.
