Broadcast address leased to a client

[Simon Hobson]

Ivo Sabev wrote:

>option domain-name "somedomain";
>default-lease-time 345600;
>max-lease-time 604800;
>use-host-decl-names on;
>option routers 192.168.62.17;
>option domain-name-servers 192.168.62.17;
>option netbios-name-servers 192.168.62.17;
>option netbios-node-type 2;
>option time-servers 192.168.62.17;
>ddns-update-style interim;
>ddns-updates on;
>
>  key DHCP {
>         algorithm somealgorithm;
>         secret "somekey";
>
>};
>
>subnet 192.168.62.16 netmask 255.255.255.240 {
>         range 192.168.62.20 192.168.62.31;
>         host kikin {
>                 fixed-address 192.168.62.20;
>                 hardware ethernet some MAC;
>         }
>         ddns-updates on;
>         ddns-domainname " somedomain.";
>
>         zone somedomain. {
>                 primary 192.168.62.17;
>                 key DHCP;
>         }
>
>         zone 0.62.168.192.in-addr.arpa. {
>                 primary 192.168.62.17;
>                 key DHCP;
>         }
>
>}
>
>
>As you can see I have made a mistake, in range 192.168.62.20 192.168.62.31;,
>because the last ip is the broadcast ip of the subnet. Bu what was my
>astonishment when a Windows XP SP2 succeeded in getting this broadcast
>address without complaining.
>
>My question is: Is it normal the dhcpd not to check that it is giving
>broadcast address?

No, the server doesn't check - as the administrator you are supposed 
to know what you are doing :-)



You have also made several other mistakes, I suggest you rearrange 
your config like this :

option domain-name "somedomain";
default-lease-time 345600;
max-lease-time 604800;
use-host-decl-names on;
option domain-name-servers 192.168.62.17;
option netbios-name-servers 192.168.62.17;
option netbios-node-type 2;
option time-servers 192.168.62.17;
ddns-update-style interim;
ddns-updates on;


subnet 192.168.62.16 netmask 255.255.255.240 {
         option routers 192.168.62.17;
         range 192.168.62.20 192.168.62.31;
         ddns-updates on;
         ddns-domainname "somedomain.";

}


host kikin {
         fixed-address 192.168.62.20;
         hardware ethernet some MAC;
}


key DHCP {
         algorithm somealgorithm;
         secret "somekey";
};

zone somedomain. {
         primary 192.168.62.17;
         key DHCP;
}

zone 0.62.168.192.in-addr.arpa. {
         primary 192.168.62.17;
         key DHCP;
}


What I've changed :

Moved routers option to subnet, it doesn't make sense outside of a 
subnet as it won't be valid anywhere else.

Moved your host statement outside of the subnet. Inside a subnet it 
inherits options from the subnet even if you move it to another 
subnet - ie the host would get a lease with invalid routers etc.

Moved your key and zone declarations to global scope and put them in 
one place together.

Removed a space from your ddns-domainname.