<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>
<br><br>
<br>
<span style=" font-family:'courier new'; font-size: 9pt; color: #800000;"><b>tlfc> Hi Greg<br>
<br>
tlfc> On Thu, Aug 14, 2014, at 10:01 AM, Gregory Sloop wrote:<br>
>> I think we need to be a bit more specific. Do you mean:<br>
<br>
tlfc> Not sure how exactly to ask, TBH :-/<br>
<br>
tlfc> I'm trying to get a handle on what happens if the server's not<br>
tlfc> available, and the LAN client needs to get it's IP address. <br>
tlfc> Without an assigned/working IP address, bootup seems to choke<br>
tlfc> somtimes, or at least stall for a very long time. Not<br>
tlfc> *entirely* sure yet if that's lack of IP or lack if intfc.<br>
<br>
>> A google search might be insightful too. [Or a search on the list archives.]<br>
<br>
tlfc> The problem there is NOT too-little info, but too-much noise. <br>
tlfc> Finding something relevant/clear is the current challenge.<br>
<br>
>> And on that note, what clients? Windows, Linux, Mac etc? And what versions?<br>
<br>
tlfc> Linux/64<br>
<br>
tlfc> One of (which was my immediately prior question)<br>
<br>
tlfc> dhcpcd (dhcpcd 3.2.3)<br>
tlfc> dhclient (isc-dhclient-4.2.5-P1)<br>
<br>
>> If you mean, the lease is expired before the station is brought back up again, then it will need a new lease from the DHCP server.<br>
<br>
tlfc> I *think* Simon's link-local solution *might* be the answer.<br>
<br>
tlfc> Atm, though, my problem's more basic. My client can't seem to<br>
tlfc> GET an IP address from the DHCP server even if the server IS up.<br>
<br>
tlfc> I keep getting lots of these:<br>
<br>
tlfc> ...<br>
tlfc> Aug 14 10:04:31 tgdesktop dhclient[4335]: DHCPDISCOVER on eth0<br>
tlfc> to 255.255.255.255 port 67 interval 2<br>
tlfc> Aug 14 10:04:33 tgdesktop dhclient[4335]: DHCPDISCOVER on eth0<br>
tlfc> to 255.255.255.255 port 67 interval 3<br>
tlfc> Aug 14 10:04:33 tgdesktop ifup-dhcp[4278]: .<br>
tlfc> Aug 14 10:04:36 tgdesktop ifup-dhcp[4278]: .<br>
tlfc> Aug 14 10:04:36 tgdesktop dhclient[4335]: DHCPDISCOVER on eth0<br>
tlfc> to 255.255.255.255 port 67 interval 5<br>
tlfc> Aug 14 10:04:38 tgdesktop ifup-dhcp[4278]: .<br>
tlfc> Aug 14 10:04:41 tgdesktop dhclient[4335]: DHCPDISCOVER on eth0<br>
tlfc> to 255.255.255.255 port 67 interval 12<br>
tlfc> ...<br>
<br>
tlfc> then it eventually times out. Same whether I use dhcpcd or dhclient.<br>
<br>
tlfc> WIth static mode, rather than dhcp mode, on my interfaces, everything works perfectly.<br>
<br>
</b><span style=" color: #000000;">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>
-Greg<br>
<br>
<br>
</body></html>