NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Nighthawk AX4: DHCP Not Working - IP not assigned automatically
So, I have had this router for a few months now and I have had issues with wifi on numerous ocassions. At random, the router will begin to not distribute and assign ipv4 ip address for devices connec...
Just reboot it until it does. Look how long this thread has been going. Look at how many other threads on the exact same issue have popped up. Netgear doesn't give a **bleep**. Horrible product, 0 support. Okay going to unsubscribe from this now, better luck next time you buy a router everyone.
Same, I personally won't be buying a netgear or dlink router again, if I hadn't decided to replace my RAX40 with a dream machine pro, I would have just bought a raspberry pi and used pi hole as a router replacement.
Been having the same issues with my R8000. Worked for months without any problems. Started getting a single device failing to pick up a dhcp address until the router was rebooted. I also tried rebooting the affected device, but that doesn't help - only rebooting the router fixes it. As time passed, it's slowly turned into multiple devices being unable to get an address and a reboot of the router at least once a day or face the kids moaning because their xbox is getting that dhcp error again.
Fortunately I have a linux machine running in the house, so I've disabled the router's dhcp server and installed dnsmasq on the llinux machine. Everything is working again.
Pretty dissapointed with the Netgear router at the moment - it's not a cheap bit of kit and it's only saving grace is that it's still better than the VirginMedia superhub for WiFi.
- I’ve gone into LAN and reserved loads of devices that never leave the house with fixed IPs, not had any issues for a few months (probably just jinxed myself posting this)
I have a 2.5yo R6350 (AC1750) running the latest firmware: V1.1.0.84_1.0.1 with the same issues. I've tried everything as noted in the first post (and downgrading to 64_1.0.1 or 78_1.0.1 didn't help). What I *did* notice, and this is a poor workaround, is that when I reduced the number of connected devices to < 32, then DHCP began working again.
In all cases, the logfile shows that the IP addresses *are* being allocated, but they never transmitted to the device. With Access Control turned on, successful connections are properly logged when things are working fine. When broken, there are no [Access Control] entries. Again, turning off Access Control does *not* resolve the issue. I believe Access Control is *not* the issue, and the root cause maybe due to an internal table overflow.
The reason that firmware changes or rebooting can temporarily fix is that you reduce the number of devices at bootup. If you have > 32 devices at bootup then it will still fail. A quick test is to change your SSID and try connecting to that one. Things will work until you, once again, connect to too many devices.
My resolution plan is to purchase a new router, but given this major core issue that is not being addressed by Netgear (a wireless router's core function is to connect to wireless devices), I plan to return to Linksys.
Good luck.