NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
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...
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
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 commit
The "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.
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.
JMU1998 wrote: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.
Yes, it would be easy to put in an "Advanced Mode" or a hidden mode if they insist, maybe via the debug page they already have, that would allow turning off auto-update, and also allow the 2.4GHz. radio to be disabled. I'm fine with the current behavior being the default, but I hate to have to wait for Netgear (or any other router manufacturer) to recognize a bug and then reproduce and fix it. This for the unlikely case that they should put out a version of firmware that doesn't work well with my wireless clients. And I should be able to disable the 2.4GHz. wireless signal if I'm not using it...I don't need to make life harder for my neighbors. There are reasons why these are usually part of the web admin interface for routers, users need to have at least that degree of control available.