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!
Just switched to Xwrt-Vortex
http://xvtx.ru/xwrt/download.htm
.... and your problems will be over
KRACK fixed
I upgraded to the new hotfix R7000-V1.0.9.20_1.2.28 and it's still acting up for me. The odd thing is, this whole time I've been able to use RDP from outside the network to connect to a computer that's connected to the router via ethernet and another via wireless, but neither one will connect to the GUI via browser or any other website. Would that make it a DNS issue? It will allow incoming connections, but not outgoing ones and port forwarding still works.
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.