do we need to do nvram wipe for this 2.1.1.16 Firmware just released today? noticed it downloaded automatically.

Installed the v2.1.1.16 firmware this morning because the release notes said it would solve the problem of the satellite NOT listing the attached devices. Not only did this new firmware NOT fix the satellite problem, it seem to have effected the stabilty of my router. My router has rebooted itself twice in the span of four hours. However, in the interest of full disclosure, I did NOT do a factory reset on either the router or the satellite after I installed the v2.1.1.16 firmware. I did do a fresh reboot though. I've actually gone back to v2.0.0.74 firmware to try and get my network stable again.

All these firmware problems might be excusable if Netgear was a newby, but Netgear has been making routers for decades. I've been using Netgear routers for decades and I never had a problem with firmware updates causing issues. This release of v2.1.1.16 firmware looks like a classic case of insufficient testing. Sure when you first install the firmware everything looks fine, but three hours later, all the attached devices have dissappeared from the satellite and the router has rebooted itself twice. Someone at Netgear seems to have dropped the ball and it is NOT giving me a good feeling about this product. If the Netgear software engineers did their job correctly, there wouldn't have to be a magic sequence of updating the satellites before the router, or doing a factor reset or not, or doing a resync or not. Unless Netgear fixes these firmware issues, word is going to get out that Orbi is NOT a very good router system after all. I checked with Amazon and I have until the end of January to return my Orbi RBK50. If the next firmware release doesn't fix the stability and functional problems, I going to send this puppy back to Amazon for a refund. If ASUS every brings a mesh wifi system to market, you can bet that it will be rock stable, it will function as advertised, and it will have all the features that you wish Orbi had.

I was auto-upgraded to 2.1.1.16 as well, from 1.11.0.20, a few nights ago. When I woke up and started running all my checks (each nodes debug.htm to check the system uptime), i noticed the upgrade. I went ahead and power cycled both the satellite and router, so that they can have similar uptimes. For the first few hours, the satellite main page and the router attached devices page were in sync, but afterwards (not sure how long it took), the satellites main page shows NO attached devices, the router attached devices page shows some devices are on the satellite, and, now, the Orbi Android app, which was just upgraded to 2.1, does NOT show which node you are connected to (it used to before). Its hard to tell what is a display issue, and what is not. But, on my phone, using wifi analyzer (far proc version), i can see which mac address i am connected to, and when i am close to router, i connect to router...when i am closer to satellite and FAR from router, i switch to satellite. Even though the device pages do not reflect that. Unfortunately, 2.1.1.16 did NOT do anything to improve the random rebooting. I woke up this morning to a satellite uptime of 22 hours, and a router uptime of 4 hours. That 4 hours elapsed corresponds to around 5 AM, and everyone was asleep. I have posted numerous times my journey with Orbi (2 versions of RBK50, one from amazon(returned), and one from Walmart (currently testing)). I have tried different power outlets, all sorts of configuration options (daisy chaining on/off, fast roaming on/off, etc...). I do NOT have any phones or devices with Android Oreo. My satellite and router are about 45-50 feet apart, and separated by a single wall and there are no interfering channels from neighbors. Really want Orbi to work, since Walmart had the RBK50 set for only $200, but based on reading almost every thread on Orbi in this forum and other places, it doesnt seem like there will be a "magic" firmware release that fixes it all. I appreciate all the posters here, relaying what information they can, in the hopes that we can maybe help find a pattern of why things happen to some, but seemingly, not to others. Keep on keeping on, i guess! For those that DO have stable systems, could you check your router and satellites debug.htm page,and check the system uptime for them? I am guess that some folks dont even know about that, and there systems may be rebooting as well, but they are unaware? Longest uptime i had was about 38 hours, and that was on 1.11.0.20 (auto upgrade to 2.1.1.16 happened). thanks everyone for your contributions!

