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...
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.
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!
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.
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.
Same here. Finally got tired of restarting these things 5x+/day and rolled back to 1.12.0.18 this evening, and I'm keeping my fingers crossed that that keeps things stable until Netgear can sort out the dearth of issues introduced in the 2.x firmwares. It's incredibly disappointing to drop this much cash on a product only to have its vendor trash it with pre-alpha firmware updates.
Just for the benefit of anyone who's following along... After rolling back from 2.1.1.16 to 1.12.0.18, I continued to deal with WAN connection issues. After the first dropout the next morning after the rollback to 1.12, I rolled back again to 1.11.0.20. I've been running that firmware without any issues for almost a week now. I had a dropped WAN connection this morning, but given the stability I've seen over the last several days, I'm almost willing to chalk that one up to my ISP (though I'll be keeping an eye on it). The only drawback I've seen to the older firmware (less being vulnerable to KRACK and probably some other security vulnerabilities that I haven't glossed over any release notes for) is that my iPhone 7+ doesn't seem to work as well at distance as it did with the 2.x firmwares. Given the stability I've gotten back, I'm willing to deal with that for the time being.
- I've been running 1.11.0.20 for the past week or so and it was working great but it started auto updating to 2.0.0.74. Every time I tried to downgrade the firmware, it would immediately update it again. I even tried the telnet method of disabling the auto updates but it would still update almost instantly after loading it with the older firmware.
Anyone else noticing this issue?
