ssahani / rpms / dhcp

Forked from rpms/dhcp 6 years ago
Clone
4060c28
.\" $Id: dhcp-options.5,v 1.1 2007/11/12 23:16:08 dcantrel Exp $
3b9e0e2
.\"
3b9e0e2
.\" Copyright (c) 2004-2007 by Internet Systems Consortium, Inc. ("ISC")
3b9e0e2
.\" Copyright (c) 1996-2003 by Internet Software Consortium
3b9e0e2
.\"
3b9e0e2
.\" Permission to use, copy, modify, and distribute this software for any
3b9e0e2
.\" purpose with or without fee is hereby granted, provided that the above
3b9e0e2
.\" copyright notice and this permission notice appear in all copies.
3b9e0e2
.\"
3b9e0e2
.\" THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES
3b9e0e2
.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
3b9e0e2
.\" MERCHANTABILITY AND FITNESS.  IN NO EVENT SHALL ISC BE LIABLE FOR
3b9e0e2
.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
3b9e0e2
.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
3b9e0e2
.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT
3b9e0e2
.\" OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
3b9e0e2
.\"
3b9e0e2
.\"   Internet Systems Consortium, Inc.
3b9e0e2
.\"   950 Charter Street
3b9e0e2
.\"   Redwood City, CA 94063
3b9e0e2
.\"   <info@isc.org>
3b9e0e2
.\"   http://www.isc.org/
3b9e0e2
.\"
3b9e0e2
.\" This software has been written for Internet Systems Consortium
3b9e0e2
.\" by Ted Lemon in cooperation with Vixie Enterprises and Nominum, Inc.
3b9e0e2
.\" To learn more about Internet Systems Consortium, see
3b9e0e2
.\" ``http://www.isc.org/''.  To learn more about Vixie Enterprises,
3b9e0e2
.\" see ``http://www.vix.com''.   To learn more about Nominum, Inc., see
3b9e0e2
.\" ``http://www.nominum.com''.
3b9e0e2
.TH dhcpd-options 5
3b9e0e2
.SH NAME
3b9e0e2
dhcp-options - Dynamic Host Configuration Protocol options
3b9e0e2
.SH DESCRIPTION
3b9e0e2
The Dynamic Host Configuration protocol allows the client to receive
3b9e0e2
.B options
3b9e0e2
from the DHCP server describing the network configuration and various
3b9e0e2
services that are available on the network.   When configuring
3b9e0e2
.B dhcpd(8)
3b9e0e2
or
3b9e0e2
.B dhclient(8) ,
3b9e0e2
options must often be declared.   The syntax for declaring options,
3b9e0e2
and the names and formats of the options that can be declared, are
3b9e0e2
documented here.
3b9e0e2
.SH REFERENCE: OPTION STATEMENTS
3b9e0e2
.PP
3b9e0e2
DHCP \fIoption\fR statements always start with the \fIoption\fR
3b9e0e2
keyword, followed by an option name, followed by option data.  The
3b9e0e2
option names and data formats are described below.   It is not
3b9e0e2
necessary to exhaustively specify all DHCP options - only those
3b9e0e2
options which are needed by clients must be specified.
3b9e0e2
.PP
3b9e0e2
Option data comes in a variety of formats, as defined below:
3b9e0e2
.PP
3b9e0e2
The
3b9e0e2
.B ip-address
3b9e0e2
data type can be entered either as an explicit IP
3b9e0e2
address (e.g., 239.254.197.10) or as a domain name (e.g.,
3b9e0e2
haagen.isc.org).  When entering a domain name, be sure that that
3b9e0e2
domain name resolves to a single IP address.
3b9e0e2
.PP
3b9e0e2
The
3b9e0e2
.B int32
3b9e0e2
data type specifies a signed 32-bit integer.   The 
3b9e0e2
.B uint32
3b9e0e2
data type specifies an unsigned 32-bit integer.   The 
3b9e0e2
.B int16
3b9e0e2
and
3b9e0e2
.B uint16
3b9e0e2
data types specify signed and unsigned 16-bit integers.   The 
3b9e0e2
.B int8
3b9e0e2
and
3b9e0e2
.B uint8
3b9e0e2
data types specify signed and unsigned 8-bit integers.
3b9e0e2
Unsigned 8-bit integers are also sometimes referred to as octets.
3b9e0e2
.PP
3b9e0e2
The
3b9e0e2
.B text
3b9e0e2
data type specifies an NVT ASCII string, which must be
3b9e0e2
enclosed in double quotes - for example, to specify a root-path
3b9e0e2
option, the syntax would be
3b9e0e2
.nf
3b9e0e2
.sp 1
3b9e0e2
option root-path "10.0.1.4:/var/tmp/rootfs";
3b9e0e2
.fi
3b9e0e2
.PP
3b9e0e2
The
3b9e0e2
.B domain-name
3b9e0e2
data type specifies a domain name, which must not
3b9e0e2
enclosed in double quotes.   This data type is not used for any
3b9e0e2
existing DHCP options.   The domain name is stored just as if it were
3b9e0e2
a text option.
3b9e0e2
.PP
3b9e0e2
The
3b9e0e2
.B domain-list
3b9e0e2
data type specifies a list of domain names, a space between each name and
3b9e0e2
the entire string enclosed in double quotes.  These types of data are used
3b9e0e2
for the domain-search option for example, and encodes an RFC1035 compressed
3b9e0e2
DNS label list on the wire.
3b9e0e2
.PP
3b9e0e2
The
3b9e0e2
.B flag
3b9e0e2
data type specifies a boolean value.   Booleans can be either true or
3b9e0e2
false (or on or off, if that makes more sense to you).
3b9e0e2
.PP
3b9e0e2
The
3b9e0e2
.B string
3b9e0e2
data type specifies either an NVT ASCII string
3b9e0e2
enclosed in double quotes, or a series of octets specified in
3b9e0e2
hexadecimal, separated by colons.   For example:
3b9e0e2
.nf
3b9e0e2
.sp 1
3b9e0e2
  option dhcp-client-identifier "CLIENT-FOO";
3b9e0e2
or
3b9e0e2
  option dhcp-client-identifier 43:4c:49:45:54:2d:46:4f:4f;
3b9e0e2
.fi
3b9e0e2
.SH SETTING OPTION VALUES USING EXPRESSIONS
3b9e0e2
Sometimes it's helpful to be able to set the value of a DHCP option
3b9e0e2
based on some value that the client has sent.   To do this, you can
3b9e0e2
use expression evaluation.   The 
3b9e0e2
.B dhcp-eval(5)
3b9e0e2
manual page describes how to write expressions.   To assign the result
3b9e0e2
of an evaluation to an option, define the option as follows:
3b9e0e2
.nf
3b9e0e2
.sp 1
3b9e0e2
  \fBoption \fImy-option \fB= \fIexpression \fB;\fR
3b9e0e2
.fi
3b9e0e2
.PP
3b9e0e2
For example:
3b9e0e2
.nf
3b9e0e2
.sp 1
3b9e0e2
  option hostname = binary-to-ascii (16, 8, "-",
3b9e0e2
                                     substring (hardware, 1, 6));