netgearguy & godspeedI'm on of those "no trouble found" folks. My uptime is currently 1 day, 3 hours, 45 minutes, which corresponds to the time I upgraded to 2.1.16. I have had zero issues since day 1. And, since I'm a cord-cutter who streams TV wirelessly from DirecTV Now through a Roku, I'd notice pretty quickly if I had dropped connections. I'm also a Pixel 2 XL owner, and there have been reports that other Pixel 2 and Pixel 2 XL owners have had reboots.I don't know what makes my setup different, or perhaps I'm lucky. But everything has been rock solid for the two months I have had the system. I'm running in AP Mode with Google Fiber as my ISP. I currently have 16 devices connected, but can have anywhere up to 50. Four Rokus, Nest, my Pixel 2 XL, my wife's iPhone, a Fire tablet, some other phones, my Windows 10 PC, my wife's laptop, security cameras, SmartThings Hub, some WeMo switches, Google Home, 2 Google Home Minis, 2 Raspberry Pis, a WiFi connected garage door opener, etc.

Decided to throw everything i could at the Orbi tonight...to try and fix the random reboots of both router and satellite. My Orbi is in AP mode, with an Asus AC68 acting as router. Router is assigned an ip address manually (outside DHCP reserve list), and Satellite is saved on a particular DHCP reserve IP. 1. both R (router) and S (satellite) are on 2.1.1.16, via auto-update2. Manually apply 2.1.1.16 firmware on S, wait till up.3. Telnet into S and do an NVRAM erase, commit, and reboot.4. Wait for it to come up, and use a pin to reset S.5. Manually apply 2.1.1.16 firmware on R, wait till up.6. Telnet into R and do an NVRAM erase, commit, and reboot.7. Wait for it to come up, and use a pin to reset R.8. Unplug modem (Arris SB6183), and change my cabling so that it goes Modem -> Orbi R9. Plug modem back in, and use the Orbi android App to begin and finish configuration.10. Use Windows PC to go to router admin page, and the ONLY thing i change here is the timezone, and then set it to AP mode (fixed IP).11. Unplug modem again, and change my cabling so that it goes Modem -> Asus AC68 -> Orbi R12. Plug modem back in At this point, i go back into the Orbi admin menu and change the 2.4 Ghz channel from AUTO to 6 (least congested in my area). Daisy chain is enabled by default, and i am going to leave it be for now, even though i only have 1 satellite. I wanted to make as little change as possible from the default settings. It took a few minutes, but on the attached devices page (on router), my devices start showing up, some connecting to router, some satellite. On the satellite status page, the list of connected devies is also populated, at least for now. Fingers crossed.

Orbi firmware v2.1.1.16 discussion

437 Replies

