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!
I thought it might be DNS as well, but wired devices work just fine:
2.4GHz Devices: If you're on a service, it continues to work (e.g accessing gmail). If you try to access a new service (e.g www.yahoo.com) it will fail. This feels like a DNS issue*.
5GHz Devices: Generall they would work fine, but lately they had the same issues as 2.4GHz
Both bands: If you detached from wireless, you couldn't re-attach. Devices such as my google homes would go in to re-configure mode (advertising as AP's so you could attach directly to them to configure).
Wired: Worked fine. I could still access the other wired devices on my network, but not my wireless ones. Internet worked fine. I could NOT connect to the GUI on the router (which also prevented me from getting the log/debug information).
*a DNS issue wouldn't prevent wireless devices from re/attaching to wireless. With respect to wired devices, they wouldn't get DHCP addresses from the router. I had to hard-code an IP to my laptop to test (including adding DNS information).
To me, it feels more like a DHCP issue. It looks like the default lease is 65ish hours. My current lease was obtained on 2 January at 22:41 and expires on 5 January at 15:28 . DHCP will generally send a keep-alive at half the lease, to verify you're still there. I'm wondering if something has happened that causes the leases to expire. This still wouldn't prevent wireless devices from re-attaching though. They don't even get to the lease reqest, as far as I can tell.
For me, the main wired device I have won't work after the wireless devices drop off. It's still connected to the network as I can still use RDP with it, but I cannot access the internet from the device. It's connected via a Powerline though, but I don't believe that should make a difference as it's still wired and not wireless.
lsummers72 when that happens, checked the dhcp lease. Try giving yourself a hard-coded IP, including a DNS like 8.8.8.8 and 8.8.4.4 (both are google). You'll still need to give it a default route (of your router).
Since my wired devices could work if I coded the IP info in and my wireless devices mostly continued to work, the router doesn't appear to be hung even when I cannot access the GUI. There are times when the 5GHz still works, but not the 2.4GHz .. but again, I've seen instances where those devices - if they were ACTIVE at the time of the "drop - remain active.
I'd be curious about the first part, though.
brianhelman, yes, the hard-coded DNS allowed me to connect to the internet from the wired computer. Thanks for the tip - at least one device works!
This is my first post here, hopefully I'm doin' thsi right..
Anyway, I've been having this problem for a while, definitely before .18 although it only affected Chromecasts the most.
After upgrading to .18 my ecobee3 lite thermostat could not connect. I know this is pretty specific but that's the one reproduceable thing I can come up with. The ecobee3 would rarely connect after rebooting the router/modem/thermostat and praying to the gods.. and then would lose connectivity shortly after.
I could connect the thermostat to other networks (I connected it the hotspot on my phone flawlessly) but then could not reconnect to the R7000.
I definitely think there is something about the DHCP at the root of this issue.. it simply would not dish out an address to the ecobee.
It almost seems like the router "forgot" it had certain (2.4) clients connected..
Anyway, I tried the access control thing, no dice. Tried turning off guest network, no luck. I did not try Tomato because I need something up to date security wise.
So, last night I installed Xwrt-Vortex and the ecobee connected to the R7000 right away and has not dropped since.. Going on 20 hours now. I spent about 10 days prior to that trying to get it to work with Netgear's firmware.
Installing Xwrt-Vortex was dead simple, just like installing a Netgear update (kudos to them for how easy that is). I did not hard reset anything or restore any factory settings I went straight from .18 to Xwrt-Vortex.
That is what I will use until this is sorted out... I'm actually starting to like it.. the logging is light years ahead of what Netgear firmware logs which for issues such as this is absolutely useless.
Anyway I really just wanted to chime in and say there's success with Xwrt-Vortex.