Use Pool for BOOTP only

Glenn Satchell glenn.satchell at
Wed Aug 22 12:28:39 UTC 2012

The whole point is moot - since 3.1.0 failover works for dynamic bootp
clients. This is from the RELNOTES file:

                        Changes since 4.2.3

- Remove outdated note in the description of the bootp keyword about the
  option not satisfying the requirement of failover peers for denying
  dynamic bootp clients.
  [ISC-bugs #28574]

                        Changes since 3.1.0 (Maintenance)

- Dynamic BOOTP leases are now load balanced in failover.

So simply remove the 'deny dynamic bootp clients;' statement from the
failover pool and don't worry about the other pool or class.

I'm sure I remember something being posted to the list way back. The
current version (4.2.4) doesn't mention this in the dhcpd.conf man page.
You should always trust the current man pages over random stuff found on
the net, most of which can be quite old.


On Wed, August 22, 2012 9:57 pm, Thomas Herrmann wrote:
> On 08/22/2012 11:35 AM, Simon Hobson wrote:
>> What might work is :
>>        class "dhcp" {
>>             match if exists dhcp-message-type;
>>         }
>>         subnet netmask {
>>             pool {
>>                 # BOOTP clients only
>>                 allow dynamic bootp clients;
>>                 deny members of "dhcp";
>>                 range;
>>             }
>>         }
> This seems to work for me; at least bootp clients receive addresses with
> this setup. I will check the logs for a while to make sure that no
> addresses from the bootp range are given to DHCP clients.
> Maybe the failover examples in the man page should be updated to include
> this construct, because failover will not work for DHCP clients which
> received addresses from the bootp range.
> Regards
> Thomas
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at

More information about the dhcp-users mailing list