steelhorse83
Guide
Dec 21, 2017
Apparently, my Orbi Router & Satellites auto-updated from 2.0.0.74 to 2.1.1.16 since I last looked at it on Monday. All my devices that are capable of 5Ghz are showing connected to 5Ghz, and all the devices are correctly showing their connection to either the router or a satellite. I haven't had any issues streaming Netflix or PSVue. I checked the debug.htm page on the router and both satellites, and they all show around 5 hours of uptime. I will check back on that later in the week, to see if they are rebooting, or if the upgrade actually happend 5 hours ago.
- ratickle
  Apprentice
  Dec 21, 2017
  steelhorse83 wrote:
  Apparently, my Orbi Router & Satellites auto-updated from 2.0.0.74 to 2.1.1.16 since I last looked at it on Monday. All my devices that are capable of 5Ghz are showing connected to 5Ghz, and all the devices are correctly showing their connection to either the router or a satellite. I haven't had any issues streaming Netflix or PSVue. I checked the debug.htm page on the router and both satellites, and they all show around 5 hours of uptime. I will check back on that later in the week, to see if they are rebooting, or if the upgrade actually happend 5 hours ago.
  I have a theory that firmware v2.1.1.12 is the version that has caused many people to have stability and functional problems. My theory also says that v2.1.1.16 indeed fix the problem caused by v2.1.1.12, but ONLY if a FACTORY RESET occured BEFORE the installation of v2.1.1.16. Since you went from v2.0.0.74 directly to v2.1.1.16 your system should be fine. If, and it's a big if, my theory about v2.1.1.12 is correct. Yes, report back in a day or two and let us know the system uptime and whether or not your satellite shows attached devices correctly.
  - howiedub
    Tutor
    Dec 21, 2017
    ratickle wrote:
    steelhorse83 wrote:
    Apparently, my Orbi Router & Satellites auto-updated from 2.0.0.74 to 2.1.1.16 since I last looked at it on Monday. All my devices that are capable of 5Ghz are showing connected to 5Ghz, and all the devices are correctly showing their connection to either the router or a satellite. I haven't had any issues streaming Netflix or PSVue. I checked the debug.htm page on the router and both satellites, and they all show around 5 hours of uptime. I will check back on that later in the week, to see if they are rebooting, or if the upgrade actually happend 5 hours ago.
    I have a theory that firmware v2.1.1.12 is the version that has caused many people to have stability and functional problems. My theory also says that v2.1.1.16 indeed fix the problem caused by v2.1.1.12, but ONLY if a FACTORY RESET occured BEFORE the installation of v2.1.1.16. Since you went from v2.0.0.74 directly to v2.1.1.16 your system should be fine. If, and it's a big if, my theory about v2.1.1.12 is correct. Yes, report back in a day or two and let us know the system uptime and whether or not your satellite shows attached devices correctly.
    I don't think 2.1.1.12 has anything to do with it. I went from 2.0.0.74 straight to 2.1.1.16 and still had issues. Went back to 1.8.0.6 and it auto updated back to 2.1.1.16. Issues still persisted. Factory reset on 2.1.1.16 did not work. Back on 1.8.0.6 and everything is stable again. Have some bugs, but they are somethings I can live with as long as my connections don't drop and devices connect correctly. Disabled auto update through telnet, so hopefully that keeps it from updating again.
    
    I'm starting to think it's hardware related. Seems like people who got their Orbis recently don't have the issues and those that have had it since the 1.* firmware days are the ones having issues. Just my 2 cents.
- steelhorse83
  Guide
  Dec 22, 2017
  Well, I'm happy to report 28.5 hrs of uptime so far. No known issues yet. I think the only non-default setting I have is I deselected Daisy Chain after the 2.0 code came out. Other than that, it's mostly a stock configuration. I have 21 devices on the network.
godspeed
Apprentice
Dec 21, 2017
Update:
This is my last attempt with Orbi. For the last few weeks, i have been using an Asus AC68 as the router, and the Orbi system in AP mode. Still getting reboots and dropped connections, no matter what settings i set, or how many times i factory reset.

This time, i am going to use the Orbi as a router. I factory reset both Router and Satellite, and setup all my port forwarding rules, changed DNS to openDNS, etc.

Will see if maybe the Asus router was causing issues with the Orbi in AP mode...

will update as the day goes on...
- southflguy
  Star
  Dec 21, 2017
  Constant WiFi loss here. Router reboots. Affecting the entire network. In one day I have had probably 5 or 6 episodes of WiFi going down. At this point I’m thinking of abandoning it and going Eero Pro. I might give it a shot and see.
  - miskaone
    Aspirant
    Dec 24, 2017
    I was having similar issues and it turned out that I had '$' in my network key (password). This stablized most of my issues. I will say I am on my 3rd set of Orbi's. I am not sure all my issues are resolved but at least I am not rebooting several times a day.
