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 and IPv6 - much happiness in my household. =)
Rodney
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
809 Replies
Replies have been turned off for this discussion
For those who have downgraded (and changed nvram settings to prevent the auto-update) - what firmware did you settle on? it seems like a lot of people are reverting to 1.11.0.20, but I was wondering if one of the even earlier ones might be better? (I have an RBK53, i.e., the Costco router + 2 satellites, and neither satellite is connecting as a satellite)
Cheers
@eattleite wrote:
For those who have downgraded (and changed nvram settings to prevent the auto-update) - what firmware did you settle on? it seems like a lot of people are reverting to 1.11.0.20, but I was wondering if one of the even earlier ones might be better? (I have an RBK53, i.e., the Costco router + 2 satellites, and neither satellite is connecting as a satellite)
Cheers
Costco RBK 53 here - 2 sets in our family - both rock stable on 1.11.0.20 downgrade. (also Mu-MIMO and beamforming off by default and not sure if you need to do but disabled 20/40 co-existence under advanced wifi settings).
Well now my Surface Pro is having the same issues as my Surface Book and S8 Plus. It seems like this firmware is degrading daily. 10 minutes ago my entire network was locked up and unusable so I had to reboot the router and then manually reboot all the satellites.
After upgrade to v1.1.12.0.18 I have lost ability to use both satelittes.
Can't re-sync.
Wireless range downgraded.
When will firmware fix be afailable?
This is utterly ridiculous. I either need firmware that works (V1.11.0.20 does) or the ability to not automatically update. I have run the nvram and config changes on both the router and the satellite multiple times.
The Orbi is starting to look like a bad investment. Time to start posting on social media about this problem. Netgear has 61K followers on Twitter. It would be good to @mention some of the big tech sites like TechCrunch, CNet, WireCutter. I think then the issue will get the attention it deserves.
This was in a comment to an Amazon review:
"Hi GBJackson,
The latest firmware should not have broken the connection from the satellite to the router, and we would like to look into this with you. Can you please email us your contact information along with a link to your review to netgearteam@netgear.com, and we will be happy to help you.
Regards,
NETGEAR Team"Are they not reading this message board???
- For those of you reporting success with 1.12 have you power cycled the satellite since update?
I reset/rebooted/resynced my Orbi Router and Every satellite again last night and my connections issues (even on my S8) seem to be gone. This is the third time I have done it so maybe one of the satellites was holding onto some cache or something? No clue but I am going to test all day to see if the connection issue comes back. I see others have had similar success.
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=64Ping 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.Has anyone tried setting a DHCP reservation for the satellite? Sorry if this is a repeat question.
For those that have tried to block downloads.netgear.com and have seen their Orbi auto-update again (like me), I have included some other domains to block that seem to have stopped them on my unit. They are the top 10 domains my satelite has tried to contact, in order, from most to least contacted. Adding them to my main router's blacklist appears to have made the firmware update server unreachable.
- www.netgear.com
- updates1.netgear.com
- ftp.updates1.netgear.com.edgesuite.net
- 472263.ftp.download.akadns.net
- A1599ER83NVYL8.iot.us-west-2.amazonaws.com
- http.fw.updates1.netgear.com
- http.fw.updates1.netgear.com.edgekey.net
- e70.g.akamaiedge.net
I will report back if blocking these domains has stopped the auto-upgrade madness. I had previously blocked downloads.netgear.com and set the appropriate nvram options, and still had my unit upgrade itself after a few days. Hope this helps!
- I'm officially done. Absolutely done.
I've spent weeks trying to solve this nonsense.
I've tried: flashing with new firmware, factory reset, AP mode, router mode... Flashing with old firmware, toggling mu-mimo and/or implicit beamforming... Everything...
The best I've achieved is four days uptime, running as a router after a fresh flash of 1.12, a factory reset, and enabling both Mu-mimo and beamforming.
The only issue I don't seem to have is the bloody satellite dropping out.
That said, my LG G4 is having issues dropping in and out regularly. However, in the grand scheme of things, the G4 drops are the least irritating part of this rubbish.
So, I'm out. It's going back into the box and back to the shop.
PoS-Orbi-Owner wrote:
I'm officially done. Absolutely done.
I've spent weeks trying to solve this nonsense.
I've tried: flashing with new firmware, factory reset, AP mode, router mode... Flashing with old firmware, toggling mu-mimo and/or implicit beamforming... Everything...
The best I've achieved is four days uptime, running as a router after a fresh flash of 1.12, a factory reset, and enabling both Mu-mimo and beamforming.
The only issue I don't seem to have is the bloody satellite dropping out.
That said, my LG G4 is having issues dropping in and out regularly. However, in the grand scheme of things, the G4 drops are the least irritating part of this rubbish.
So, I'm out. It's going back into the box and back to the shop.This is why you guys need to pull your heads out of the sand and start really communicating with your customers.
If I bought a 4K TV and a forced update meant it would all of a sudden only display intermittently or only in SD, there is no way any customer would accept radio silence for three weeks, followed by a little more than a "hey, we hear you, but we have no idea when it'll be fixed". Yeah I get it, software is hard, but that's no excuse for delivering a crippled product, with substandard support, at a premium price.
Where are the features you removed and why did you pull them without saying anything?
When will ALL the features on the box, the ones that should have been working from day one, actually work?
When will you sort out the mess that is the V1.12.0.18 firmware?
When will you allow us to disable the ridiculous forced updates? It shouldn't take more than a day or two to roll that out.How freaking hard is it to keep your customers in the loop? And no, sending me a terse PM telling me to "have some patience" isn't communicating, it's rude and condescending. Your customer service blows (still waiting on that call), as does this "community" and frankly, this product is garbage in it's present state. I've put my order in for Google WiFi today, but I still need this POC fixed so I can sell it on.
I've never been more disappointed with a tech purchase than the Orbi and I expected better from a big name like Netgear.
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.
