Firmware V2.1.1.16 auto update

Darren,

Can you tell us what issues the engineering team is aware of and investigating?

Beyond the display errors of devices not showing connected to the satellite, are the engineers aware of and actively investigating the reboot issues that are occuring with a large number of users?

---

DarrenM wrote:

We are aware of the issues and working on fixes I have no ETA on the next firmware release past .16.

 

DarrenM

---

Hey DarrenM - Happy New Year.

I know you probably can't commit to a release schedule, but I am curious to hear if your engineering team has been able to replicate any of the issues reported here (or if there is something that we can do to help). 

EDIT:  I see the beta release here now.  Thanks!  https://community.netgear.com/t5/Orbi/OrbiOS-2-1-1/m-p/1476960#M19962

M

---

DarrenM wrote:

yes the reboot and disconnect issues are all being investigated.

 

DarrenM

---

Might I suggest you strongly look at the UPNP handling subsystem, I and at least one other person found that to be the cause. Both of us have seen UPNP activity when the reboots would occur. 

I have every setting on except Circle and everything else is stable. I use the Netgear OpenDNS for content protection. I run it as a router not an AP.  In fact I would recommend everyone just try to repeat my settings because this has been the most stable router I've had since my old netgear N600 a long time ago, which was way more stable than my Linksys WRT54G, Apple airport extreme, Dlink AC1200, Asus AC87U, etc... 

---

DarrenM wrote:

yes the reboot and disconnect issues are all being investigated.

 

DarrenM

---

I am not facing any issues yet with 2.1.1.16. That being said, speaking of Auto Update, I think Netgear should allow users to disable automatic firmware updates; instead just send them a notification via the Orbi app and email (e.g.) stating that a new firmware is available with a link to the release notes and let users decide if they want to upgrade based on the benefits of the new firmware.

I realize it is a double-edged sword given important updates like the KRACK patch and MAJOR performance improvements e.g. where auto update ensures everyone gets the update, even people who are not tech savvy and who would not update on their own.

However, when stability issues come into play (I am not facing any luckily), auto update can be frustrating someime staking a well working system and impacting its connection stability. I have family members using routers who would need help from other family members / friends to download an older version of the firmware and update it for them, so this is especially frustrating in those situations. This is exarcerbated in case where non tech savvy family members live far away.

It doesn't mean it isn't connected, at least.  I have all sorts of listing "anomalies", but I know the devices are connected (since the list is wrong, it's hard to trust what the Orbi says in terms of where/how it's connected, though).

For instance:

* I have a couple of Amcrest cameras that don't show in the router/satellite lists at all.  I know they're connected, I can view them - but since they're not listed, I can't be sure to which unit they connect.

* My satellite's list is empty again.  The router does show connections to satellite, and those mostly seem plausible...

* I have a couple of devices connected wirelesssly, that the router list shows as "wired."   Which is impossible, not sure how it's gotten that idea, and disconnecting and reconnecting the client (wireless) isn't changing that.

Appears what they thought was "cosmetic" is more a bad breakdown in its connection accounting code across the board.  2.0.0.76 wasn't great, but 2.1.1.16 fails epically.

---

Retired_Member wrote:

On the Orbi web GUI...some mention ..."my so and so is NOT listed showing connection".....does that affect it's connectivity?   Does the device still work?  I guess for me...if it works yet fails to show on a GUI list yet it still works, and they are aware, all well.  

---

---

jvaudio wrote:

Hello,

I have had a few disconnect issues, but have been more fortunate than others in that regard - but I am glad you are still investigating those issues.

 

One issue that I would like investigated is the backhaul speed between the RBK50 and the RBS50's.  When I purchased my Orbi setup (one RBK50 and two RBS50's), I was getting transfer speeds of 100MB/s or more between my PC and my Synology.  After I updated the firmware (on the third day - to 2.0.0.74(?)), the speeds have been abysmal. I am lucky to get 5MB/s.  The connection is good between the satellite and router. They are 23 feet away from each other. 

 

I have tried everything other users have recommended in these forums (turning on/of beamforming, MU-MIMO, fast roaming, daisy-chain topology) to no avail. 

 

I hope that this is being investigated by the team at Netgear.

 

Thank you

---

Can you tell which units your PC and your Synology are connected to? What does your setup look like? Are you daisy chaining (R -> S1 -> S2) or wagon wheeling (S1 <- R -> S2) the satellites to the router? Can you turn off the satellites and hook up both devices to the router, and does the connection speed return to normal?

rhester72 I thought they were going to stop auto push until Firmware was corrected and fixed before re-release or new version

My system auto-updated to 2.1.1.16 in the wee hours of 12/27, when I was on vacation. The satellites immediately disconnected, taking down my security cameras and other household infrastructure.

WiFi is now unstable. The router truncates my password after the first character ("$") and shuts down WiFi entirely when rebooted.

Bringing satellites into same room for troubleshooting and I can reconnect one but not the other.  The one connected satellite disconnects every few hours.  

I manually rolled back to 2.0.0.74. This corrected the password flaw on the router, but now neither satellite will connect.  

The system was working flawlessly since August until this auto firmware update.