fixed-address problem

[Graham Clinch]

On 26/01/2016 19:30, Bernard Fay wrote:
> subnet 192.168.99.0 netmask 255.255.255.0 {
> [...]
>        fixed-address 192.168.98.101;
 > [...]
> What am I doing wrong?

There's no subnet defined that contains the fixed-address, so dhcpd 
can't offer that address to a client.  Perhaps you meant to allocate 
'192.168.99.101', or use a different netmask?

Unrelated to the problem, option inheritance can work unexpectedly when 
hosts are defined within subnets - you might find this less confusing in 
future:

=-=
subnet 192.168.99.0 netmask 255.255.255.0 {
#   range 192.168.99.201 192.168.99.250;
     option broadcast-address 192.168.99.255;
     option routers 192.168.99.1;
     option domain-name "cts.org";
}

group {
     host vault {
         option host-name "vault.cts.org";
         hardware ethernet 52:af:12:cf:87:c5;
         fixed-address 192.168.98.101;
     }
}
=-=

(additionally the 'empty' group (i.e. no options defined) doesn't really 
gain anything in this case, so you could move the 'host' to the outer 
layer and dispense with the group entirely)

Graham