TL-WPA4220 and DHCP

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

TL-WPA4220 and DHCP

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
TL-WPA4220 and DHCP
TL-WPA4220 and DHCP
2023-01-27 21:43:18
Tags: #DHCP
Model: TL-WPA4220  
Hardware Version: V5
Firmware Version: 1.0.11 Build 221123 Rel.33987n (6985/8575)

Hello,

 

I saw my TL-WPA4220 is sending DHCP requests approx every minute. I was looking for information and I found  this trehad but it is already closed since it is almost four years old.

 

The thing is that I am having the same issue, even with a different HW and FW version.

 

Someone said in that thread that it was maybe by design to identify if there was other DHCP server in the network. Well, that could make sense if the DHCP server option in the device is set to 'auto', but in my case I have it disabled.

 

 

The point here is that the TL-WPA4200 is completely ignoring the lease time, and T1 & T2 options, and simply sending the request every minute. Even in the device log it says the gotten lease time is 130 seconds, when it is not.

 

1 INFO 0days, 09:28:58, [dhcpc]DHCPC: Send REQUEST to server 172.16.0.2

2 INFO 0days, 09:28:58, [dhcpc]DHCPC: Recv ACK from server 172.16.0.2 with ip 172.16.0.15 lease time 130

3 INFO 0days, 09:30:05, [dhcpc]DHCPC: Send REQUEST to server 172.16.0.2

4 INFO 0days, 09:30:05, [dhcpc]DHCPC: Recv ACK from server 172.16.0.2 with ip 172.16.0.15 lease time 130

5 INFO 0days, 09:31:12, [dhcpc]DHCPC: Send REQUEST to server 172.16.0.2

6 INFO 0days, 09:31:12, [dhcpc]DHCPC: Recv ACK from server 172.16.0.2 with ip 172.16.0.15 lease time 130

7 INFO 0days, 09:32:19, [dhcpc]DHCPC: Send REQUEST to server 172.16.0.2

8 INFO 0days, 09:32:19, [dhcpc]DHCPC: Recv ACK from server 172.16.0.2 with ip 172.16.0.15 lease time 130

 

2023-01-27 21:42:08 cinemateka dnsmasq-dhcp[1089]: 3047620317 client provides name: TL-WPA4220
2023-01-27 21:42:08 cinemateka dnsmasq-dhcp[1089]: 3047620317 DHCPREQUEST(eth0) 172.16.0.15 1c:61:b4:4a:6e:f6
2023-01-27 21:42:08 cinemateka dnsmasq-dhcp[1089]: 3047620317 tags: static, known, eth0
2023-01-27 21:42:08 cinemateka dnsmasq-dhcp[1089]: 3047620317 DHCPACK(eth0) 172.16.0.15 1c:61:b4:4a:6e:f6 WPA4220-Gym
2023-01-27 21:42:08 cinemateka dnsmasq-dhcp[1089]: 3047620317 requested options: 1:netmask, 3:router, 6:dns-server, 15:domain-name,
2023-01-27 21:42:08 cinemateka dnsmasq-dhcp[1089]: 3047620317 requested options: 43:vendor-encap, 44:netbios-ns, 46:netbios-nodetype,
2023-01-27 21:42:08 cinemateka dnsmasq-dhcp[1089]: 3047620317 requested options: 47:netbios-scope, 33:static-route, 121:classless-static-route,
2023-01-27 21:42:08 cinemateka dnsmasq-dhcp[1089]: 3047620317 requested options: 249
2023-01-27 21:42:08 cinemateka dnsmasq-dhcp[1089]: 3047620317 next server: 172.16.0.2
2023-01-27 21:42:08 cinemateka dnsmasq-dhcp[1089]: 3047620317 sent size:  1 option: 53 message-type  5
2023-01-27 21:42:08 cinemateka dnsmasq-dhcp[1089]: 3047620317 sent size:  4 option: 54 server-identifier  172.16.0.2
2023-01-27 21:42:08 cinemateka dnsmasq-dhcp[1089]: 3047620317 sent size:  4 option: 51 lease-time  1d
2023-01-27 21:42:08 cinemateka dnsmasq-dhcp[1089]: 3047620317 sent size:  4 option: 58 T1  10h37m14s
2023-01-27 21:42:08 cinemateka dnsmasq-dhcp[1089]: 3047620317 sent size:  4 option: 59 T2  19h37m14s
2023-01-27 21:42:08 cinemateka dnsmasq-dhcp[1089]: 3047620317 sent size:  4 option:  1 netmask  255.255.255.0
2023-01-27 21:42:08 cinemateka dnsmasq-dhcp[1089]: 3047620317 sent size:  4 option: 28 broadcast  172.16.0.255
2023-01-27 21:42:08 cinemateka dnsmasq-dhcp[1089]: 3047620317 sent size:  4 option:  3 router  172.16.0.1
2023-01-27 21:42:08 cinemateka dnsmasq-dhcp[1089]: 3047620317 sent size:  4 option:  6 dns-server  172.16.0.1

 

Has anyone found any solution to this?

 

Thanks

 

  2      
  2      
#1
Options
2 Reply
Re:TL-WPA4220 and DHCP
2023-02-01 12:13:21

  @JesusM 

Hi, you could have a look at this link:

https://community.tp-link.com/en/home/forum/topic/265692

The latest firmware should have fixed this issue but it doesn't seem like this.

I believe 172.16.0.2 is the static IP that you have set up for 4220?

Can I have a picture of your network topology, from the main router to 4220?

By the way, can I have the model number of your main router/main DHCP server?

 

Thank you very much.

bets regards.

 

  0  
  0  
#2
Options
Re:TL-WPA4220 and DHCP
2023-02-01 12:35:10 - last edited 2023-02-01 12:36:32

  @David-TP unfortunately that doesn't solve the problem.

 

Actually, I am running a later version of the firmware (FW: 1.0.11 Build 221123 Rel.33987n (6985/8575)) and the issue is still there, clearly visible from both DHCP client and DHCP server sides logs.

 

I opened a case with TP-Link support (TKID230147549) and they were trying to get the same device to reproduce the issue and see from there.

 

My network has:

- main router (Vodafone Gigabox - SGH3000) but it is NOT working as DHCP server (172.16.0.1)

- Linux box running DNSMASQ acting as DHCP server (172.16.0.2), connected to the router by ethernet cable

- TL-WPA4220 connected through power line to the main router and DHCP client acquiring the IP address 172.16.0.15

 

EDIT to remind that the DHCP server option in the TL-WPA4220 is set to off.

 

Thanks

  2  
  2  
#3
Options

Information

Helpful: 2

Views: 333

Replies: 2

Tags

DHCP
Related Articles