NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Firmware V2.1.1.16 auto update
we'll be removing the v2.1.1.16 firmware from the auto update server over the holidays and will resume pushing it in the new year. Firmware will still be available on product support pages for manual...
aaz wrote:
richlin71 wrote:for what it's worth, I'm another previously happy Orbi owner who's now incredibly frustrated with Netgear and regretting my purchase.
if I recall correctly, my wifi started dropping with the old firmware 2.0.0.74, which is why I started checking these forums. Upgrading to 2.1.1.16 didn't help. Downgrading to 2.0.0.74 hasn't helped either.
It's hard to quantify how often wifi drops bc the logs are so unhelpful, but it's 5-10 times/day that I notice. VERY frustrating!
Most certaily it has nothing to do which version of firmware you are on.
As someone else here mentioned - it's most likely something new to your environment. If you had my very stable Orbi with my current 2.1.1.16 firmware on it in your home it would likely be crashing just as often if you set your settings on it the same.
The trick is to find out what device is causing it to crash - or what setting is allowing that device to crash it and disable that setting or disable the device from connecting.
It most certainly does have everything to do with the firmware, hence the over 130 postings in the other 2.1.1.16 post in this forum. And the number of complaints that started with the 2.x versions (1.x versions were rock solid) IS EXPONENTIAL. Please don’t just assume that since you are lucky and not having issues, that the countless number of other people who are having issues since moving to 2.x who are having multiple reboots PER DAY are just clueless and don’t know what’s going on with their system. That’s just condescending and unhelpful. Glad it’s working for you. Good for you. But there’s no environmental reason whatsoever that a router should be maxing out CPU and rebooting mutilple times per day since moving to new FW versions. NONE.
Fine dude - do what you've been doing and don't listen to what I say, because what you are doing has been working so well for you.
aaz wrote:Fine dude - do what you've been doing and don't listen to what I say, because what you are doing has been working so well for you.
Dude, you’re the one not listening to what others are saying, and then want to come in here and tell us we’re all doing it wrong, just cause your system happens to be working? Read post 157 of the long 2.1.1.16 thread. Guy had his system working fine for months. System autoupdated itself to 2.1.1.16, and he is now experiencing reboots with no changes to his system other than FW. Tell me what changed in his environment, if you’re all knowing? I’ll help you. It was the FW! If the system was working, and nothing changed, and Netgear auto installs FW that makes the previously stable system start crashing, that’s the FW’s fault, not “the environment”.
If you’re not going to help, spare us the lectures that this is all our fault, when it’s clearly not. Unless you happen to work for Netgear, and you’re just trolling to trying to take the heat off yourself...
EDIT
How about post 169 in that same thread. Same situation. Working fine for weeks, no changes, system autoupdated, now crashing. Sound familiar?
kmichalec wrote:Dude, you’re the one not listening to what others are saying, and then want to come in here and tell us we’re all doing it wrong, just cause your system happens to be working? Read post 157 of the long 2.1.1.16 thread. Guy had his system working fine for months. System autoupdated itself to 2.1.1.16, and he is now experiencing reboots with no changes to his system other than FW. Tell me what changed in his environment, if you’re all knowing? I’ll help you. It was the FW! If the system was working, and nothing changed, and Netgear auto installs FW that makes the previously stable system start crashing, that’s the FW’s fault, not “the environment”.
If you’re not going to help, spare us the lectures that this is all our fault, when it’s clearly not. Unless you happen to work for Netgear, and you’re just trolling to trying to take the heat off yourself...
EDIT
How about post 169 in that same thread. Same situation. Working fine for weeks, no changes, system autoupdated, now crashing. Sound familiar?
Well, forgive me for being blunt - I keep reading the same comments over and over, with every firmware update that I've seen on here now for 3 months - a new batch of people come online saying that the latest firmware has caused their systems to start rebooting.
This happened with 1.12.0.18, then 2.0.0.74, then 2.1.1.12, now 2.1.1.16
Then they claim that after they rolled back it stopped rebooting. Then they come back a few days later saying it still rebooting but it's still on the old firmware so that means the firmware update must have done something that changed it. Not once do they consider that it's something else on their network that just started happening coincidentally around the same time.
Meanwhile many others are running the new firmware without any reboots.
I've been in the IT game long enough to know that people are not good at replaying changes that they made and really don't know everything that's new on their network. I hear what you are saying, it's just that chances are that it's not the whole story. People make really poor witnesses. Yes, even if there are 20 people on here saying the same thing - there are 5000 running the firmware without any issue. So it's not the firmware in a vacuum that is causing the issue. Find what the cause is and you can fix your reboot issue.
I am not blaming anyone - where have I said it's your fault? I am trying to point to another way of solving this. It seems more like you are just saying that you are helpless in solving this and just want to heap blame on netgear (though they do deserve it since never have I seen envirnomental factors that are not power related before reboot a router)
You need to stop taking everything as a personal afront and start thinking in a solution mindset instead of a blame mindset.
Sure there is some blame that netgear is not helping resolve this, but I've posted elsewhere how many routers I've run in the past 10 years and most of them had some issues that required a weekly reboot because of loss of internet connection or devices could not connect to them. Asus just accepted that fact and built in a function to reboot the router on a schedule you set. I set that to reboot every night and even then there where days where it would crap out. The Orbi has been the most stable home router I've ever owned and that is saying something.
aaz wrote:I am not blaming anyone - where have I said it's your fault? I am trying to point to another way of solving this. It seems more like you are just saying that you are helpless in solving this and just want to heap blame on netgear (though they do deserve it since never have I seen envirnomental factors that are not power related before reboot a router)
Except for the part where you said it wasn’t Netgear or their FW, but our systems (whigh were working fine before the update with no changes.) Remember this?
aaz wrote:
“Most certaily it has nothing to do which version of firmware you are on.
As someone else here mentioned - it's most likely something new to your environment.“Funny you want to twist it around and say we’re not doing anything to help ourselves, despite the pages and pages of self analysis and information sharing people on this site have been doing, as we try to diagnose the issue FOR Netgear.
But, your equivalent of “your holding it wrong” is OH SO helpful. Thank god your here with you extensive years of IT experience. How would we survive without you?! Keep stroking off Netgear for us since you love them so much. The rest of us will try to figure out what’s really going on, and hold Netgear accountable for poor QA testing, and forcing us to be their Beta testers without giving us the choice whether to upgrade or not (thanks autoupdate).