Use Pool for BOOTP only

[Thomas Herrmann]

I set up isc-dhcpd on two servers and configured failover. DHCP failover
seems to work properly. BOOTP clients receive the proper addresses, too.

This is my subnet part:

subnet 10.10.0.0 netmask 255.255.0.0 {
  pool {
    failover peer "adwin";
    deny dynamic bootp clients;
    range 10.10.101.50 10.10.101.250;
  }
  pool { # bootp cannot do failover
    range 10.10.101.40 10.10.101.49;
  }
  authoritative;

  option routers 10.10.100.19;
  option broadcast-address 10.10.255.255;
  option domain-name-servers routersrv1.adwin.jcm, filesrv2.adwin.jcm;
  option domain-name "adwin.jcm";

  default-lease-time 1200;
  max-lease-time 2400;

  zone 101.10.10.in-addr.arpa. {
    primary 10.10.100.19;
    key "rndc-key";
  }
  zone adwin.jcm. {
    primary 10.10.100.19;
    key "rndc-key";
  }
}

Observing the logs, I found one entry where the IP 10.10.101.44 was
given out to a DHCP client (not a BOOTP client!). How can I restrict the
IP addresses from 10.10.101.40-10.10.101.49 for bootp only? Using the
current setup, the DHCP client would get a new IP address after the
primary server was down for a while, because the second does not do
failover for bootp.

The solution in this thread [1] seems to be exactly what I need, but
unfortunately, it does not work:

Aug 21 16:29:15 routersrv1 dhcpd: BOOTREQUEST from 00:0c:29:33:38:b2 via
eth0.1: BOOTP from dynamic client and no dynamic leases

I am using the debian testing version of isc-dhcpd (4.2.2.dfsg.1-5), but
I assume the error is not debian specific.

Regards
Thomas Herrmann

[1] https://lists.isc.org/pipermail/dhcp-users/2008-July/006805.html