NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Your experience with Firmware 2.2.1.210 released as of 10/3/18
The other long thread on the new firmware is useless and has become a tech support thread. Please only post your experience after upgrading to the new firmware, good or bad. I'd like to see everyone'...
Something to try,
You might set up the ISP modem for router mode and change the Orbi to AP mode and test to see if the Orbi still looses the conntection. You can try router mode as well with the Orbi if you want. Just use DMZ on the ISP modem for the Orbi.
When you get time, I would also do a full manual re-load of the FW as well and start from scratch if the above suggestion also fails. If this fails as well with continued disconnections from the ISP modem, would contact NG support and get an RMA.
To answer your (and ekhalil's) questions:
- I have several items with reserved IP addresses (5 currently) and around 12 devices that are assigned IP address dynamically by the router.
- The DHCP pool size is 150
- Deafult DNS currently though I've tried Google's DNS servers; it make no difference.
- Both wired and wireless intenet connectivity goes down.
- I do have several Sonos speakers but they ARE NOT hard wired.
- My modem is the Netgear LB2120 4G modem operating in Bridge Mode. I get my home broadband via a 4G mobile/cell network. I know the modem is working for two reasons: I can connect my laptop via Ethernet and its connected. Additionally, I can connect (via IP) to the modem fom my desktop and send a text to my mobile showing that it is connected.
- I haven't yet done a full install and reconfigure of the firmware and won't get the time to do this for several days.
Just adding to the data
RBR50+RBS50, router mode, wireless backhaul. Xfinity gigabit-ish speed service, with an SB8200 cable modem. Everything worked great until 2.2.1.210 was pushed to me.
After I got the auto-update, my RBR50 started rebooting every few hours.
A manual update and factory reset cleared up that problem for about a week. However, while I was out of town yesterday, my wife complained "the internet is down". She wasn't willing to troubleshoot, so I had her cycle power on the power strip both are connected to.
I got back late last night, and during the day today, I've been plagued by the reboot issue again. Since we rely on PSVue to keep the wife entertained, and I have VOIP phones for work...this is not a good situation.
I'm going to be poking through recent posts to see which firmware I should roll back to and how to block the auto-updates.
Generally I believe that auto-updates are a good concept, given the issues caused by folks who don't stay up to date with security patches. So it's worth noting that debacles like this actually do a significant amount of harm, by turning people against the auto-update concept.
Let us know if reverting back and blocking updates works for you...
MikeTheActuary wrote:
Just adding to the data
RBR50+RBS50, router mode, wireless backhaul. Xfinity gigabit-ish speed service, with an SB8200 cable modem. Everything worked great until 2.2.1.210 was pushed to me.
After I got the auto-update, my RBR50 started rebooting every few hours.
A manual update and factory reset cleared up that problem for about a week. However, while I was out of town yesterday, my wife complained "the internet is down". She wasn't willing to troubleshoot, so I had her cycle power on the power strip both are connected to.
I got back late last night, and during the day today, I've been plagued by the reboot issue again. Since we rely on PSVue to keep the wife entertained, and I have VOIP phones for work...this is not a good situation.
I'm going to be poking through recent posts to see which firmware I should roll back to and how to block the auto-updates.
Generally I believe that auto-updates are a good concept, given the issues caused by folks who don't stay up to date with security patches. So it's worth noting that debacles like this actually do a significant amount of harm, by turning people against the auto-update concept.
Just to follow-up on my earlier post ( 2.2.1.210 reboots, temporarily fixed by manual reload of firmware and factory reset...but eventually went back to frequent reboots) -- downgrading to .146 and disabling the auto-update seems (knock wood) to have restored stability to my network.
I waited until after the end of the work week to make the changes. Considering how easy they turned out to be, I wish I had done it earlier.
same here, also reverted back from V2.2.1.210 to V2.1.4.16, because it worked like ****. Had lots of wireless disconnects and even after a manual firmware flash and factory reset I still had problems like one satellite was only able to connect on the 2.4G band and after some time it was completely unable to connect the network in an daisy chain topology.
I am using an RBK40 Kit with an additional RBW30.
Try a Manual FW load next time:
https://community.netgear.com/t5/Orbi/Firmware-2-2-1-210-released-as-of-10-3-18/m-p/1647303/highlight/true#M42416Also,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.
Walhalla wrote:
same here, also reverted back from V2.2.1.210 to V2.1.4.16, because it worked like ****. Had lots of wireless disconnects and even after a manual firmware flash and factory reset I still had problems like one satellite was only able to connect on the 2.4G band and after some time it was completely unable to connect the network in an daisy chain topology.
I am using an RBK40 Kit with an additional RBW30.
An update to my earlier update --
I had rolled back to .146 and thought I had blocked the auto-updates.
Just got home to a rebooting Orbi. Apparently it auto-updated back to .210.
I'll re-downgrade. This is extremely annoying.
Has anyone else had issues with the nvram commands not being as "sticky" as they should be?
Since I made my last post, I've had to downgrade my RBR50 and RBS50 twice, even after setting and committing the nvram settings (including the newer orbi_auto_upg) to supposedly block auto-updates.
While I have not tested this fully (I'm trying to get some work done without the corporate VPN getting disconnected every couple of hours), the behavior is almost as if the Orbi triggers a flag for an auto-update once it learns that firmware updates are available, as it tends to do if you have gone to the firmware update page in the Advanced menu.
I'm hoping that re-resetting the nvram settings after an update is detected, and then simply not going back to that section in the Orbi settings will do it.
....and while typing this message, my Orbi just auto-updated back to .210.
I think I'm going to go check and see if I'm in some kind of warranty/return period, and figure out what I need to order from Ubiquiti. I've wasted too much time on this already, and as a telecommuter, I can't risk my corporate VPN or VOIP going down every couple of hours.
I downgraded over a week ago and did the Telnet commands. Apparently today, NetGear force the upgrade on my unit. Aparently is not scape of this horror.... I am close to start a class action again the company....
I am mad, and calling right now support and creating a complain... this is out of hand, from the bigining of october.. They dont look at their community and see this is a major issue....
I downgraded over a week ago, did the telnet commands to the nvram, everything was working perfectly until today, aparently they force the upgrade to .210....I am calling.... No way to disable autoupdate aparently
Great, they hang-up on me! Class Action Sude! Anyone!
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:
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.
- Is Netgear going to do ANYTHING to help, or just ignore and provide ridiculous “suggestions” of “try to disable daisy chain”....”try factory reset”....”change your radio channel”...etc, etc, etc...unplug your product you paid $1000 or more for and see is that helps (LOL)....???!
Or maybe....
REMOVE 210 FROM THE UPDATE SERVERS, LET US DOWNGRADE TO 204 AND PROVIDE SOME IDEA OF “WHEN A FIX WILL BE PROVIDED?!!!!!”
Even APPLE, which rarely admits to bad updates, removes updates when they hear its causing problem....E.G....Apple Watch OS 5.1....
This is truly sad of Netgear.
Very, very....sad.... 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#M43338You'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
Is blocking Auto udpate not working for you?
MikeTheActuary wrote:
An update to my earlier update --
I had rolled back to .146 and thought I had blocked the auto-updates.
Just got home to a rebooting Orbi. Apparently it auto-updated back to .210.
I'll re-downgrade. This is extremely annoying.
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 :-)
