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 tried the factory reset (hold down the reset button) on the satellite last night, having previously manually re-flashed 1.12 and erased the router settings. And it actually solved the satellite problem (where it's recognised as an attached device rather than a satellite, and the satellite's wifi channels are disabled). But then I power cycled the satellite, and the problem returned :(
I'll test it a bit more tonight, but then I think I'm done. Support haven't managed to call me this week, so if the problem is still there on Monday it's going back to Amazon.
currently the only solution is to downgrade to 1.11.0.20 - unfortunately not everyone is a tech expert (that's why they probably chose orbi for a painless system). DarrenM & Netgear et al, why don't u guys release 1.12.0.20 to be a copy of 1.11.0.20 which will auto-update until this is all sorted out. IN that update push an advanced debug feature for disabled auto update (or the next one) just get 1.11.0.20 out as 1.12.0.20
cyberprashant wrote:currently the only solution is to downgrade to 1.11.0.20 - unfortunately not everyone is a tech expert (that's why they probably chose orbi for a painless system). DarrenM & Netgear et al, why don't u guys release 1.12.0.20 to be a copy of 1.11.0.20 which will auto-update until this is all sorted out. IN that update push an advanced debug feature for disabled auto update (or the next one) just get 1.11.0.20 out as 1.12.0.20
My system is working perfectly on 1.12. Why would I want to go backwards?
ArtLee wrote:
cyberprashant wrote:currently the only solution is to downgrade to 1.11.0.20 - unfortunately not everyone is a tech expert (that's why they probably chose orbi for a painless system). DarrenM & Netgear et al, why don't u guys release 1.12.0.20 to be a copy of 1.11.0.20 which will auto-update until this is all sorted out. IN that update push an advanced debug feature for disabled auto update (or the next one) just get 1.11.0.20 out as 1.12.0.20
My system is working perfectly on 1.12. Why would I want to go backwards?
a lot of ppl are having issues with 1.12.0.18 - if you're good then leave it alone (and consider yourself lucky!!) - also i didn't realize I had issues till I had to unplug and replug in the orbi and that's when all h--- broke loose.