3b9e0e2
.fi
3b9e0e2
.SH STANDARD DHCP OPTIONS
3b9e0e2
The documentation for the various options mentioned below is taken
3b9e0e2
from the latest IETF draft document on DHCP options.  Options not
3b9e0e2
listed below may not yet be implemented, but it is possible to use
3b9e0e2
such options by defining them in the configuration file.  Please see
3b9e0e2
the DEFINING NEW OPTIONS heading later in this document for more
3b9e0e2
information.
3b9e0e2
.PP
3b9e0e2
Some of the options documented here are automatically generated by
3b9e0e2
the DHCP server or by clients, and cannot be configured by the user.
3b9e0e2
The value of such an option can be used in the configuration file of
3b9e0e2
the receiving DHCP protocol agent (server or client), for example in
3b9e0e2
conditional expressions. However, the value of the option cannot be
3b9e0e2
used in the configuration file of the sending agent, because the value
3b9e0e2
is determined only \fIafter\fR the configuration file has been
3b9e0e2
processed. In the following documentation, such options will be shown
3b9e0e2
as "not user configurable"
3b9e0e2
.PP
3b9e0e2
The standard options are:
3b9e0e2
.PP
3b9e0e2
.B option \fBall-subnets-local\fR \fIflag\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option specifies whether or not the client may assume that all
3b9e0e2
subnets of the IP network to which the client is connected use the
3b9e0e2
same MTU as the subnet of that network to which the client is
3b9e0e2
directly connected.  A value of true indicates that all subnets share
3b9e0e2
the same MTU.  A value of false means that the client should assume that
3b9e0e2
some subnets of the directly connected network may have smaller MTUs.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBarp-cache-timeout\fR \fIuint32\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option specifies the timeout in seconds for ARP cache entries.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBbcms-controller-address\fR \fIip-address\fR [\fB,\fR
3b9e0e2
\fIip-address\fR... ]\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option configures a list of IPv4 addresses for use as Broadcast and
3b9e0e2
Multicast Controller Servers ("BCMS").
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBbootfile-name\fR \fItext\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option is used to identify a bootstrap file.  If supported by the
3b9e0e2
client, it should have the same effect as the \fBfilename\fR
3b9e0e2
declaration.  BOOTP clients are unlikely to support this option.  Some
3b9e0e2
DHCP clients will support it, and others actually require it.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBboot-size\fR \fIuint16\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option specifies the length in 512-octet blocks of the default
3b9e0e2
boot image for the client.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBbroadcast-address\fR \fIip-address\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option specifies the broadcast address in use on the client's
3b9e0e2
subnet.  Legal values for broadcast addresses are specified in
3b9e0e2
section 3.2.1.3 of STD 3 (RFC1122).
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBcookie-servers\fR \fIip-address\fR [\fB,\fR \fIip-address\fR...
3b9e0e2
]\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
The cookie server option specifies a list of RFC 865 cookie
3b9e0e2
servers available to the client.  Servers should be listed in order
3b9e0e2
of preference.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBdefault-ip-ttl\fR \fIuint8;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option specifies the default time-to-live that the client should
3b9e0e2
use on outgoing datagrams.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBdefault-tcp-ttl\fR \fIuint8\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option specifies the default TTL that the client should use when
3b9e0e2
sending TCP segments.  The minimum value is 1.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBdefault-url\fR \fIstring\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
The format and meaning of this option is not described in any standards
3b9e0e2
document, but is claimed to be in use by Apple Computer.  It is not known
3b9e0e2
what clients may reasonably do if supplied with this option.  Use at your
3b9e0e2
own risk.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBdhcp-client-identifier\fR \fIstring\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option can be used to specify a DHCP client identifier in a
3b9e0e2
host declaration, so that dhcpd can find the host record by matching
3b9e0e2
against the client identifier.
3b9e0e2
.PP
3b9e0e2
Please be aware that some DHCP clients, when configured with client
3b9e0e2
identifiers that are ASCII text, will prepend a zero to the ASCII
3b9e0e2
text.   So you may need to write:
3b9e0e2
.nf
3b9e0e2
3b9e0e2
	option dhcp-client-identifier "\\0foo";
3b9e0e2
3b9e0e2
rather than:
3b9e0e2
3b9e0e2
	option dhcp-client-identifier "foo";
3b9e0e2
.fi
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBdhcp-lease-time\fR \fIuint32\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option is used in a client request (DHCPDISCOVER or DHCPREQUEST)
3b9e0e2
to allow the client to request a lease time for the IP address.  In a
3b9e0e2
server reply (DHCPOFFER), a DHCP server uses this option to specify
3b9e0e2
the lease time it is willing to offer.                                    
3b9e0e2
.PP
3b9e0e2
This option is not directly user configurable in the server; refer to the
3b9e0e2
\fImax-lease-time\fR and \fIdefault-lease-time\fR server options in
3b9e0e2
.B dhcpd.conf(5).
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBdhcp-max-message-size\fR \fIuint16\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option, when sent by the client, specifies the maximum size of
3b9e0e2
any response that the server sends to the client.   When specified on
3b9e0e2
the server, if the client did not send a dhcp-max-message-size option,
3b9e0e2
the size specified on the server is used.   This works for BOOTP as
3b9e0e2
well as DHCP responses.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBdhcp-message\fR \fItext\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option is used by a DHCP server to provide an error message to a
3b9e0e2
DHCP client in a DHCPNAK message in the event of a failure. A client
3b9e0e2
may use this option in a DHCPDECLINE message to indicate why the
3b9e0e2
client declined the offered parameters.
3b9e0e2
.PP
3b9e0e2
This option is not user configurable.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBdhcp-message-type\fR \fIuint8\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option, sent by both client and server, specifies the type of DHCP
3b9e0e2
message contained in the DHCP packet. Possible values (taken directly from
3b9e0e2
RFC2132) are:
3b9e0e2
.PP
3b9e0e2
.nf
3b9e0e2
             1     DHCPDISCOVER
3b9e0e2
             2     DHCPOFFER
3b9e0e2
             3     DHCPREQUEST
3b9e0e2
             4     DHCPDECLINE
3b9e0e2
             5     DHCPACK
3b9e0e2
             6     DHCPNAK
3b9e0e2
             7     DHCPRELEASE
3b9e0e2
             8     DHCPINFORM               
3b9e0e2
.fi
3b9e0e2
.PP
3b9e0e2
This option is not user configurable.
3b9e0e2
.PP
3b9e0e2
.RE
3b9e0e2
.B option \fBdhcp-option-overload\fR \fIuint8\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option is used to indicate that the DHCP 'sname' or 'file'
3b9e0e2
fields are being overloaded by using them to carry DHCP options. A
3b9e0e2
DHCP server inserts this option if the returned parameters will
3b9e0e2
exceed the usual space allotted for options.
3b9e0e2
.PP
3b9e0e2
If this option is present, the client interprets the specified
3b9e0e2
additional fields after it concludes interpretation of the standard
3b9e0e2
option fields.
3b9e0e2
.PP
3b9e0e2
Legal values for this option are:
3b9e0e2
.PP
3b9e0e2
.nf
3b9e0e2
             1     the 'file' field is used to hold options
3b9e0e2
             2     the 'sname' field is used to hold options
3b9e0e2
             3     both fields are used to hold options                        
