<html><head><title>Re: DHCP client state if rebooted when local DHCPD server is offline?</title>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-15">
</head>
<body>
<span style=" font-family:'courier new'; font-size: 9pt; color: #800000;"><b>tlfc> On Thu, Aug 14, 2014, at 10:30 AM, Gregory Sloop wrote:<br>
>> It seems clear that there's some problem with the DHCP server, [or perhaps VLAN's or network connectivity.]<br>
<br>
>> How about a quick packet capture to be sure the DHCP server is actually seeing the requests. [I think this is the first, most important step.]<br>
>> -If it IS seeing them, then there's some configuration problem.<br>
>> -If it isn't, then figuring out what's preventing the communication from occurring, would be important. [Broadcast filtering, DHCP server and DHCP client on different VLANs without a DHCP helper/relay etc.]<br>
<br>
tlfc> Assuming that dhcping is a useful way to test, <br>
<br>
tlfc> checking from my client<br>
<br>
tlfc> dhcping -h XX:XX:XX:XX:XX:XX -s 10.16.10.1 -c 10.16.10.26<br>
tlfc> Got answer from: 10.16.10.1<br>
<br>
tlfc> Watching on the server<br>
<br>
tlfc> tcpdump -vvv -i eth1 -s 1500 port bootps or port bootpc<br>
tlfc> tcpdump: listening on eth1, link-type EN10MB<br>
tlfc> (Ethernet), capture size 1500 bytes<br>
tlfc> 11:31:52.432820 IP (tos 0x0, ttl 64, id 33227,<br>
tlfc> offset 0, flags [DF], proto UDP (17), length 278)<br>
tlfc> tgdesktop.MYDOMAIN.net.bootpc ><br>
tlfc> edgerouter.MYDOMAIN.net.bootps: [udp sum ok] BOOTP/DHCP, Request<br>
tlfc> from XX:XX:XX:XX:XX:XX (oui Unknown), length 250, xid<br>
tlfc> 0x9800ed53, Flags [none] (0x0000)<br>
tlfc> Client-IP tgdesktop.MYDOMAIN.net<br>
tlfc> Client-Ethernet-Address XX:XX:XX:XX:XX:XX (oui Unknown)<br>
tlfc> Vendor-rfc1048 Extensions<br>
tlfc> Magic Cookie 0x63825363<br>
tlfc> DHCP-Message Option 53, length 1: Request<br>
tlfc> Requested-IP Option 50, length 4: tgdesktop.MYDOMAIN.net<br>
tlfc> END Option 255, length 0<br>
tlfc> 11:31:52.433206 IP (tos 0x0, ttl 64, id 5840,<br>
tlfc> offset 0, flags [DF], proto UDP (17), length 328)<br>
tlfc> edgerouter.MYDOMAIN.net.bootps ><br>
tlfc> tgdesktop.MYDOMAIN.net.bootpc: [bad udp cksum 0x6fed -> 0x1b16!]<br>
tlfc> BOOTP/DHCP, Reply, length 300, xid 0x9800ed53, Flags [none] (0x0000)<br>
tlfc> Client-IP tgdesktop.MYDOMAIN.net<br>
tlfc> Your-IP tgdesktop.MYDOMAIN.net<br>
tlfc> Client-Ethernet-Address XX:XX:XX:XX:XX:XX (oui Unknown)<br>
tlfc> Vendor-rfc1048 Extensions<br>
tlfc> Magic Cookie 0x63825363<br>
tlfc> DHCP-Message Option 53, length 1: ACK<br>
tlfc> Server-ID Option 54, length 4: edgerouter.MYDOMAIN.net<br>
tlfc> Lease-Time Option 51, length 4: 14400<br>
tlfc> Subnet-Mask Option 1, length 4: 255.255.252.0<br>
tlfc> Default-Gateway Option 3, length 4: edgerouter.MYDOMAIN.net<br>
tlfc> Domain-Name-Server Option 6, length 4: edgerouter.MYDOMAIN.net<br>
tlfc> Domain-Name Option 15, length 18: "MYDOMAIN.net"<br>
tlfc> END Option 255, length 0<br>
tlfc> PAD Option 0, length 0, occurs 6<br>
tlfc> 11:31:52.433580 IP (tos 0x0, ttl 64, id 33228,<br>
tlfc> offset 0, flags [DF], proto UDP (17), length 272)<br>
tlfc> tgdesktop.MYDOMAIN.net.bootpc ><br>
tlfc> edgerouter.MYDOMAIN.net.bootps: [udp sum ok] BOOTP/DHCP, Request<br>
tlfc> from XX:XX:XX:XX:XX:XX (oui Unknown), length 244, xid<br>
tlfc> 0x9800ed53, Flags [none] (0x0000)<br>
tlfc> Client-IP tgdesktop.MYDOMAIN.net<br>
tlfc> Client-Ethernet-Address XX:XX:XX:XX:XX:XX (oui Unknown)<br>
tlfc> Vendor-rfc1048 Extensions<br>
tlfc> Magic Cookie 0x63825363<br>
tlfc> DHCP-Message Option 53, length 1: Release<br>
tlfc> END Option 255, length 0<br>
<br>
tlfc> There's a "bad udp cksum" in there that doesn't look so good. <br>
tlfc> But the server IS getting the request it seems, and the client DOES get a reply.<br>
<br>
</b><span style=" color: #000000;">I'm not the most skilled at looking at that trace - the quick look I gave it looks fine - though that shouldn't be a stamp of approval either. :)<br>
<br>
This dhcp client [or server] isn't hanging off a wireless network/bridge is it? IIRC, there's been a number of cases where DHCP broadcasts and/or replies get munged in certain situations like that. <br>
<br>
Can you describe the physical network setup. <br>
<br>
Finally, if you think it's not a network problem, I'd set the DHCP server up very simply. Make sure it works in a *very* basic setup, then tweak to do more esoteric things.<br>
[I'm likely to be tied up with other things soon, so I hope someone else will chime in too...]<br>
<br>
-Greg<br>
<br>
</body></html>