FW: DHCP and BOOTP

[Doug Caviness]

Aww, phooey. I subscribed to the BIND mailing list, not the DHCP list.
Second try.
 

________________________________

From: Doug Caviness 
Sent: Tuesday, June 12, 2007 3:26 PM
To: DHCP Users (dhcp-users at isc.org)
Subject: DHCP and BOOTP

 

I am running ISC DHCP 3.0.5 in a failover configuration. A new
requirement has come down the pipeline: I need to be able to provide IP
addresses via BOOTP on one subnet.

 

I am currently trying to get BOOTP working on the same subnet the DCHP
servers are located. Once that works then I will move the BOOTP client
to the final subnet. I have the client box on the subnet the DHCP
servers are on to eliminate any routing issues.

 

What do I need in the DHCP configuration file to have it respond to
BOOTP requests? Will it work in a failover configuration? I don't want
to have to hard code the MAC/IP because these are units coming in for
repair and the MAC address will change frequently.

 

Here are the relevant (I hope) parts of dhcpd.conf and dhcpd.master
which is included in dhcpd.conf.

Dhcpd.conf:

log-facility local0;

 

# Failover

failover peer "building1" {

primary;

address 10.10.1.10;

port 51000;

peer address 10.10.1.11;

peer port 51001;

                        max-response-delay 30;

max-unacked-updates 10;

mclt 3600;

                        split 128;

load balance max seconds 3;

}

 

include "/etc/dhcpd.master";

 

Dhcpd.master:

#

# Global Parameters

#

default-lease-time 43200;       # 12 hours

#default-lease-time 259200;     # 3 days

max-lease-time 86400;           # 24 hours

#max-lease-time 1296000;

 

allow bootp;

 

authoritative;

 

option domain-name "XXXX.XXXX.net";

option domain-name-servers 10.10.1.118, 10.10.1.10, 10.75.0.16;

option netbios-name-servers 10.10.1.129, 10.10.1.98, 10.75.0.36;

option netbios-node-type 8;

 

ddns-update-style none;

ignore client-updates;

The subnet where I currently have the BOOTP client:

subnet 10.10.1.0 netmask 255.255.255.0 {

  pool {

    range 10.10.1.243 10.10.1.254;

    failover peer "building1";

    deny dynamic bootp clients;

  }

    option broadcast-address 10.10.1.255;

    option subnet-mask 255.255.255.0;

    option routers 10.10.1.1;

}