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
hsheppard None. In a month the only thing we've heard from Netgear is that they are aware of the issues. No list of what they're working on, no ETA, and they're ignoring any attempts to get more information.
If you have the option, I'd recommend taking your Orbi back now and look at an alternative. Even if Netgear do manage to sort these issues out, who's to say it won't happen again with the next release.
If you have the option, I'd recommend taking your Orbi back now and look at an alternative. Even if Netgear do manage to sort these issues out, who's to say it won't happen again with the next release.
I do have an online support ticket open and have already answered the questions but not optomistic to a quick resolution from the standpoint that one version of the FW works fine the other does not, just push back the old version or allow the option to not update to the newest version. This is too bad as I really liked the week of solid performance with this set up, so shopping now for a similar system.
RBR50
RBS50(2)
1.11.x was broken for many users. 1.12.x appears now to be broken for even more users- they're not heading in the right direction.
I believe they've lost control of the releases, and are now playing Whack-A-Mole trying to correct the issues, but cause more after each try.
They need to go back to 1.10.x or previous branch, and start from there.