Update documentation

4 files changed, 292 insertions, 195 deletions

diff --git a/server/dhcpd.8 b/server/dhcpd.8
index c0f9aa9a..4bc6ff60 100644
--- a/server/dhcpd.8
+++ b/server/dhcpd.8
@@ -298,7 +298,7 @@ in dhcpd.conf(5).
 .B ETCDIR/dhcpd.conf, DBDIR/dhcpd.leases, RUNDIR/dhcpd.pid,
 .B DBDIR/dhcpd.leases~.
 .SH SEE ALSO
-dhcpd.conf(5), dhcpd.leases(5)
+dhclient(8), dhcrelay(8), dhcpd.conf(5), dhcpd.leases(5)
 .SH AUTHOR
 .B dhcpd(8)
 was written by Ted Lemon <mellon@vix.com>
diff --git a/server/dhcpd.cat8 b/server/dhcpd.cat8
index d046e509..02850687 100644
--- a/server/dhcpd.cat8
+++ b/server/dhcpd.cat8
@@ -105,9 +105,9 @@ CCOOMMMMAANNDD LLIINNEE
        unable to identify non-broadcast  interfaces,  but  should
        not  be  required on other systems.  If no interface names
        are specified on the command line dhcpd will identify  all
-       network   interfaces  which  are  up,  elimininating  non-
-       broadcast interfaces if  possible,  and  listen  for  DHCP
-       broadcasts on each interface.
+       network  interfaces which are up, elimininating non-broad-
+       cast interfaces if possible, and listen  for  DHCP  broad-
+       casts on each interface.
 
        If  dhcpd  should listen on a port other than the standard
        (port 67), the --pp flag may used.  It should be followed by
@@ -301,7 +301,7 @@ FFIILLEESS
        //vvaarr//ddbb//ddhhccppdd..lleeaasseess~~..
 
 SSEEEE AALLSSOO
-       dhcpd.conf(5), dhcpd.leases(5)
+       dhclient(8), dhcrelay(8), dhcpd.conf(5), dhcpd.leases(5)
 
 AAUUTTHHOORR
        ddhhccppdd((88)) was written by Ted Lemon <mellon@vix.com> under a
diff --git a/server/dhcpd.conf.5 b/server/dhcpd.conf.5
index a0dbc51a..0f93d92e 100644
--- a/server/dhcpd.conf.5
+++ b/server/dhcpd.conf.5
@@ -443,6 +443,50 @@ be used for all clients that may boot using the BOOTP protocol.
 The group statement is used simply to apply one or more parameters to
 a group of declarations.   It can be used to group hosts, shared
 networks, subnets, or even other groups.
+.SH REFERENCE: ALLOW and DENY
+.PP
+The
+.I allow
+and
+.I deny
+statements can be used to control the behaviour of dhcpd to various
+sorts of requests.
+.PP
+.PP
+.B The
+.I unknown-clients
+.B keyword
+.PP
+ \fBallow unknown-clients;\fR
+ \fBdeny unknown-clients;\fR
+.PP
+The \fBunknown-clients\fR flag is used to tell dhcpd whether
+or not to dynamically assign addresses to unknown clients.   Dynamic
+address assignment to unknown clients is \fBallow\fRed by default.
+.PP
+.B The
+.I bootp
+.B keyword
+.PP
+ \fBallow bootp;\fR
+ \fBdeny bootp;\fR
+.PP
+The \fBunknown-clients\fR flag is used to tell dhcpd whether
+or not to respond to bootp queries.  Bootp queries are \fBallow\fRed
+by default.
+.PP
+.B The
+.I booting
+.B keyword
+.PP
+ \fBallow booting;\fR
+ \fBdeny booting;\fR
+.PP
+The \fBbooting\fR flag is used to tell dhcpd whether or not to respond
+to queries from a particular client.  This keyword only has meaning
+when it appears in a host declaration.   By default, booting is
+\fBallow\fRed, but if it is disabled for a particular client, then
+that client will not be able to get and address from the DHCP server.
 .SH REFERENCE: PARAMETERS
 .PP
 .B The
@@ -591,19 +635,6 @@ Needless to say, this parameter should be adjusted with extreme
 caution.
 .PP
 .B The
