NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
New firmware released 1.11.0.20
Some people were saying the 1.11.0.N beta was helping with a lot of issues. There is a new version released, but the release notes don't list any fixes. Has anybody tried the new version to see if it...
Hello Everyone
We have release firmware version 1.12.0.18 this firmware has fixes for disconnects and many more I posted the release notes below.
https://kb.netgear.com/000044171/RBR50-Firmware-Version-1-12-0-18
If you are still having issues after updating your Orbi unit you may want to factory reset the Orbi and test again. If you are still having disconnect issues or other issues with this firmware please create a new thread or contact our support team.
http://www.netgear.com/support/contact.aspx
Thanks
DarrenM
Flash008,
LOL (not really), you are correct. with the beta 1.11.0.8 version loaded it wants to upgrade me to .20
Oh well,
DarrenM, let us know when we can reach out to support and ask for an updated beta that .20 won't update on us, please.
PettyTesting,
Support requested that after I loaded the beta I do a hard factory reset on all of the devices.
There is definitely a difference as after updating to .8 in the connected devices table it still showed 5G or 2.4G or Wired.
Then hard factory reset with .8 installed
Then the connected devices table only showed Wireless or Wired.
So... even though I updated to .8 something was hanging around until I did the hard reset.
I just presume that if I am willing to beta test, I should be willing to hard reset. No fun, but I want to give the firmware a fair shake as I have 61 devices attached of which only 9 are wired.
More problematic for me than all my Apple devices are a Wink Hub2 and an iSmart Alarm Spot camera (go figure).
My friend,
I did a hard factory reset, as instructed. Not difficult.
Are you saying I should do it again? How many times?
Are you saying the Orbi .8 code (after a hard reset) doesn't have the inteligence to know it is the newer firmware, and it should ignore the 0.20, which is newer than 0.8?
Just asking....
im just saying you should never use a saved config file from an older fw version on a new fw version as it could and might currupt the current fw
I would never use a config from a previous version.
20+ years of I.T.
Always clean install....
i was replying to wchp comment with regard to backup
Flash008,
DarenM posted this:
"Re: New firmware released 1.11.0.20
Hello Flash008
orbi should not auto update to the live firmware if you are on the beta since it is version 1.11.0.80 which is higher than current firmware.
DarrenM"
So, if I understood DarenM .8 is actually .80 so .20 should not be newer, yet what he posted and what I am experiencing are at odds.
I am running .8 beta, with a hard reset on both satellites and the router. Now it wants to automagically update me to .20 even though DarenM said that shouldn't happen.
An in-place upgrade should carry your config forward. It does but it seems the prior config is at odds with the newer firmware and I am just reporting on what I saw prior to and then post hard reset.
Each time Netgear sends me a new beta the procedure I follow is.
1) make sure I have the prior version of firmware local
2) backup current config
3) update both satellites
4) update router
5) See if the whole network comes back up post updates
6) Hard Reset both satellites and then the router
7) Configure as new
8) Allow Router and Satellites to all come back up with from scratch config.
9) Rachio, Chamberlain, Honeywell (2), Amazon Echo, Dots (8) and Tap, Harmony, Belkin, Yamaha (2), Xbox, Sonos (9), Linksys media link (2), Android devices (3), Rokus (3), Arlo Hub, iPhone 7, iPhhone 5S, iMac27 2014, MacBook Pro late 2016 OS Siera) all come back on without a touch.
10) Apple TV2, Apple TV3 (2), Apple TV4, Wink Hub2 and iSmart Alarm Spot camera require a power cycle.
11) iPhone 5C and 6 and 6s, iPad Mini1 and Mini2, 2011 MBP (2), 2012 MBP, 2013 MBA cycle WiFi.
-Reboot router for any reason, repeat steps 10 and 11
-Apple TV4 and Wink Hub2 struggle to stay connected (1-3 daily loss)
-Cable Modem, Untangle Firewall and Orbi Router all plugged into Battery Backup with sine wave stabilized supply
-I manually set Orbi to Chan 1 on 2.4GHz and 48 on 5GHz. I trick the Arlo hub into staying on Chan 11 2.4GHz.
-No Guest WiFi
-No Parental controls
-MUMIMO and Beamforming enabled or disabled in any combination makes no perceivable difference on x.x.x.8
-Orbi satellites cause RF interference if placed within 6 feet of motion sensing switches (lights keeping turning on and off)
Hope all this helps
Hey Netgear,
Simple solution.
Very SIMPLE.
Hope you can handle it since giving us an option to disable autoupdate seems too hard for you.
Recompile the .8 beta with a version of .80. This should allow Orbi to understand that 80 is greater than 20.
I think Orbi is using SIMPLE math. 20 is greater than 8.
just to and clear this up
what i think has happened .20 is based on a slighty older vw version but is reported as stable , .8 is a slightly newer fw that was released to some for testing in the wild , the next fw release will address this which wont be that far away which should be a combination of the 2 releases , the .8 was a test fw for some who had stability issues .20 is the release candidate
well thats how i read it
So, you are saying when I wake up and find my Orbi updated to the .20 (devices dropping every 30 seconds) I need to downgrade (upgrade) to .8 (oh, wait, I mean .80), then another hard reset to wipe the .20 config?
And, I may need to do this a few times until Netgear releases a newer version number which contains the .8 fixes (sorry, I meant .80), and any other changes they make?
LOL....And you find this acceptable?
You believe that DarrenM and Netgear Support telling us that Orbi should not auto update, even though it is happening, is not a CLEAR demonstration that the left hand has NO CLUE what the right hand is doing.
The fact it has taken 8+ code releases in 90+ days to get .8 working (sorry again, I meant .80), but not .20 (as DarrenM has stated).
I am not attacking you, just asking if you feel this is normal and acceptable behavior for a company who claims to be premium and who priced Orbi is a premium range.
I have had busy past 2-3 weeks which means I haven’t had time to replace Orbi, and I am holding hope that ASUS Lyra is released soon. Many are saying July. I am ready to pull the trigger on UBNT, but Lyra is attractive.
And a small, dim-burning, PRAYER that Orbi “somehow” gets fixed and matures (beyond “working”) within the next 30 days.
Come on, you must admit that Orbi has taken many steps backwards. We went from, what node your client is using, then to ONLY connected client with 2G, 5G, Wired, now to ONLY connected wired or wireless.
No auto-update option to disable, no true mesh (as Netgear stated they were planning for that months ago)……
At what point do you say, “I got played”.
So...
As a tester of BETA firmware, I simply presume if it happens to be working I found something I can report.
So I am running 1.11.0.8
Orbi Router now says there is a newer version of the firmware.
I believe the consensus (from the other thread) is that as long as you don't restart your router it won't automagically upgrade you.
Support has advised us NOT to upgrade from .8 to .20
DarenM Stated that .8 is actually .80 so it won't upgrade
Our routers disagree with DarenM
SO...
If someone who is running .8 and whose router is displaying the message there is a newer version of firmware wants to restart their router, and report back to us here on this thread, we will know if .20 will, in fact, auto install. (Not me, sticking to .8 for the time being).
IF it does, in fact, do an auto upgrade that means you should also do a hard reset and re-set up your system.
As end users, we can only speculate on the WHYs of the versions and fixes. As beta testers, it is our responsibility to report WHAT we are experiencing with the version they provide us.
The net-net here is something is broken (maybe its just our devices that aren't actually behaving or out of standard). Sounds like some folks have had improvements on .8 and are upset about the potential loss of functionality again. If you don't want to get your hopes up by running a beta and then having it break again, don't run the Beta. After a mostly peaceful 2 days (except for the DARN WINK HUB2 and ATV4) things are fairly peaceful for me so I am going to hope as long as I don't restart, I can stay where I am till they release the next beta. Seems to me its the same group of folks here and on the other two threads that are having the issues (myself included) and I
Seems to me its the same group of folks here and on the other two threads that are having the issues (myself included) and I wonder, if we are the exception, or if more folks are just blissfully oblivious to the issue.
Hmmmm
So, who on .8 is going to reboot?
P.S. if you use a website grabber and download the entire Orbi Interface, there is a javascript for the firmware update page with a section to disable auto-update rem'd out. Who knows, again not my place to know if that is a future feature placeholder, a carry over from other code or they were just teasing me. ;)
RE: "If someone who is running .8 and whose router is displaying the message there is a newer version of firmware wants to restart their router, and report back to us here on this thread, we will know if .20 will, in fact, auto install. (Not me, sticking to .8 for the time being)."
Is no one going to bite?
Signed NOT ME
As with the 100s of Beta’s I have “played” with over the years, it has mostly been due to curiosity into the future. I used those betas with full knowledge NEVER to complain about stability and features I would like to have. You accept Betas “as they are”, and not what you want them to be. And yes, report back your experaince(s). Of course, you ask for new features, but never hold your breathe for it.
With Netgear Orbi, the features I am asking for are not “enhancements”, but rather fixes to very popular and known problems with Orbi.
The problem we have with Orbi is the GA releases are not stable, they don’t work, and using them renders some of our Orbis’ useless.
Hence, we are forced to use beta code to make our product work.
Typically, OEMs keep their most stable code available as GA for all to download and use.
Seems Netgear has this backwards.
“Let’s put our most unstable and buggy code on our update servers which will force an update onto EVERYONE. But, we will allow our beta testers to have the working version(s), But, since they can’t disable auto update we will make their lives HELL by updating their product to the GA unstable version every 48-72 hours, if they don’t do it themselves.”
Having been using Netgear betas now for a few weeks/months. I can tell you that if Orbi can see a newer code version it will download it, and it will not update immediately. But 2-3 days later I can see my devices dropping. I login, and guess what…it updated itself. Reboot was not required.
Now, tell me what would happen if Apple, Samsung, Cisco, Microsoft, Dell-EMC, Juniper, ASUS, and the other BIG NAME tech companies did things this way.
We would crucify them! Which is why they DON’T DO IT THIS WAY.
Sure, nag to me, annoy me to death, that a new update is available. But give me the option to ignore and reject it.
How many GA releases have we seen other tech firms PULL from their servers because something didn’t work and was causing mass problems. They didn’t turn their users into beta testers, and for those who chose to be testers knew what they were signing up for and did not have bad code shoved down their throat. If you didn’t like the beta, if it caused too many headaches, you backed out to the stable GA version. But usually the GA version is stable.
Sorry, not seeing your point concerning Netgear’s policy.
after 20+ years of IT, sh*t shouldnt work this way.
should i even apply this new firmware? i've seen nothing but issues with it from the Orbi community.
ive ever really experienced any network disconnects, but i'm pretty annoyed that my devices can't/won't switch between the router and satellite. i've also seem some lag/buffering when using amazon fire box (currently on V1.10.1.2).I've noticed no improvements with the beta firmware. Disconnects wer never really my biggest problem so it may have fixed that, I am not sure. My problem is the slow/flucuating speeds that I've narrowed down to Orbi being the cause. I think you should still try the beta because it may work for you like many people are reporting but there are still problems that need to be addressed. Good luck!