3b9e0e2
.fi
3b9e0e2
.PP
3b9e0e2
This option is not user configurable.
3b9e0e2
.PP
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBdhcp-parameter-request-list\fR \fIuint16\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option, when sent by the client, specifies which options the
3b9e0e2
client wishes the server to return.   Normally, in the ISC DHCP
3b9e0e2
client, this is done using the \fIrequest\fR statement.   If this
3b9e0e2
option is not specified by the client, the DHCP server will normally
3b9e0e2
return every option that is valid in scope and that fits into the
3b9e0e2
reply.   When this option is specified on the server, the server
3b9e0e2
returns the specified options.   This can be used to force a client to
3b9e0e2
take options that it hasn't requested, and it can also be used to
3b9e0e2
tailor the response of the DHCP server for clients that may need a
3b9e0e2
more limited set of options than those the server would normally
3b9e0e2
return.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBdhcp-rebinding-time\fR \fIuint32\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option specifies the number of seconds from the time a client gets
3b9e0e2
an address until the client transitions to the REBINDING state.
3b9e0e2
.PP
3b9e0e2
This option is not user configurable.
3b9e0e2
.PP
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBdhcp-renewal-time\fR \fIuint32\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option specifies the number of seconds from the time a client gets
3b9e0e2
an address until the client transitions to the RENEWING state.
3b9e0e2
.PP
3b9e0e2
This option is not user configurable.
3b9e0e2
.PP
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBdhcp-requested-address\fR \fIip-address\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option is used by the client in a DHCPDISCOVER to
3b9e0e2
request that a particular IP address be assigned.                 
3b9e0e2
.PP
3b9e0e2
This option is not user configurable.
3b9e0e2
.PP
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBdhcp-server-identifier\fR \fIip-address\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option is used in DHCPOFFER and DHCPREQUEST messages, and may
3b9e0e2
optionally be included in the DHCPACK and DHCPNAK messages.  DHCP
3b9e0e2
servers include this option in the DHCPOFFER in order to allow the
3b9e0e2
client to distinguish between lease offers.  DHCP clients use the
3b9e0e2
contents of the 'server identifier' field as the destination address
3b9e0e2
for any DHCP messages unicast to the DHCP server.  DHCP clients also
3b9e0e2
indicate which of several lease offers is being accepted by including
3b9e0e2
this option in a DHCPREQUEST message.
3b9e0e2
.PP
3b9e0e2
The value of this option is the IP address of the server.
3b9e0e2
.PP
3b9e0e2
This option is not directly user configurable. See the 
3b9e0e2
\fIserver-identifier\fR server option in
3b9e0e2
.B \fIdhcpd.conf(5).
3b9e0e2
.PP
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBdomain-name\fR \fItext\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option specifies the domain name that client should use when
3b9e0e2
resolving hostnames via the Domain Name System.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBdomain-name-servers\fR \fIip-address\fR [\fB,\fR \fIip-address\fR...
3b9e0e2
]\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
The domain-name-servers option specifies a list of Domain Name System
3b9e0e2
(STD 13, RFC 1035) name servers available to the client.  Servers
3b9e0e2
should be listed in order of preference.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBdomain-search\fR \fIstring\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
The domain-search option specifies a 'search list' of Domain Names to be
3b9e0e2
used by the client to locate not-fully-qualified domain names.  The difference
3b9e0e2
between this option and historic use of the domain-name option for the same
3b9e0e2
ends is that this option is encoded in RFC1035 compressed labels on the wire.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBextensions-path\fR \fItext\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option specifies the name of a file containing additional options
3b9e0e2
to be interpreted according to the DHCP option format as specified in
3b9e0e2
RFC2132.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBfinger-server\fR \fIip-address\fR [\fB,\fR
3b9e0e2
\fIip-address\fR... ]\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
The Finger server option specifies a list of Finger servers available
3b9e0e2
to the client.  Servers should be listed in order of preference.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBfont-servers\fR \fIip-address\fR [\fB,\fR \fIip-address\fR...
3b9e0e2
]\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option specifies a list of X Window System Font servers available
3b9e0e2
to the client. Servers should be listed in order of preference.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBhost-name\fR \fIstring\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option specifies the name of the client.  The name may or may
3b9e0e2
not be qualified with the local domain name (it is preferable to use
3b9e0e2
the domain-name option to specify the domain name).  See RFC 1035 for
3b9e0e2
character set restrictions.  This option is only honored by
3b9e0e2
.B dhclient-script(8)
3b9e0e2
if the hostname for the client machine is not set.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBieee802-3-encapsulation\fR \fIflag\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option specifies whether or not the client should use Ethernet
3b9e0e2
Version 2 (RFC 894) or IEEE 802.3 (RFC 1042) encapsulation if the
3b9e0e2
interface is an Ethernet.  A value of false indicates that the client
3b9e0e2
should use RFC 894 encapsulation.  A value of true means that the client
3b9e0e2
should use RFC 1042 encapsulation.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBien116-name-servers\fR \fIip-address\fR [\fB,\fR \fIip-address\fR...
3b9e0e2
];
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
The ien116-name-servers option specifies a list of IEN 116 name servers
3b9e0e2
available to the client.  Servers should be listed in order of
3b9e0e2
preference.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBimpress-servers\fR \fIip-address\fR [\fB,\fR \fIip-address\fR...
3b9e0e2
]\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
The impress-server option specifies a list of Imagen Impress servers
3b9e0e2
available to the client.  Servers should be listed in order of
3b9e0e2
preference.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBinterface-mtu\fR \fIuint16\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option specifies the MTU to use on this interface.   The minimum
3b9e0e2
legal value for the MTU is 68.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBip-forwarding\fR \fIflag\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option specifies whether the client should configure its IP
3b9e0e2
layer for packet forwarding.  A value of false means disable IP
3b9e0e2
forwarding, and a value of true means enable IP forwarding.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBirc-server\fR \fIip-address\fR [\fB,\fR
3b9e0e2
\fIip-address\fR... ]\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
The IRC server option specifies a list of IRC servers available
3b9e0e2
to the client.  Servers should be listed in order of preference.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBlog-servers\fR \fIip-address\fR [\fB,\fR \fIip-address\fR...
3b9e0e2
]\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
The log-server option specifies a list of MIT-LCS UDP log servers
3b9e0e2
available to the client.  Servers should be listed in order of
3b9e0e2
preference.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBlpr-servers\fR \fIip-address \fR [\fB,\fR \fIip-address\fR...
3b9e0e2
]\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
The LPR server option specifies a list of RFC 1179 line printer
3b9e0e2
servers available to the client.  Servers should be listed in order
3b9e0e2
of preference.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBmask-supplier\fR \fIflag\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option specifies whether or not the client should respond to
3b9e0e2
subnet mask requests using ICMP.  A value of false indicates that the
3b9e0e2
client should not respond.  A value of true means that the client should
3b9e0e2
respond.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBmax-dgram-reassembly\fR \fIuint16\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option specifies the maximum size datagram that the client
3b9e0e2
should be prepared to reassemble.  The minimum legal value is
3b9e0e2
576.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBmerit-dump\fR \fItext\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option specifies the path-name of a file to which the client's
3b9e0e2
core image should be dumped in the event the client crashes.  The
3b9e0e2
path is formatted as a character string consisting of characters from
3b9e0e2
the NVT ASCII character set.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBmobile-ip-home-agent\fR \fIip-address\fR [\fB,\fR \fIip-address\fR... ]\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option specifies a list of IP addresses indicating mobile IP
3b9e0e2
home agents available to the client.  Agents should be listed in
3b9e0e2
order of preference, although normally there will be only one such
3b9e0e2
agent.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBnds-context\fR \fIstring\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
The nds-context option specifies the name of the initial Netware
3b9e0e2
Directory Service for an NDS client.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBnds-servers\fR \fIip-address\fR [\fB,\fR \fIip-address\fR... ]\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
The nds-servers option specifies a list of IP addresses of NDS servers.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBnds-tree-name\fR \fIstring\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
The nds-tree-name option specifies NDS tree name that the NDS client
3b9e0e2
should use.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBnetbios-dd-server\fR \fIip-address\fR [\fB,\fR \fIip-address\fR...
3b9e0e2
]\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
The NetBIOS datagram distribution server (NBDD) option specifies a
3b9e0e2
list of RFC 1001/1002 NBDD servers listed in order of preference.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBnetbios-name-servers\fR \fIip-address\fR [\fB,\fR \fIip-address\fR...]\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
The NetBIOS name server (NBNS) option specifies a list of RFC
3b9e0e2
1001/1002 NBNS name servers listed in order of preference.   NetBIOS
3b9e0e2
Name Service is currently more commonly referred to as WINS.   WINS
3b9e0e2
servers can be specified using the netbios-name-servers option.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBnetbios-node-type\fR \fIuint8\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
The NetBIOS node type option allows NetBIOS over TCP/IP clients which
3b9e0e2
are configurable to be configured as described in RFC 1001/1002.  The
3b9e0e2
value is specified as a single octet which identifies the client type.
3b9e0e2
.PP
3b9e0e2
Possible node types are:
3b9e0e2
.PP
3b9e0e2
.TP 5
3b9e0e2
.I 1
3b9e0e2
B-node: Broadcast - no WINS
3b9e0e2
.TP
3b9e0e2
.I 2
3b9e0e2
P-node: Peer - WINS only
3b9e0e2
.TP
3b9e0e2
.I 4
3b9e0e2
M-node: Mixed - broadcast, then WINS
3b9e0e2
.TP
3b9e0e2
.I 8
3b9e0e2
H-node: Hybrid - WINS, then broadcast
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBnetbios-scope\fR \fIstring\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
The NetBIOS scope option specifies the NetBIOS over TCP/IP scope
3b9e0e2
parameter for the client as specified in RFC 1001/1002. See RFC1001,
3b9e0e2
RFC1002, and RFC1035 for character-set restrictions.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBnetinfo-server-address\fR \fIip-address\fR [\fB,\fR
3b9e0e2
\fIip-address\fR... ]\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
The \fBnetinfo-server-address\fR option has not been described in any
3b9e0e2
RFC, but has been allocated (and is claimed to be in use) by Apple
3b9e0e2
Computers.  It's hard to say if the above is the correct format, or
3b9e0e2
what clients might be expected to do if values were configured.  Use
3b9e0e2
at your own risk.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBnetinfo-server-tag\fR \fItext\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
The \fBnetinfo-server-tag\fR option has not been described in any
3b9e0e2
RFC, but has been allocated (and is claimed to be in use) by Apple
3b9e0e2
Computers.  It's hard to say if the above is the correct format,
3b9e0e2
or what clients might be expected to do if values were configured.  Use
3b9e0e2
at your own risk.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBnis-domain\fR \fItext\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option specifies the name of the client's NIS (Sun Network
3b9e0e2
Information Services) domain.  The domain is formatted as a character
3b9e0e2
string consisting of characters from the NVT ASCII character set.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBnis-servers\fR \fIip-address\fR [\fB,\fR \fIip-address\fR...
3b9e0e2
]\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option specifies a list of IP addresses indicating NIS servers
3b9e0e2
available to the client.  Servers should be listed in order of
3b9e0e2
preference.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBnisplus-domain\fR \fItext\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option specifies the name of the client's NIS+ domain.  The
3b9e0e2
domain is formatted as a character string consisting of characters
3b9e0e2
from the NVT ASCII character set.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBnisplus-servers\fR \fIip-address\fR [\fB,\fR \fIip-address\fR...
3b9e0e2
]\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option specifies a list of IP addresses indicating NIS+ servers
3b9e0e2
available to the client.  Servers should be listed in order of
3b9e0e2
preference.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBnntp-server\fR \fIip-address\fR [\fB,\fR
3b9e0e2
\fIip-address\fR... ]\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
The NNTP server option specifies a list of NNTP servesr available
3b9e0e2
to the client.  Servers should be listed in order of preference.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBnon-local-source-routing\fR \fIflag\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option specifies whether the client should configure its IP
3b9e0e2
layer to allow forwarding of datagrams with non-local source routes
3b9e0e2
(see Section 3.3.5 of [4] for a discussion of this topic).  A value
3b9e0e2
of false means disallow forwarding of such datagrams, and a value of true
3b9e0e2
means allow forwarding.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBntp-servers\fR \fIip-address\fR [\fB,\fR \fIip-address\fR...
3b9e0e2
]\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option specifies a list of IP addresses indicating NTP (RFC 1035)
3b9e0e2
servers available to the client.  Servers should be listed in order
3b9e0e2
of preference.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBnwip-domain\fR \fIstring\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
The name of the NetWare/IP domain that a NetWare/IP client should
3b9e0e2
use.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBnwip-suboptions\fR \fIstring\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
A sequence of suboptions for NetWare/IP clients - see RFC2242 for
3b9e0e2
details.   Normally this option is set by specifying specific
3b9e0e2
NetWare/IP suboptions - see the NETWARE/IP SUBOPTIONS section for more
3b9e0e2
information.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBpath-mtu-aging-timeout\fR \fIuint32\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option specifies the timeout (in seconds) to use when aging Path
3b9e0e2
MTU values discovered by the mechanism defined in RFC 1191.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBpath-mtu-plateau-table\fR \fIuint16\fR [\fB,\fR \fIuint16\fR...
3b9e0e2
]\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option specifies a table of MTU sizes to use when performing
3b9e0e2
Path MTU Discovery as defined in RFC 1191.  The table is formatted as
3b9e0e2
a list of 16-bit unsigned integers, ordered from smallest to largest.
3b9e0e2
The minimum MTU value cannot be smaller than 68.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBperform-mask-discovery\fR \fIflag\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option specifies whether or not the client should perform subnet
3b9e0e2
mask discovery using ICMP.  A value of false indicates that the client
3b9e0e2
should not perform mask discovery.  A value of true means that the
3b9e0e2
client should perform mask discovery.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.nf
3b9e0e2
.B option \fBpolicy-filter\fR \fIip-address ip-address\fR
3b9e0e2
                  [\fB,\fR \fIip-address ip-address\fR...]\fB;\fR
