Business Community > Gateways > I know it's been asked before, but question about "DHCP Server allocated IP address"
< Gateways

I know it's been asked before, but question about "DHCP Server allocated IP address"

I know it's been asked before, but question about "DHCP Server allocated IP address"

I know it's been asked before, but question about "DHCP Server allocated IP address"
I know it's been asked before, but question about "DHCP Server allocated IP address"
Friday
Model: ER605 (TL-R605)  
Hardware Version: V2
Firmware Version: 2.3.0 Build 20230428 Rel. 18967

I looked up these repeating "DHCP Server allocated IP address" messages here and elsewhere, and the end result was mostly "why is your lease time 120?"  But I don't know if raising a lease time could help with devices checking in every handful of seconds.

 

Looking at the logged devices in question, they are mostly IoT things - Ring Doorbell, an amazon Echo, and a very chatty Apple watch.  The watch in particular being chatty with the log showing it requested an IP three times in seven minutes. I would assume this is the watch "waking up" to check for notifications, getting an IP, and then immediately going back to sleep, only to repeat the process a few minutes later.

 

So I suppose the question here is -  is this normal for wifi devices like these?  I might be incorrectly assuming that this is not indicative of a problem, as when my Deco xe75 pros were in router mode, they'd be dealing with the same things. But I'm just curious to know - Is there a problem here? Is this just what I would expect in the logs.  And is there a way to to visually quell the storm?

 

Just a sample:

========

2026-03-27 09:55:36 dhcp_server[17262]: <5> 01712251 [OMADA]DHCP Server allocated IP address 192.168.1.121 for the [client:6a:9c:24:59:5f:a0].
2026-03-27 09:55:30 dhcp_server[17262]: <5> 01712251 [OMADA]DHCP Server allocated IP address 192.168.1.121 for the [client:6a:9c:24:59:5f:a0].
2026-03-27 09:55:30 dhcp_server[17262]: <5> 01712251 [OMADA]DHCP Server allocated IP address 192.168.1.120 for the [client:7e:4a:db:f4:ca:3e].
2026-03-27 09:55:26 dhcp_server[17262]: <5> 01712251 [OMADA]DHCP Server allocated IP address 192.168.1.121 for the [client:6a:9c:24:59:5f:a0].
2026-03-27 09:55:22 dhcp_server[17262]: <5> 01712251 [OMADA]DHCP Server allocated IP address 192.168.1.121 for the [client:6a:9c:24:59:5f:a0].
2026-03-27 09:55:04 dhcp_server[17262]: <5> 01712251 [OMADA]DHCP Server allocated IP address 192.168.1.120 for the [client:7e:4a:db:f4:ca:3e].
2026-03-27 09:51:48 dhcp_server[17262]: <5> 01712251 [OMADA]DHCP Server allocated IP address 192.168.1.131 for the [client:58:7a:62:1c:23:90].
2026-03-27 09:51:47 dhcp_server[17262]: <5> 01712251 [OMADA]DHCP Server allocated IP address 192.168.1.131 for the [client:58:7a:62:1c:23:90].
2026-03-27 09:51:47 dhcp_server[17262]: <5> 01712251 [OMADA]DHCP Server allocated IP address 192.168.1.131 for the [client:58:7a:62:1c:23:90].
2026-03-27 09:51:47 dhcp_server[17262]: <5> 01712251 [OMADA]DHCP Server allocated IP address 192.168.1.131 for the [client:58:7a:62:1c:23:90].
2026-03-27 09:51:46 dhcp_server[17262]: <5> 01712251 [OMADA]DHCP Server allocated IP address 192.168.1.131 for the [client:58:7a:62:1c:23:90].
2026-03-27 09:51:46 dhcp_server[17262]: <5> 01712251 [OMADA]DHCP Server allocated IP address 192.168.1.131 for the [client:58:7a:62:1c:23:90].
2026-03-27 09:51:46 dhcp_server[17262]: <5> 01712251 [OMADA]DHCP Server allocated IP address 192.168.1.131 for the [client:58:7a:62:1c:23:90].

====================

 

Thanks for help / advice!

 

  0      
 
  0      
 
#1
Options
1 Reply
Re:I know it's been asked before, but question about "DHCP Server allocated IP address"
Monday

Hi, @bruno_sardine 
Thanks for posting in our business forum.
 

Some IoT devices may disable Wi-Fi connectivity during sleep mode to reduce power consumption, and re-send a request to obtain a new IP address when waking up for network access. However, judging from the logs you sent, your devices are making too many IP requests in a short time.Since you mentioned that the same issue also occurs when using Deco, it is unlikely that the problem stems from the DHCP server. Instead, the issue is more likely related to the IOT devices or the network connections. To resolve potential connectivity issues, we recommend the following solutions:

  • Please upgrade your ER605 to the latest official firmware.
  • Please check the connection status of your client devices to ensure they maintain a stable network connection.
  • Try to change the 2.4Ghz channel.
  • Try to move the IOT devices closer to the Internet source.
     

We also suggest you provide the following information if the issue is not resolved:
1.Full details of your network topology
2.Are all of your IoT devices connected to the network wirelessly? Does the same connectivity issue also occur on any wired-connected devices on your network?
3.Is the problem limited to specific devices, or do multiple devices all experience the same issue?

  0  
  0  
#2
Options

Information

Helpful: 0

Views: 92

Replies: 1

About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.