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

Forum Discussion

The 2.1.2.18 nightmare