From: David Hankins <dhankins@isc.org>
Date: Fri, 20 Jul 2007 19:18:24 +0000 (+0000)
Subject: Update failover documentation for dynamic bootp.
X-Git-Tag: v4_0_0a3~31
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=70aa0d58990448f141f66a669bc73c5bbc12373b;p=thirdparty%2Fdhcp.git

Update failover documentation for dynamic bootp.
---

diff --git a/server/dhcpd.conf.5 b/server/dhcpd.conf.5
index 212ccd5be..1244076a5 100644
--- a/server/dhcpd.conf.5
+++ b/server/dhcpd.conf.5
@@ -28,7 +28,7 @@
 .\" see ``http://www.vix.com''.   To learn more about Nominum, Inc., see
 .\" ``http://www.nominum.com''.
 .\"
-.\" $Id: dhcpd.conf.5,v 1.86 2007/05/19 19:16:26 dhankins Exp $
+.\" $Id: dhcpd.conf.5,v 1.87 2007/07/20 19:18:24 dhankins Exp $
 .\"
 .TH dhcpd.conf 5
 .SH NAME
@@ -509,14 +509,10 @@ failover.  A pool declaration that utilizes failover would look like this:
 .nf
 pool {
 	failover peer "foo";
-	deny dynamic bootp clients;
 	\fIpool specific parameters\fR
 };
 .fi
 .PP
-Dynamic BOOTP leases are not compatible with failover, and, as such,
-you need to disallow BOOTP in pools that you are using failover for.
-.PP
 The  server currently  does very  little  sanity checking,  so if  you
 configure it wrong, it will just  fail in odd ways.  I would recommend
 therefore that you either do  failover or don't do failover, but don't