NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
The 2.1.2.18 nightmare
I won't bother going through how angry I am at Netgear for this firmware MESS (I already have in several posts) since they don't bother offering ANY customer support after they screw you out of your money. I just wanted to tell everyone if you hate 2.1.2.18 as much as I do (well hate isn't the word, it just physically BREAKS my entire wired network... nothing wired has a connection NOTHING. I verified it 2 times because I reverted back to 2.1.2.16, when it was all working ok. Then it decided last night to RE-DOWNLOAD 2.1.2.18. You would think if you manually tell a product to revert back it wouldn't just re-do it. This is so dumb, my computer is hooked to a switch, that is connected to Orbi... when it updates to 2.1.2.18 I have to disconnect my computer from the switch because it breaks EVERYTHING on the switch nothing gets an ip... I have to connect directly to the orbi from my computer, I have to disconnect all the other wired connections to the orbi. Then I downgraded the firmware ONCE again, then I telnet into the router to change the NVram to not let this piece of crap update itself. That is my solution Netgear. A consumer had to do all that stuff because your firmware BREAKS everything. This started with me being angry at Google for breaking everything, now I blame netgear. It isn't my switch or any of my wired stuff, because it all magically works perfectly on 2.1.2.16. But the second I upgrade it all breaks, I even did the factory reset 2x, nothing wired works.. the funny thing is my switch is a netgear switch too... I have NEVER in my life had such a complicated product to keep running. In case anyone else is dealing with the same problems, below is how to telnet and stop it from updating. This is my only solution, I have absolutely 0 ZERO confidence in any firmware update from Netgear... based on a 100% failure rate:
1) Launch your favorite web browser and go to <Router IP Address>/debug.htm
2) Login <username> <password> when prompted
3) Check Enable Telnet
4) Start a Telnet session. I use Putty. Enter the <Router IP Address> Telnet is using port 23
5) You can skip this step if you like. I am calling it out for illustration purposes only...
Type nvram show | grep auto_* <ENTER>
You will see a list similar to this:
root@RBR50:/# nvram show | grep auto_
vpn_access_mode=auto
wl_auto_antenna=1
set_auto_agreement=0
orbi_auto_upgrade=1
ipv6_autoConfig_dns_assign=0
ipv6_autoConfig_dns1=
ipv6_autoConfig_dns2=
upnp_enable_autoScan=0
ipv6_auto_dns_assign=0
bas_auto_conn_flag=0
orbi_auto_upg=0
autofw_port0=
ipv6_auto_dns1=
ipv6_auto_dns2=
qos_auto_bandwidth=0
green_enable_autorefresh_status=0
enable_dev_auto_refresh=1
wl_rate=auto
auto_check_for_upgrade=1
auto_update=1
root@RBR50:/# root@RBR50:/#
The 3 configurations highlighted above you will want to update the value from =1 to =0
orbi_auto_upgrade=1
auto_check_for_upgrade=1
auto_update=1
6) To update run the following commands:
nvram set orbi_auto_upgrade=0 <ENTER> (no spaces after set)
nvram set auto_check_for_upgrade=0 <ENTER> (no spaces after set)
nvram set auto_update=0 <ENTER> (no spaces after set)
7) Type the following commands to confirm the 3 configurations are set to =0
nvram show | grep orbi_auto_upgrade <ENTER>
nvram show | grep auto_check_for_upgrade <ENTER>
nvram show | grep auto_update <ENTER>
8) After you confirmed the 3 configuration values are set to =0 then type nvram commit <ENTER> (this step will save the changes)
9) Type exit to terminate the telnet session
10) Go back to the <Router IP Address>/debug.htm web page and uncheck Enable Telnet
Please note within a day or so the Orbi will know there is an updated firmware release available but it will not automatically install it. If you do go back into a Telnet session after the Orbi knows there is an updated firmware release the configuration orbi_auto_upgrade will have a value greater than 1. That is okay. Do not change the value back to =0
43 Replies
Thank you so much for this. I am so frustrated with this flipping router. I'm working from home today and it's been rediculous. The reboots have kicked me off 2 conference calls and constantly interrupted work. I was just headed out to BestBuy now and will be purchasing Google wifi. I may try downgrading now that I have your instructions.. I can't believe how crappy their QA must be for these releases to be so bad.
Previous firmware link for those looking: https://www.netgear.com/support/product/RBK50#RBR50 (Orbi Router) Firmware Version 2.1.1.16
Thanks - wasn't as bad as I expected. Upon running the final nvram show | grep command, I noted there was another value that might need to be changed (I didn't change it).
orbi_auto_ upg=1
Does anyone know how to check if NetGear is going to fix the 2.1.2.18 release? I am having issues with my wired ethernet backhaul since the upgrade. I guess the only solution at this point is back out the upgrade? Is there an easy way to do this, or do I need to just download the 2.1.2.16 version and manually upload it? And then I guess turn off automatic upgrades?
I am assuming waiting for a fix in the next couple of days is pointless. My satellites are useless without ethernet backhaul at this point as the distances are too far for wireless backhaul.
Any plans on a new Beta Firmware coming out soon?
I upgraded my satellite and router manually, and have not had a single problem since then. Wireless devices nicely connect to the closest device and all it shown fine under connected devices. I’m doing a lot of high res music streaming through the house and – although I had disconnects and buffering issues prior to the 2.1.2.x, using the 2.1.2.10 (beta version) and now 2.1.2.18 all works great.
My nightmare ended and turned into a dream!
Gotta love someone with a Supertramp handle. Did you have any special methods of upgrading?? Aside from a lot of chatter here, a friend who also has an Orbi system said the upgrade took out his entire network, wired connections and all!
No special upgrade methods. I'm not a router specialist, so followed the upgrade instructions to the letter: first the satellite then the router. That's all.
Oh, and before I forget: I'm using the Orbi mostly with its default settings. Maybe these are the only ones tested before a FW gets released?
This is the worst router I have EVER purchased. Who is QCing these software updates? Constant reboots, devices falling off the network, I wish my return period was not over so I can get my money back. What a piece of S%it for a PREMIUM PRICE!
Just as I thought this can't get any worse, I found that after the factory reset the password on my satellite didn't update after the sync and remains the default one.
Really, Netgear?!
I have a 1 router + 4 satellites network: the 2.1.2.18 firmware update created a big mess. Satellite randomly loosing connection multiple time per day and router not able to maintain 1000M speed on WAN port. Router downgrades its speed to 100M few minutes after a reboot. I tried to diable all wireless fancy features such daisy chain: it did not help. I finally disabled auto-update via Telnet and downgraded everything to 2.1.2.16. So far so good but I am very disappointed considering how much money I invested on this system. I was considering the outdoor unit but I will not spend any more on this system.
For what it's worth I'm on 2.1.2.18 with the Google Play Services 11.9.75 beta on all android phones and it removed all reboots. My orbi has never been quicker. All fine here. The issue was Google, not Orbi for almost everyone's reboots.
https://www.apkmirror.com/apk/google-inc/google-play-services/google-play-services-11-9-75-release/
I had a tiny bit of trouble getting my satelitte to sync with the router on 2.1.2.18 but I left it be for about 10 minutes and it was fine after that.
TP-Link, Linksys, and others were all was able to patch against the Chromecast/Android issue, so yes, it's still Netgear's fault for the reboots
Netgear, since you can't seem to fix the Orbi, are you going to start issuing refunds? or exchanging everyone to Orbi Pros (which doesn't appear to have these problems, because you value business customers over regular consumers?)?
Here is my story: Installed the Orbi AC3000 12 days ago with firmward V2.1.2.16 and it had been stable. Woke up on a nice Sunday morning to find the entire home network down (including the 20 wired deviced out of 27 total). Rebooted the modem; nope. Connected laptop to modem; connection to internet OK. Rebooted router; nothing. At this point I removed the Orbi and reinstalled my old Netgear X4 router just to get internet access for a while. Later hooked the Orbi router back up; still not behaving. Rebooted the satallite; showed signs of life, but network down again. Unplugged the satellite from the ethernet backhaul; Problem located. Rebooted Satellite and let it connect using wireless backhaul; system back up and running. Hey, but I purchased this system specifically for the ethernet backhaul ! At this point I looked back to see what firmware I installed 12 days ago and realized I was the victom of a push update. Powered down the satellite and reconnected the ethernet cable and powered up; amazingly it works now... but I wasted several hours of a weekend. Is there a way to Op OUT of getting push firmware updates?
Instructions to disable automatic firmware updates can be found in the first post of the thread below.
I work out of town during the week, so when I came home this past weekend and saw there was a firmware update pending, I hit these boards to get a feel for how it was working. As there appeared to be much difficulty around the 2.1.2.18 firmware, I decided to look for a way to keep the update from happening automatically and came across this thread. Having familiarity with Telnet sessions and Putty, I followed the steps as outlined by the OP. I logged out and logged in to check the settings. I also found the ability to log in to the router while away from home. Note also that one of my two satellites was unable to download the firmware update, which I thought would have also prevented the auto-update from happening. Like many of us, I didn’t want a toasted network with me being away from home for the week. There would have been chaos.
I left for work, and from the hotel this morning I wanted to test out the remote access feature. Lo and behold I was able to attach the router from the hotel, and then noted that my firmware had been upgraded. Fortunately, the network appears to be running as I immediately connected to my TiVos remotely (hardwired via MoCA). I had wifey confirm by checking her laptop (wifi). I’m also happy to report that my wireless settings appear to of been preserved i.e. my custom SSIDs and passwords.
I did see two things of note however. First, the satellite that was unable to download the firmware is still listed as on the old 2.0.0.34 Software. This satellite is furthest from the router and when I come home this weekend I’ll move it closer and attempt update it. Or if everything is working, maybe I won’t :-). Also, on the interface the satellite that was updated shows the backhaul connection as poor. I wonder if there is a way to address this.
I guess im one of the lucky ones.
I was reading your message about lost time on Sunday fixing your orbi. It was like dejavu because the exact same thing happened to me and I did the exact same steps as you in the exact same order. There was one small thing that did not match your message, I lost time on the very next day Monday
Here is an update to my router/satellite reliability experience and firmware push updates.
About a month ago, while still running 2.1.2.18 my network went down for a random unknown reason. I fixed the problem by rebooting the satellite. This makes me suspicous that the satellite(s) reduce overall reliability of the network. At that point, since my satellite is within good signal strength of the router, I unplugged / abandoned the wired backhaul and went to wireless backhaul.
I do not have the Netgear app on my moble devices and did not receive or did not see the notice for the upgrade to 2.1.4.10. The push upgrade went smoothly without a network outage. I only noticed after checking this community and then confirming with orbilogin. We have since had a wall added in the exact center of our house. With the hope of improving overall network reliability, I am tempted to pull CAT5 wires to this point and only use the router without the satellite. The signal strength should be adequate. Would still have the advantage of a single wireless connection for both bands (instead of using a traditional dual band router). Reliability is very important to me as so many Smart Home devices depend on it while I am away. Thoughts?
cmftblynu wrote:I won't bother going through how angry I am at Netgear for this firmware MESS (I already have in several posts) since they don't bother offering ANY customer support after they screw you out of your money. I just wanted to tell everyone if you hate 2.1.2.18 as much as I do (well hate isn't the word, it just physically BREAKS my entire wired network... nothing wired has a connection NOTHING. I verified it 2 times because I reverted back to 2.1.2.16, when it was all working ok. Then it decided last night to RE-DOWNLOAD 2.1.2.18. You would think if you manually tell a product to revert back it wouldn't just re-do it. This is so dumb, my computer is hooked to a switch, that is connected to Orbi... when it updates to 2.1.2.18 I have to disconnect my computer from the switch because it breaks EVERYTHING on the switch nothing gets an ip... I have to connect directly to the orbi from my computer, I have to disconnect all the other wired connections to the orbi. Then I downgraded the firmware ONCE again, then I telnet into the router to change the NVram to not let this piece of crap update itself. That is my solution Netgear. A consumer had to do all that stuff because your firmware BREAKS everything. This started with me being angry at Google for breaking everything, now I blame netgear. It isn't my switch or any of my wired stuff, because it all magically works perfectly on 2.1.2.16. But the second I upgrade it all breaks, I even did the factory reset 2x, nothing wired works.. the funny thing is my switch is a netgear switch too... I have NEVER in my life had such a complicated product to keep running. In case anyone else is dealing with the same problems, below is how to telnet and stop it from updating. This is my only solution, I have absolutely 0 ZERO confidence in any firmware update from Netgear... based on a 100% failure rate:
1) Launch your favorite web browser and go to <Router IP Address>/debug.htm
2) Login <username> <password> when prompted
3) Check Enable Telnet
4) Start a Telnet session. I use Putty. Enter the <Router IP Address> Telnet is using port 23
5) You can skip this step if you like. I am calling it out for illustration purposes only...
Type nvram show | grep auto_* <ENTER>
You will see a list similar to this:
root@RBR50:/# nvram show | grep auto_
vpn_access_mode=auto
wl_auto_antenna=1
set_auto_agreement=0
orbi_auto_upgrade=1
ipv6_autoConfig_dns_assign=0
ipv6_autoConfig_dns1=
ipv6_autoConfig_dns2=
upnp_enable_autoScan=0
ipv6_auto_dns_assign=0
bas_auto_conn_flag=0
orbi_auto_upg=0
autofw_port0=
ipv6_auto_dns1=
ipv6_auto_dns2=
qos_auto_bandwidth=0
green_enable_autorefresh_status=0
enable_dev_auto_refresh=1
wl_rate=auto
auto_check_for_upgrade=1
auto_update=1
root@RBR50:/# root@RBR50:/#The 3 configurations highlighted above you will want to update the value from =1 to =0
orbi_auto_upgrade=1
auto_check_for_upgrade=1
auto_update=16) To update run the following commands:
nvram set orbi_auto_upgrade=0 <ENTER> (no spaces after set)
nvram set auto_check_for_upgrade=0 <ENTER> (no spaces after set)
nvram set auto_update=0 <ENTER> (no spaces after set)
7) Type the following commands to confirm the 3 configurations are set to =0
nvram show | grep orbi_auto_upgrade <ENTER>
nvram show | grep auto_check_for_upgrade <ENTER>
nvram show | grep auto_update <ENTER>
8) After you confirmed the 3 configuration values are set to =0 then type nvram commit <ENTER> (this step will save the changes)
9) Type exit to terminate the telnet session
10) Go back to the <Router IP Address>/debug.htm web page and uncheck Enable Telnet
Please note within a day or so the Orbi will know there is an updated firmware release available but it will not automatically install it. If you do go back into a Telnet session after the Orbi knows there is an updated firmware release the configuration orbi_auto_upgrade will have a value greater than 1. That is okay. Do not change the value back to =0
You are doing complicated this.
You need to setup using next next next, and orbi will do the best for you.
I dont' have any issue, i use default settings.
I have RBK50 kit for EU.
So RBR50 router is ok, no issue, but when i connect RBS50 using Europe country i have issue with 2.4Ghz /5Ghz.
What it did to fix satellite:
- i set RBR50 (router) to United States
- i set 2.4Ghz and 5Ghz channels to AUTO
- i checked Enable Daisy-Chain Topology
- i enabled BEAMFORMING
- i enabled MU-MIMO
- Fast-Roaming can be enabled or disabled as you wish.
- i did a reset to default factory satellite, then after reboot it connected automatically to RBR50 router.
What i saw:
- if satellite is close to router , it select 5Ghz
- if satellite is in same room but not near router, it select 2.4Ghz
- if satellite is in other room, it select 5Ghz , after i did previously steps.
What we need from netgear team is to let user separate 2.4Ghz and 5Ghz SSID and also a option where user can select bandwith between satellite and router:
for example Auto will select 2.4ghz if signal is lower than 5Ghz, 2.4ghz if user want 2.4ghz and 5ghz if user want 5ghz.
I get using satellite connected to router using wireless, then lan on satellite almost 700-800mbps on speedtest.
-----------
I tested this firmware using RBS50 on next room, between 1 wall, and i get also using wireless 650-700mbps.
So this is very good.
I don't see where i can reboot RBS50 satellite.
Next test was latency: between RBS50 satellite and RBS50 router i aget 0.4-0.7ms, but latency is between 0.5-0.7ms, and can get lower.
Note that MU-MIMO and beamforming is enabled.
--------
Name (SSID) yourname
Region United States
Channel 36(P)+40+44+48
Mode Up to 866.7 Mbps
2.4Ghz channel auto
5Ghz channel 36
WPA2-PSK [AES]
WMM enabled
20/40 Mhz Coexistence enabled
CTS/RTS 2347
Preamble automatic
Enable Daisy... checked
Beamforming -- enabled
MU-MIMO -enable
For me , this is working.You don't ever want the wireless backhaul to go over 2.4GHz, because there's no radio dedicated to it.
Update to my post above:
The disconnect problems with my satellites continued to grow worse. Got so bad that I found that my network performance of distant devices improved when I unplugged a nearby satellite.
I poked around for a while with the config pages. I discovered that even though my base station had auto-updated to 2.1.2.8 - contrary to its own configuration! - the base stations were running 2.0.0.74. This is weird, because I'm pretty sure that the base station reported that they had also been updated to 2.1.2.8...
I manually downloaded the 2.1.2.8 RBS50 firmware and pushed it to both of my satellites. So far, satellite performance has actually been quite good.
I'm not going to start hoping that I'm out of the woods, that my firmware troubles are over. The true test will be whether it's still holding up a week from now. But I am mildly encouraged by this initial experience, and others' reports of better experiences with this firmware.
I wonder why everybody seems to have problems with FW 2.1.2.18 as this is the only FW working w/o problems on my RBR20/RBS20. RBR20 is in AP mode and I need Ethernet backhaul and daisy chain option as I have armored-concrete in the ceiling between 1st (satellite) and 2nd floor (AP) and two simple switches between the AP and the satellite. Last week my whole network was down in the morning because AP and satellite had updated to 2.1.4.10. Downgraded both to 2.1.218 again, disabled auto update as described above and everything was fine.
Until today. Exactly one week after downgrading my Orbis were updated to 2.1.4.10 again automatically. And auto update is still disabled:
root@RBR20:/# nvram show | grep -E "orbi_auto_upgrade|auto_check_for_upgrade|auto_update" orbi_auto_upgrade=13064382 auto_update=0 auto_check_for_upgrade=0
Network was down again and I downgraded both to 2.1.2.18 again. Still wondering why they were updated automatically.
Did you try a reboot of the system or full factory reset and set up from scratch after it updated to v2.1.4.10?
Oceanwaves wrote:
I wonder why everybody seems to have problems with FW 2.1.2.18 as this is the only FW working w/o problems on my RBR20/RBS20. RBR20 is in AP mode and I need Ethernet backhaul and daisy chain option as I have armored-concrete in the ceiling between 1st (satellite) and 2nd floor (AP) and two simple switches between the AP and the satellite. Last week my whole network was down in the morning because AP and satellite had updated to 2.1.4.10. Downgraded both to 2.1.218 again, disabled auto update as described above and everything was fine.
Until today. Exactly one week after downgrading my Orbis were updated to 2.1.4.10 again automatically. And auto update is still disabled:
root@RBR20:/# nvram show | grep -E "orbi_auto_upgrade|auto_check_for_upgrade|auto_update" orbi_auto_upgrade=13064382 auto_update=0 auto_check_for_upgrade=0
Network was down again and I downgraded both to 2.1.2.18 again. Still wondering why they were updated automatically.
