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
What I've gathered from reading this thread and my own experience is that v1.11 is broken for some, and v1.12 is broken for others. For me, v1.11 and v1.12 are both fine in router mode, but v1.11 is broken in AP mode. V1.12 is working well for me in AP mode, aside from the functionality that Netgear has removed (like disabling 2.4GHz. wireless and being able to disable auto-update for the firmware if needed). This makes it virtually impossible to go back to a previous version and have a stable router, since the Orbi will just auto-update itself for most people.
So a situation has been created where if the latest firmware doesn't work for you, then you're pretty much out of business. It would be helpful if Netgear would give out some useful information like what domains to block to prevent the Orbi from finding new firmware on it's own, and settings (using telnet) that will prevent the firmware from auto-updating. But to this point, they've avoided giving out any work-arounds, as far as I've seen.
The time has passed for Netgear to expect it's customers to just wait for the next firmware. It's time for Netgear to give out the information needed for users to work around these problems. While this isn't a Netgear support forum, it's a user peer-to-peer forum, Netgear clearly monitors this forum, and needs to help it's users. If they don't feel that they should help their users just because they need help, then they should help because having all these public postings can't be good for Netgear's business. If I had read this thread before getting an Orbi, I'm pretty sure I would have found a different solution for my router needs. This has gone on way too long.
I just purchased the Orbi RBK50 and found these forums.
Before setting everything up, I downgraded the firmware on both router and satellite.
I then used https://community.netgear.com/t5/Orbi/Firmware-V1-12-0-18-Discussion/td-p/1320421/page/5 to stop the auto update from happening.
Everything is runnning fine for me. My auto update settings were slightly different than the post above and after commiting the NVRAM and performing a reboot, one of the settings when back to enabled. I then set it to disabled for a 2nd time, commited the NVRAM and rebooted 10+ times and it's been running perfect for a few nights now.
Thanks dazzywazzy, that's good to know. I'll have to re-check the NVRAM settings after doing some reboots to make sure the auto-update stays off.
dazzywazzy wrote:Everything is runnning fine for me. My auto update settings were slightly different than the post above and after commiting the NVRAM and performing a reboot, one of the settings when back to enabled. I then set it to disabled for a 2nd time, commited the NVRAM and rebooted 10+ times and it's been running perfect for a few nights now.
A few nights is not really long enough. Tell us when it's been more than a week without an update.
Sure thing.
I've been monitoring a few times a day.
FWIW my NVRAM settings which I changed are belowRouter:
orbi_auto_upgrade=0
orbi_auto_upg=0
auto_update=0
auto_check_for_upgrade=0
auto_upgrade_flag=0
fwupgrade_Method=MANUAL
Satellite:
auto_check_for_upgrade=0
auto_upgrade_flag=0
fwupgrade_Method=MANUAL
Settings I'm monitoring but haven't changed as I don't know the outcome
Router:
detect_update=899798033
manual_upgrade=109908109666630
green_download_upgrade_stat=0
upgrade_satellite_image=109908109666630Satellite:
upg_status=1
upgrade_check=49902240
Thanks dazzywazzy! That's plenty more settings than I changed - and I didn't change any settings on the satellite since I didn't know that was necessary. I'll give those a shot and see what happens... (or _doesn't_ happen, as I'll hope) :)
root@# nvram show | grep auto_*
vpn_access_mode=auto
wl_auto_antenna=1
set_auto_agreement=0
orbi_auto_upgrade=2649318224781159
ipv6_autoConfig_dns_assign=0
auto_upgrade_flag=0
ipv6_autoConfig_dns1=
ipv6_autoConfig_dns2=
upnp_enable_autoScan=0
ipv6_auto_dns_assign=0
orbi_auto_upg=0
bas_auto_conn_flag=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_update=0
auto_check_for_upgrade=0Mine has been stable for several weeks on 1.11.0.20 (only difference here is Orbi is in AP mode with a R7000 ahead of it with downloads.netgear.com blocked - perhaps thats it).
Mine has been stable for a week now.
Router mode, no websites blocked. NVRAM config I did was posted previously. Hopefully it can help some users.