3b9e0e2
.RE
3b9e0e2
.fi
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option specifies policy filters for non-local source routing.
3b9e0e2
The filters consist of a list of IP addresses and masks which specify
3b9e0e2
destination/mask pairs with which to filter incoming source routes.
3b9e0e2
.PP
3b9e0e2
Any source routed datagram whose next-hop address does not match one
3b9e0e2
of the filters should be discarded by the client.
3b9e0e2
.PP
3b9e0e2
See STD 3 (RFC1122) for further information.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBpop-server\fR \fIip-address\fR [\fB,\fR \fIip-address\fR... ]\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
The POP3 server option specifies a list of POP3 servers available
3b9e0e2
to the client.  Servers should be listed in order of preference.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBresource-location-servers\fR \fIip-address\fR
3b9e0e2
                              [\fB, \fR\fIip-address\fR...]\fB;\fR
3b9e0e2
.fi
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option specifies a list of RFC 887 Resource Location
3b9e0e2
servers available to the client.  Servers should be listed in order
3b9e0e2
of preference.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBroot-path\fR \fItext\fB;\fR\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option specifies the path-name that contains the client's root
3b9e0e2
disk.  The path is formatted as a character string consisting of
3b9e0e2
characters from the NVT ASCII character set.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBrouter-discovery\fR \fIflag\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option specifies whether or not the client should solicit
3b9e0e2
routers using the Router Discovery mechanism defined in RFC 1256.
3b9e0e2
A value of false indicates that the client should not perform
3b9e0e2
router discovery.  A value of true means that the client should perform
3b9e0e2
router discovery.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBrouter-solicitation-address\fR \fIip-address\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option specifies the address to which the client should transmit
3b9e0e2
router solicitation requests.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option routers \fIip-address\fR [\fB,\fR \fIip-address\fR...
3b9e0e2
]\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
The routers option specifies a list of IP addresses for routers on the
3b9e0e2
client's subnet.  Routers should be listed in order of preference.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option slp-directory-agent \fIboolean ip-address
3b9e0e2
[\fB,\fR \fIip-address\fR... ]\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option specifies two things: the IP addresses of one or more
3b9e0e2
Service Location Protocol Directory Agents, and whether the use of
3b9e0e2
these addresses is mandatory.   If the initial boolean value is true,
3b9e0e2
the SLP agent should just use the IP addresses given.   If the value
3b9e0e2
is false, the SLP agent may additionally do active or passive
3b9e0e2
multicast discovery of SLP agents (see RFC2165 for details).
3b9e0e2
.PP
3b9e0e2
Please note that in this option and the slp-service-scope option, the
3b9e0e2
term "SLP Agent" is being used to refer to a Service Location Protocol
3b9e0e2
agent running on a machine that is being configured using the DHCP
3b9e0e2
protocol.
3b9e0e2
.PP
3b9e0e2
Also, please be aware that some companies may refer to SLP as NDS.
3b9e0e2
If you have an NDS directory agent whose address you need to
3b9e0e2
configure, the slp-directory-agent option should work.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option slp-service-scope \fIboolean text\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
The Service Location Protocol Service Scope Option specifies two
3b9e0e2
things: a list of service scopes for SLP, and whether the use of this
3b9e0e2
list is mandatory.  If the initial boolean value is true, the SLP
3b9e0e2
agent should only use the list of scopes provided in this option;
3b9e0e2
otherwise, it may use its own static configuration in preference to
3b9e0e2
the list provided in this option.
3b9e0e2
.PP
3b9e0e2
The text string should be a comma-separated list of scopes that the
3b9e0e2
SLP agent should use.   It may be omitted, in which case the SLP Agent
3b9e0e2
will use the aggregated list of scopes of all directory agents known
3b9e0e2
to the SLP agent.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBsmtp-server\fR \fIip-address\fR [\fB,\fR
3b9e0e2
\fIip-address\fR... ]\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
The SMTP server option specifies a list of SMTP servers available to
3b9e0e2
the client.  Servers should be listed in order of preference.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.nf
3b9e0e2
.B option \fBstatic-routes\fR \fIip-address ip-address\fR
3b9e0e2
                  [\fB,\fR \fIip-address ip-address\fR...]\fB;\fR
3b9e0e2
.fi
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option specifies a list of static routes that the client should
3b9e0e2
install in its routing cache.  If multiple routes to the same
3b9e0e2
destination are specified, they are listed in descending order of
3b9e0e2
priority.
3b9e0e2
.PP
3b9e0e2
The routes consist of a list of IP address pairs.  The first address
3b9e0e2
is the destination address, and the second address is the router for
3b9e0e2
the destination.
3b9e0e2
.PP
3b9e0e2
The default route (0.0.0.0) is an illegal destination for a static
3b9e0e2
route.  To specify the default route, use the
3b9e0e2
.B routers
3b9e0e2
option.   Also, please note that this option is not intended for
3b9e0e2
classless IP routing - it does not include a subnet mask.   Since
3b9e0e2
classless IP routing is now the most widely deployed routing standard,
3b9e0e2
this option is virtually useless, and is not implemented by any of the
3b9e0e2
popular DHCP clients, for example the Microsoft DHCP client.
3b9e0e2
.PP
3b9e0e2
NOTE to @PRODUCTNAME@ dhclient users:
3b9e0e2
.br
3b9e0e2
dhclient-script interprets trailing 0 octets of the target
3b9e0e2
as indicating the subnet class of the route - so for this
3b9e0e2
static-routes value:
3b9e0e2
.br
3b9e0e2
        option static-routes 172.0.0.0 172.16.2.254,
