NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Problem with R7000 freezing - possibly due to assigning IP addresses/DHCP
I'm running the latest firmware V1.0.9.60_10.2.60
The wireless connections keep freezing and the router recovers within about five minutes. When I look in the log after this has happened I see ...
you can also install FreshTomato as it works great on the R7000. You also have DD/OpenWrt as options in case the horrible stock firmware is making you bald :)
I've taken the bull by the horns and done a factory reset and set up from scratch again so we'll see if this helps.
DHCP requests were for lots of devices (I have 30 on my network) but about half were for a single device located on the edge of my wireless range so I've given that a static IP address (and also reserved the IP address internally so I don't get any clashes). We'll see if that makes a difference
I've also been hit by the bug posted on this forum where devices are refused a connection with an authentication error. This coincides with the mass of DHCP entries so I suspect the two are related. For now I'll see how things go!
Thanks for the input :)
I did a hard reset today on an R7000 along with updating firmware to latest version. I had problems right away. The Router has froze multiple times seems to be locking up more on 5 GHz then I'll switch to 2.4 GHz (I don't use the auto switch) and then the router freezes and reboots. Everything drops offline. Man I have never seen such botched firmware. Every since Netgear released Circle the firmware has been absolute garbage. I have installed dozens of these it's been my go to for a long time. I never have to reboot this thing in the past and it handles everything you throw at it. Netgear, please stop putting efforts into some stupid Circle app and spend it debugging new firmware. Leave stuff like that to consumer friendly all in ones that ISP's have a backdoor into. Not sure what's going on at Netgear but this has been my favorite router but like I said since Circle even if you disable it, it's garbage and unstable be it QOS or speed issues and now it's rebooting and dumbing devices which I have never seen reboots like this since this latest release. Sad you have to rollback but at least they let you or I would have a new router and brand already.
Latest firmware, .60, has issues. Would suggest going to an older version. When doing so also do a reset after the downgrade and reconfigure.
Yes you are correct that Netgear has lost their way in building good firmware. Seems to be especially true for routers with Broadcomm chip sets like the r7000. Used to be my go to until a r8000 and r8000p both sold due to on going firmware issues. That is when I vowed no Netgear routers on my home network and moved on.
I think the problem has been going on for about a month, meanwhile, the Netgear software engineers are sat on their hands and doing nothing. Still stuck on V1.0.9.60_10.2.60
I can almost set a clock by the loss of wifi between 9 and 10pm - I'm constantly rebooting and switching my iPad to a cellular connection to the point I'm considering buying another brand of router - preferably one that cares about customer service.
I shouldn't have to revert to an earlier version of firmware to make my router work - Netgear sent the update, so it is down to Netgear to fix it.
Cleverfiend wrote:
I think the problem has been going on for about a month, meanwhile, the Netgear software engineers are sat on their hands and doing nothing. Still stuck on V1.0.9.60_10.2.60
I can almost set a clock by the loss of wifi between 9 and 10pm - I'm constantly rebooting and switching my iPad to a cellular connection to the point I'm considering buying another brand of router - preferably one that cares about customer service.
I shouldn't have to revert to an earlier version of firmware to make my router work - Netgear sent the update, so it is down to Netgear to fix it.
While I agree with the last statement, you do have a work-around, backlevel the firmware. Yes, this shouldn't be required, but it seems it is.
I wouldn't think a 'fix' should/would' come as fast as you think... especially given the fact of the other problems with that f/w and that the last 'solid' one was the .42 release. A .58 release was pulled within a week or so of release, and then the .60 was released a short time later. You see how that turned out. NG did a 'partial' recall on .60, it is off the automated d/l servers I understand. Also there are people without problems, so I don't think it is a simple fix or easy to possibly identify the cause.
I suspect NG Support did some testing before release, at least I hope they did. If they learned anything about the .58/.60 release fiasco, it would be they better get it right and do whatever it takes to be sure it ships as problem free as it can be. Still surprised no PUBLIC call for beta testers, but quite possible those that did report the problem are getting code to test.
