Fix an error in spawn example. Document always-broadcast.

diff --git a/server/dhcpd.conf.5 b/server/dhcpd.conf.5
index a42f0cf0bac8e93fd0314b9f764f6d487be4ef71..6d1dd5d12130b24e0b0625303d0095884b42be2f 100644 (file)
--- a/server/dhcpd.conf.5
+++ b/server/dhcpd.conf.5
@@ -459,7 +459,7 @@ of this, you can write a class declaration as follows:
 .nf
 class "customer" {
   match if exists agent.circuit-id;
-  spawn with agent.circuit-id;
+  spawn with option agent.circuit-id;
   lease limit 4;
 }
 .fi
@@ -1031,6 +1031,23 @@ be set in any scope, and will affect all clients covered by that
 scope.
 .PP
 .B The
+.I always-broadcast
+.B statement
+.PP
+ \fBalways-broadcast\fR \fIflag\fR\fB;\fR
+.PP
+The DHCP and BOOTP protocols both require DHCP and BOOTP clients to
+set the broadcast bit in the flags field of the BOOTP message header.
+Unfortunately, some DHCP and BOOTP clients do not do this, and
+therefore may not receive responses from the DHCP server.   The DHCP
+server can be made to always broadcast its responses to clients by
+setting this flag to 'on' for the relevant scope.   To avoid creating
+excess broadcast traffic on your network, we recommend that you
+restrict the use of this option to as few clients as possible.   For
+example, the Microsoft DHCP client is known not to have this problem,
+as are the OpenTransport and ISC DHCP clients.
+.PP
+.B The
 .I use-lease-addr-for-default-route
 .B statement
 .PP