Home Network Community > Wi-Fi Routers > AX72 AP requesting DHCP very regularly
< Wi-Fi Routers

AX72 AP requesting DHCP very regularly

AX72 AP requesting DHCP very regularly

AX72 AP requesting DHCP very regularly
AX72 AP requesting DHCP very regularly
Yesterday
Tags: #DHCP
Model: Archer AX72  
Hardware Version: V1
Firmware Version: 1.45

I have recently setup my own DHCP server, as was finding the recent rebuilds of the main AX72 router to be a little bit of a pain.

 

Since doing that however I have noticed something a little odd: My DHCP logs are getting filled with lease requests from my 3 AX72 routers (setup in AP mode).

There is nothing from the main one.. but that has a static IP.

 

But I would not expect, especially as a I have my lease set to 24 hours, the devices to be hitting the DHCP so often

 

I won't dump the whole logs (6MB from  day) but in a 10 minute window I see: DHCP Server leased IP address times.. now that does include the normal renewal of other devices, but if I just look at 1 minute: 

 

2025-10-19 21:37:13 Local DHCP Server leased IP address 345678901 to ArcherAX72 AA-AA-AA-AA-AA for scope: DHCP Standard

2025-10-19 21:37:15 Local DHCP Server leased IP address 234567890 to ArcherAX72 BB-AA-AA-AA-AA for scope: DHCP Standard

2025-10-19 21:37:20 Local DHCP Server leased IP address 123456789 to ArcherAX72 CC-AA-AA-AA-AA for scope: DHCP Standard

2025-10-19 21:37:47 Local DHCP Server leased IP address 345678901 to ArcherAX72 AA-AA-AA-AA-AA for scope: DHCP Standard

2025-10-19 21:37:49 Local DHCP Server leased IP address 234567890 to ArcherAX72 BB-AA-AA-AA-AA for scope: DHCP Standard

2025-10-19 21:37:54 Local DHCP Server leased IP address 123456789 to ArcherAX72 CC-AA-AA-AA-AA for scope: DHCP Standard

2025-10-19 21:38:22 Local DHCP Server leased IP address 345678901 to ArcherAX72 AA-AA-AA-AA-AA for scope: DHCP Standard

2025-10-19 21:38:23 Local DHCP Server leased IP address 234567890 to ArcherAX72 BB-AA-AA-AA-AA for scope: DHCP Standard

2025-10-19 21:38:28 Local DHCP Server leased IP address 123456789 to ArcherAX72 CC-AA-AA-AA-AA for scope: DHCP Standard

 

