www.pudn.com > dhcp-2.0pl5.zip > dhcp-options.cat5, change:2000-07-01,size:36432b
ddddhhhhccccppppdddd----ooooppppttttiiiioooonnnnssss((((5555)))) ddddhhhhccccppppdddd----ooooppppttttiiiioooonnnnssss((((5555))))
NNNNAAAAMMMMEEEE
dhcp-options - Dynamic Host Configuration Protocol options
DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
The Dynamic Host Configuration protocol allows the client to
receive ooooppppttttiiiioooonnnnssss from the DHCP server describing the network
configuration and various services that are available on the
network. When configuring ddddhhhhccccppppdddd((((8888)))) or ddddhhhhcccclllliiiieeeennnntttt((((8888)))) ,,,,
options must often be declared. The syntax for declaring
options, and the names and formats of the options that can
be declared, are documented here.
RRRREEEEFFFFEEEERRRREEEENNNNCCCCEEEE:::: OOOOPPPPTTTTIIIIOOOONNNN SSSSTTTTAAAATTTTEEEEMMMMEEEENNNNTTTTSSSS
DHCP _o_p_t_i_o_n statements always start with the _o_p_t_i_o_n keyword,
followed by an option name, followed by option data. The
option names and data formats are described below. It is
not necessary to exhaustively specify all DHCP options -
only those options which are needed by clients must be
specified.
Option data comes in a variety of formats, as defined below:
The iiiipppp----aaaaddddddddrrrreeeessssssss data type can be entered either as an
explicit IP address (e.g., 239.254.197.10) or as a domain
name (e.g., haagen.isc.org). When entering a domain name,
be sure that that domain name resolves to a single IP
address.
The iiiinnnntttt33332222 data type specifies a signed 32-bit integer. The
uuuuiiiinnnntttt33332222 data type specifies an unsigned 32-bit integer. The
iiiinnnntttt11116666 and uuuuiiiinnnntttt11116666 data types specify signed and unsigned 16-
bit integers. The iiiinnnntttt8888 and uuuuiiiinnnntttt8888 data types specify signed
and unsigned 8-bit integers. Unsigned 8-bit integers are
also sometimes referred to as octets.
The ssssttttrrrriiiinnnngggg data type specifies an NVT ASCII string, which
must be enclosed in double quotes - for example, to specify
a domain-name option, the syntax would be
option domain-name "isc.org";
The ffffllllaaaagggg data type specifies a boolean value. Booleans can
be either true or false (or on or off, if that makes more
sense to you).
The ddddaaaattttaaaa----ssssttttrrrriiiinnnngggg data type specifies either an NVT ASCII
string enclosed in double quotes, or a series of octets
specified in hexadecimal, seperated by colons. For
example:
option dhcp-client-identifier "CLIENT-FOO";
or
Page 1 (printed 11/17/99)
ddddhhhhccccppppdddd----ooooppppttttiiiioooonnnnssss((((5555)))) ddddhhhhccccppppdddd----ooooppppttttiiiioooonnnnssss((((5555))))
option dhcp-client-identifier 43:4c:49:45:54:2d:46:4f:4f;
The documentation for the various options mentioned below is
taken from the latest IETF draft document on DHCP options.
Options which are not listed by name may be defined by the
name option-_n_n_n, where _n_n_n _i_s _t_h_e _d_e_c_i_m_a_l _n_u_m_b_e_r _o_f _t_h_e
_o_p_t_i_o_n _c_o_d_e. _T_h_e_s_e _o_p_t_i_o_n_s _m_a_y _b_e _f_o_l_l_o_w_e_d _e_i_t_h_e_r _b_y _a
_s_t_r_i_n_g, _e_n_c_l_o_s_e_d _i_n _q_u_o_t_e_s, _o_r _b_y _a _s_e_r_i_e_s _o_f _o_c_t_e_t_s,
_e_x_p_r_e_s_s_e_d _a_s _t_w_o-_d_i_g_i_t _h_e_x_a_d_e_c_i_m_a_l _n_u_m_b_e_r_s _s_e_p_e_r_a_t_e_d _b_y
_c_o_l_o_n_s. _F_o_r _e_x_a_m_p_l_e:
option option-133 "my-option-133-text";
option option-129 1:54:c9:2b:47;
Because dhcpd does not know the format of these undefined
option codes, no checking is done to ensure the correctness
of the entered data.
The standard options are:
ooooppppttttiiiioooonnnn ssssuuuubbbbnnnneeeetttt----mmmmaaaasssskkkk _i_p-_a_d_d_r_e_s_s;;;;
The subnet mask option specifies the client's subnet mask
as per RFC 950. If no subnet mask option is provided
anywhere in scope, as a last resort dhcpd will use the
subnet mask from the subnet declaration for the network on
which 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 subnet declaration.
ooooppppttttiiiioooonnnn ttttiiiimmmmeeee----ooooffffffffsssseeeetttt _i_n_t_3_2;;;;
The time-offset option specifies the offset of the
client's subnet in seconds from Coordinated Universal Time
(UTC).
ooooppppttttiiiioooonnnn rrrroooouuuutttteeeerrrrssss _i_p-_a_d_d_r_e_s_s [,,,, _i_p-_a_d_d_r_e_s_s... ];;;;
The routers option specifies a list of IP addresses for
routers on the client's subnet. Routers should be listed
in order of preference.
ooooppppttttiiiioooonnnn ttttiiiimmmmeeee----sssseeeerrrrvvvveeeerrrrssss _i_p-_a_d_d_r_e_s_s [, _i_p-_a_d_d_r_e_s_s... ];;;;
The time-server option specifies a list of RFC 868 time
servers available to the client. Servers should be listed
in order of preference.
ooooppppttttiiiioooonnnn iiiieeeennnn111111116666----nnnnaaaammmmeeee----sssseeeerrrrvvvveeeerrrrssss _i_p-_a_d_d_r_e_s_s [,,,, _i_p-_a_d_d_r_e_s_s... ];
The ien116-name-servers option specifies a list of IEN 116
Page 2 (printed 11/17/99)
ddddhhhhccccppppdddd----ooooppppttttiiiioooonnnnssss((((5555)))) ddddhhhhccccppppdddd----ooooppppttttiiiioooonnnnssss((((5555))))
name servers available to the client. Servers should be
listed in order of preference.
ooooppppttttiiiioooonnnn ddddoooommmmaaaaiiiinnnn----nnnnaaaammmmeeee----sssseeeerrrrvvvveeeerrrrssss _i_p-_a_d_d_r_e_s_s [,,,, _i_p-_a_d_d_r_e_s_s... ];;;;
The domain-name-servers option specifies a list of Domain
Name System (STD 13, RFC 1035) name servers available to
the client. Servers should be listed in order of
preference.
ooooppppttttiiiioooonnnn lllloooogggg----sssseeeerrrrvvvveeeerrrrssss _i_p-_a_d_d_r_e_s_s [,,,, _i_p-_a_d_d_r_e_s_s... ];;;;
The log-server option specifies a list of MIT-LCS UDP log
servers available to the client. Servers should be listed
in order of preference.
ooooppppttttiiiioooonnnn ccccooooooookkkkiiiieeee----sssseeeerrrrvvvveeeerrrrssss _i_p-_a_d_d_r_e_s_s [,,,, _i_p-_a_d_d_r_e_s_s... ];;;;
The cookie server option specifies a list of RFC 865
cookie servers available to the client. Servers should be
listed in order of preference.
ooooppppttttiiiioooonnnn llllpppprrrr----sssseeeerrrrvvvveeeerrrrssss _i_p-_a_d_d_r_e_s_s [,,,, _i_p-_a_d_d_r_e_s_s... ];;;;
The LPR server option specifies a list of RFC 1179 line
printer servers available to the client. Servers should
be listed in order of preference.
ooooppppttttiiiioooonnnn iiiimmmmpppprrrreeeessssssss----sssseeeerrrrvvvveeeerrrrssss _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
Impress servers available to the client. Servers should
be listed in order of preference.
ooooppppttttiiiioooonnnn rrrreeeessssoooouuuurrrrcccceeee----llllooooccccaaaattttiiiioooonnnn----sssseeeerrrrvvvveeeerrrrssss _i_p-_a_d_d_r_e_s_s [,,,, _i_p-_a_d_d_r_e_s_s...
];;;;
This option specifies a list of RFC 887 Resource Location
servers available to the client. Servers should be listed
in order of preference.
ooooppppttttiiiioooonnnn hhhhoooosssstttt----nnnnaaaammmmeeee _s_t_r_i_n_g;;;;
This option specifies the name of the client. The name
may or may not be qualified with the local domain name (it
is preferable to use the domain-name option to specify the
domain name). See RFC 1035 for character set
restrictions.
ooooppppttttiiiioooonnnn bbbbooooooootttt----ssssiiiizzzzeeee _u_i_n_t_1_6;;;;
This option specifies the length in 512-octet blocks of
Page 3 (printed 11/17/99)
ddddhhhhccccppppdddd----ooooppppttttiiiioooonnnnssss((((5555)))) ddddhhhhccccppppdddd----ooooppppttttiiiioooonnnnssss((((5555))))
the default boot image for the client.
ooooppppttttiiiioooonnnn mmmmeeeerrrriiiitttt----dddduuuummmmpppp _s_t_r_i_n_g;;;;
This option specifies the path-name of a file to which the
client's core image should be dumped in the event the
client crashes. The path is formatted as a character
string consisting of characters from the NVT ASCII
character set.
ooooppppttttiiiioooonnnn ddddoooommmmaaaaiiiinnnn----nnnnaaaammmmeeee _s_t_r_i_n_g;;;;
This option specifies the domain name that client should
use when resolving hostnames via the Domain Name System.
ooooppppttttiiiioooonnnn sssswwwwaaaapppp----sssseeeerrrrvvvveeeerrrr _i_p-_a_d_d_r_e_s_s;;;;
This specifies the IP address of the client's swap server.
ooooppppttttiiiioooonnnn rrrrooooooootttt----ppppaaaatttthhhh _s_t_r_i_n_g;;;;
This option specifies the path-name that contains the
client's root disk. The path is formatted as a character
string consisting of characters from the NVT ASCII
character set.
ooooppppttttiiiioooonnnn iiiipppp----ffffoooorrrrwwwwaaaarrrrddddiiiinnnngggg _f_l_a_g;;;;
This option specifies whether the client should configure
its IP layer for packet forwarding. A value of 0 means
disable IP forwarding, and a value of 1 means enable IP
forwarding.
ooooppppttttiiiioooonnnn nnnnoooonnnn----llllooooccccaaaallll----ssssoooouuuurrrrcccceeee----rrrroooouuuuttttiiiinnnngggg _f_l_a_g;;;;
This option specifies whether the client should configure
its IP layer to allow forwarding of datagrams with non-
local source routes (see Section 3.3.5 of [4] for a
discussion of this topic). A value of 0 means disallow
forwarding of such datagrams, and a value of 1 means allow
forwarding.
ooooppppttttiiiioooonnnn ppppoooolllliiiiccccyyyy----ffffiiiilllltttteeeerrrr _i_p-_a_d_d_r_e_s_s _i_p-_a_d_d_r_e_s_s [,,,, _i_p-_a_d_d_r_e_s_s ];;;;
This option specifies policy filters for non-local source
routing. The filters consist of a list of IP addresses
and masks which specify destination/mask pairs with which
to filter incoming source routes.
Any source routed datagram whose next-hop address does not
match one of the filters should be discarded by the
client.
Page 4 (printed 11/17/99)
ddddhhhhccccppppdddd----ooooppppttttiiiioooonnnnssss((((5555)))) ddddhhhhccccppppdddd----ooooppppttttiiiioooonnnnssss((((5555))))
See STD 3 (RFC1122) for further information.
ooooppppttttiiiioooonnnn mmmmaaaaxxxx----ddddggggrrrraaaammmm----rrrreeeeaaaasssssssseeeemmmmbbbbllllyyyy _u_i_n_t_1_6;;;;
This option specifies the maximum size datagram that the
client should be prepared to reassemble. The minimum
value legal value is 576.
ooooppppttttiiiioooonnnn ddddeeeeffffaaaauuuulllltttt----iiiipppp----ttttttttllll _u_i_n_t_8;
This option specifies the default time-to-live that the
client should use on outgoing datagrams.
ooooppppttttiiiioooonnnn ppppaaaatttthhhh----mmmmttttuuuu----aaaaggggiiiinnnngggg----ttttiiiimmmmeeeeoooouuuutttt _u_i_n_t_3_2;;;;
This option specifies the timeout (in seconds) to use when
aging Path MTU values discovered by the mechanism defined
in RFC 1191.
ooooppppttttiiiioooonnnn ppppaaaatttthhhh----mmmmttttuuuu----ppppllllaaaatttteeeeaaaauuuu----ttttaaaabbbblllleeee _u_i_n_t_1_6 [,,,, _u_i_n_t_1_6... ];;;;
This option specifies a table of MTU sizes to use when
performing Path MTU Discovery as defined in RFC 1191. The
table is formatted as a list of 16-bit unsigned integers,
ordered from smallest to largest. The minimum MTU value
cannot be smaller than 68.
ooooppppttttiiiioooonnnn iiiinnnntttteeeerrrrffffaaaacccceeee----mmmmttttuuuu _u_i_n_t_1_6;;;;
This option specifies the MTU to use on this interface.
The minimum legal value for the MTU is 68.
ooooppppttttiiiioooonnnn aaaallllllll----ssssuuuubbbbnnnneeeettttssss----llllooooccccaaaallll _f_l_a_g;;;;
This option specifies whether or not the client may assume
that all subnets of the IP network to which the client is
connected use the same MTU as the subnet of that network
to which the client is directly connected. A value of 1
indicates that all subnets share the same MTU. A value of
0 means that the client should assume that some subnets of
the directly connected network may have smaller MTUs.
ooooppppttttiiiioooonnnn bbbbrrrrooooaaaaddddccccaaaasssstttt----aaaaddddddddrrrreeeessssssss _i_p-_a_d_d_r_e_s_s;;;;
This option specifies the broadcast address in use on the
client's subnet. Legal values for broadcast addresses are
specified in section 3.2.1.3 of STD 3 (RFC1122).
ooooppppttttiiiioooonnnn ppppeeeerrrrffffoooorrrrmmmm----mmmmaaaasssskkkk----ddddiiiissssccccoooovvvveeeerrrryyyy _f_l_a_g;;;;
This option specifies whether or not the client should
perform subnet mask discovery using ICMP. A value of 0
Page 5 (printed 11/17/99)
ddddhhhhccccppppdddd----ooooppppttttiiiioooonnnnssss((((5555)))) ddddhhhhccccppppdddd----ooooppppttttiiiioooonnnnssss((((5555))))
indicates that the client should not perform mask
discovery. A value of 1 means that the client should
perform mask discovery.
ooooppppttttiiiioooonnnn mmmmaaaasssskkkk----ssssuuuupppppppplllliiiieeeerrrr _f_l_a_g;;;;
This option specifies whether or not the client should
respond to subnet mask requests using ICMP. A value of 0
indicates that the client should not respond. A value of
1 means that the client should respond.
ooooppppttttiiiioooonnnn rrrroooouuuutttteeeerrrr----ddddiiiissssccccoooovvvveeeerrrryyyy _f_l_a_g;;;;
This option specifies whether or not the client should
solicit routers using the Router Discovery mechanism
defined in RFC 1256. A value of 0 indicates that the
client should not perform router discovery. A value of 1
means that the client should perform router discovery.
ooooppppttttiiiioooonnnn rrrroooouuuutttteeeerrrr----ssssoooolllliiiicccciiiittttaaaattttiiiioooonnnn----aaaaddddddddrrrreeeessssssss _i_p-_a_d_d_r_e_s_s;;;;
This option specifies the address to which the client
should transmit router solicitation requests.
ooooppppttttiiiioooonnnn ssssttttaaaattttiiiicccc----rrrroooouuuutttteeeessss _i_p-_a_d_d_r_e_s_s _i_p-_a_d_d_r_e_s_s [,,,, _i_p-_a_d_d_r_e_s_s ];;;;
This option specifies a list of static routes that the
client should install in its routing cache. If multiple
routes to the same destination are specified, they are
listed in descending order of priority.
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.
The default route (0.0.0.0) is an illegal destination for
a static route. To specify the default route, use the
rrrroooouuuutttteeeerrrrssss option.
ooooppppttttiiiioooonnnn ttttrrrraaaaiiiilllleeeerrrr----eeeennnnccccaaaappppssssuuuullllaaaattttiiiioooonnnn _f_l_a_g;;;;
This option specifies whether or not the client should
negotiate the use of trailers (RFC 893 [14]) when using
the ARP protocol. A value of 0 indicates that the client
should not attempt to use trailers. A value of 1 means
that the client should attempt to use trailers.
ooooppppttttiiiioooonnnn aaaarrrrpppp----ccccaaaacccchhhheeee----ttttiiiimmmmeeeeoooouuuutttt _u_i_n_t_3_2;;;;
This option specifies the timeout in seconds for ARP cache
entries.
Page 6 (printed 11/17/99)
ddddhhhhccccppppdddd----ooooppppttttiiiioooonnnnssss((((5555)))) ddddhhhhccccppppdddd----ooooppppttttiiiioooonnnnssss((((5555))))
ooooppppttttiiiioooonnnn iiiieeeeeeeeeeee888800002222----3333----eeeennnnccccaaaappppssssuuuullllaaaattttiiiioooonnnn _f_l_a_g;;;;
This option specifies whether or not the client should use
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
encapsulation. A value of 1 means that the client should
use RFC 1042 encapsulation.
ooooppppttttiiiioooonnnn ddddeeeeffffaaaauuuulllltttt----ttttccccpppp----ttttttttllll _u_i_n_t_8;;;;
This option specifies the default TTL that the client
should use when sending TCP segments. The minimum value
is 1.
ooooppppttttiiiioooonnnn ttttccccpppp----kkkkeeeeeeeeppppaaaalllliiiivvvveeee----iiiinnnntttteeeerrrrvvvvaaaallll _u_i_n_t_3_2;;;;
This option specifies the interval (in seconds) that the
client TCP should wait before sending a keepalive message
on a TCP connection. The time is specified as a 32-bit
unsigned integer. A value of zero indicates that the
client should not generate keepalive messages on
connections unless specifically requested by an
application.
ooooppppttttiiiioooonnnn ttttccccpppp----kkkkeeeeeeeeppppaaaalllliiiivvvveeee----ggggaaaarrrrbbbbaaaaggggeeee _f_l_a_g;;;;
This option specifies the whether or not the client should
send TCP keepalive messages with a octet of garbage for
compatibility with older implementations. A value of 0
indicates that a garbage octet should not be sent. A value
of 1 indicates that a garbage octet should be sent.
ooooppppttttiiiioooonnnn nnnniiiissss----ddddoooommmmaaaaiiiinnnn _s_t_r_i_n_g;;;;
This option specifies the name of the client's NIS (Sun
Network Information Services) domain. The domain is
formatted as a character string consisting of characters
from the NVT ASCII character set.
ooooppppttttiiiioooonnnn nnnniiiissss----sssseeeerrrrvvvveeeerrrrssss _i_p-_a_d_d_r_e_s_s [,,,, _i_p-_a_d_d_r_e_s_s... ];;;;
This option specifies a list of IP addresses indicating
NIS servers available to the client. Servers should be
listed in order of preference.
ooooppppttttiiiioooonnnn nnnnttttpppp----sssseeeerrrrvvvveeeerrrrssss _i_p-_a_d_d_r_e_s_s [,,,, _i_p-_a_d_d_r_e_s_s... ];;;;
This option specifies a list of IP addresses indicating
NTP (RFC 1035) servers available to the client. Servers
should be listed in order of preference.
Page 7 (printed 11/17/99)
ddddhhhhccccppppdddd----ooooppppttttiiiioooonnnnssss((((5555)))) ddddhhhhccccppppdddd----ooooppppttttiiiioooonnnnssss((((5555))))
ooooppppttttiiiioooonnnn nnnneeeettttbbbbiiiioooossss----nnnnaaaammmmeeee----sssseeeerrrrvvvveeeerrrrssss _i_p-_a_d_d_r_e_s_s [,,,, _i_p-_a_d_d_r_e_s_s... ];;;;
The NetBIOS name server (NBNS) option specifies a list of
RFC 1001/1002 NBNS name servers listed in order of
preference. NetBIOS Name Service is currently more
commonly referred to as WINS. WINS servers can be
specified using the netbios-name-servers option.
ooooppppttttiiiioooonnnn nnnneeeettttbbbbiiiioooossss----dddddddd----sssseeeerrrrvvvveeeerrrr _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
specifies a list of RFC 1001/1002 NBDD servers listed in
order of preference.
ooooppppttttiiiioooonnnn nnnneeeettttbbbbiiiioooossss----nnnnooooddddeeee----ttttyyyyppppeeee _u_i_n_t_8;;;;
The NetBIOS node type option allows NetBIOS over TCP/IP
clients which are configurable to be configured as
described in RFC 1001/1002. The value is specified as a
single octet which identifies the client type.
Possible node types are:
_1 B-node: Broadcast - no WINS
_2 P-node: Peer - WINS only.
_4 M-node: Mixed - broadcast, then WINS
_8 H-node: Hybrid - WINS, then broadcast
ooooppppttttiiiioooonnnn nnnneeeettttbbbbiiiioooossss----ssssccccooooppppeeee _s_t_r_i_n_g;;;;
The NetBIOS scope option specifies the NetBIOS over TCP/IP
scope parameter for the client as specified in RFC
1001/1002. See RFC1001, RFC1002, and RFC1035 for
character-set restrictions.
ooooppppttttiiiioooonnnn ffffoooonnnntttt----sssseeeerrrrvvvveeeerrrrssss _i_p-_a_d_d_r_e_s_s [,,,, _i_p-_a_d_d_r_e_s_s... ];;;;
This option specifies a list of X Window System Font
servers available to the client. Servers should be listed
in order of preference.
ooooppppttttiiiioooonnnn xxxx----ddddiiiissssppppllllaaaayyyy----mmmmaaaannnnaaaaggggeeeerrrr _i_p-_a_d_d_r_e_s_s [,,,, _i_p-_a_d_d_r_e_s_s... ];;;;
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
preference.
ooooppppttttiiiioooonnnn ddddhhhhccccpppp----cccclllliiiieeeennnntttt----iiiiddddeeeennnnttttiiiiffffiiiieeeerrrr _d_a_t_a-_s_t_r_i_n_g;;;;
Page 8 (printed 11/17/99)
ddddhhhhccccppppdddd----ooooppppttttiiiioooonnnnssss((((5555)))) ddddhhhhccccppppdddd----ooooppppttttiiiioooonnnnssss((((5555))))
This option can be used to specify the a DHCP client
identifier in a host declaration, so that dhcpd can find
the host record by matching against the client identifier.
ooooppppttttiiiioooonnnn nnnniiiisssspppplllluuuussss----ddddoooommmmaaaaiiiinnnn _s_t_r_i_n_g;;;;
This option specifies the name of the client's NIS+
domain. The domain is formatted as a character string
consisting of characters from the NVT ASCII character set.
ooooppppttttiiiioooonnnn nnnniiiisssspppplllluuuussss----sssseeeerrrrvvvveeeerrrrssss _i_p-_a_d_d_r_e_s_s [,,,, _i_p-_a_d_d_r_e_s_s... ];;;;
This option specifies a list of IP addresses indicating
NIS+ servers available to the client. Servers should be
listed in order of preference.
ooooppppttttiiiioooonnnn ttttffffttttpppp----sssseeeerrrrvvvveeeerrrr----nnnnaaaammmmeeee _s_t_r_i_n_g;;;;
This option is used to identify a TFTP server and, if
supported by the client, should have the same effect as
the sssseeeerrrrvvvveeeerrrr----nnnnaaaammmmeeee declaration. BOOTP clients are unlikely
to support this option. Some DHCP clients will support
it, and others actually require it.
ooooppppttttiiiioooonnnn bbbboooooooottttffffiiiilllleeee----nnnnaaaammmmeeee _s_t_r_i_n_g;;;;
This option is used to identify a bootstrap file. If
supported by the client, it should have the same effect as
the ffffiiiilllleeeennnnaaaammmmeeee declaration. BOOTP clients are unlikely to
support this option. Some DHCP clients will support it,
and others actually require it.
ooooppppttttiiiioooonnnn mmmmoooobbbbiiiilllleeee----iiiipppp----hhhhoooommmmeeee----aaaaggggeeeennnntttt _i_p-_a_d_d_r_e_s_s [,,,, _i_p-_a_d_d_r_e_s_s... ];;;;
This option specifies a list of IP addresses indicating
mobile IP home agents available to the client. Agents
should be listed in order of preference, although normally
there will be only one such agent.
ooooppppttttiiiioooonnnn ssssmmmmttttpppp----sssseeeerrrrvvvveeeerrrr _i_p-_a_d_d_r_e_s_s [,,,, _i_p-_a_d_d_r_e_s_s... ];;;;
The SMTP server option specifies a list of SMTP servers
available to the client. Servers should be listed in
order of preference.
ooooppppttttiiiioooonnnn ppppoooopppp----sssseeeerrrrvvvveeeerrrr _i_p-_a_d_d_r_e_s_s [,,,, _i_p-_a_d_d_r_e_s_s... ];;;;
The POP3 server option specifies a list of POP3 available
to the client. Servers should be listed in order of
preference.
ooooppppttttiiiioooonnnn nnnnnnnnttttpppp----sssseeeerrrrvvvveeeerrrr _i_p-_a_d_d_r_e_s_s [,,,, _i_p-_a_d_d_r_e_s_s... ];;;;
The NNTP server option specifies a list of NNTP available
Page 9 (printed 11/17/99)
ddddhhhhccccppppdddd----ooooppppttttiiiioooonnnnssss((((5555)))) ddddhhhhccccppppdddd----ooooppppttttiiiioooonnnnssss((((5555))))
to the client. Servers should be listed in order of
preference.
ooooppppttttiiiioooonnnn wwwwwwwwwwww----sssseeeerrrrvvvveeeerrrr _i_p-_a_d_d_r_e_s_s [,,,, _i_p-_a_d_d_r_e_s_s... ];;;;
The WWW server option specifies a list of WWW available to
the client. Servers should be listed in order of
preference.
ooooppppttttiiiioooonnnn ffffiiiinnnnggggeeeerrrr----sssseeeerrrrvvvveeeerrrr _i_p-_a_d_d_r_e_s_s [,,,, _i_p-_a_d_d_r_e_s_s... ];;;;
The Finger server option specifies a list of Finger
available to the client. Servers should be listed in
order of preference.
ooooppppttttiiiioooonnnn iiiirrrrcccc----sssseeeerrrrvvvveeeerrrr _i_p-_a_d_d_r_e_s_s [,,,, _i_p-_a_d_d_r_e_s_s... ];;;;
The IRC server option specifies a list of IRC available to
the client. Servers should be listed in order of
preference.
ooooppppttttiiiioooonnnn ssssttttrrrreeeeeeeettttttttaaaallllkkkk----sssseeeerrrrvvvveeeerrrr _i_p-_a_d_d_r_e_s_s [,,,, _i_p-_a_d_d_r_e_s_s... ];;;;
The StreetTalk server option specifies a list of
StreetTalk servers available to the client. Servers
should be listed in order of preference.
ooooppppttttiiiioooonnnn ssssttttrrrreeeeeeeettttaaaallllkkkk----ddddiiiirrrreeeeccccttttoooorrrryyyy----aaaassssssssiiiissssttttaaaannnncccceeee----sssseeeerrrrvvvveeeerrrr _i_p-_a_d_d_r_e_s_s [,,,,
_i_p-_a_d_d_r_e_s_s... ];;;;
The StreetTalk Directory Assistance (STDA) server option
specifies a list of STDA servers available to the client.
Servers should be listed in order of preference.
SSSSEEEEEEEE AAAALLLLSSSSOOOO
dhcpd.conf(5), dhcpd.leases(5), dhclient.conf(5), dhcpd(8),
dhclient(8), RFC2132, RFC2131.
AAAAUUUUTTTTHHHHOOOORRRR
ddddhhhhccccppppdddd((((8888)))) was written by Ted Lemon <mellon@vix.com> under a
contract with Vixie Labs. Funding for this project was
provided by the Internet Software Corporation. Information
about the Internet Software Consortium can be found at
hhhhttttttttpppp::::////////wwwwwwwwwwww....iiiisssscccc....oooorrrrgggg////iiiisssscccc....
Page 10 (printed 11/17/99)