NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Feedback for R7000 New firmware 1.0.9.18
Hi All,
Please post here for any update/issue related to the latest firmware 1.0.9.18.
You should review this and maybe revert back to this recommended version of FW:
Alfikwrote:I've looked here again after a while and I can't belive the problem is still not solved....
Since I've flashed Tomato a few weeks ago I've forgotten that I have a router- it's working perfectly getting dust because i do not touch it at all :-)...
Parental control works perfectly, 0 drops, strong signal - save your time and do a similar thing!
896 Replies
Installed the .20 firmware hotfix about 5 minutes ago. So far, everything is back up and running. I will give you guys an update when I can. Thanks.
Is the .20 code still beta; I'm not seeing anything that looks like a final release.
not to happy after upgrade
after firmware V1.0.9.18_1.2.27 no android device will give internet connectivity.
did downgrade v1.0.9.14_1.2.25 works now
dowloaded from netgear
good luck
Holy cow, I just ran into this issue HARD on 1.0.9.18, after running on it basically since it came out. I saw that the .20 hotfix was out, and even attempted a factory reset on that version as well. After the factory reset the only thing I configured was the basic Wifi settings, and clients immediately had issues, basically everything else was default.
I also tried downgrading back as far as 1.0.9.6, and the same problems came up at every previous version. It seems like once this bug triggers, it's pretty darn persistant.
So after a lot of random attempts, I re-upgraded to 1.0.9.20 (along with another factory reset). While my problems were primarily related to the 2.4Ghz band, I went ahead and tried something different. I disabled the 5Ghz radio completely, and changed the 2.4Ghz radio to disable the 20/40Mhz coexistance & set the mode to 54Mbps specifically. Sure enough after that the 2.4Ghz band appears to at least allow clients to connect (granted the performance is relatively terrible).
Based on this behavior, I don't think the 1.0.9.20 version is fixing the issue on all devices. I really hope that a complete software fix comes out soon on this, as it stands I'll have to replace the router within a few days (family complaints), and I'm sure not replacing it with another Netgear if these problems still exist.
One thing I'm noticing, is that the 2.4Ghz band has massive latency spikes across the board when it's broken. Reducing the mode down to 54Mbps also reduces the latency spikes, though they are certainly still there (seeing spikes of +100ms or so at 54Mbps, but at 289 or 600Mbps the spikes jump to 1000-2000ms, with lots of packet drops.
Seems like 54Mbps might just be masking the problem, but at least it get's clients somewhat reconnected.
I am having the same problems with the 5G network. It keeps kicking everyting off the network and has to be reset. Is there a fix for this yet or is there one on the way?
I am up for suggestions!!!
- The suggestions seem to be a combination of:
* Turn on QOS, update the QOS database/engine, then turn it back off
* Turn off the guest Network
* Turn on access control and allow all devicesWill I did it. Installed Tomato firmware about three days ago. It was something I wanted to do for awhile, but now feel I was force to.
The setting pages pop up faster.
The login is faster.
I can find the setting I need easier.
But there are so many settings I don’t know what they are or how to use them.
Wifi seems faster – Now getting 9.8Mbs instead of 6.8Mbs
That may be anecdotal. Xfinity may have sped up my connection.
I am still struggling with getting my laser printer to work with the USB connection. Both with linux and Windows 10
I feel satisfied with the changes.
For those that have made the same changes with adding Tomato firmware, please post your experience.
Update has caused my internet speed for wired systems to drop to 12mbps, where wireless connectivity is around 90mbps. Before update my wired connections were around 90mbps. When I go back to older firmware my wired speed increases to where it should be.
JamesGL wrote:Hi All,
Please post here for any update/issue related to the latest firmware 1.0.9.18.
Lost WIFI 2.4 after 5+ days. I had downgraded and reset router, I think to 1.0.9.6 and all was working great for more than 5 days but since yesterday, it started dropping 2.4 again every few hrs even at that old firmware. Netgear, please help us!!
- I stop trying and waiting today.
I don't want to be a tester when I paid 100%. I bought a TP Link C2300 and it's working like a charm.
I wish you all the luck in the world with solving the problem you cause.
I'm on the cusp of ditching Netgear and returning some Netgear EX6120 extenders I recently bought. It's a race between Netgear's ability to fix this problem completely in the coming days, the availability of sale prices on alternative solutions from competing companies, and my patience with this problem even if sales don't come. I'm not betting on Netgear. in this race. Why should I? Have they shown any competence or willingness to support their products?
If Netgear doesn't start communicating soon - they act as if this problem doesn't exist - I'll just move on. So will any others that I can influence, and I do so regularly. If Netgear can't be bothered to even reply with some coherent acknowledgement of the problem, they don't deserve our business again.
I'm researching mesh network options. Netgear Orbi seems highly rated, but of course I'll dismiss it out of hand. Netgear simply doesn't support it's products, so buying Orbi is like gambling on flushing that money down the toilet. Does anyone have any opinion or experience with Eero? If I get by with an R7000 and one EX6120 extender today, can I expect the Eero coverage to be better, worse, or about the same?
Now, a little more info to satisfy the small sliver of hope that this problem might yet get solved and save us from having to all spend more money immediately....
I've been running 1.0.9.18 since a day or two after its release. Plenty of 2.4 GHz drops, even after I disabled the guest network.
Without rebooting the router, I've been stable for at least 24 hours after having done nothing in particular. It may have been longer - I was not home and simply didn't check often. I still think there's a chance this issue is not purely a firmware problem, and may have an environmental component.
It looks like the jury is out with 1.0.9.20. If instability of the 2.4GHz connections resurfaces, and I think it likely will, I'll upgrade to that firmware immediately.
The worst part of all of this is that Netgear recently implemented the auto-update firmware feature, which likely pushed down the affected firmware to countless devices worldwide. I haven't seen anything from Netgear acknowledging an issue, nor have I seen anything indicating that some firmwares have been pulled from the website (meaning that Netgear is continuing to push affected firmwares down to customers even today).
The only reason I haven't bought a new router is that CES-2018 is in two weeks, and I'm hoping I can limp my R7000 along until then. I suspect this year will see vendors releasing routers/switches supporting Nbase-T (2.5 & 5Gbps ethernet!), and if so I'll ditch the broken R7000 & move to one of those immediately.
- mzguy...earlier post from someone said he did a complete overhaul and used advanced tomato. The problem persisted. Honestly, .18 lasted 5 days for me and im on day 3 of hotfix. And im not hopeful. I feel, at this point, netgear broke their own gear. I truly dont know what else anyone can do. I, being a soho user, am out of patience and time. If the hotfix fails, i already picked out the next router. Something in a nice triband sounds good.
AtoZ wrote:
mzguy...earlier post from someone said he did a complete overhaul and used advanced tomato. The problem persisted. Honestly, .18 lasted 5 days for me and im on day 3 of hotfix. And im not hopeful. I feel, at this point, netgear broke their own gear. I truly dont know what else anyone can do. I, being a soho user, am out of patience and time. If the hotfix fails, i already picked out the next router. Something in a nice triband sounds good.Thanks for the nice summary. Version .18 lasted less than a few hours for me, so that was an easy one to dismiss. In the absence of complete stability or a clear statement from Netgear, one would be insane to be hopeful, and insane to ever buy a Netgear product again! Based on reports here, it appears that Netgear indeed broke its own gear, or is completely susceptible to some type of environmental factor where other brands aren't. I'm out of patience and time too. I'm doing only easy fixes at this point, and waiting for the problem to get worse, or a sale to come for a competitor. For me to stay with Netgear, they have to really fall on the sword and issue a clear statement indicating they screwed up, they understand the problem, including why it persisted across firmware that was otherwise fine for months, and offer an immediate working solution.
If Netgear permanently broke thousands of devices through an error, they should immediately reach out and offer compensation. That's what a good company would do. Some companies only respond to public or legal pressure though. If they keep this up, I'm confident that one or both of those will arrive at their doorstep before too long. I wrote a long post almost 2 weeks ago, urging Netgear to step up and start communicating. Instead we just get firmware updates every few days for "security issues".
I tried to get firmware 1.0.9.18 last night ( after an automatic shutdown problem).
The download went quick, the install went quick, BUT it hung up on the REBOOTING. The crawl line was completely filled, but the darned thing never completed a REBOOT after D/L and Install.
Speed are good. 50M down and 16M up on a 50M service. (Speettest on native Android)
I'm giving .20 another try. Speeds improved. I remembered that after reboot I've always required a sort of ramp-up period over a few minutes, before speeds were good. I have not cancelled my Eero order, given that others haven't had luck with .20. If it's flawless over the course of a week and Netgear chimes in, I'll reconsider. Otherwise, my R7000 will likely be demoted to a switch.
Hi All,
All issues you have raised are gathered and has been reported. This includes the version 1.0.9.20. I will provide an update with this issue.
> [...] This includes the version 1.0.9.20. [...]
Might it be time to unpin the announcement of "New: R7000 Firmware
Version 1.0.9.12"?:
https://community.netgear.com/t5/x/x/m-p/1391950
One might reasonably think that any pinned topic with "new" in its
title, and which has been up for, say, six months, might be due for
retirement. Just a thought.
> I will provide an update with this issue.
Do you intend to provide any more information than the
always-information-free firmware Release Notes?Hi antinode,
Thank you for that. I will unpin the said topic. The update I will provide is regarding the issue raised using the latest firmware. The release notes focused on the security issues that has been reported which NETGEAR wanted to address right away.- Regarding security, please also alert the developers that:
- There is a topic here claiming the VPN service uses an MD5-based cert. That is, honestly, attrocious if it's true.
- There is still no button in the admin console to generate a new VPN key (replace the old one). This is also super bad.
Please stop ignoring security issues.
Pass thru Bandwidth speeds is limited to 25Mbs. 200+ straight connect. Disable QoS and pass thru nears 200. Reenable = ~25-50Mbs on manual and back to <25Mbs on Dynamic.
Disabling QoS makes gaming latency imposible. "Teleporting" FPS; and "Strict" or "Moderate" NAT at best.
My latency is erratic and rarely below 80ms. This further wrecks havoc on gaming. Some of it is Spectrum sourced (technician to come tomorrow) but numbers are worse through router. Latency numbers were mimicked prior new firmware.
This all started when I upgraded firmware to V1.0.9.18_1.2.27 yesterday. I had no problem with old firmware that was over a year old. I should have noted which release it was so I could revert to it.
After reading many of the posts in conjunction with my own experience and posts on other sites. I believe I will forego any futher investment in NetGear products. Complaints are numerous and varied and appreciable response has been lukewarm and infrequent. I will be shelving or discarding all my suspect NG equipment. Simply donating them to someone would be giving them a unnecessary frustration.
Thank you NetGear but I think we should see other routers. Good luck but lose my number.
I received this from Jamesgl last night...
Hi AtoZ, Please provide me the following information. I will endorse you to support team. Name: Phone number: Email Address: Best time to contact: Timezone Regards, JamesGL Community Team
Just a question or two to everyone on this board...has anyone been helped by calling tech support about this issue?! Have they even acknowledged this issue in the last month and a half?! If I am wrong about this, I will get on hold with India or wherever, right now, but I don't think I am. Hey netgear, FIX IT! We didn't cause this, you did!
