dhcpd static binding problem

[Frank Leonhardt]

On 03/12/2013 14:18, Maciej Milewski wrote:
> On 03.12.2013 14:15, Frank Leonhardt wrote:
>> option domain-name "test.junk.foo";
>> option domain-name-servers 192.168.1.205, 192.168.1.206;
>> default-lease-time 600;
>> max-lease-time 7200;
>> ddns-update-style none;
>> log-facility local7;
>>
>> subnet 192.168.1.0  netmask 255.255.255.0 {
>>    range 192.168.1.145 192.168.1.192;
>>     option routers 192.168.1.210;
>>     authoritative;
>> }
>>
>> host WINDOWSXP-PC {
>>          hardware ethernet 00:19:21:10:83:13;
>>          fixed-address 192.169.1.194;
>> }
>>
>> host WINDOWSVISTA-PC {
>>          hardware ethernet 00:21:97:02:b2:3e;
>>          fixed-address 192.169.1.229;
>> }
>>
> Why are you binding Class C, non private IP to your Windows PC? There is
> 192.16_9_ and it should be 192.168
> And that's the reason for not setting correct IP for your host.
I wasn't! It was a typo and it was cut/pasted so subsequent entries, so 
thanks for spotting it as it's been driving me crazy.

Next questions (assuming it now works):

How come WINDOWXP-PC did get the address 192.168.1.194? Very weird.

How come dhcpd didn't complain; even when I ran it with the -t option to 
check the config file, and the -d option to explain exactly what it was 
doing. Of course I didn't want to assign 192.16*9*.1.229, but I can't 
see why it didn't just do what I asked OR complain it was illegal? Just 
silently ignoring it wasn't very helpful.

Regards, Frank.