NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
2.1.2.18
5 TopicsThe 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 =0Orbi firmware version numbers
Looking at the support site, I see there is new firmware available for the Orbi. My concern is that the "new" version is listes as 2.0.1.4 whereas the version listed as being the most recent older version (the one I am running) is 2.1.2.18. I'm either confused or there is a numbering issue here. Shouldn't the newer version have a higher revision number? One would think that 2.1.2.18 would be newer than 2.0.1.4. What gives?SolvedI just had an epiphany... hear me out on 2.1.2.18
So you can read through all my anger and rant on 2.1.2.18. I have started several threads on how horrible this has been. But someone wrote something that made me think why I may be having issues with this firmware and others are not. First, when I install this firmware, it completely breaks all my wired connections. I have a netgear switch and everything behind that switch including 2 hubs will not get an ip. My main computer the same, I can't even log into the router to downgrade it. This all works perfectly fine with 2.1.2.16. But since Netgear has forced the update on me 3 times, I have confirmed everytime it is complete chaos when it updates, without fail. But one thing I didn't mention was that one of my orbi satellites is hardwired through the switch and hub that goes all the way out to the garage. I believe I read someone said their backhaul that was wired was giving them fits on 2.1.2.18, but when they disconnected it, everything was ok. So if anyone from Netgear is listening, maybe test that out. The weird thing is that 2.1.2.16 is just fine with the same configuration. But 2.1.2.18 just cripples my network. The symptoms are similar to that endless network loop if you plug a device into itself on the network. So I suspect something between the new firmware and hardwiring the satellite my be the issue. I cannot confirm as I am UNWILLING to go through the hell of 2.1.2.18 again, until the router forces it upon me again. I did change the NVRAM to tell it not to update, but it seems like it still did anyway the last time. The other funny thing I noticed on this new firmware is that I have a wired HP printer an x576. I gave it a DHCP address to make it static since I scan to it over the network. When I did it the Orbi firmware recognizes it as a sattelite. It lists under the attached devices sattelite. I don't think that is supposed to happen, once again Netgear, if you are monitoring this stuff (which I sincerely hope that you are, because you provide crap for customer service, so at least pay your people to read through all of us going through hell to troubleshoot for you), maybe you can test and check out those 2 issues. Anything behind my switch is completely dead everytime I upgrade to 2.1.2.18. I just also have that satellite plugged in and just thought of that when someone else posted about it. I didn't even get into my anger about Orbi and Google with all the stuff going on, I am just trying to solve one crazy issue at a time. It is very annoying to pay 1000.00 for a mesh system that I have to spend this much time diagnosing for a company who will not provide me any customer support.. very annoying. Get your stuff together Netgear... stop releasing half a$$ed firmware updates that are ridden full of bugs, and give customers the option to opt out of auto updates without having to telnet into NVram settings on the router. That is ridiculous.RBS50 Firmware Version 2.1.2.18
I don't know where to begin. I have never been so angry at a company. I don't know whether to blame Google / Oreo / Google Home / Chrome Cast... but I DEFINITELY blame Netgear in all of this. I have had nothing but complete trouble for the last 4 firmware updates. I finally after BREAKING MY ENTIRE SMART home, including lights, doorbells, garage door, motion sensors, sonos, Wi-Fi... I got a relatively stable release with 2.1.2.16. We have apple and android at home, we also have nest security cameras. I have a couple Logitech security cameras that use power over ethernet, and have a switch (hub) and lots of wired connections. 2.1.2.16 ended up ok, but that was really only when we disconnected the pixel 2. At first this firmware seemed to work with pixel 2 then it got more and more unstable, with the pixel connected it would slowly start making the network flaky. The previous firmware I couldn't see attached devices, the satellites would not update or connect, I had to start from scratch etc. every time. Then last night it said 2.1.2.18 fixed the high CPU issue (which I assume means the crazy android mess). So, like an IDIOT I updated. Immediately I noticed I had no Wi-Fi, I figured it just needed to all reboot, NOPE nothing, I couldn't even get a wired connection to get internet, I got so frustrated I went to bed. I had to connect my main computer directly to my cable modem and download the previous firmware. Then I had to disconnect my switch/hub and everything from the Orbi router, and just connect my computer, to downgrade the firmware to everything. Then I had to do a complete network reset including the cable modem, and wait for it all to come back up. So slowly I think I am back to as stable as I have had. What I don't understand is that this is all a mixed bag. Some people say they have the same exact issues as I do, some say this has been very stable. I know android is pushing some fix. Right now, we have all pixels and google homes and chrome casts disconnected from the network so they don't break it. I don't know whether to blame/class action sue google or Netgear or both for being incompetent companies. No product should take down your entire network like this. Orbi needs to get their stuff together, no firmware update should disconnect your own product satellites. That makes no sense, that is instability among your OWN products. No firmware update should ever break a WIRED connection to your computer... what the heck Netgear? You guys have to stop experimenting with us on these firmware updates. RELEASE STABLE FIRMWARE. You don't just break people's connection to the internet, you break our home security, our smart home devices including garage doors etc. You literally make our life hell when you release this stuff. I know there are thousands or millions of combinations of stuff on networks that may work for some people on some firmware, but providing home networking cannot be this difficult, I don't understand how a device connected to a network can break the entire network or communication between your product satellites or router or wired connections that seems like it is on you! I know there is a bunch of security stuff you are also dealing with, but I am not updating anything anymore, I don't care if you promise me that it will be the best experience in the entire world. I DON'T TRUST YOU ANYMORE. Your product is junk I am convinced. I just need to smash this stuff up and go to a different company, I have owned at least 10 different company’s routers over the years and never been so frustrated. When your Orbi system works, it works perfectly when it breaks (which is the majority of the time) it is useless JUNK.