summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorShawn Routhier <sar@isc.org>2015-08-20 13:12:05 -0700
committerShawn Routhier <sar@isc.org>2015-08-20 13:12:05 -0700
commit13e4b9942fcee6820f2ad181ec27376b3c1ddcb3 (patch)
tree509c33751681911133a5b790c4e5f97afb714899
parentb67dbd9e089059f7e6c81456d02d9bf922edf5f5 (diff)
downloadisc-dhcp-13e4b9942fcee6820f2ad181ec27376b3c1ddcb3.tar.gz
[v4_1_esv] Add comment that declines is only usable for v4 servers
[rt40206] Add comment that declines is only usable for v4 servers
-rw-r--r--server/dhcpd.conf.511
1 files changed, 8 insertions, 3 deletions
diff --git a/server/dhcpd.conf.5 b/server/dhcpd.conf.5
index e459d82a..1598c065 100644
--- a/server/dhcpd.conf.5
+++ b/server/dhcpd.conf.5
@@ -1772,9 +1772,9 @@ a DHCPDECLINE for a particular address, it normally abandons that
address, assuming that some unauthorized system is using it.
Unfortunately, a malicious or buggy client can, using DHCPDECLINE
messages, completely exhaust the DHCP server's allocation pool. The
-server will reclaim these leases, but while the client is running
-through the pool, it may cause serious thrashing in the DNS, and it
-will also cause the DHCP server to forget old DHCP client address
+server will eventually reclaim these leases, but not while the client
+is running through the pool. This may cause serious thrashing in the DNS,
+and it will also cause the DHCP server to forget old DHCP client address
allocations.
.PP
The \fBdeclines\fR flag tells the DHCP server whether or not to honor
@@ -1782,6 +1782,11 @@ DHCPDECLINE messages. If it is set to \fBdeny\fR or \fBignore\fR in
a particular scope, the DHCP server will not respond to DHCPDECLINE
messages.
.PP
+The \fBdeclines\fR flag is only supported by DHCPv4 servers. Given the large
+IPv6 address space and the internal limits imposed by the server's
+address generation mechanism we don't think it is necessary for DHCPv6
+servers at this time.
+.PP
.B The
.I client-updates
.B keyword