client took a host assigned ip

[anthony]

Thanks,

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.



Simon Hobson wrote:
> anthony wrote:
> 
>> I have a mac os client that for some reason requested an ip that was not
>> in dhcp range but rather was a host assigned ip.
>>
>> The logs show the dhcp server never offered the ip to that mac os.
>>
>> How do I ensure not no clients get host assigned ip's.
> 
> It is sufficient (with the ISC server) to not include the address in 
> a range or a fixed-address statement, it will then NOT be offered to 
> any client.
> 
> The server will not however NACK an address that a client might 
> request if the address is a valid address for the subnet - eg in the 
> example config you give, 10.15.49.100 would be considered valid (and 
> not NACKed) but would NOT be offered to a client. So if you have 
> another dhcp server on the subnet then it is quite easy for the other 
> server to hand out addresses you did not intend to be used.
> 
> Another explanation is that a client has moved from another network 
> and is requesting the address it last had.
> 
>> Do I need to   make a pool of host assigned ip's and deny the clients
>> like this?
>>
>>
>>         pool {
>>                  failover peer "dhcp-failover";
>>                  range 10.15.49.101 10.15.49.119;
>>                  range 10.15.49.130 10.15.49.254;
>>                  option domain-name-servers 10.15.61.5;
>>                  deny dynamic bootp clients;
>>
>>          }
>>          pool {
>>                  range 10.15.49.33 10.15.49.35;
>>                  deny all clients;
>>          }
>>
>> host procurve2wp {
>>          hardware ethernet 00:08:83:FF:FA:80;
>>          fixed-address procurve2.whiteplains.domain.com;
>> }
> 
> No, there is no need for that.
> 
> 
>