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
I've had to put my Orbi into Acess Point mode to get it to work properly on this firmware. There are all kinds of routing issues. At first I thought it was because I was doublr-nat'd, but after bridging my modem and disabling all firewalls/routing on my cable modem, I experienced all the same issues and was only able to browse successfully after downgrading.
Only after re-enabling all the routing on the cable modem and placing the Orbi in AP mode did it start to work properly. I am okay with the performance. I am typing this from a desktop PC that is hard-wired into a satellite. My understanding is it still uses the back channel to communicate so I am not losing much:
Pinging orbilogin.com [192.168.0.5] with 32 bytes of data
Reply from 192.168.0.5: bytes=32 time=3ms TTL=64
Reply from 192.168.0.5: bytes=32 time=2ms TTL=64
Reply from 192.168.0.5: bytes=32 time=3ms TTL=64
Reply from 192.168.0.5: bytes=32 time=2ms TTL=64
Reply from 192.168.0.5: bytes=32 time=1ms TTL=64
Reply from 192.168.0.5: bytes=32 time=4ms TTL=64
Reply from 192.168.0.5: bytes=32 time=2ms TTL=64
Reply from 192.168.0.5: bytes=32 time=3ms TTL=64
Ping statistics for 192.168.0.5:
Packets: Sent = 8, Received = 8, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 4ms, Average = 2ms
I am getting my advertsised internet speeds up and down and pinging 17ms to the speedtest server. This is not an ideal setup for me, I would prefer to use the Orbi's routing capabilities, but they are simply not working with this firmware.