DHCP request is missing

eXPlosion · ‎02-26-2016

In sysloger loggs we see when tplink is connected

Feb 26 19:24:09 src@dhcp2. dhcpd: DHCPDISCOVER from 64:66:b3:f8:xx:xx (TL-WR740N) c-id 0:10:1:7e r-id fc:f5:28:62:e:xx via xxx.xxx.55.254
Feb 26 19:24:09 src@dhcp2. dhcpd: DHCPOFFER on xxx.xxx.38.13 to 64:66:b3:f8:xx:xx (TL-WR740N) via xxx.xxx.55.254
Feb 26 19:24:11 src@dhcp2. dhcpd: Lease for xxx.xxx.38.13 , is connected to interface 1/126 , VLAN 382 , on switch 28:62:e:xx , client MAC 64:66:b3:f8:xx:xx , Vendor MSFT 5.0 Len: fcf52862ee8
Feb 26 19:24:11 src@dhcp2. dhcpd: DHCPDISCOVER from 64:66:b3:f8:xx:xx (TL-WR740N) c-id 0:10:1:7e r-id fc:f5:28:62:e:xx via xxx.xxx.55.254
Feb 26 19:24:11 src@dhcp2. dhcpd: DHCPOFFER on xxx.xxx.38.13 to 64:66:b3:f8:xx:xx (TL-WR740N) via xxx.xxx.55.254

when stbox is connected - similar issue. but when pc is directly connected, it is getting an IP.

Where could be the problem?

chrfrye2 · ‎03-01-2016

Hello,

After analyzing the TP user guide for the TLWR740N, the problem might lie either in how you have the wireless router connected to the device, or how you have the WAN connection type set up via the router's GUI interface. Are you connecting the WAN port on the back of the wireless router to your switch? Also, is the WAN connection type set to dynamic IP in the GUI? For clarity, what kind of switch are you using, and what is an stbox? It seems like you have your dhcp pool set up correctly due to your pc getting an IP address.

See the attached link for the TP user guide.

Thanks,

eXPlosion · ‎03-09-2016

Cable is in wan on the router. It is dynamic ip and it is getting request from client's router. So dhcp is turned on.

chrfrye2 · ‎03-09-2016

It looks like you have at least 2 vlans on your switch. Since there are two vlans on your switch, the broadcasts are coming in on vlan 382 from the TLWR740N, and are forwarded to your dhcp router. Since the switch is associating the broadcasts with vlan 1 due to the interface on your dhcp router not being associated with any specific vlan, the dhcp request is unable to be sent to vlan 382. Either you have to set up subinterfaces to allow for your dhcp requests to get to the TLWR740N on vlan 382, or you can set the port that goes to the TLWR740N set to vlan 1 as an access port.

Thanks,

eXPlosion · ‎03-10-2016

The dhcp client TL-WR740N is on 382 vlan, but dhcp server is on uplink trunk port. But if dhcpdiscover reaches dhcp server, then dhcprequest also should reach