client took a host assigned ip

[Simon Hobson]

anthony wrote:

>It happened again this morning.
>
>My host entry
>
>#MAC
>host dhcp33 {
>          hardware ethernet 00:0a:95:9c:28:b0;
>          fixed-address dhcp33.domain.com;
>}
>
>my logs
>dhcpd: DHCPDISCOVER from 00:15:c5:c2:59:f6 via 10.15.49.8
>   dhcpd: DHCPREQUEST for 10.15.49.33 (10.15.49.5) from 00:15:c5:c2:59:f6
>via 10.15.49.8: lease 10.15.49.33 unavailable.
>   dhcpd: DHCPNAK on 10.15.49.33 to 00:15:c5:c2:59:f6 via 10.15.49.8
>dhcpd: DHCPOFFER on 10.15.49.137 to 00:15:c5:c2:59:f6 (hr-cdecresc) via
>10.15.49.8
>
>And yet the pc still used it.


It looks like you have another server at 10.15.49.5, so the exchange 
goes like this :

client does discover :
   DHCPDISCOVER from 00:15:c5:c2:59:f6 via 10.15.49.8

remote server offers 10.15.49.33

client requests 10.15.49.33 :
   DHCPREQUEST for 10.15.49.33 (10.15.49.5) from 00:15:c5:c2:59:f6
   via 10.15.49.8: lease 10.15.49.33 unavailable.

remote server ACKs request for 10.15.49.33, client goes on to use address.

local server NACKs request for 10.15.49.33, but it is ignored because 
client has already had an ACK and so has finished configuration

local server makes own offer (in response to discover), it too is 
ignored as the client has finished configuration.


If you are responsible for the server at 10.15.49.5 then go and 
berate yourself. If someone else has done it then go and "educate 
them" - a piece of 2x4 has been suggested as a suitable educating 
tool ;-)

The server identifier of the server that made the offer being 
requested is shown in the log line inside "( ... )" - it's a useful 
diagnostic.