AX5400 DHCP Server stops working for wired clients

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

AX5400 DHCP Server stops working for wired clients

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
AX5400 DHCP Server stops working for wired clients
AX5400 DHCP Server stops working for wired clients
2022-12-01 18:22:43
Tags: #DHCP
Model: Archer AX75  
Hardware Version: V1
Firmware Version: 1.1.0 Build 20220531 rel.45673(5553)

It seems the DHCP server for wired clients stops working after a few weeks. This is the second time this has happened to me since I got this router in August 2022. I got a number of clients direclty connected via Ethernet to the router. These clients include:

 

Alarm/Security system

Video Camera hub

MacBook Pro

Samsung Smart TVs

 

When this issue suddenly happens the wired clients have a self-assigned IP address. However, all the wireless clients work normally.

 

I tried the following troubleshooting steps without success:

 

1) Reloading router from the GUI

2) Hard reload via on/off switch

3) Disabling/Renabling DHCP server on router.

4) Manually relese/renew IP on client side

 

I looked at the router logs and there are no messages/issues reported.

Ran tcpdump on MacPro and it seems the router is not responding to DHCP messages while renew/release is performed. see below

 

In the past the issue goes away after a few days without intervention. The issue is currently happening and I am unable to recover. Please assist.

 

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

 

en8: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

options=6467<RXCSUM,TXCSUM,VLAN_MTU,TSO4,TSO6,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM>

ether 64:4b:f0:2b:82:b1

inet6 fe80::1008:edfa:1daf:430d%en8 prefixlen 64 secured scopeid 0xd

inet 169.254.229.38 netmask 0xffff0000 broadcast 169.254.255.255

nd6 options=201<PERFORMNUD,DAD>

media: autoselect (1000baseT <full-duplex>)

status: active

**********@MacBook-Pro ~ % sudo tcpdump -i en8 port 67 or port 68 -e -n -vv

tcpdump: listening on en8, link-type EN10MB (Ethernet), capture size 262144 bytes

12:18:02.646808 64:4b:f0:2b:82:b1 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: (tos 0x0, ttl 255, id 59755, offset 0, flags [none], proto UDP (17), length 328)

    0.0.0.0.68 > 255.255.255.255.67: [udp sum ok] BOOTP/DHCP, Request from 64:4b:f0:2b:82:b1, length 300, xid 0xabd3b48, secs 9, Flags [none] (0x0000)

  Client-Ethernet-Address 64:4b:f0:2b:82:b1

  Vendor-rfc1048 Extensions

    Magic Cookie 0x63825363

    DHCP-Message Option 53, length 1: Discover

    Parameter-Request Option 55, length 12:

      Subnet-Mask, Classless-Static-Route, Default-Gateway, Domain-Name-Server

      Domain-Name, Option 108, URL, Option 119

      Option 252, LDAP, Netbios-Name-Server, Netbios-Node

    MSZ Option 57, length 2: 1500

    Client-ID Option 61, length 7: ether 64:4b:f0:2b:82:b1

    Lease-Time Option 51, length 4: 7776000

    Hostname Option 12, length 11: "MacBook-Pro"

12:18:05.258158 64:4b:f0:2b:82:b1 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: (tos 0x0, ttl 255, id 59756, offset 0, flags [none], proto UDP (17), length 328)

    0.0.0.0.68 > 255.255.255.255.67: [udp sum ok] BOOTP/DHCP, Request from 64:4b:f0:2b:82:b1, length 300, xid 0xabd3b49, Flags [none] (0x0000)

  Client-Ethernet-Address 64:4b:f0:2b:82:b1

  Vendor-rfc1048 Extensions

    Magic Cookie 0x63825363

    DHCP-Message Option 53, length 1: Discover

    Parameter-Request Option 55, length 12:

      Subnet-Mask, Classless-Static-Route, Default-Gateway, Domain-Name-Server

      Domain-Name, Option 108, URL, Option 119

      Option 252, LDAP, Netbios-Name-Server, Netbios-Node

    MSZ Option 57, length 2: 1500

    Client-ID Option 61, length 7: ether 64:4b:f0:2b:82:b1

    Lease-Time Option 51, length 4: 7776000

    Hostname Option 12, length 11: "MacBook-Pro"