3b9e0e2
.br
3b9e0e2
                             192.168.0.0 192.168.2.254;
3b9e0e2
.br
3b9e0e2
dhclient-script will create routes:
3b9e0e2
.br
3b9e0e2
        172/8 via 172.16.2.254 dev $interface
3b9e0e2
.br
3b9e0e2
        192.168/16 via 192.168.2.254 dev $interface
3b9e0e2
.br
3b9e0e2
which slightly increases the usefulness of the static-routes option.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.nf
3b9e0e2
.B option \fBstreettalk-directory-assistance-server\fR \fIip-address\fR
3b9e0e2
                                           [\fB,\fR \fIip-address\fR...]\fB;\fR
3b9e0e2
.fi
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
The StreetTalk Directory Assistance (STDA) server option specifies a
3b9e0e2
list of STDA servers available to the client.  Servers should be
3b9e0e2
listed in order of preference.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBstreettalk-server\fR \fIip-address\fR [\fB,\fR \fIip-address\fR... ]\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
The StreetTalk server option specifies a list of StreetTalk servers
3b9e0e2
available to the client.  Servers should be listed in order of
3b9e0e2
preference.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option subnet-mask \fIip-address\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
The subnet mask option specifies the client's subnet mask as per RFC
3b9e0e2
950.  If no subnet mask option is provided anywhere in scope, as a
3b9e0e2
last resort dhcpd will use the subnet mask from the subnet declaration
3b9e0e2
for the network on which an address is being assigned.  However,
3b9e0e2
.I any
3b9e0e2
subnet-mask option declaration that is in scope for the address being
3b9e0e2
assigned will override the subnet mask specified in the subnet
3b9e0e2
declaration.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBsubnet-selection\fR \fIstring\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
Sent by the client if an address is required in a subnet other than the one
3b9e0e2
that would normally be selected (based on the relaying address of the
3b9e0e2
connected subnet the request is obtained from). See RFC3011. Note that the
3b9e0e2
option number used by this server is 118; this has not always been the
3b9e0e2
defined number, and some clients may use a different value. Use of this
3b9e0e2
option should be regarded as slightly experimental!
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
This option is not user configurable in the server.
3b9e0e2
.PP
3b9e0e2
.PP
3b9e0e2
.B option \fBswap-server\fR \fIip-address\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This specifies the IP address of the client's swap server.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBtcp-keepalive-garbage\fR \fIflag\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option specifies whether or not the client should send TCP
3b9e0e2
keepalive messages with an octet of garbage for compatibility with
3b9e0e2
older implementations.  A value of false indicates that a garbage octet
3b9e0e2
should not be sent. A value of true indicates that a garbage octet
3b9e0e2
should be sent.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBtcp-keepalive-interval\fR \fIuint32\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option specifies the interval (in seconds) that the client TCP
3b9e0e2
should wait before sending a keepalive message on a TCP connection.
3b9e0e2
The time is specified as a 32-bit unsigned integer.  A value of zero
3b9e0e2
indicates that the client should not generate keepalive messages on
3b9e0e2
connections unless specifically requested by an application.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBtftp-server-name\fR \fItext\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option is used to identify a TFTP server and, if supported by the
3b9e0e2
client, should have the same effect as the \fBserver-name\fR
3b9e0e2
declaration.   BOOTP clients are unlikely to support this option.
3b9e0e2
Some DHCP clients will support it, and others actually require it.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option time-offset \fIint32\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
The time-offset option specifies the offset of the client's subnet in
3b9e0e2
seconds from Coordinated Universal Time (UTC).
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option time-servers \fIip-address\fR [, \fIip-address\fR...
3b9e0e2
]\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
The time-server option specifies a list of RFC 868 time servers
3b9e0e2
available to the client.  Servers should be listed in order of
3b9e0e2
preference.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBtrailer-encapsulation\fR \fIflag\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option specifies whether or not the client should negotiate the
3b9e0e2
use of trailers (RFC 893 [14]) when using the ARP protocol.  A value
3b9e0e2
of false indicates that the client should not attempt to use trailers.  A
3b9e0e2
value of true means that the client should attempt to use trailers.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBuap-servers\fR \fItext\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option specifies a list of URLs, each pointing to a user
3b9e0e2
authentication service that is capable of processing authentication
3b9e0e2
requests encapsulated in the User Authentication Protocol (UAP).  UAP
3b9e0e2
servers can accept either HTTP 1.1 or SSLv3 connections.  If the list
3b9e0e2
includes a URL that does not contain a port component, the normal
3b9e0e2
default port is assumed (i.e., port 80 for http and port 443 for
3b9e0e2
https).  If the list includes a URL that does not contain a path
3b9e0e2
component, the path /uap is assumed.   If more than one URL is
3b9e0e2
specified in this list, the URLs are separated by spaces.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBuser-class\fR \fIstring\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option is used by some DHCP clients as a way for users to
3b9e0e2
specify identifying information to the client.   This can be used in a
3b9e0e2
similar way to the vendor-class-identifier option, but the value of
3b9e0e2
the option is specified by the user, not the vendor.   Most recent
3b9e0e2
DHCP clients have a way in the user interface to specify the value for
3b9e0e2
this identifier, usually as a text string.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBvendor-class-identifier\fR \fIstring\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option is used by some DHCP clients to identify the vendor
3b9e0e2
type and possibly the configuration of a DHCP client.  The information
3b9e0e2
is a string of bytes whose contents are specific to the vendor and are
3b9e0e2
not specified in a standard.   To see what vendor class identifier
3b9e0e2
clients are sending, you can write the following in your DHCP server
3b9e0e2
configuration file:
3b9e0e2
.nf
3b9e0e2
.PP
3b9e0e2
set vendor-string = option vendor-class-identifier;
3b9e0e2
.fi
3b9e0e2
.PP
3b9e0e2
This will result in all entries in the DHCP server lease database file
3b9e0e2
for clients that sent vendor-class-identifier options having a set
3b9e0e2
statement that looks something like this:
3b9e0e2
.nf
3b9e0e2
.PP
3b9e0e2
set vendor-string = "SUNW.Ultra-5_10";
3b9e0e2
.fi
3b9e0e2
.PP
3b9e0e2
The vendor-class-identifier option is normally used by the DHCP server
3b9e0e2
to determine the options that are returned in the
3b9e0e2
.B vendor-encapsulated-options
3b9e0e2
option.   Please see the VENDOR ENCAPSULATED OPTIONS section later in this
3b9e0e2
manual page for further information.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBvendor-encapsulated-options\fR \fIstring\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
The \fBvendor-encapsulated-options\fR option can contain either a
3b9e0e2
single vendor-specific value or one or more vendor-specific
3b9e0e2
suboptions.   This option is not normally specified in the DHCP server
3b9e0e2
configuration file - instead, a vendor class is defined for each
3b9e0e2
vendor, vendor class suboptions are defined, values for those
3b9e0e2
suboptions are defined, and the DHCP server makes up a response on
3b9e0e2
that basis.
3b9e0e2
.PP
3b9e0e2
Some default behaviours for well-known DHCP client vendors (currently,
3b9e0e2
the Microsoft Windows 2000 DHCP client) are configured automatically,
3b9e0e2
but otherwise this must be configured manually - see the VENDOR
3b9e0e2
ENCAPSULATED OPTIONS section later in this manual page for details.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBwww-server\fR \fIip-address\fR [\fB,\fR
3b9e0e2
\fIip-address\fR... ]\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
The WWW server option specifies a list of WWW servers available
3b9e0e2
to the client.  Servers should be listed in order of preference.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBx-display-manager\fR \fIip-address\fR [\fB,\fR \fIip-address\fR...
3b9e0e2
]\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option specifies a list of systems that are running the X Window
3b9e0e2
System Display Manager and are available to the client.  Addresses
3b9e0e2
should be listed in order of preference.
3b9e0e2
.RE
3b9e0e2
.SH RELAY AGENT INFORMATION OPTION
3b9e0e2
An IETF draft, draft-ietf-dhc-agent-options-11.txt, defines a series
3b9e0e2
of encapsulated options that a relay agent can add to a DHCP packet
3b9e0e2
when relaying it to the DHCP server.   The server can then make
3b9e0e2
address allocation decisions (or whatever other decisions it wants)
3b9e0e2
based on these options.   The server also returns these options in any
3b9e0e2
replies it sends through the relay agent, so that the relay agent can
3b9e0e2
use the information in these options for delivery or accounting
3b9e0e2
purposes.
3b9e0e2
.PP
3b9e0e2
The current draft defines two options.   To reference
3b9e0e2
these options in the dhcp server, specify the option space name,
3b9e0e2
"agent", followed by a period, followed by the option name.   It is
3b9e0e2
not normally useful to define values for these options in the server,
3b9e0e2
although it is permissible.   These options are not supported in the
3b9e0e2
client.
3b9e0e2
.PP
3b9e0e2
.B option \fBagent.circuit-id\fR \fIstring\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
The circuit-id suboption encodes an agent-local identifier of the
3b9e0e2
circuit from which a DHCP client-to-server packet was received.  It is
3b9e0e2
intended for use by agents in relaying DHCP responses back to the
3b9e0e2
proper circuit.   The format of this option is currently defined to be
3b9e0e2
vendor-dependent, and will probably remain that way, although the
3b9e0e2
current draft allows for for the possibility of standardizing the
3b9e0e2
format in the future.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBagent.remote-id\fR \fIstring\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
The remote-id suboption encodes information about the remote host end
3b9e0e2
of a circuit.   Examples of what it might contain include caller ID
3b9e0e2
information, username information, remote ATM address, cable modem ID,
3b9e0e2
and similar things.   In principal, the meaning is not well-specified,
3b9e0e2
and it should generally be assumed to be an opaque object that is
3b9e0e2
administratively guaranteed to be unique to a particular remote end of
3b9e0e2
a circuit.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBagent.DOCSIS-device-class\fR \fIuint32\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
The DOCSIS-device-class suboption is intended to convey information about
3b9e0e2
the host endpoint, hardware, and software, that either the host operating
3b9e0e2
system or the DHCP server may not otherwise be aware of (but the relay is
3b9e0e2
able to distinguish).  This is implemented as a 32-bit field (4 octets),
3b9e0e2
each bit representing a flag describing the host in one of these ways.
3b9e0e2
So far, only bit zero (being the least significant bit) is defined in
3b9e0e2
RFC3256.  If this bit is set to one, the host is considered a CPE
3b9e0e2
Controlled Cable Modem (CCCM).  All other bits are reserved.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBagent.link-selection\fR \fIip-address\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
The link-selection suboption is provided by relay agents to inform servers
3b9e0e2
what subnet the client is actually attached to.  This is useful in those
3b9e0e2
cases where the giaddr (where responses must be sent to the relay agent)
3b9e0e2
is not on the same subnet as the client.  When this option is present in
3b9e0e2
a packet from a relay agent, the DHCP server will use its contents to find
3b9e0e2
a subnet declared in configuration, and from here take one step further
3b9e0e2
backwards to any shared-network the subnet may be defined within...the
3b9e0e2
client may be given any address within that shared network, as normally
3b9e0e2
appropriate.
3b9e0e2
.RE
3b9e0e2
.SH THE CLIENT FQDN SUBOPTIONS
3b9e0e2
The Client FQDN option, currently defined in the Internet Draft
3b9e0e2
draft-ietf-dhc-fqdn-option-00.txt is not a standard yet, but is in
3b9e0e2
sufficiently wide use already that we have implemented it.   Due to
3b9e0e2
the complexity of the option format, we have implemented it as a
3b9e0e2
suboption space rather than a single option.   In general this
3b9e0e2
option should not be configured by the user - instead it should be
3b9e0e2
used as part of an automatic DNS update system.
3b9e0e2
.PP
3b9e0e2
.B option fqdn.no-client-update \fIflag\fB;
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
When the client sends this, if it is true, it means the client will not
3b9e0e2
attempt to update its A record.   When sent by the server to the client,
3b9e0e2
it means that the client \fIshould not\fR update its own A record.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option fqdn.server-update \fIflag\fB;
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
When the client sends this to the server, it is requesting that the server
3b9e0e2
update its A record.   When sent by the server, it means that the server
3b9e0e2
has updated (or is about to update) the client's A record.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option fqdn.encoded \fIflag\fB;
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
If true, this indicates that the domain name included in the option is
3b9e0e2
encoded in DNS wire format, rather than as plain ASCII text.   The client
3b9e0e2
normally sets this to false if it doesn't support DNS wire format in the
3b9e0e2
FQDN option.   The server should always send back the same value that the
3b9e0e2
client sent.   When this value is set on the configuration side, it controls
3b9e0e2
the format in which the \fIfqdn.fqdn\fR suboption is encoded.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option fqdn.rcode1 \fIflag\fB;
3b9e0e2
.PP
3b9e0e2
.B option fqdn.rcode2 \fIflag\fB;
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
These options specify the result of the updates of the A and PTR records,
3b9e0e2
respectively, and are only sent by the DHCP server to the DHCP client.
3b9e0e2
The values of these fields are those defined in the DNS protocol specification.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option fqdn.fqdn \fItext\fB;
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
Specifies the domain name that the client wishes to use.   This can be a
3b9e0e2
fully-qualified domain name, or a single label.   If there is no trailing
3b9e0e2
'.' character in the name, it is not fully-qualified, and the server will
3b9e0e2
generally update that name in some locally-defined domain.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option fqdn.hostname \fI--never set--\fB;
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option should never be set, but it can be read back using the \fBoption\fR
3b9e0e2
and \fBconfig-option\fR operators in an expression, in which case it returns
3b9e0e2
the first label in the \fBfqdn.fqdn\fR suboption - for example, if
3b9e0e2
the value of \fBfqdn.fqdn\fR is "foo.example.com.", then \fBfqdn.hostname\fR
3b9e0e2
will be "foo".
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option fqdn.domainname \fI--never set--\fB;
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This option should never be set, but it can be read back using the \fBoption\fR
3b9e0e2
and \fBconfig-option\fR operators in an expression, in which case it returns
3b9e0e2
all labels after the first label in the \fBfqdn.fqdn\fR suboption - for
3b9e0e2
example, if the value of \fBfqdn.fqdn\fR is "foo.example.com.",
3b9e0e2
then \fBfqdn.hostname\fR will be "example.com.".   If this suboption value
3b9e0e2
is not set, it means that an unqualified name was sent in the fqdn option,
3b9e0e2
or that no fqdn option was sent at all.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
If you wish to use any of these suboptions, we strongly recommend that you
3b9e0e2
refer to the Client FQDN option draft (or standard, when it becomes a
3b9e0e2
standard) - the documentation here is sketchy and incomplete in comparison,
3b9e0e2
and is just intended for reference by people who already understand the
3b9e0e2
Client FQDN option specification.
3b9e0e2
.SH THE NETWARE/IP SUBOPTIONS
3b9e0e2
RFC2242 defines a set of encapsulated options for Novell NetWare/IP
3b9e0e2
clients.  To use these options in the dhcp server, specify the option
3b9e0e2
space name, "nwip", followed by a period, followed by the option name.
3b9e0e2
The following options can be specified:
3b9e0e2
.PP
3b9e0e2
.B option \fBnwip.nsq-broadcast\fR \fIflag\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
If true, the client should use the NetWare Nearest Server Query to
3b9e0e2
locate a NetWare/IP server.   The behaviour of the Novell client if
3b9e0e2
this suboption is false, or is not present, is not specified.
3b9e0e2
.PP
3b9e0e2
.RE
3b9e0e2
.B option \fBnwip.preferred-dss\fR \fIip-address\fR [\fB,\fR \fIip-address\fR... ]\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This suboption specifies a list of up to five IP addresses, each of
3b9e0e2
which should be the IP address of a NetWare Domain SAP/RIP server
3b9e0e2
(DSS).
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBnwip.nearest-nwip-server\fR \fI\fIip-address\fR
3b9e0e2
                             [\fB,\fR \fIip-address\fR...]\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
