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
scornwell
Aug 02, 2017Apprentice
Can we get anything from you guys or is dumping Orbi the only way to resolve these issues?
Traz_13
Aug 02, 2017Star
Running into problems with 1.12.0.18. We have the RBR50 and RBS50s. Certain clients started dropping off of our wireless pretty frequently and it is causing a huge disruption.
After the issues started showing up, I tried various configurations between router and sats. I have tried factory resetting all devices and force installing the new firmware update one at a time without any change. Tried turning off guest wifi and toggling beam forming & MuMIMO. WIth the same dropping problem. Even tried bringing the devices much closer with the same effect. I have my devices set in AP mode, i have tried toggling back and forth to force them into AP mode.I even tried getting on these wireless devices and doing a standard dhcp test on wireshark to esnure there arent any other conflicting dhcp servers and tried changing the password to be certain that there wasnt some lingering server.
After pulling logs from the FIrewall and the devices, I was able to piece together some information.
It appears that the sats run into an IP conflict every hour so one sat is kicked and the devices connected through that have to wait for the sat to pull a new IP from the DHCP server/firewall. The lease time is 1 day, but the Orbi sats seem to always lease for one hour. After that hour, it looks as though there is a problem through the lease and renew process where the sats fall back out of their assigned IP and try to self assign 192.168.1.250. where I have these devices statically assigned in the 192.168.128.2xx range from the DHCP server. I also pulled a log on the sats where it started assigning the wirelessly connected devices to 192.168.1.xxx range before getting back to the DHCP server and then reassigning all of the IPs correctly.
| Aug 2 00:16:13 | Orbi Sat1 | Client IP conflict | MAC: 9C:3D:CF:F0:9A:8D also claims IP: 192.168.1.250 |
| Aug 2 00:16:13 | Orbi Sat2 | Client IP conflict | MAC: B0:B9:8A:64:F7:08 also claims IP: 192.168.1.250 |