- NickC4555
  Star
  Dec 21, 2017
  My Orbi and 2 satellites had all been previously updated manually, but still did an auto update to the new release without prompting, so the suggestion that this switches it off is not correct. I was left with a completely unusable system this morning. The information here seems to be the best advice to disable it: https://community.netgear.com/t5/Orbi/Firmware-V1-12-0-18-Discussion/td-p/1320421/page/5
  
  I rolled back to beta V2.0.1.2, which has been rock solid for a couple of months.
  - RogerSC
    Virtuoso
    Dec 21, 2017
    NickC4555 wrote:
    My Orbi and 2 satellites had all been previously updated manually, but still did an auto update to the new release without prompting, so the suggestion that this switches it off is not correct. I was left with a completely unusable system this morning. The information here seems to be the best advice to disable it: https://community.netgear.com/t5/Orbi/Firmware-V1-12-0-18-Discussion/td-p/1320421/page/5
    
    I rolled back to beta V2.0.1.2, which has been rock solid for a couple of months.
    I wouldn't waste your time trying to block auto-update, unless you have a lot of time to burn. I've tried everything mentioned in this forum to block auto-update, including using dd-wrt on my R7800 (Orbi is in AP mode) and restricting access to "netgear.downloads.com" and "netgear.download.com" as well as all the telnet stuff on both the router and satellite. The dd-wrt dodge that I had high hopes for doesn't seem to have worked. When 2.1.1.16 went out, my Orbi said that there was new firmware available from Netgear, a bad sign for blocking auto-update. While I didn't wait to see if the Orbi could download it or not, I sort of assumed that the path that the Orbi uses to check for new firmware is the same path that it would use to download it. Once I find out what that path is, I can block it until Netgear changes it, but not there yet.
    
    Sometimes it takes days for auto-update to catch up to you, but you can just assume that it will sooner or later *smile*.
warrior101
Aspirant
Dec 21, 2017
Updated R and S to latest firmware.
Orbi Network unable to connect via PC/iOS devices.
Performed Factory Reset.
Reconfigured Orbi Network.
Connect to Orbi Network via PC/iOS - **Checked OK**
Set Orbi-R to AP Mode (AT&T gateway/5268ac)
Reboots. Attempt to connect to Orbi Network via PC/iOS device - "Invalid password".

Everything has been fine since purchase (12/15) till updating to 2.1.1.16.

Is there anyway to roll-back firmware? Thanks
- netgearguy
  Apprentice
  Dec 22, 2017
  Download the version you want from Netgear's web site and flash using the Manual option in the firmware update screen. Very simple.
  
  Supposedly after a manual update the auto-update is disabled, but not sure that has been confirmed 100%.
tomsliwowski
Apprentice
Dec 22, 2017
Seeing the same weirdness with all wireless connections being reported as connected to the main Orbi router. Connected devices are 1 satellite and 23 clients, all but 2 show as connected to the RBR, the 2 that are not are PCs hardwired to the RBS. I wonder if this is for real or another bug. Also, daisy chain topology is disabled.
njweb
Luminary
Dec 22, 2017
My RBK 50 (3 unit system - router and 2 satellites) was upgradeded to 2.1.1.16 a few days ago (automatically). No issues so far. Have not tested all my devices yet but the ones we use are working fine.
Since that upgrade, I have used at least 3 laptops, 1 tablet, Android, iPhone and TiVO MoCA setup and Roku with it and things are working well.
I work remotely and not one disconnect yet from my home connection to my company virtual desktop (which requires a constant connection - if my router connection drops, my virtual desktop connection would get dropped too).

So far so good.

Settings (mostly default, using WPA2-AES security):

Daisy chaining is disabled.

I do have all of the following enabled:
BEAMFORMING
MU-MIMO
Enable Fast Roaming
- cyberprashant
  Luminary
  Dec 23, 2017
  no problems here either with 2.1.1.6 wth the following settings:
  
  CHECKED Enable Implicit BEAMFORMING - Boosts WiFi speed, reliability, & range for all mobile devices
  CHECKED Enable MU-MIMO
  NOT CHECKED Enable Fast Roaming