This suboption specifies a list of up to five IP addresses, each of
3b9e0e2
which should be the IP address of a Nearest NetWare IP server.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBnwip.autoretries\fR \fIuint8\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
Specifies the number of times that a NetWare/IP client should attempt
3b9e0e2
to communicate with a given DSS server at startup.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBnwip.autoretry-secs\fR \fIuint8\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
Specifies the number of seconds that a Netware/IP client should wait
3b9e0e2
between retries when attempting to establish communications with a DSS
3b9e0e2
server at startup.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBnwip.nwip-1-1\fR \fIuint8\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
If true, the NetWare/IP client should support NetWare/IP version 1.1
3b9e0e2
compatibility.   This is only needed if the client will be contacting
3b9e0e2
Netware/IP version 1.1 servers.
3b9e0e2
.RE
3b9e0e2
.PP
3b9e0e2
.B option \fBnwip.primary-dss\fR \fIip-address\fR\fB;\fR
3b9e0e2
.RS 0.25i
3b9e0e2
.PP
3b9e0e2
Specifies the IP address of the Primary Domain SAP/RIP Service server
3b9e0e2
(DSS) for this NetWare/IP domain.   The NetWare/IP administration
3b9e0e2
utility uses this value as Primary DSS server when configuring a
3b9e0e2
secondary DSS server.
3b9e0e2
.RE
3b9e0e2
.SH DEFINING NEW OPTIONS
3b9e0e2
The Internet Systems Consortium DHCP client and server provide the
3b9e0e2
capability to define new options.   Each DHCP option has a name, a
3b9e0e2
code, and a structure.   The name is used by you to refer to the
3b9e0e2
option.   The code is a number, used by the DHCP server and client to
3b9e0e2
refer to an option.   The structure describes what the contents of an
3b9e0e2
option looks like.
3b9e0e2
.PP
3b9e0e2
To define a new option, you need to choose a name for it that is not
3b9e0e2
in use for some other option - for example, you can't use "host-name"
3b9e0e2
because the DHCP protocol already defines a host-name option, which is
3b9e0e2
documented earlier in this manual page.   If an option name doesn't
3b9e0e2
appear in this manual page, you can use it, but it's probably a good
3b9e0e2
idea to put some kind of unique string at the beginning so you can be
3b9e0e2
sure that future options don't take your name.   For example, you
3b9e0e2
might define an option, "local-host-name", feeling some confidence
3b9e0e2
that no official DHCP option name will ever start with "local".
3b9e0e2
.PP
3b9e0e2
Once you have chosen a name, you must choose a code.  All codes between
3b9e0e2
224 and 254 are reserved as 'site-local' DHCP options, so you can pick
3b9e0e2
any one of these for your site (not for your product/application).  In
3b9e0e2
RFC3942, site-local space was moved from starting at 128 to starting at
3b9e0e2
224.  In practice, some vendors have interpreted the protocol rather
3b9e0e2
loosely and have used option code values greater than 128 themselves.
3b9e0e2
There's no real way to avoid this problem, and it was thought to be
3b9e0e2
unlikely to cause too much trouble in practice.  If you come across
3b9e0e2
a vendor-documented option code in either the new or old site-local
3b9e0e2
spaces, please contact your vendor and inform them about rfc3942.
3b9e0e2
.PP
3b9e0e2
The structure of an option is simply the format in which the option
3b9e0e2
data appears.   The ISC DHCP server currently supports a few simple
3b9e0e2
types, like integers, booleans, strings and IP addresses, and it also
3b9e0e2
supports the ability to define arrays of single types or arrays of
3b9e0e2
fixed sequences of types.
3b9e0e2
.PP
3b9e0e2
New options are declared as follows:
3b9e0e2
.PP
3b9e0e2
.B option
3b9e0e2
.I new-name
3b9e0e2
.B code
3b9e0e2
.I new-code
3b9e0e2
.B =
3b9e0e2
.I definition
3b9e0e2
.B ;
3b9e0e2
.PP
3b9e0e2
The values of
3b9e0e2
.I new-name
3b9e0e2
and
3b9e0e2
.I new-code
3b9e0e2
should be the name you have chosen for the new option and the code you
3b9e0e2
have chosen.   The
3b9e0e2
.I definition
3b9e0e2
should be the definition of the structure of the option.
3b9e0e2
.PP
3b9e0e2
The following simple option type definitions are supported:
3b9e0e2
.PP
3b9e0e2
.B BOOLEAN
3b9e0e2
.PP
3b9e0e2
.B option
3b9e0e2
.I new-name
3b9e0e2
.B code
3b9e0e2
.I new-code
3b9e0e2
.B =
3b9e0e2
.B boolean
3b9e0e2
.B ;
3b9e0e2
.PP
3b9e0e2
An option of type boolean is a flag with a value of either on or off
3b9e0e2
(or true or false).   So an example use of the boolean type would be:
3b9e0e2
.nf
3b9e0e2
3b9e0e2
option use-zephyr code 180 = boolean;
3b9e0e2
option use-zephyr on;
3b9e0e2
3b9e0e2
.fi
3b9e0e2
.B INTEGER
3b9e0e2
.PP
3b9e0e2
.B option
3b9e0e2
.I new-name
3b9e0e2
.B code
3b9e0e2
.I new-code
3b9e0e2
.B =
3b9e0e2
.I sign
3b9e0e2
.B integer
3b9e0e2
.I width
3b9e0e2
.B ;
3b9e0e2
.PP
3b9e0e2
The \fIsign\fR token should either be blank, \fIunsigned\fR
3b9e0e2
or \fIsigned\fR.   The width can be either 8, 16 or 32, and refers to
3b9e0e2
the number of bits in the integer.   So for example, the following two
3b9e0e2
lines show a definition of the sql-connection-max option and its use:
3b9e0e2
.nf
3b9e0e2
3b9e0e2
option sql-connection-max code 192 = unsigned integer 16;
3b9e0e2
option sql-connection-max 1536;
3b9e0e2
3b9e0e2
.fi
3b9e0e2
.B IP-ADDRESS
3b9e0e2
.PP
3b9e0e2
.B option
3b9e0e2
.I new-name
3b9e0e2
.B code
3b9e0e2
.I new-code
3b9e0e2
.B =
3b9e0e2
.B ip-address
3b9e0e2
.B ;
3b9e0e2
.PP
3b9e0e2
An option whose structure is an IP address can be expressed either as
3b9e0e2
a domain name or as a dotted quad.  So the following is an example use
3b9e0e2
of the ip-address type:
3b9e0e2
.nf
3b9e0e2
3b9e0e2
option sql-server-address code 193 = ip-address;
3b9e0e2
option sql-server-address sql.example.com;
3b9e0e2
3b9e0e2
.fi
3b9e0e2
.PP
3b9e0e2
.B TEXT
3b9e0e2
.PP
3b9e0e2
.B option
3b9e0e2
.I new-name
3b9e0e2
.B code
3b9e0e2
.I new-code
3b9e0e2
.B =
3b9e0e2
.B text
3b9e0e2
.B ;
3b9e0e2
.PP
3b9e0e2
An option whose type is text will encode an ASCII text string.   For
3b9e0e2
example:
3b9e0e2
.nf
3b9e0e2
3b9e0e2
option sql-default-connection-name code 194 = text;
3b9e0e2
option sql-default-connection-name "PRODZA";
3b9e0e2
3b9e0e2
.fi
3b9e0e2
.PP
3b9e0e2
.B DATA STRING
3b9e0e2
.PP
3b9e0e2
.B option
3b9e0e2
.I new-name
3b9e0e2
.B code
3b9e0e2
.I new-code
3b9e0e2
.B =
3b9e0e2
.B string
3b9e0e2
.B ;
3b9e0e2
.PP
3b9e0e2
An option whose type is a data string is essentially just a collection
3b9e0e2
of bytes, and can be specified either as quoted text, like the text
3b9e0e2
type, or as a list of hexadecimal contents separated by colons whose
3b9e0e2
values must be between 0 and FF.   For example:
3b9e0e2
.nf
3b9e0e2
3b9e0e2
option sql-identification-token code 195 = string;
3b9e0e2
option sql-identification-token 17:23:19:a6:42:ea:99:7c:22;
3b9e0e2
3b9e0e2
.fi
3b9e0e2
.PP
3b9e0e2
.B ENCAPSULATION
3b9e0e2
.PP
3b9e0e2
.B option
3b9e0e2
.I new-name
3b9e0e2
.B code
3b9e0e2
.I new-code
3b9e0e2
.B =
3b9e0e2
.B encapsulate
3b9e0e2
.I identifier
3b9e0e2
.B ;
3b9e0e2
.PP
3b9e0e2
An option whose type is \fBencapsulate\fR will encapsulate the
3b9e0e2
contents of the option space specified in \fIidentifier\fR.   Examples
3b9e0e2
of encapsulated options in the DHCP protocol as it currently exists
3b9e0e2
include the vendor-encapsulated-options option, the netware-suboptions
3b9e0e2
option and the relay-agent-information option.
3b9e0e2
.nf
3b9e0e2
3b9e0e2
option space local;
3b9e0e2
option local.demo code 1 = text;
3b9e0e2
option local-encapsulation code 197 = encapsulate local;
3b9e0e2
option local.demo "demo";
3b9e0e2
3b9e0e2
.fi
3b9e0e2
.PP
3b9e0e2
.B ARRAYS
3b9e0e2
.PP
3b9e0e2
Options can contain arrays of any of the above types except for the
3b9e0e2
text and data string types, which aren't currently supported in
3b9e0e2
arrays.   An example of an array definition is as follows:
3b9e0e2
.nf
3b9e0e2
3b9e0e2
option kerberos-servers code 200 = array of ip-address;
3b9e0e2
option kerberos-servers 10.20.10.1, 10.20.11.1;
3b9e0e2
3b9e0e2
.fi
3b9e0e2
.B RECORDS
3b9e0e2
.PP
3b9e0e2
Options can also contain data structures consisting of a sequence of
3b9e0e2
data types, which is sometimes called a record type.   For example:
3b9e0e2
.nf
3b9e0e2
3b9e0e2
option contrived-001 code 201 = { boolean, integer 32, text };
3b9e0e2
option contrived-001 on 1772 "contrivance";
3b9e0e2
3b9e0e2
.fi
3b9e0e2
It's also possible to have options that are arrays of records, for
3b9e0e2
example:
3b9e0e2
.nf
3b9e0e2
3b9e0e2
option new-static-routes code 201 = array of {
3b9e0e2
	ip-address, ip-address, ip-address, integer 8 };
