Your experience with Firmware 2.2.1.210 released as of 10/3/18

Hmmmmm mine is also back to 210.

I also blocked auto update with telnet.

That's why my wifi was so bad today.

In 2.2.1.210 Netgear has fixed issues related to wired backhaul and I guess that this might have affected the sensitivity of the system to wired devices.

I'm saying this because I had all different types of issues with this release when it first came out in October: Wifi drops, no internet, worst internet speed, ... etc. I simply could not work from home becaue of my bad wifi at that time.

When I dosconnected the wired devices connected to the Satellite all issues were solved at once. I found out then that my wired speakers -for some reason- caused all issues.

I have now the best wifi network I've ever had, a very stable network with excellent coverage.

Please troubleshoot you issues by looking at your configuration and try to locate where the problems are. Look specifically at your wired devices. try first to disconnect all wired devices and if you see improvement, try to connect them back one by one to find the culprits.

Sorry, but sound sad, that you must disconnect your equipment to get everything working that was working perfectly before .210

Try this:

https://community.netgear.com/t5/Orbi/Firmware-2-2-1-210-released-as-of-10-3-18/m-p/1647303/highlight/true#M42416

Try setting manual channel 1, 6 or 11 on 2.4Ghz and any unused channel on 5Ghz.

Try disabling the following and see:
MIMO, Daisy Chain, Fast Roaming, IPv6 and Set 20/40Mhz Coexistence to 40Mhz only. Save settings and reboot the router and satellite(s).

If you updated to recent FW v.210, try enabling Daisy Chain. Some have mentioned that this seems to be working in reverse order, enabling means disabled actually.

---

JeroenM wrote:

Hmmmmm mine is also back to 210.

I also blocked auto update with telnet.

That's why my wifi was so bad today.

---

100% agreed, I just downgraded again! And Modify the nvram again! Will see how it goes...I have a case open with support…. I just want to know if anyone that have issues had call and complain… apparently NG don’t care about their community or they don’t read anything…

We all have done this, too many times, again disable features that where working before is not a good way to fix it... Just pull out the firmware and stop auto update until NG fix the issue!

Or easier, stop auto-updating our Orbi systems!!! I still don't understand why they started auto-updating us. Luckily all my LIfx bulbs are ok now on the latest firmware but stop with the auto-updates. I want to update on my terms.

---

LycanChief wrote:

Sorry, but sound sad, that you must disconnect your equipment to get everything working that was working perfectly before .210

---

Yes, not that optimum for me, but at least I solved my issue and now have a great wifi. I have the speakers connected wirelessly to Orbi and working great since the wifi coverage is excellent. 

I’m saying this to tell you that Orbi is working for some people, the Orbi firmware is not perfect yet for sure, and seems very sensitive to ccertain conncted devices. I hope that NG will fix this soon. 

I meant that with some troubleshooting, everyone can locate where the problems are, get Orbi working and get the best out of it. This will also help NG fix the right things in the coming software releases. 

After again disappointed kids because the rented online movie keeped stopping (on a smart tv with a LAN cable connected), called our cable internet provider to switch the modem back to router modus (i was on bridge modus, as i hoped the orbi system could handle all the router "things").

So now back on the (ziggo) modem & router and switched Orbi to AP modus.

FURRYe38 did all the things you suggested here (and also other tips on other topics).

My conclusion: The 210 firmware of Orbi can't handle big streams Lan or Wlan

You can down grade to v.16 and see if this might help:

Download version 2.1.1.16 for both the router and satellite.
https://community.netgear.com/t5/Orbi/Orbi-RBK50-firmware-V2-2-1-210-update-slows-WAN-speed-with-30-to/m-p/1651159/highlight/true#M43338

You'll need to block the auto updater...

---

JeroenM wrote:

After again disappointed kids because the rented online movie keeped stopping (on a smart tv with a LAN cable connected), called our cable internet provider to switch the modem back to router modus (i was on bridge modus, as i hoped the orbi system could handle all the router "things").

So now back on the (ziggo) modem & router and switched Orbi to AP modus.

FURRYe38 did all the things you suggested here (and also other tips on other topics).

 

My conclusion: The 210 firmware of Orbi can't handle big streams Lan or Wlan

---

I did downgrade to 2.1.4.16 and telnetted to block auto update.

Fortunate the orbi's felt like updating and did??? (could it be because i logged in with the orbi app??)

I now downgraded to 2.1.1.16 and again blocked auto upgrade.

Wil post an update if i got news :-)

Ya, possible the app checks updates regardless of whats set on the Router itself.

Let us know...

---

JeroenM wrote:

I did downgrade to 2.1.4.16 and telnetted to block auto update.

Fortunate the orbi's felt like updating and did??? (could it be because i logged in with the orbi app??)

 

I now downgraded to 2.1.1.16 and again blocked auto upgrade.

 

Wil post an update if i got news :-)

---

You didn't forget the "nvram commit" or something?

It'll be frustrating if blocking auto-updates doesn't work. Next step will be to figure out what traffic to block.

Yes i did the commit :-)

Don't be surprised if NG is working to disable any kind of update blocking. :smileyfrustrated:

They shouldn't be surprised either if I never buy one of their products again.

Not the first one and probably not the last.

should they be focussing on fixing the 210 ????? :robottongue:

---

UnhappyOrbiUser wrote:

They shouldn't be surprised either if I never buy one of their products again.

---

Yep, too bad too, as I've had decent luck with their stuff over the years.  Most of the consumer network providers have gotten better since the early days.  But these messy firmware changes have become a horror for all of us that rely on their hardware to enable our networks.  You don't see these kind of really bad problems with the companies that sell enterprise/commercial products as often, which is why I've used mostly that stuff for years.   Figured I'd try some new consumer stuff this time around, and I now regret it.  The consumer network companies are completely non communicative with their customer bases, which is somewhat undstandable as they are enormous, but these are true Severity 1 problems, and Netgear is really failing us all.

---

nanohead wrote:

Yep, too bad too, as I've had decent luck with their stuff over the years.  Most of the consumer network providers have gotten better since the early days.  But these messy firmware changes have become a horror for all of us that rely on their hardware to enable our networks.  You don't see these kind of really bad problems with the companies that sell enterprise/commercial products as often, which is why I've used mostly that stuff for years.   Figured I'd try some new consumer stuff this time around, and I now regret it.  The consumer network companies are completely non communicative with their customer bases, which is somewhat undstandable as they are enormous, but these are true Severity 1 problems, and Netgear is really failing us all.

---

No kidding.. after years of getting by with cheap routers and messing around with OpenWRT, I finally bit the bullet and decided to spend the money for one of these supposedly better systems, especially as I needed something to extend the range. I tried the Orbi and another one (I forget which), and stuck with Orbi for some reason.

Like you, I regret the purchase, it isn't worth the money I shelled out for it.

Regarding my report of auto-update-blocking not taking:

When I originally attempted to block the auto-update, it looks like I didn't change the orbi_auto_upg setting - the 4th one that was added after the common instructions were written.

Aggravating matters this weekend was that I think I went through three rounds of downgrade-then-immediately-auto-update.  In one of the more memorable iterations, it auto-updated while I was working on the nvram settings.

My threat to shop for Ubiquity gear seems to have done the trick, as my Orbi became stable (on .146, without auto-updates) shortly thereafter.