-.I boot-unknown-clients
-.B statement
-.PP
- \fBboot-unknown-clients\fR \fIflag\fR\fB;\fR
-.PP
-The \fIboot-unknown-clients\fR statement is used to tell dhcpd whether
-or not to dynamically assign addresses to unknown clients.  If
-\fIflag\fR is true (the default), then addresses are dynamically
-assigned to unknown clients when available.  If \fIflag\fR is
-false, then addresses are provided only to clients which match at
-least one host declaration.
-.PP
-.B The
 .I get-lease-hostnames
 .B statement
 .PP
diff --git a/server/dhcpd.conf.cat5 b/server/dhcpd.conf.cat5
index ea02aab4..ddbe2fbc 100644
--- a/server/dhcpd.conf.cat5
+++ b/server/dhcpd.conf.cat5
@@ -14,10 +14,10 @@ DDEESSCCRRIIPPTTIIOONN
        The dhcpd.conf file is a free-form ASCII text  file.    It
        is  parsed  by  the  recursive-descent  parser  built into
        dhcpd.   The file may contain extra tabs and newlines  for
-       formatting  purposes.   Keywords  in  the  file  are case-
-       insensitive.   Comments may be placed anywhere within  the
-       file  (except  within quotes).   Comments begin with the #
-       character and end at the end of the line.
+       formatting purposes.  Keywords in the file are case-insen-
+       sitive.   Comments may be placed anywhere within the  file
+       (except  within quotes).   Comments begin with the # char-
+       acter and end at the end of the line.
 
        The file essentially consists of  a  list  of  statements.
        Statements fall into two broad categories - parameters and
@@ -268,11 +268,11 @@ dhcpd.conf(5)                                       dhcpd.conf(5)
 dhcpd.conf(5)                                       dhcpd.conf(5)
 
 