3b9e0e2
option static-routes
3b9e0e2
	10.0.0.0 255.255.255.0 net-0-rtr.example.com 1,
3b9e0e2
	10.0.1.0 255.255.255.0 net-1-rtr.example.com 1,
3b9e0e2
	10.2.0.0 255.255.224.0 net-2-0-rtr.example.com 3;
3b9e0e2
3b9e0e2
.fi	
3b9e0e2
.SH VENDOR ENCAPSULATED OPTIONS
3b9e0e2
The DHCP protocol defines the \fB vendor-encapsulated-options\fR
3b9e0e2
option, which allows vendors to define their own options that will be
3b9e0e2
sent encapsulated in a standard DHCP option.   The format of the
3b9e0e2
.B vendor-encapsulated-options
3b9e0e2
option is either a series of bytes whose format is not specified, or
3b9e0e2
a sequence of options, each of which consists of a single-byte
3b9e0e2
vendor-specific option code, followed by a single-byte length,
3b9e0e2
followed by as many bytes of data as are specified in the length (the
3b9e0e2
length does not include itself or the option code).
3b9e0e2
.PP
3b9e0e2
The value of this option can be set in one of two ways.   The first
3b9e0e2
way is to simply specify the data directly, using a text string or a
3b9e0e2
colon-separated list of hexadecimal values.   For example:
3b9e0e2
.PP
3b9e0e2
.nf
3b9e0e2
option vendor-encapsulated-options
3b9e0e2
    2:4:AC:11:41:1:
3b9e0e2
    3:12:73:75:6e:64:68:63:70:2d:73:65:72:76:65:72:31:37:2d:31:
3b9e0e2
    4:12:2f:65:78:70:6f:72:74:2f:72:6f:6f:74:2f:69:38:36:70:63;
3b9e0e2
.fi
3b9e0e2
.PP
3b9e0e2
The second way of setting the value of this option is to have the DHCP
3b9e0e2
server generate a vendor-specific option buffer.   To do this, you
3b9e0e2
must do four things: define an option space, define some options in
3b9e0e2
that option space, provide values for them, and specify that that 
3b9e0e2
option space should be used to generate the
3b9e0e2
.B vendor-encapsulated-options
3b9e0e2
option.
3b9e0e2
.PP
3b9e0e2
To define a new option space in which vendor options can be stored,
3b9e0e2
use the \fRoption space\fP statement:
3b9e0e2
.PP
3b9e0e2
.B option
3b9e0e2
.B space
3b9e0e2
.I name
3b9e0e2
.B [ [ code width
3b9e0e2
.I number
3b9e0e2
.B ] [ length width
3b9e0e2
.I number
3b9e0e2
.B ] [ hash size
3b9e0e2
.I number
3b9e0e2
.B ] ] ;
3b9e0e2
.PP
3b9e0e2
Where the numbers following \fBcode width\fR, \fBlength width\fR,
3b9e0e2
and \fBhash size\fR respectively identify the number of bytes used to
3b9e0e2
describe option codes, option lengths, and the size in buckets of the
3b9e0e2
hash tables to hold options in this space.
3b9e0e2
.PP
3b9e0e2
The code and length widths are used in DHCP protocol - you must configure
3b9e0e2
these numbers to match the applicable option space you are configuring.
3b9e0e2
They each default to 1.  Valid values for code widths are 1, 2 or 4.
3b9e0e2
Valid values for length widths are 1 or 2.
3b9e0e2
.PP
3b9e0e2
The hash size defaults depend upon the \fBcode width\fR selected, and
3b9e0e2
may be 254 or 1009.  Valid values range between 1 and 65535.  Note
3b9e0e2
that the higher you configure this value, the more memory will be used.  It
3b9e0e2
is considered good practice to configure a value that is slightly larger
3b9e0e2
than the estimated number of options you plan to configure within the
3b9e0e2
space.  Due to limitations in previous versions of ISC DHCP (up to and
3b9e0e2
including DHCP 3.0.*), this value was fixed at 9973.
3b9e0e2
.PP
3b9e0e2
The name can then be used in option definitions, as described earlier in
3b9e0e2
this document.   For example:
3b9e0e2
.nf
3b9e0e2
3b9e0e2
option space SUNW code width 1 length width 1 hash size 3;
3b9e0e2
option SUNW.server-address code 2 = ip-address;
3b9e0e2
option SUNW.server-name code 3 = text;
3b9e0e2
option SUNW.root-path code 4 = text;
3b9e0e2
3b9e0e2
.fi
3b9e0e2
Once you have defined an option space and the format of some options,
3b9e0e2
you can set up scopes that define values for those options, and you
3b9e0e2
can say when to use them.   For example, suppose you want to handle
3b9e0e2
two different classes of clients.   Using the option space definition
3b9e0e2
shown in the previous example, you can send different option values to
3b9e0e2
different clients based on the vendor-class-identifier option that the
3b9e0e2
clients send, as follows:
3b9e0e2
.PP
3b9e0e2
.nf
3b9e0e2
class "vendor-classes" {
3b9e0e2
  match option vendor-class-identifier;
3b9e0e2
}
3b9e0e2
3b9e0e2
option SUNW.server-address 172.17.65.1;
3b9e0e2
option SUNW.server-name "sundhcp-server17-1";
3b9e0e2
3b9e0e2
subclass "vendor-classes" "SUNW.Ultra-5_10" {
3b9e0e2
  vendor-option-space SUNW;
3b9e0e2
  option SUNW.root-path "/export/root/sparc";
3b9e0e2
}
3b9e0e2
3b9e0e2
subclass "vendor-classes" "SUNW.i86pc" {
3b9e0e2
  vendor-option-space SUNW;
3b9e0e2
  option SUNW.root-path "/export/root/i86pc";
3b9e0e2
}
3b9e0e2
.fi
3b9e0e2
.PP
3b9e0e2
As you can see in the preceding example, regular scoping rules apply,
3b9e0e2
so you can define values that are global in the global scope, and only
3b9e0e2
define values that are specific to a particular class in the local
3b9e0e2
scope.   The \fBvendor-option-space\fR declaration tells the DHCP
3b9e0e2
server to use options in the SUNW option space to construct the
3b9e0e2
.B vendor-encapsulated-options
3b9e0e2
option.
3b9e0e2
.SH SEE ALSO
3b9e0e2
dhcpd.conf(5), dhcpd.leases(5), dhclient.conf(5), dhcp-eval(5), dhcpd(8),
3b9e0e2
dhclient(8), RFC2132, RFC2131, draft-ietf-dhc-agent-options-??.txt.
3b9e0e2
.SH AUTHOR
3b9e0e2
The Internet Systems Consortium DHCP Distribution was written by Ted
3b9e0e2
Lemon under a contract with Vixie Labs.  Funding for
3b9e0e2
this project was provided through Internet Systems Consortium.
3b9e0e2
Information about Internet Systems Consortium can be found at
3b9e0e2
.B http://www.isc.org.