- njweb
  Luminary
  Dec 23, 2017
  njweb wrote:
  My RBK 50 (3 unit system - router and 2 satellites) was upgradeded to 2.1.1.16 a few days ago (automatically). No issues so far. Have not tested all my devices yet but the ones we use are working fine.
  Since that upgrade, I have used at least 3 laptops, 1 tablet, Android, iPhone and TiVO MoCA setup and Roku with it and things are working well.
  I work remotely and not one disconnect yet from my home connection to my company virtual desktop (which requires a constant connection - if my router connection drops, my virtual desktop connection would get dropped too).
  
  So far so good.
  
  Settings (mostly default, using WPA2-AES security):
  
  Daisy chaining is disabled.
  
  I do have all of the following enabled:
  BEAMFORMING
  MU-MIMO
  Enable Fast Roaming
  
  Just to add:
  
  I should perhaps have clarified - I saw a number of members posting about connection stability issues with 2.1.1.16. Thus, when I referred to no issues, I meant I was not observing any connectivity or other performance issues.
  
  Connected Devices DISPLAY issue (does not impact performance?):
  I see 21 devices connected (8 wired and 13 wireless). All 13 wireless devices show connected to the router which is not correct, so that issue indeed needs to be resolved. Luckily it appears to be a display issue only (correct me if anyone is seeing issues where all devices are actually connected to the router) and does NOT (appear to) impact throughput.
  I'll have to run some signal strength and speedtests to confirm the devices are connected to the satellites.
  
  I did run a test on my mobile phone a few days ago and it showed a signal strength consistent with being connected to the satellite (will need to double check though).
  
  PS: I did not perform a factory reset (or NVRAM clear etc.).
diesunddas
Guide
Dec 22, 2017
the two new firmwares (v2.1.1.12 + v2.1.1.16) are very buggy !

it is a shame what for poor quality netgear delivers with such an expensive product.

