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
Hmm I have the RBK50 on this way today and have an Amplifi HD system just now, I was thinking the Orbi would give me better overall speed but looking at this thread I think I may just send the Orbi back without testing it as it seems its let down by the firmware updates. May just stick with the Amplifi HD (its certainly not the worst system out there).
- So Orbis arrived yesterday and I did some testing with them, of course they auto updated to V1.12.0.18 during setup. I did some testing and got much the same in speed/range as the Amplifi HD. So based on that and what seems to be bad firmware these are going back. Didn't leave them on for too long so can't say much about stability.
- 1st off Netgear you guys gotta get your acts together and figure this Orbi situation out! I personally paid over $500 for a orbi system and I do love me some Netgear but the only feature I want is the actual mesh in this mesh system lol! Why cant one satalite connect to
Another instead of the router! 1 year and this last firmware still nothing! I don't even wanna get started with all the stuff we want that have been mentioned in this community post! Netgear you guys will lose customers left & right if you guys dont speed up this firmware issue. I never knew we purchased an item that was defective that needs so much updates lmfao! #FIX #SAD #UbetterTHANthatHaving been one on the thread that had praised 1.12.0.1x from the disaster that 1.11 was, after a complete system reboot (due to swapping a UPS on the router) I can say that after that reboot, my first since 1.12.0.18 was released, my system now is a complete mess.
I'm not sure how a reboot could take a perfectly working system on 1.12.0.18 to what I have now, but it did.
My S8+ and my Surface Pro (2017) now continually show the WIFI icon with the ! sign, with the message "Waiting for the quality to improve" to "no internet". They'll connect for a few minutes, then go back to the weird connected, but disconnected state.
I have 6 chromecasts and at least 3 are now continually buffering or reconnecting every minute or so.
1.12.0.18 had been, up until yesterday a God send, but now (and following subsequent reboots) is a complete mess as so many are reporting.
I don't want to speculate but can't help it; it seems to me like Netgear's quiet Insistance on everyone getting updated to 1.12.0.18 is probably that they're hiding a big boo-boo from us.
Ucchi wrote:I don't want to speculate but can't help it; it seems to me like Netgear's quiet Insistance on everyone getting updated to 1.12.0.18 is probably that they're hiding a big boo-boo from us.
Speculating is just what you are doing. The auto-updates have been there since Orbi was released. There is no reason to believe there is anything special about forcing update to 1.12.0.18 more than any other release.
And regardless, 1.12.0.18 has made the whole Orbi system useless for many of us - satellites completely drop off, when they were stable with previous releases. Can't get much worse than that.
Ucchi wrote:I don't want to speculate but can't help it; it seems to me like Netgear's quiet Insistance on everyone getting updated to 1.12.0.18 is probably that they're hiding a big boo-boo from us.
Don't know if you saw this, but the last time I reset and reconfigured my router, I noticed a window in passing that I needed to agree to...something to the effect of "you agree that Netgear is entitled to flash firmware on your Orbi without your permission" or something to that effect. Don't remember the exact wording, but it was an agreement that would allow Netgear to auto-update my Orbi...so I doubt that this was related to a single boo-boo, but more a general policy that they'll see that we're always on the latest firmware. Of course, if there are any boo-boos (heaven forfend) in the latest firmware, you'll be stuck with them is the (very likely unintended) side effect.
I do not understand why everyone "has" to have the same Firmware??? SERIOUSLY does every human "has" to wear the same shoe?? Everyone's environments are different everybody has different scenarios everyone's networking needs are different, people have specific requirements for their situation for their networks...along with forcing the pollution and unnecessary interference by not allowing radio power adjustment or turning off radio not needed as per individual needs and requirements... these are very basic networking concepts being flagrantly ignored by the experts at Engineering is baffling!! Can someone explain why we are now being forced to blast radio at full strength in all directions introducing and contributing to interference already in our neighborhood is this considered smart? I have no way to adjust power on radios any more this is smart? Sorry just running out of patience with Netgear after a year of optimistically waiting... Things with Firmware are regressing instead of forward progress.
My Sprint S8 Plus received a firmware update this morning which appears to fix my disconnect issue it was having with this firmware. I will test throughout the day but if this fixes it then all my issues with this firmware are done and I am a happy camper.
- How hard is to get an update with the things they are working to fix? Orbi (when working) is by far the best system out there and you are ruining the product with lack of response. I got the EERO system (2nd gen) after getting sick of the disconnects and it is so much slower and has issues changing from beacons ... Still was connected all the time though. I'm going to give Orbi one last chance on the next firmware.... GET US AN ETA on next update and block the stupid auto update feature.
Like many other folks, as soon as the 1.12.0.18 firmware got auto-updated onto my Orbi system, my satellite stopped syncing with the router. It would show up in the list of attached devices, but not in the list of satellites. I even went so far as to go to local retailer and purchase a new Orbi RBK50 system to use in the meantime, and sure enough, the satellite stopped syncing on that (brand new) system after a few days. Very bad.
After doing the reset-button-and-setup dance on my original router and satellite I downgraded both of their firmware to 1.9.1.12 - and my satellite stayed connected! I even used telnet to turn off auto updates. ...yet somehow this morning my satellite stopped syncing with the router! The 1.12.0.18 firmware came back! Maybe I didn't set _all_ the required don't-auto-update parameters. Ugh.
Nothing new to report - just wanted to vent. The Orbi is a great system when it's working - it's just _so_ determined to sabotage itself!
Brian
- There are so many firmware versions available for Orbi since it came out that it is ashame the auto update feature kills the option to choose what works for your system. In the perfect world, every firmware update should be an improvement but clearly it is not the case for Orbi. I know some people figured a way for the auto update to stop working but we should not be spending 3 hours with reboots and googling a way to do it... I don't buy that because some dude here mention a lawsuit Netgear cannot communicate in this thread anymore. The ratings for this product everywhere went from 4.7 stars to 4.2 and keep going down because of this lack of customer service. I sure hope this company is not charging customers for wasting their time with a rep after the three month "free" support. Not to justify Orbi but other mesh wifi systems are plagued with issues as well. Difference is that their customer service responds and make people feel that they are heard and things will get better. It's been almost a month since the last update. I hope the new firmware comes soon and definitely turns the auto update off. We can then at least pick which firmware works best for our situation...
Working with a support call on a Orbi System router + 3 sattelites because of constant wifi signal dropouts. After numerous resets and many times emails back and forth with support i summarize: 1.12.0.18 seems not to be ready for prime time for a lot of people who spent a lot of money.
some people here are already happy if the systems works for a few days with out issues., i would not call that a reliable stable technology at all.
no ETA's for new firmware. maybe one day they will fix it, till then hardly to be recommended.
Lucky those people where it works, great signal strength , great penetrations through difficult walls, but stability sucks ..
Just out of curiousity, since 1.12 remains broken for lots of folks and 1.11 seems to have a nasty habit of regularly dropping iOS devices, what are others' thoughts on rolling farther back? Is there any sort of consensus on what the last stable version of the system's firmware was?
I am also gettign frequent disconects on 1.12.0.18. Is the best option to just wait for an upgrade or jump through all these hoops to downgrade?
n4cho wrote:I am also gettign frequent disconects on 1.12.0.18. Is the best option to just wait for an upgrade or jump through all these hoops to downgrade?
It's been out for about 6 weeks, so it's up to you. No word from Netgear on if they're aware of how bad, or widespread it is, or if a fix is on the way.
Netgear support offers to replace my satelittes. I have three and dont know which of them is "Defect"
Has anybody went through such a replace action with the problem of disconnects solved ?
II'am not sure all the effort of replacing the satelittes does any good if the firmware is the big issue (what it clearly seems to be)
Will be interesting in Germany we have 2 years warranty by law, not just 90 days ...
Albert
So, I seem to have fixed my issues on the latest firmware (1.12). After going back and forth a number of times and playing with various NVRAM settings, I decided to start from scratch. Here's exactly what I did:
- Enable telnet and sign into the router.
- nvram erase
- nvram commit
- reboot
Items 2-4 above are commands to enter into the console. Once it's rebooted, sign into the admin panel and then restore firmware defaults.
After doing this, running latest firmware, my WiFi and wired speeds are super fast. I'm getting over 900Mbps wired on Speedtest, and my iPhone 7 Plus is regularly exceeding 300Mbps down and goes over 400Mbps up.
I strongly suspect that corrupt NVRAM settings are the source of these problems. Whether it's bad defaults or perhaps corruption when upgrading, the end result is pain. I also think the QoS implementation is the main source of the problem. As others have noted, re-running the Speed Test seems to help things, but I think the key to a working 1.12 installation is to NEVER RUN THE SPEED TEST. The instant you run it the router saves the results and the problems set in. If you reset to defaults and never touch the speedtest settings you may find it improves things.
As always, YMMV. Hope this helps somebody.
gbjackson wrote:nxc To clarify, which particular sort of problems were you having?
I had a variety of issues. At least once a day the satellite would disconnect. I’d see it flashing the light for a bit as it fixed itself. Sometimes it needed a manual reboot to reconnect. In general, I was seeing very slow wireless and wired speeds. WiFi speeds would top out around 60-70 Mbps. Wired would reach around double that. After reflashing and testing a variety of things it seems to be to be squarely a problem with QoS settings. Regardless of what I tried, once I ran a Speedtest, problems started. Even messing with the Speedtest results in NVRAM wouldn’t fix it. Obviously I’ll need to watch and see what happens, but everything is flying fast and reliably now.
One advantage to using the Orbi as an AP is that when you do a factory reset or clear nvram to get a fresh start, there's little configuration to be done. So I have less temptation to restore a saved configuraton file that might itself be corrupt. I agree that simply flashing a router time after time without ever resetting and renewing one's configuration settings is an invitation to problems. While I don't see the need to do this for every flash, especially since Netgear doesn't say that it's required, it is good to do this when problems come up. If only to verify that problems are really firmware problems as opposed to accumulated nvram corruption problems. No router is immune to those.
nxc wrote:So, I seem to have fixed my issues on the latest firmware (1.12). After going back and forth a number of times and playing with various NVRAM settings, I decided to start from scratch. Here's exactly what I did:
- Enable telnet and sign into the router.
- nvram erase
- nvram commit
- reboot
Items 2-4 above are commands to enter into the console. Once it's rebooted, sign into the admin panel and then restore firmware defaults.
After doing this, running latest firmware, my WiFi and wired speeds are super fast. I'm getting over 900Mbps wired on Speedtest, and my iPhone 7 Plus is regularly exceeding 300Mbps down and goes over 400Mbps up.
I strongly suspect that corrupt NVRAM settings are the source of these problems. Whether it's bad defaults or perhaps corruption when upgrading, the end result is pain. I also think the QoS implementation is the main source of the problem. As others have noted, re-running the Speed Test seems to help things, but I think the key to a working 1.12 installation is to NEVER RUN THE SPEED TEST. The instant you run it the router saves the results and the problems set in. If you reset to defaults and never touch the speedtest settings you may find it improves things.
As always, YMMV. Hope this helps somebody.
So it's been five days, and everything has been rock solid. Again, your mileage may vary, but updating to v1.12, wiping NVRAM settings via telnet and subsequently performing a factory reset, and never using the built-in Speedtest seems to have fixed my issues. My satellite doesn't appear to have dropped connections, the satellite is currently handling about 1/3 of the devices on my network, and my speed test results (from the website -- NOT THE ADMIN) are fantastic:
This is approaching the effective limit of what you can expect from a modern iOS device. I'm very happy with the results. Orbi is finally living up to its reviewer reputation.
nxc wrote:
nxc wrote:So, I seem to have fixed my issues on the latest firmware (1.12). After going back and forth a number of times and playing with various NVRAM settings, I decided to start from scratch. Here's exactly what I did:
- Enable telnet and sign into the router.
- nvram erase
- nvram commit
- reboot
Items 2-4 above are commands to enter into the console. Once it's rebooted, sign into the admin panel and then restore firmware defaults.
After doing this, running latest firmware, my WiFi and wired speeds are super fast. I'm getting over 900Mbps wired on Speedtest, and my iPhone 7 Plus is regularly exceeding 300Mbps down and goes over 400Mbps up.
I strongly suspect that corrupt NVRAM settings are the source of these problems. Whether it's bad defaults or perhaps corruption when upgrading, the end result is pain. I also think the QoS implementation is the main source of the problem. As others have noted, re-running the Speed Test seems to help things, but I think the key to a working 1.12 installation is to NEVER RUN THE SPEED TEST. The instant you run it the router saves the results and the problems set in. If you reset to defaults and never touch the speedtest settings you may find it improves things.
As always, YMMV. Hope this helps somebody.
So it's been five days, and everything has been rock solid. Again, your mileage may vary, but updating to v1.12, wiping NVRAM settings via telnet and subsequently performing a factory reset, and never using the built-in Speedtest seems to have fixed my issues. My satellite doesn't appear to have dropped connections, the satellite is currently handling about 1/3 of the devices on my network, and my speed test results (from the website -- NOT THE ADMIN) are fantastic:
Well what do you know, this seems to have worked for me too. NVRAM reset, follow by factory reset. Reconfigured everything manually and it's working fine so far. Before I could only get 70-80Mbps wired to the router, now I'm gettting 800Mbps+. I'll do some testing later to see if I can narrow the cause of the issue down, starting with the speed test which has some broken QOS settings hidden behind it.
