Clients getting dynamic leases instead of fixed addresses.

[Niall O'Reilly]

At Tue, 23 Sep 2014 15:06:45 +0200,
Eugène Ngontang wrote:
> 
> My dhcod.conf file :
> 
> # DHCP Server Configuration file.
> # see /usr/share/doc/dhcp*/dhcpd.conf.sample 
> #
> ddns-update-style interim;
> ignore client-updates;
> subnet X.X.X.0 netmask 255.255.255.0 {
> option routers X.X.X.1;
> option subnet-mask 255.255.255.0;
> option nis-domain "jcd.priv";
> option domain-name "fr.jcdecaux.org";
> option domain-name-servers X.X.X.11, X.X.X.10, 10.231.2.3, 10.232.2.3;
> range X.X.X.100 X.X.X.200;
> default-lease-time 21600;
> max-lease-time 43200;
> } 
> 
> # create as hosts as players
> 
> host CN-SHT-LX001 { hardware ethernet 00:01:80:81:d2:e1; fixed-address
> X.X.X.15; }
> host CN-SHT-LX002 { hardware ethernet 00:01:80:81:d2:ad; fixed-address
> X.X.X.16; }

  Is it the case that your new hosts are first connected to the
  network, each obtaining an address from the ...100 - ...200 range,
  and subsequently assigned a fixed address?  If so, the DHCP protocol
  requires the previously-used address to be used again, if this is
  not now forbidden.

  In my experience, simply specifying 

host { ... fixed-address ...; }

  isn't enough to forbid such re-use of an address.  You'll need to
  use a pool specification.

  Instead of

range X.X.X.100 X.X.X.200;

  use

pool {
  deny known clients;
  range X.X.X.100 X.X.X.200;
}

  I hope this helps.


  Best regards,
  Niall O'Reilly