the version 2.0.0.0.74, this is the only stable firmware version, downgrade router and satellit to this version (but this version has the security-leak KRACK)
sandsstl
Tutor
Dec 23, 2017
Fingers crossed.
Yesterday I updated to 2.1.1.16 and started having issues - lost the satellite, yada, yada, yada. Switched back to 2.0.0.74 and everything settled down.
This morning (≈ 14 hours ago), the system had auto-updated back to 2.1.1.16 and seemed to be reasonably stable...all devices were showing connected to the router, nothing to the satellite, and the Attached Devices page kept reloading every five seconds on Safari, but wifi speed was excellent and nothing appeared to be getting dropped.
Had some issues streaming with Sonos, so rebooted the system a couple of times through the day (still not sure that's resolved), but everthing seemed to continue to work.
So, this afternoon I decided to factory reset the satellite (saw someone had done that somewhere in this rather long topic) to see if the satellite would show up. Had a devil of a time getting the satellite to reconnect, but when it did the devices started showing up connected to the satellite. I had to forget the network on iPhones and iPad and reconnect, but it worked. That's been about five hours ago and, as far as I can tell, everthing seems to be stable and correct.
Attached Devices page reloading seems to be an issue with Safari, Chrome works fine.

Enable Daisy-Chain Topology is off
Beamforming, MU MIMO and Fast Roaming are on
oldcake
Aspirant
Dec 23, 2017
when i up to 2.1.1.16, my homekit 2.4g device was lost connection, when the 5G SSID was heidden and singal set to 25%, some device will back. if any setting change will make conection lost again.

i give up and back to 2.0.0.74
- Mayhugh1
  Apprentice
  Dec 23, 2017
  According to my uptime status indicators, I've had no stability problems with .16, and my speeds on all my wired and wireless devices look great, and so my complaint is relatively minor. I have two satellites with multiple devices wired to them, as well as seven wireless devices distributed among the router and satellites. Neither the Orbi app nor logging into the router shows either of the two devices that are wired to one of my satellites. The physical placement of my router and satellites is such that a star connection makes much more sense than a daisy chain connection, and so I don't have the 'use daisy chain option' checked. The backhaul status shows 'good' on both satellites. And so, I'm guessing this is a display bug in the firmware. I have mu-mimo and beamforming enabled, but otherwise am using default settings for the rest. One other detail that might help the developers is that the two satellite-wired computers that are not showing up happened to be sleeping when I decided to disable the daisy chaining (days after updating to .16) which rebooted the system. When the computers were awakened, they received IP addresses and had access to the internet, but neither showed up as connected to the internet.
orbirick
Apprentice
Dec 23, 2017
With the knowledge that Orbi recently supported wired backhaul, I was in Costco about a week ago and saw the RBK53 system on sale for $70 off and impulsively decided to splurge on it.

I haven't had time to install it yet, but have already downloaded 2.1.1.12 and 2.1.1.16 for a manual upgrade when I do get around to cracking open the box.

However, reading the posts here, I find myself wondering if Orbi is worth the effort, but then I also realize that only the posters with problems tend to create posts. But man, the Orbi system certainly sounds like a problematic system with as many posting issues as there are.

Regardless, I intend to give it a try and plan to replace my existing RT-AC56U router and RT-N66U configured as an AP. I have ethernet run from my office to the den and living room where I plan to place the router and satellites and know to update the satellites before the router.

Other than that, is there anything special I should do to prep the Orbi system for installation? Are you guys separating the 2.4 and 5 GHz bands using separate SSIDs? It's been my experience with iPads, iPhones, Android phones, etc. that they tend to grab the first signal they get (typically the 2.4 band) and hang onto it for dear life.

I presently have separate SSIDs for the 2.4 GHz and 5 GHz bands so the 5 GHz devices can roam and stay with 5 GHz leaving the 2.4 GHz devices to do their own thing on the 2.4 GHz bands.

I have a couple of 8 port Gb switches, but am considering using my old primary router (RT-AC56U as a switch in the office (configured with wifi and DHCP disabled):
Internet/modem->RBR50 WAN port->RT-AC56U (now a switch)
AC56U->RBS50->4k TV
AC56U->printer
AC56U->PC
AC56U->8 port Gb switch on the other side of the house->RBS50, PS3, PS4, Fire TV, TV, etc.

I don't see a need right now for that 2nd 8 port Gb switch.

Once I have the new firmware upgraded, I should have wired backhaul and I expect the upstairs to get excellent wifi coverage with the 3 units positioned pretty much at either end of the house and a satellite near the center.

Any comments/suggestions?
House layout.pdf210 KB
RogerSC
Virtuoso
Dec 23, 2017
Trying an experiment here. I've flashed back to v2.0.0.76, and am waiting to see if I get auto-updated. In addition, I have the Orbi in AP mode, and R7800 in "wired-only" mode. And dd-wrt firmware on the R7800, with "netgear.downloads.com" and "netgear.download.com" blocked via dd-wrt "access restriction". Going to wait to see if the Orbi gets auto-updated...so far, after almost a day, I'm not getting the "there is newer firmware available" message yet, and things are stable and working well.

We'll see if Netgear can find me and auto-update my Orbi :-). Got a while to wait before I'll know.
- aaz
  Virtuoso
  Dec 23, 2017
  RogerSC wrote:
  Trying an experiment here. I've flashed back to v2.0.0.76, and am waiting to see if I get auto-updated. ....
  Um, you won't get any auto updates since Negear has stopped auto updates over the holidays. You'll get it in the new year.
  - RogerSC
    Virtuoso
    Dec 28, 2017
    aaz wrote:
    RogerSC wrote:
    Trying an experiment here. I've flashed back to v2.0.0.76, and am waiting to see if I get auto-updated. ....
    Um, you won't get any auto updates since Negear has stopped auto updates over the holidays. You'll get it in the new year.
    We'll see how long I can wait, since the latest was working fine for me as well *smile*. I'm not sure that just because I see the "there's newer firmware" message that the Orbi in AP mode will be able to download it with the "wired-only" main router access restrictions in place. Time will tell.
- orbirick
  Apprentice
  Dec 23, 2017
  I confess I’m having 2nd thoughts about setting up the Orbi system. The issues here greatly concern me that I’ll have to nurse the system along to keep it running.
  
  Im starting to reconsider deploying a trio of Ubiquiti USP-AC-LITEs in lieu of the Orbi system and continue to use my AC56U as a router only and disable WiFi on it.
  
  I’d much rather have a reliable system that just works vs dealing with a temperamental system that lives on the bleeding edge to see a performance difference I may not even notice.
  
  Am I reading too much into all these posts about firmware issues?
  - orbirick
    Apprentice
    Dec 23, 2017
    *UAP, not usp. Thanks autocorrect.

Forum Discussion

Orbi firmware v2.1.1.16 discussion