NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
rhester72
Jul 11, 2017Virtuoso
Firmware V1.12.0.18 Discussion
This does indeed appear to be based on (identical to?) the last private beta V1.12.0.16 and has been released to the public. Hope it helps!
Guest mode AP isolation finally works 100% over IPv4...
- Jul 11, 2017
New Features and Enhancements:
- Supports ReadySHARE Printer for Orbi devices that are equipped with a USB port
- Updated the OrbiOS API to v3.14
Bug Fixes:
- Fixes the iOS disconnection issue.
- Fixes the Dropcam disconnection issue.
- Fixes the convergence issue when an Ethernet connected device moves from one Orbi to another.
- Fixes the issue where the Orbi app can’t find the Orbi router if the router is using IPv6 and is in AP mode.
- Fixes the issue where the Orbi app can’t display more than 20 connected devices.
- Fixes the issue where the installation assistant might not display if the device is connected to the Orbi network wirelessly.
- Fixes the issue where the 2.4 GHz backhaul setting is disabled if the fronthaul MU-MIMO and TxBF is disabled.
- Fixes the issue where IPv6 devices on the guest network can access the Orbi router’s web GUI.
- Includes security fixes for the following security vulnerabilities:
PSV-2016-0133, PSV-2017-0607, PSV-2017-0615, PSV-2017-0736, PSV-2017-2190
Download Link:
RBR50 - http://www.downloads.netgear.com/files/GDC/RBK50/RBR50-V1.12.0.18.zip
RBS50 - http://www.downloads.netgear.com/files/GDC/RBK50/RBS50-V1.12.0.18.zip
cyberprashant
Jul 27, 2017Luminary
Butch1326 wrote:To stop the Orbi from installing the updated firmware automatically follow the steps below.
Perform these step after you downgraded the firmware to a prior release.
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
^^^^ This works great. Couple tips
1. There's another parameter not listed:
orbi_auto_upg
orbi_auto_upgrade
Follow the same instructions as above for this parameter.
2. Also download the downgraded firmware and have it all ready.
3. load the instructions of page 5 of this thread in separate tabs and have your telnet client ready
4. Then disconnect the wan side (cable modem side) of the orbi so it doesn't immediately try to download the new firmware post-downgrade (you will lose internet connectivity so make sure you have a telnet client, firmware and these instructions from page 5 all loaded up in a browser ahead of time)
5. Be very quick in the following procedures: a) downgrade the firmware (I did the satellties first, then router) followed by the b) enable telnet in the orbilogin.com/debug.htm as above and c) issue the actual telnet commands. After everything is sucessful hook wan/cable modem side ethernet cable back in a few minutes later.
Netgear hurry up and fix this!!
Basura3d
Jul 28, 2017Guide
Was so happy that I could go back to 1.11.00.20 but today I started getting a lot of disconnects and saw that the stupid router auto updated itself bacck to 1.12.00.18. This seems super advanced for a no techy dude that just wants a functioning firmware and a simple checkbox if you want to auto update. My wife keeps asking me why I'm in a bad mood and then, is it the wifi again?
- RogerSCJul 28, 2017Virtuoso
Since I haven't seen this posted on this thread, I thought that I'd post it. Here are the telnet/ssh commands that are working for me on my Orbi to keep it from auto-reflashing the latest firmware release. This has been working for me for several days now, keeping me on the previous to the latest version of the firmware (V1.11.0.20), and was given to me by an inside source:
shell> config set auto_update=0 OR config set auto_check_for_upgrade=0
shell> config commitThe "shell>" above represents the command line shell prompt from the telnet or ssh session. The key thing to notice about this is that you're using "config set" and "config commit" commands instead of "nvram set" and "nvram commit" commands.
Please try this, it works.
- RogerSCJul 31, 2017Virtuoso
RogerSC wrote:Since I haven't seen this posted on this thread, I thought that I'd post it. Here are the telnet/ssh commands that are working for me on my Orbi to keep it from auto-reflashing the latest firmware release. This has been working for me for several days now, keeping me on the previous to the latest version of the firmware (V1.11.0.20), and was given to me by an inside source:
shell> config set auto_update=0 OR config set auto_check_for_upgrade=0
shell> config commitThe "shell>" above represents the command line shell prompt from the telnet or ssh session. The key thing to notice about this is that you're using "config set" and "config commit" commands instead of "nvram set" and "nvram commit" commands.
Please try this, it works.
Okay, my Orbi auto-flashed today, after about a week. So this tip from Netgear is just not good enough. Sorry to mislead folks, I really thought that this had solved my problem for good and all.
Back to the drawing board.
- JMU1998Jul 31, 2017Luminary
A simple check box to toggle between on/off for auto updates is needed apparently it will take an act of god for it to happen.