Firmware 2.2.1.210 released as of 10/3/18

As per Netgear's recommendation I proceeded to upgrade the satellite firmware first. While the satellite was upgrading the router decided to upgrade on its own automatically.

Netgear, why are you recommending the satellite upgrade first?

Netgear, why don't you guard against the router upgrading automatically while the user manually upgrades the satellite?

Netgear, if you recommend to upgrade the satellite first is the upgrade order respected when the user clicks Upgrade All?

After all upgrades completed both satellite and router show the new firmware. Now for the problems:

• One device, an iPhone 8 which normally connects to the satellite since most of the time is much closer to it than to the router, now shows in Attached Devices (router's web page) as connected to the router at 2.4GHz. But if I check the satellite's web page the same iPhone is connected to the satellite at 5GHz, connection type unknown. Same MAC address shown on both web pages.
• Since version 2.1.4.10 I was having trouble with the logs emailing. I had initially set the log emailing when the logs are full but I would rarely get an email because apparently the logs were cleared before being emailed. Since I only upgraded to the current 2.2.1.210 version just  today I cannot yet verify that the log email problem is still preset. But I notice a new log problem: Since I performed the firmware upgrade the logs no longer show anything about DoS Attacks and other forms of attempts. They only show Admin Login, DHCP, Access Control and so events.

With my previous version, 2.1.4.16 the only problem I was aware of were the logs apparently getting cleared prematurely. Now add to it the issue with no longer logging intrusion attempts. Honestly the quality on Netgear's programming seems to suffer a lot, dragging their brand name into the gutter. Maybe it's time to fire the entire team in software development and hire more competent people. I know that operating systems like Windows or Mac have bugs when new versions are realeased but their number compared to the complexity of the project makes it more reasonable. Can you imagine if the monthly Windows update would be as buggy as the past several versions of Orbi firmware? Can you imagine Microsoft recommending that after you install the monthly update you hard reset Windows?

Come on, Netgear... for the sake of your current clients, for the sake of your future clients, for the sake of your brand name get serious.

I operate my Orbi in AP mode as router mode caused problems.

Just successfully updated to 2.2.1.21, still in AP mode. 

I'd prefer to use the Orbi in router mode and remove the DLink router. It's a pain to swap out router, so just wondering if anyone has seen router mode improvements in this version, or swapped back to router from AP mode? (info on what has been fixed is scarce).

So I spent some time last night downloading something that would run TELNET on my MAC... then I downgraded all the firmware, went into the router and changed the auto update settings to 0 - I saw something on reddit that said they wouldnt update if I did that...

AND THE ROUTER AUTO UPDATED...

My macbook connects but gets internet slowly or not at all.

Something wrong here.

And now I cant stop the thing from updating.

Anyone having HomeKit devices issues with this FW? I can’t acces any device from my home app on my iPhone when I’m not connected to my home wifi. I can however access all the devices using their manufacturer app. Example Wemo  I have a bunch of Wemo switches in my house and I use the Wemo bridge to enable HomeKit compatibility and use the home app to control them all. Before this FW I was able to access and control the devices when I was away from home now I can only do it when I’m in my home WiFi, if I’m on LTE or another WiFi away from home all the devices show UPDATING  and eventually NOT RESPONDING on the app. However if I use the Wemo app from outside my network it works no issues looks like this is an specific issue with the HomeKit protocol. 

I have been following this thread and was dreading the update.  My system is a simple setup of a router on level 1 of the house and a satellite on level 2.  

I was updated automatically on Saturday and was unable to connect to the internet after the update.  I then powered off the router and satellite.  I rebooted the satellite and when I was able to connect to the internet a few minutes later I then plugged in the satellite.  Since then the system  is perfect.  I have both 2.4 and 5g connected with approximately 9 evices connected, 8 wireless and 1 wired printer connected directly to the router. Everything is working flawlessly.  

Under the old firmware I was disconected randomly from the internet, especially (as I work from home) when I was connected to my firm's VPN.  Note that these disconnects never happended while connecting to a non-orbi router system.  It was definitely an Orbi problem as has been documented by manhy other users.  

Today is the first day back at work and after 2 hours I have (Thank G-d) not experienced any disconnects.  I will report back after the work day concludes with an update.  

Daisy Chain is supposed to let the satellites connect off each other when positioned in a line to each other. Sounds like that something may have changed possibly in the code regarding Daisy Chain.

 https://kb.netgear.com/000048458/What-is-daisy-chain-and-how-does-it-work-with-my-Orbi-WiFi-System

I am curious to know, for all of you having issues with the Daisy Chain option being on/off, are you connected via Wired or Wireless Backhaul?

For the Wired Backhaul users, are you seeing issues with this setting? I am running on Wired Backhaul and have Daisy Chain set to off, with no issues.  Only problem I am seeing is that the web GUI is not recognizing devices being connected to the Satellite, and instead reports them as being wired to the main Orbi unit.  My iPhone is definitely not wired to the main Orbi. :smileytongue:

Cable Modem: Arris SB6183.

Orbi: RBK50 (router + 1 satellite).

I did a manual update of the satellite first. While the satellite was updated the router decided to auto-update. The router was connected to the cable modem at the time of the auto-update.

Several days after the update to v2.2.1.210:

• iPhone connected to the satellite shows connection type as "unknown".
• Problems with the logs:
  *  I have the email logs set to Daily. The logs are emailed but do not seem to clear after that as they did in the past. Next day the email will include the previous logs as well.
  *  Intrusion attems do not appear to be logged. Only Login, DHCP, Access Control, Email Sent and so on events are logged. No DoS Attacks.
• As mentioned, I only have one satellite. My Daisy-Chain Topology is enabled and I do not seem to have connection problems.

Other than the above everything else seems to be normal so far.

i had 2 systems upgrade - the daisy chaining of the satellites seems to be working better.   One satellite far away is finally daisy chaining instead of before I would get "poor" signal strength. 

One 2.4 ghz device breadmaker seems to be no longer able to connect - tried many different resets and guest network.  Finally had to use an extender to get this device connected. 

My router updated last night and now my iPhone won't connect, when I try to connect to websites I get a certificate error that is pointing to routerlogin.net.  It only affects my iPhone from what I can tell.  No other devices, not my Apple TV's or cameras or TVs or computers.

I've turned off daisy chain and I would rather not hard reset the router.

Any fix for this BS issue?