-       Imagine  that  you  have  a  site  with  a  lot  of NCD X-
-       Terminals.   These terminals come in a variety of  models,
-       and  you  want  to specify the boot files for each models.
-       One way to do this would be to have host declarations  for
-       each server and group them by model:
+       Imagine  that  you  have a site with a lot of NCD X-Termi-
+       nals.   These terminals come in a variety of  models,  and
+       you  want to specify the boot files for each models.   One
+       way to do this would be to have host declarations for each
+       server and group them by model:
 
        group {
          filename "Xncd19r";
@@ -363,8 +363,8 @@ dhcpd.conf(5)                                       dhcpd.conf(5)
 
        The  _s_u_b_n_e_t statement is used to provide dhcpd with enough
        information to tell whether or not an  IP  address  is  on
-       that  subnet.   It  may  also  be  used to provide subnet-
-       specific parameters and to specify what addresses  may  be
+       that  subnet.   It may also be used to provide subnet-spe-
+       cific parameters and to  specify  what  addresses  may  be
        dynamically  allocated  to clients booting on that subnet.
        Such addresses are specified using the _r_a_n_g_e  declaration.
 
@@ -473,6 +473,42 @@ dhcpd.conf(5)                                       dhcpd.conf(5)
        group hosts,  shared  networks,  subnets,  or  even  other
        groups.
 
+RREEFFEERREENNCCEE:: AALLLLOOWW aanndd DDEENNYY
+       The  _a_l_l_o_w  and _d_e_n_y statements can be used to control the
+       behaviour of dhcpd to various sorts of requests.
+
+
+       TThhee _u_n_k_n_o_w_n_-_c_l_i_e_n_t_s kkeeyywwoorrdd
+
+        aallllooww uunnkknnoowwnn--cclliieennttss;;
+        ddeennyy uunnkknnoowwnn--cclliieennttss;;
+
+       The uunnkknnoowwnn--cclliieennttss flag is used to tell dhcpd whether  or
+       not  to  dynamically  assign addresses to unknown clients.
+       Dynamic address assignment to unknown clients  is  aalllloowwed
+       by default.
+
+       TThhee _b_o_o_t_p kkeeyywwoorrdd
+
+        aallllooww bboooottpp;;
+        ddeennyy bboooottpp;;
+
+       The  uunnkknnoowwnn--cclliieennttss flag is used to tell dhcpd whether or
+       not to  respond  to  bootp  queries.   Bootp  queries  are
+       aalllloowwed by default.
+
+       TThhee _b_o_o_t_i_n_g kkeeyywwoorrdd
+
+        aallllooww bboooottiinngg;;
+        ddeennyy bboooottiinngg;;
+
+       The  bboooottiinngg  flag is used to tell dhcpd whether or not to
+       respond to queries from a particular client.  This keyword
+       only  has  meaning  when it appears in a host declaration.
+       By default, booting is aalllloowwed, but if it is disabled  for
+       a  particular client, then that client will not be able to
+       get and address from the DHCP server.
+
 RREEFFEERREENNCCEE:: PPAARRAAMMEETTEERRSS
        TThhee _d_e_f_a_u_l_t_-_l_e_a_s_e_-_t_i_m_e ssttaatteemmeenntt
 
@@ -484,34 +520,46 @@ RREEFFEERREENNCCEE:: PPAARRAAMMEETTEERRSS
 
        TThhee _m_a_x_-_l_e_a_s_e_-_t_i_m_e ssttaatteemmeenntt
 
+
+
+
+                                                                8
+
+
+
+
+
+dhcpd.conf(5)                                       dhcpd.conf(5)
+
+
         mmaaxx--lleeaassee--ttiimmee _t_i_m_e;;
 
-       _T_i_m_e  should be the maximum length in seconds that will be
-       assigned to a lease if the  client  requesting  the  lease
+       _T_i_m_e should be the maximum length in seconds that will  be
+       assigned  to  a  lease  if the client requesting the lease
        asks for a specific expiration time.
 
        TThhee _h_a_r_d_w_a_r_e ssttaatteemmeenntt
 
         hhaarrddwwaarree _h_a_r_d_w_a_r_e_-_t_y_p_e _h_a_r_d_w_a_r_e_-_a_d_d_r_e_s_s;;
 
-       In  order for a BOOTP client to be recognized, its network
-       hardware address must be declared using a _h_a_r_d_w_a_r_e  clause
-       in  the _h_o_s_t statement.  _h_a_r_d_w_a_r_e_-_t_y_p_e must be the name of
-       a physical hardware interface type.   Currently, only  the
-       eetthheerrnneett  type  is recognized, although support for ttookkeenn--
+       In order for a BOOTP client to be recognized, its  network
+       hardware  address must be declared using a _h_a_r_d_w_a_r_e clause
+       in the _h_o_s_t statement.  _h_a_r_d_w_a_r_e_-_t_y_p_e must be the name  of
+       a  physical hardware interface type.   Currently, only the
+       eetthheerrnneett type is recognized, although support  for  ttookkeenn--
        rriinngg and ffddddii hardware types would also be desirable.  The
-       _h_a_r_d_w_a_r_e_-_a_d_d_r_e_s_s  should  be  a  set of hexadecimal octets
-       (numbers from 0 through ff)  seperated  by  colons.    The
+       _h_a_r_d_w_a_r_e_-_a_d_d_r_e_s_s should be a  set  of  hexadecimal  octets
+       (numbers  from  0  through  ff) seperated by colons.   The
        _h_a_r_d_w_a_r_e_f_R _s_t_a_t_e_m_e_n_t _m_a_y _a_l_s_o _b_e _u_s_e_d _f_o_r _D_H_C_P _c_l_i_e_n_t_s_.
 
        TThhee _f_i_l_e_n_a_m_e ssttaatteemmeenntt
 
         ffiilleennaammee ""_f_i_l_e_n_a_m_e"";;
 
-       The  _f_i_l_e_n_a_m_e statement can be used to specify the name of
-       the initial boot file which is to be loaded by  a  client.
+       The _f_i_l_e_n_a_m_e statement can be used to specify the name  of
+       the  initial  boot file which is to be loaded by a client.
        The _f_i_l_e_n_a_m_e should be a filename recognizable to whatever
-       file transfer protocol the client can be expected  to  use
+       file  transfer  protocol the client can be expected to use
        to load the file.
 
        TThhee _s_e_r_v_e_r_-_n_a_m_e ssttaatteemmeenntt
@@ -520,44 +568,44 @@ RREEFFEERREENNCCEE:: PPAARRAAMMEETTEERRSS
 
        The _s_e_r_v_e_r_-_n_a_m_e statement can be used to inform the client
        of the name of the server from which it is booting.   _N_a_m_e
+       should be the name that will be provided to the client.
 
+       TThhee _n_e_x_t_-_s_e_r_v_e_r ssttaatteemmeenntt
 
+        nneexxtt--sseerrvveerr _s_e_r_v_e_r_-_n_a_m_e;;
 
-                                                                8
+       The _n_e_x_t_-_s_e_r_v_e_r statement is  used  to  specify  the  host
+       address  of  the  server  from which the initial boot file
+       (specified in the _f_i_l_e_n_a_m_e statement)  is  to  be  loaded.
+       _S_e_r_v_e_r_-_n_a_m_e  should  be  a  numeric IP address or a domain
+       name.   If no _n_e_x_t_-_s_e_r_v_e_r parameter  applies  to  a  given
+       client,  the  address  specified  in the _s_e_r_v_e_r_-_i_d_e_n_t_i_f_i_e_r
+       statement is used.
 
+       TThhee _f_i_x_e_d_-_a_d_d_r_e_s_s ssttaatteemmeenntt
 
+        ffiixxeedd--aaddddrreessss _a_d_d_r_e_s_s [,, _a_d_d_r_e_s_s ... ];;
 
 
 
-dhcpd.conf(5)                                       dhcpd.conf(5)
 
+                                                                9
 
-       should be the name that will be provided to the client.
 
-       TThhee _n_e_x_t_-_s_e_r_v_e_r ssttaatteemmeenntt
 
-        nneexxtt--sseerrvveerr _s_e_r_v_e_r_-_n_a_m_e;;
 
-       The  _n_e_x_t_-_s_e_r_v_e_r  statement  is  used  to specify the host
-       address of the server from which  the  initial  boot  file
-       (specified  in  the  _f_i_l_e_n_a_m_e  statement) is to be loaded.
-       _S_e_r_v_e_r_-_n_a_m_e should be a numeric IP  address  or  a  domain
-       name.    If  no  _n_e_x_t_-_s_e_r_v_e_r  parameter applies to a given
-       client, the address  specified  in  the  _s_e_r_v_e_r_-_i_d_e_n_t_i_f_i_e_r
-       statement is used.
 
-       TThhee _f_i_x_e_d_-_a_d_d_r_e_s_s ssttaatteemmeenntt
+dhcpd.conf(5)                                       dhcpd.conf(5)
 
-        ffiixxeedd--aaddddrreessss _a_d_d_r_e_s_s [,, _a_d_d_r_e_s_s ... ];;
 
-       The  _f_i_x_e_d_-_a_d_d_r_e_s_s statement is used to assign one or more
-       fixed IP addresses to a client.  It should only appear  in
+       The _f_i_x_e_d_-_a_d_d_r_e_s_s statement is used to assign one or  more
+       fixed  IP addresses to a client.  It should only appear in
        a _h_o_s_t declaration.  If more than one address is supplied,
-       then when the  client  boots,  it  will  be  assigned  the
-       address  which  corresponds  to the network on which it is
-       booting.  If none of the addresses  in  the  _f_i_x_e_d_-_a_d_d_r_e_s_s
-       statement  are on the network on which the client is boot-
-       ing, that client will not match the _h_o_s_t declaration  con-
+       then  when  the  client  boots,  it  will  be assigned the
+       address which corresponds to the network on  which  it  is
+       booting.   If  none  of the addresses in the _f_i_x_e_d_-_a_d_d_r_e_s_s
+       statement are on the network on which the client is  boot-
+       ing,  that client will not match the _h_o_s_t declaration con-
        taining that _f_i_x_e_d_-_a_d_d_r_e_s_s statement.  Each _a_d_d_r_e_s_s should
        be either an IP address or a domain name which resolves to
        one or more IP addresses.
@@ -566,13 +614,13 @@ dhcpd.conf(5)                                       dhcpd.conf(5)
 
         ddyynnaammiicc--bboooottpp--lleeaassee--ccuuttooffff _d_a_t_e;;
 
-       The  _d_y_n_a_m_i_c_-_b_o_o_t_p_-_l_e_a_s_e_-_c_u_t_o_f_f  statement sets the ending
+       The _d_y_n_a_m_i_c_-_b_o_o_t_p_-_l_e_a_s_e_-_c_u_t_o_f_f statement sets  the  ending
        time for all leases assigned dynamically to BOOTP clients.
-       Because  BOOTP  clients  do  not  have any way of renewing
-       leases, and don't know that their leases could expire,  by
+       Because BOOTP clients do not  have  any  way  of  renewing
+       leases,  and don't know that their leases could expire, by
        default  dhcpd  assignes  infinite  leases  to  all  BOOTP
        clients.  However, it may make sense in some situations to
-       set  a cutoff date for all BOOTP leases - for example, the
+       set a cutoff date for all BOOTP leases - for example,  the
        end of a school term, or the time at night when a facility
        is closed and all machines are required to be powered off.
 
@@ -581,52 +629,40 @@ dhcpd.conf(5)                                       dhcpd.conf(5)
 
                          W YYYY/MM/DD HH:MM:SS
 
-       W  is  the day of the week expressed as a number from zero
-       (Sunday) to six (Saturday).  YYYY is the  year,  including
+       W is the day of the week expressed as a number  from  zero
+       (Sunday)  to  six (Saturday).  YYYY is the year, including
        the century.  MM is the month expressed as a number from 1
-       to 12.  DD is the day of the month, counting from  1.   HH
-       is  the hour, from zero to 23.  MM is the minute and SS is
-
-
-
-                                                                9
-
-
-
-
-
-dhcpd.conf(5)                                       dhcpd.conf(5)
-
-
-       the second.  The time is always  in  Greenwich  Mean  Time
+       to  12.   DD is the day of the month, counting from 1.  HH
+       is the hour, from zero to 23.  MM is the minute and SS  is
+       the  second.   The  time  is always in Greenwich Mean Time
        (GMT), not local time.
 
        TThhee _d_y_n_a_m_i_c_-_b_o_o_t_p_-_l_e_a_s_e_-_l_e_n_g_t_h ssttaatteemmeenntt
 
         ddyynnaammiicc--bboooottpp--lleeaassee--lleennggtthh _l_e_n_g_t_h;;
 
-       The  _d_y_n_a_m_i_c_-_b_o_o_t_p_-_l_e_a_s_e_-_l_e_n_g_t_h  statement  is used to set
-       the  length  of  leases  dynamically  assigned  to   BOOTP
-       clients.    At  some  sites,  it may be possible to assume
-       that a lease is no longer in use if  its  holder  has  not
-       used  BOOTP  or  DHCP  to get its address within a certain
+       The _d_y_n_a_m_i_c_-_b_o_o_t_p_-_l_e_a_s_e_-_l_e_n_g_t_h statement is  used  to  set
+       the   length  of  leases  dynamically  assigned  to  BOOTP
+       clients.   At some sites, it may  be  possible  to  assume
+       that  a  lease  is  no longer in use if its holder has not
+       used BOOTP or DHCP to get its  address  within  a  certain
        time period.   The period is specified in _l_e_n_g_t_h as a num-
-       ber  of  seconds.   If a client reboots using BOOTP during
+       ber of seconds.   If a client reboots using  BOOTP  during
        the timeout period, the lease duration is reset to _l_e_n_g_t_h,
-       so  a BOOTP client that boots frequently enough will never
+       so a BOOTP client that boots frequently enough will  never
        lose its lease.  Needless to say, this parameter should be
        adjusted with extreme caution.
 
-       TThhee _b_o_o_t_-_u_n_k_n_o_w_n_-_c_l_i_e_n_t_s ssttaatteemmeenntt
 
-        bboooott--uunnkknnoowwnn--cclliieennttss _f_l_a_g;;
 
-       The  _b_o_o_t_-_u_n_k_n_o_w_n_-_c_l_i_e_n_t_s  statement is used to tell dhcpd
-       whether or not to dynamically assign addresses to  unknown
-       clients.   If  _f_l_a_g  is true (the default), then addresses
-       are dynamically assigned to unknown  clients  when  avail-
-       able.   If _f_l_a_g is false, then addresses are provided only
-       to clients which match at least one host declaration.
+                                                               10
+
+
+
+
+
+dhcpd.conf(5)                                       dhcpd.conf(5)
+
 
        TThhee _g_e_t_-_l_e_a_s_e_-_h_o_s_t_n_a_m_e_s ssttaatteemmeenntt
 
@@ -652,18 +688,6 @@ dhcpd.conf(5)                                       dhcpd.conf(5)
            group {
              use-host-decl-names on;
 
-
-
-
-                                                               10
-
-
-
-
-
-dhcpd.conf(5)                                       dhcpd.conf(5)
-
-
              host joe {
             hardware ethernet 08:00:2b:4c:29:32;
             fixed-address joe.fugue.com;
@@ -694,6 +718,18 @@ RREEFFEERREENNCCEE:: OOPPTTIIOONN SSTTAATTEEMMEENNTTSS
 
        The  iipp--aaddddrreessss  data  type  can  be  entered either as an
        explicit IP address (e.g., 239.254.197.10) or as a  domain
+
+
+
+                                                               11
+
+
+
+
+
+dhcpd.conf(5)                                       dhcpd.conf(5)
+
+
        name (e.g., haagen.isc.org).  When entering a domain name,
        be sure that that domain name  resolves  to  a  single  IP
        address.
@@ -717,20 +753,8 @@ RREEFFEERREENNCCEE:: OOPPTTIIOONN SSTTAATTEEMMEENNTTSS
 
        The ddaattaa--ssttrriinngg data type specifies either  an  NVT  ASCII
        string  enclosed  in  double quotes, or a series of octets
-       specified  in  hexadecimal,  seperated  by  colons.    For
-
-
-
-                                                               11
-
-
-
-
-
-dhcpd.conf(5)                                       dhcpd.conf(5)
-
-
-       example:
+       specified in hexadecimal, seperated by colons.   For exam-
+       ple:
 
             option client-identifier "CLIENT-FOO";
        or
@@ -760,6 +784,18 @@ dhcpd.conf(5)                                       dhcpd.conf(5)
        as per RFC 950.  If no subnet mask option is provided any-
        where in scope, as a last resort dhcpd will use the subnet
        mask  from the subnet declaration for the network on which
+
+
+
+                                                               12
+
+
+
+
+
+dhcpd.conf(5)                                       dhcpd.conf(5)
+
+
        an address is being assigned.   However,  _a_n_y  subnet-mask
        option  declaration that is in scope for the address being
        assigned will override the subnet mask  specified  in  the
@@ -785,17 +821,6 @@ dhcpd.conf(5)                                       dhcpd.conf(5)
 
         ooppttiioonn nnaammee--sseerrvveerrss _i_p_-_a_d_d_r_e_s_s [,, _i_p_-_a_d_d_r_e_s_s ... ];
 
-
-
-                                                               12
-
-
-
-
-
-dhcpd.conf(5)                                       dhcpd.conf(5)
-
-
        The  name-servers  option specifies a list of IEN 116 name
        servers available to the client.  Servers should be listed
        in order of preference.
@@ -826,6 +851,17 @@ dhcpd.conf(5)                                       dhcpd.conf(5)
        printer servers available to the client.   Servers  should
        be listed in order of preference.
 
+
+
+                                                               13
+
+
+
+
+
+dhcpd.conf(5)                                       dhcpd.conf(5)
+
+
         ooppttiioonn iimmpprreessss--sseerrvveerrss _i_p_-_a_d_d_r_e_s_s [,, _i_p_-_a_d_d_r_e_s_s ... ];;
 
        The  impress-server  option  specifies  a  list  of Imagen
@@ -850,18 +886,6 @@ dhcpd.conf(5)                                       dhcpd.conf(5)
         ooppttiioonn bboooott--ssiizzee _u_i_n_t_1_6;;
 
        This option specifies the length in  512-octet  blocks  of
-
-
-
-                                                               13
-
-
-
-
-
-dhcpd.conf(5)                                       dhcpd.conf(5)
-
-
        the default boot image for the client.
 
         ooppttiioonn mmeerriitt--dduummpp _s_t_r_i_n_g;;
@@ -892,6 +916,18 @@ dhcpd.conf(5)                                       dhcpd.conf(5)
 
        This option specifies whether the client should  configure
        its  IP  layer  for packet forwarding.  A value of 0 means
+
+
+
+                                                               14
+
+
+
+
+
+dhcpd.conf(5)                                       dhcpd.conf(5)
+
+
        disable IP forwarding, and a value of 1  means  enable  IP
        forwarding.
 
@@ -916,18 +952,6 @@ dhcpd.conf(5)                                       dhcpd.conf(5)
        match  one  of  the  filters  should  be  discarded by the
        client.
 
-
-
-
-                                                               14
-
-
-
-
-
-dhcpd.conf(5)                                       dhcpd.conf(5)
-
-
        See STD 3 (RFC1122) for further information.
 
         ooppttiioonn mmaaxx--ddggrraamm--rreeaasssseemmbbllyy _u_i_n_t_1_6;;
@@ -958,6 +982,18 @@ dhcpd.conf(5)                                       dhcpd.conf(5)
         ooppttiioonn iinntteerrffaaccee--mmttuu _u_i_n_t_1_6;;
 
        This  option  specifies  the MTU to use on this interface.
+
+
+
+                                                               15
+
+
+
+
+
+dhcpd.conf(5)                                       dhcpd.conf(5)
+
+
        The minimum legal value for the MTU is 68.
 
         ooppttiioonn aallll--ssuubbnneettss--llooccaall _f_l_a_g;;
@@ -982,18 +1018,6 @@ dhcpd.conf(5)                                       dhcpd.conf(5)
        perform  subnet  mask  discovery using ICMP.  A value of 0
        indicates that the client should not perform mask  discov-
        ery.   A  value  of 1 means that the client should perform
-
-
-
-                                                               15
-
-
-
-
-
-dhcpd.conf(5)                                       dhcpd.conf(5)
-
-
        mask discovery.
 
         ooppttiioonn mmaasskk--ssuupppplliieerr _f_l_a_g;;
@@ -1024,6 +1048,18 @@ dhcpd.conf(5)                                       dhcpd.conf(5)
        routes  to  the  same  destination are specified, they are
        listed in descending order of priority.
 
+
+
+
+                                                               16
+
+
+
+
+
+dhcpd.conf(5)                                       dhcpd.conf(5)
+
+
        The routes consist of a list of  IP  address  pairs.   The
        first  address  is the destination address, and the second
        address is the router for the destination.
@@ -1048,18 +1084,6 @@ dhcpd.conf(5)                                       dhcpd.conf(5)
         ooppttiioonn iieeeeee880022--33--eennccaappssuullaattiioonn _f_l_a_g;;
 
        This option specifies whether or not the client should use
-
-
-
-                                                               16
-
-
-
-
-
-dhcpd.conf(5)                                       dhcpd.conf(5)
-
-
        Ethernet Version 2 (RFC 894)  or  IEEE  802.3  (RFC  1042)
        encapsulation if the interface is an Ethernet.  A value of
        0 indicates that the client should use RFC 894  encapsula-
@@ -1091,6 +1115,17 @@ dhcpd.conf(5)                                       dhcpd.conf(5)
 
         ooppttiioonn nniiss--ddoommaaiinn _s_t_r_i_n_g;;
 
+
+
+                                                               17
+
+
+
+
+
+dhcpd.conf(5)                                       dhcpd.conf(5)
+
+
        This  option  specifies  the name of the client's NIS (Sun
        Network Information Services) domain.  The domain is  for-
        matted as a character string consisting of characters from
@@ -1115,17 +1150,6 @@ dhcpd.conf(5)                                       dhcpd.conf(5)
        RFC 1001/1002 NBNS name servers listed in order of prefer-
        ence.
 
-
-
-                                                               17
-
-
-
-
-
-dhcpd.conf(5)                                       dhcpd.conf(5)
-
-
         ooppttiioonn nneettbbiiooss--dddd--sseerrvveerr _i_p_-_a_d_d_r_e_s_s [,, _i_p_-_a_d_d_r_e_s_s ... ];;
 
        The  NetBIOS  datagram  distribution  server (NBDD) option
@@ -1157,6 +1181,17 @@ dhcpd.conf(5)                                       dhcpd.conf(5)
 
         ooppttiioonn xx--ddiissppllaayy--mmaannaaggeerr _i_p_-_a_d_d_r_e_s_s [,, _i_p_-_a_d_d_r_e_s_s ... ];;
 
+
+
+                                                               18
+
+
+
+
+
+dhcpd.conf(5)                                       dhcpd.conf(5)
+
+
        This option specifies a list of systems that  are  running
        the  X  Window System Display Manager and are available to
        the client.  Addresses should be listed in order of  pref-
@@ -1183,6 +1218,37 @@ AAUUTTHHOORR
 
 
 
-                                                               18
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+                                                               19