(FYI I can't seem to get my logs to work) but if you can say whta I need to do to tell this forum I am not posting "illegal links" that would be great; 

 

The above can't be usual and clearly shows that the routers are not picking up the lease time, or just ignoring it.

 

How do I resolve this, as thats alot of noise for no benefit.

  0      
 
  0      
 
#1
Options
4 Reply
Re:AX72 AP requesting DHCP very regularly
Yesterday

  @Tail_uk 
And here is a tcpdump over 1 minute monitoring my server (DHCP) to 1 of the APs on port 67 and 68
 

 

23:14:21.948347 enp4s0 In  IP (tos 0x0, ttl 64, id 4905, offset 0, flags [DF], proto UDP (17), length 399)
    192.168.87.3.68 > 192.168.87.10.67: BOOTP/DHCP, Request from AA:AA:AA:AA:AA, length 371, xid 0x9a35be13, Flags [none]
          Client-IP 192.168.87.3
          Client-Ethernet-Address AA:AA:AA:AA:AA
          Vendor-rfc1048 Extensions
            Magic Cookie 0x63825363
            DHCP-Message (53), length 1: Request
            Client-ID (61), length 7: ether AA:AA:AA:AA:AA
            MSZ (57), length 2: 1024
            Parameter-Request (55), length 10:
              Subnet-Mask (1), Default-Gateway (3), Domain-Name-Server (6), Hostname (12)
              Domain-Name (15), BR (28), Static-Route (33), NTP (42)
              Classless-Static-Route (121), Classless-Static-Route-Microsoft (249)
            Vendor-Class (60), length 8: "MSFT 5.0"
            Hostname (12), length 10: "[REDACTED_CLIENT_HOSTNAME]"
23:14:21.948580 enp4s0 Out IP (tos 0x0, ttl 64, id 27180, offset 0, flags [DF], proto UDP (17), length 382)
    192.168.87.10.67 > 192.168.87.3.68: BOOTP/DHCP, Reply, length 354, xid 0x9a35be13, Flags [none]
          Client-IP 192.168.87.3
          Your-IP 192.168.87.3
          Server-IP 192.168.87.10
          Client-Ethernet-Address AA:AA:AA:AA:AA
          Vendor-rfc1048 Extensions
            Magic Cookie 0x63825363
            DHCP-Message (53), length 1: ACK
            Server-ID (54), length 4: 192.168.87.10
            Lease-Time (51), length 4: 86400
            RN (58), length 4: 43200
            RB (59), length 4: 75600
            Subnet-Mask (1), length 4: 255.255.255.0
            BR (28), length 4: 192.168.87.255
            Default-Gateway (3), length 4: 192.168.87.1
            Domain-Name-Server (6), length 8: 192.168.87.10,192.168.87.11
            Hostname (12), length 16: "[REDACTED_SERVER_HOSTNAME]"
            Domain-Name (15), length 4: "[REDACTED_DOMAIN]"
            NTP (42), length 32: [REDACTED_NTP_IP_LIST]
23:14:56.128630 enp4s0 In  IP (tos 0x0, ttl 64, id 6435, offset 0, flags [DF], proto UDP (17), length 399)
    192.168.87.3.68 > 192.168.87.10.67: BOOTP/DHCP, Request from AA:AA:AA:AA:AA, length 371, xid 0x9a35be13, Flags [none]
          Client-IP 192.168.87.3
          Client-Ethernet-Address AA:AA:AA:AA:AA
          Vendor-rfc1048 Extensions
            Magic Cookie 0x63825363
            DHCP-Message (53), length 1: Request
            Client-ID (61), length 7: ether AA:AA:AA:AA:AA
            MSZ (57), length 2: 1024
            Parameter-Request (55), length 10:
              Subnet-Mask (1), Default-Gateway (3), Domain-Name-Server (6), Hostname (12)
              Domain-Name (15), BR (28), Static-Route (33), NTP (42)
              Classless-Static-Route (121), Classless-Static-Route-Microsoft (249)
            Vendor-Class (60), length 8: "MSFT 5.0"
            Hostname (12), length 10: "[REDACTED_CLIENT_HOSTNAME]"
23:14:56.129312 enp4s0 Out IP (tos 0x0, ttl 64, id 49000, offset 0, flags [DF], proto UDP (17), length 382)
    192.168.87.10.67 > 192.168.87.3.68: BOOTP/DHCP, Reply, length 354, xid 0x9a35be13, Flags [none]
          Client-IP 192.168.87.3
          Your-IP 192.168.87.3
          Server-IP 192.168.87.10
          Client-Ethernet-Address AA:AA:AA:AA:AA
          Vendor-rfc1048 Extensions
            Magic Cookie 0x63825363
            DHCP-Message (53), length 1: ACK
            Server-ID (54), length 4: 192.168.87.10
            Lease-Time (51), length 4: 86400
            RN (58), length 4: 43200
            RB (59), length 4: 75600
            Subnet-Mask (1), length 4: 255.255.255.0
            BR (28), length 4: 192.168.87.255
            Default-Gateway (3), length 4: 192.168.87.1
            Domain-Name-Server (6), length 8: 192.168.87.10,192.168.87.11
            Hostname (12), length 16: "[REDACTED_SERVER_HOSTNAME_2]"
            Domain-Name (15), length 4: "[REDACTED_DOMAIN]"
            NTP (42), length 32: [REDACTED_NTP_IP_LIST]
  0  
  0  
#2
Options
Re:AX72 AP requesting DHCP very regularly
Yesterday - last edited Yesterday

  @Tail_uk 

 

This behavior is probably due to Smart DHCP feature - just set your other APs with a static IP (DHCP turned off) and these requests should stop.

If this was helpful click on the arrow pointing upward to make it blue. If this solves your issue, click the star to make it blue and mark the post as a "Recommended Solution".
  0  
  0  
#3
Options
Re:AX72 AP requesting DHCP very regularly
Yesterday

  @terziyski hey, is that the DHCP server = auto?

If so I have DHCP Server set to off on all of them to disable that. 

 

And yes I could 100% go to static, it's a weird bug and clearly shows that one side or the other is not confirming to the standards, as I know that, within the DHCP lease the device can extend it, normally around half way, but ever 30 seconds or so is a little extreme. 

I like the IP management to be in one place (my DHCP server), so that any changes to DNS or that devices IP can be managed once and it will propagate out within a day.

  0  
  0  
#4
Options
Re:AX72 AP requesting DHCP very regularly
Yesterday

  @terziyski

I have finally read through the information you linked to, I am following what it says "set to off", which is already done:

 

Wifi-dhcp-screen

 

So while I believe that the DHCP noise could be turned down with a static IP (Ill test this shortly), I should not need to as the DHCP settings are set inline with what is expected and could be the thing (it's set to off but is not) as to why my network collapsed on easymesh, as I saw this noise on easy mesh as well

 

Thanks 

  0  
  0  
#5
Options

Information

Helpful: 0

Views: 53

Replies: 4

Tags

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