12:18:06.677086 64:4b:f0:2b:82:b1 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: (tos 0x0, ttl 255, id 59757, offset 0, flags [none], proto UDP (17), length 328)

    0.0.0.0.68 > 255.255.255.255.67: [udp sum ok] BOOTP/DHCP, Request from 64:4b:f0:2b:82:b1, length 300, xid 0xabd3b49, secs 1, Flags [none] (0x0000)

  Client-Ethernet-Address 64:4b:f0:2b:82:b1

  Vendor-rfc1048 Extensions

    Magic Cookie 0x63825363

    DHCP-Message Option 53, length 1: Discover

    Parameter-Request Option 55, length 12:

      Subnet-Mask, Classless-Static-Route, Default-Gateway, Domain-Name-Server

      Domain-Name, Option 108, URL, Option 119

      Option 252, LDAP, Netbios-Name-Server, Netbios-Node

    MSZ Option 57, length 2: 1500

    Client-ID Option 61, length 7: ether 64:4b:f0:2b:82:b1

    Lease-Time Option 51, length 4: 7776000

    Hostname Option 12, length 11: "MacBook-Pro"

12:18:09.229773 64:4b:f0:2b:82:b1 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: (tos 0x0, ttl 255, id 59758, offset 0, flags [none], proto UDP (17), length 328)

    0.0.0.0.68 > 255.255.255.255.67: [udp sum ok] BOOTP/DHCP, Request from 64:4b:f0:2b:82:b1, length 300, xid 0xabd3b49, secs 4, Flags [none] (0x0000)

  Client-Ethernet-Address 64:4b:f0:2b:82:b1

  Vendor-rfc1048 Extensions

    Magic Cookie 0x63825363

    DHCP-Message Option 53, length 1: Discover

    Parameter-Request Option 55, length 12:

      Subnet-Mask, Classless-Static-Route, Default-Gateway, Domain-Name-Server

      Domain-Name, Option 108, URL, Option 119

      Option 252, LDAP, Netbios-Name-Server, Netbios-Node

    MSZ Option 57, length 2: 1500

    Client-ID Option 61, length 7: ether 64:4b:f0:2b:82:b1

    Lease-Time Option 51, length 4: 7776000

    Hostname Option 12, length 11: "MacBook-Pro"

^C

4 packets captured

6 packets received by filter

0 packets dropped by kernel

  0      
  0      
#1
Options
3 Reply
Re:AX5400 DHCP Server stops working for wired clients
2022-12-02 02:11:54

@Panini_grill 

 

Thank you very much for bringing this up to our attention.

 

Can I know how are these wired clients connected to the AX75? Are they plugged into the LAN ports of the AX75 directly with Ethernet cables, or they are connected via a switch? If there is a switch between, please try to connect one of the four wired devices to the AX75 directly, then confirm if it connects to the internet permanently.

 

To assist and figure it out efficiently, I've forwarded your case to the TP-Link support engineers who will contact you with your registered email address later. Please pay attention to your email box for follow-up.

Nice to Meet You in Our TP-Link Community. Check Out the Latest Posts: Connect TP-Link Archer BE550 to Germany's DS-Lite (Dual Stack Lite) Internet via WAN Archer GE550 - BE9300 Tri-Band Wi-Fi 7 Gaming Router EasyMesh Is Available When Wi-Fi Routers Work in AP Mode as A Controller. Archer AX90 New Firmware Added Support for EasyMesh and Ethernet Backhaul If you found a post or response helpful, please click Helpful (arrow pointing upward icon). If you are the author of a topic, remember to mark a helpful reply as the "Recommended Solution" (star icon) so that others can benefit from it.
  0  
  0  
#2
Options
Re:AX5400 DHCP Server stops working for wired clients
2022-12-02 02:43:53

  @Kevin_Z , Thanks for your reply. The MacPro I am using to capture DHCP packets is directly connected to the AX75 router via one of the Ethernet ports. Connecting/Disconnecting the port does not help.

 

Regards 

  3  
  3  
#3
Options
Re:AX5400 DHCP Server stops working for wired clients
2022-12-02 05:43:49

@Panini_grill 

 

Thank you very much for getting back with the detailed info.


To assist and figure it out efficiently, I've forwarded your case to the TP-Link support engineers who will contact you with your registered email address later. Please pay attention to your email box for follow-up.

Nice to Meet You in Our TP-Link Community. Check Out the Latest Posts: Connect TP-Link Archer BE550 to Germany's DS-Lite (Dual Stack Lite) Internet via WAN Archer GE550 - BE9300 Tri-Band Wi-Fi 7 Gaming Router EasyMesh Is Available When Wi-Fi Routers Work in AP Mode as A Controller. Archer AX90 New Firmware Added Support for EasyMesh and Ethernet Backhaul If you found a post or response helpful, please click Helpful (arrow pointing upward icon). If you are the author of a topic, remember to mark a helpful reply as the "Recommended Solution" (star icon) so that others can benefit from it.
  0  
  0  
#4
Options