Deco M5 DHCP not assigning IP addresses
Deco M5 DHCP not assigning IP addresses
I recently purchased a 3 Deco M5 kit and I'm quite happy with it in terms of range and speed. However, it is VERY common that it will not pick up an IP address when a device (new or existing) tries to connect to it.
This issue happened with one kit I purchased and upgraded immediately upon installation to firmware version 1.4.4. Because it was happening so much, I exchanged it for another of the same kit. Now, I did not upgrade the firmware, as I thought that could be the issue. Evidently, it wasn't. I keep getting devices (iMac, MacBook, Windows laptop, iPad, Apple Watch, iPhone, smart tv, etc...) to get 169.254.x.x self assigned ips for a while (sometimes seconds, sometimes many minutes or until I give up) instead of an assigned 192.168.68.x IP address.
Looking at the logs, there are several entries of this kind:
"Mon Jul 20 23:20:53 2020 daemon.err udhcpd[18648]: no free IP addresses. OFFER abandoned"
Which is very odd, as I have about 25 connected devices, and the DHCP pool is set at 192.168.68.100-192.168.68.250 (in the device that I returned I had changed it to .2-.250, but to no avail).
I thought it could be some issue with the DHCP server, either in the firmware or hardware. But the problem persists with a new device (kit) and older FW.
If I set the IP address as manual, rather than automatic, the device connects with no problem, but really it's a pain to do that, and DHCP should work.
I have not seen this issue in other posts, so I hope someone can shed some light. Otherwise, I will return and look for an alternative whole home system.
Thank you
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@jhbass worked for me. Wondering if resetting the DNS fixed the issue or just reset the IP reservations table (or whatever is filling up and causing new devices to receive the error). Time will tell. Thanks to all for sharing your insights.
- Copy Link
- Report Inappropriate Content
DNS seemed to do the trick for me but the issue that crops up from time to time is that if the main Deco is rebooted it will disregard the IP range that I previously specified (10.0.0.x) and roll back to 192.168.1.x. which requires me to change it back in the settings, this happens almost every time.
:/
- Copy Link
- Report Inappropriate Content
HI, it seemed more like there was an IP conflict in your network.
There are two typical situations:
1. a local device has been configured as a WAN DNS server, such as raspberry Pi-Hole.
2. WAN IP+ subnet mask has covered the IP range of LAN DHCP.
If you do not mind, you could send a picture of your IPv4 settings under Deco App>More>advanced, and a picture of the LAN settings to support.forum@tp-link.com.
Thank you very much.
- Copy Link
- Report Inappropriate Content
@TP-Link There are only a few devices with static IPs, everything else is DHCP. The only thing that I do to resolve it is to specify the local IP range in the Deco app. Once I do that everything is back to normal.
- Copy Link
- Report Inappropriate Content
@jhbass I gave up long ago, after trying everything. Maybe a more recent firmware upgrade has solved the issue. I moved on to an Eero system, and have been pretty happy with it.
- Copy Link
- Report Inappropriate Content
@regisk Sorry for the dump
But i kind of having the same but in router mode, I have 2 dhcp with diffrent network setups, but also 2 nics in the NAS.
Did work for weeks for sudden not working even if i set a static deco address, second nic will not come alive for the deco.
But I can access the nas on the other nic from on dhcp address, from pc that got deco dhcp address.
I cannot even setting a static addres from deco access nas. It did work for months.
so strange.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 6
Views: 12300
Replies: 17