summaryrefslogtreecommitdiff
path: root/common
diff options
context:
space:
mode:
authorTed Lemon <source@isc.org>1999-02-05 20:55:39 +0000
committerTed Lemon <source@isc.org>1999-02-05 20:55:39 +0000
commit1ea23fc80f4273582cb336dd7edaac8fb28695c5 (patch)
tree81a971c396d4e693f5c2ca2188e1a5b165d4ab75 /common
parentc04e384455f859b636ca5ca006e4a6bfeee8bcaf (diff)
downloadisc-dhcp-1ea23fc80f4273582cb336dd7edaac8fb28695c5.tar.gz
Diffstat (limited to 'common')
-rw-r--r--common/dhcp-options.cat5572
1 files changed, 319 insertions, 253 deletions
diff --git a/common/dhcp-options.cat5 b/common/dhcp-options.cat5
index b941ad0d..8d3833db 100644
--- a/common/dhcp-options.cat5
+++ b/common/dhcp-options.cat5
@@ -88,42 +88,42 @@ dhcpd-options(5) dhcpd-options(5)
The standard options are:
- ooppttiioonn ssuubbnneett--mmaasskk _i_p_-_a_d_d_r_e_s_s;;
+ ooppttiioonn ssuubbnneett--mmaasskk _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 any­
- where 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.
+ The subnet mask option specifies the client's subnet
+ mask as per RFC 950. If no subnet mask option is pro­
+ vided 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. How­
+ ever, _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.
- ooppttiioonn ttiimmee--ooffffsseett _i_n_t_3_2;;
+ ooppttiioonn ttiimmee--ooffffsseett _i_n_t_3_2;;
- The time-offset option specifies the offset of the
- client's subnet in seconds from Coordinated Universal Time
- (UTC).
+ The time-offset option specifies the offset of the
+ client's subnet in seconds from Coordinated Universal
+ Time (UTC).
- ooppttiioonn rroouutteerrss _i_p_-_a_d_d_r_e_s_s [,, _i_p_-_a_d_d_r_e_s_s ... ];;
+ ooppttiioonn rroouutteerrss _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.
+ The routers option specifies a list of IP addresses for
+ routers on the client's subnet. Routers should be
+ listed in order of preference.
- ooppttiioonn ttiimmee--sseerrvveerrss _i_p_-_a_d_d_r_e_s_s _[_, _i_p_-_a_d_d_r_e_s_s ... ];;
+ ooppttiioonn ttiimmee--sseerrvveerrss _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.
+ The time-server option specifies a list of RFC 868 time
+ servers available to the client. Servers should be
+ listed in order of preference.
- ooppttiioonn iieenn111166--nnaammee--sseerrvveerrss _i_p_-_a_d_d_r_e_s_s [,, _i_p_-_a_d_d_r_e_s_s ...
- ];
+ ooppttiioonn iieenn111166--nnaammee--sseerrvveerrss _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
- name servers available to the client. Servers should be
- listed in order of preference.
+ The ien116-name-servers option specifies a list of IEN
+ 116 name servers available to the client. Servers
+ should be listed in order of preference.
+ ooppttiioonn ddoommaaiinn--nnaammee--sseerrvveerrss _i_p_-_a_d_d_r_e_s_s [,, _i_p_-_a_d_d_r_e_s_s... ];;
@@ -136,60 +136,60 @@ dhcpd-options(5) dhcpd-options(5)
dhcpd-options(5) dhcpd-options(5)
- ooppttiioonn ddoommaaiinn--nnaammee--sseerrvveerrss _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 prefer­
- ence.
+ 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.
- ooppttiioonn lloogg--sseerrvveerrss _i_p_-_a_d_d_r_e_s_s [,, _i_p_-_a_d_d_r_e_s_s ... ];;
+ ooppttiioonn lloogg--sseerrvveerrss _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.
+ 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.
- ooppttiioonn ccooookkiiee--sseerrvveerrss _i_p_-_a_d_d_r_e_s_s [,, _i_p_-_a_d_d_r_e_s_s ... ];;
+ ooppttiioonn ccooookkiiee--sseerrvveerrss _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.
+ The cookie server option specifies a list of RFC 865
+ cookie servers available to the client. Servers should
+ be listed in order of preference.
- ooppttiioonn llpprr--sseerrvveerrss _i_p_-_a_d_d_r_e_s_s [,, _i_p_-_a_d_d_r_e_s_s ... ];;
+ ooppttiioonn llpprr--sseerrvveerrss _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.
+ 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.
- ooppttiioonn iimmpprreessss--sseerrvveerrss _i_p_-_a_d_d_r_e_s_s [,, _i_p_-_a_d_d_r_e_s_s ... ];;
+ ooppttiioonn iimmpprreessss--sseerrvveerrss _i_p_-_a_d_d_r_e_s_s [,, _i_p_-_a_d_d_r_e_s_s... ];;
- The impress-server option specifies a list of Imagen
- Impress servers available to the client. Servers should
- be listed in order of preference.
+ The impress-server option specifies a list of Imagen
+ Impress servers available to the client. Servers
+ should be listed in order of preference.
- ooppttiioonn rreessoouurrccee--llooccaattiioonn--sseerrvveerrss _i_p_-_a_d_d_r_e_s_s [,, _i_p_-_a_d_d_r_e_s_s
- ... ];;
+ ooppttiioonn rreessoouurrccee--llooccaattiioonn--sseerrvveerrss _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.
+ This option specifies a list of RFC 887 Resource Loca­
+ tion servers available to the client. Servers should
+ be listed in order of preference.
- ooppttiioonn hhoosstt--nnaammee _s_t_r_i_n_g;;
+ ooppttiioonn hhoosstt--nnaammee _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 restric­
- tions.
+ 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.
- ooppttiioonn bboooott--ssiizzee _u_i_n_t_1_6;;
+ ooppttiioonn bboooott--ssiizzee _u_i_n_t_1_6;;
- This option specifies the length in 512-octet blocks of
- the default boot image for the client.
+ This option specifies the length in 512-octet blocks of
+ the default boot image for the client.
- ooppttiioonn mmeerriitt--dduummpp _s_t_r_i_n_g;;
+ ooppttiioonn mmeerriitt--dduummpp _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
@@ -202,60 +202,60 @@ dhcpd-options(5) dhcpd-options(5)
dhcpd-options(5) dhcpd-options(5)
- 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 charac­
- ter set.
+ character string consisting of characters from the NVT
+ ASCII character set.
- ooppttiioonn ddoommaaiinn--nnaammee _s_t_r_i_n_g;;
+ ooppttiioonn ddoommaaiinn--nnaammee _s_t_r_i_n_g;;
- This option specifies the domain name that client should
- use when resolving hostnames via the Domain Name System.
+ This option specifies the domain name that client
+ should use when resolving hostnames via the Domain Name
+ System.
- ooppttiioonn sswwaapp--sseerrvveerr _i_p_-_a_d_d_r_e_s_s;;
+ ooppttiioonn sswwaapp--sseerrvveerr _i_p_-_a_d_d_r_e_s_s;;
- This specifies the IP address of the client's swap server.
+ This specifies the IP address of the client's swap
+ server.
- ooppttiioonn rroooott--ppaatthh _s_t_r_i_n_g;;
+ ooppttiioonn rroooott--ppaatthh _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 charac­
- ter set.
+ This option specifies the path-name that contains the
+ client's root disk. The path is formatted as a charac­
+ ter string consisting of characters from the NVT ASCII
+ character set.
- ooppttiioonn iipp--ffoorrwwaarrddiinngg _f_l_a_g;;
+ ooppttiioonn iipp--ffoorrwwaarrddiinngg _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.
+ This option specifies whether the client should config­
+ ure its IP layer for packet forwarding. A value of 0
+ means disable IP forwarding, and a value of 1 means
+ enable IP forwarding.
- ooppttiioonn nnoonn--llooccaall--ssoouurrccee--rroouuttiinngg _f_l_a_g;;
+ ooppttiioonn nnoonn--llooccaall--ssoouurrccee--rroouuttiinngg _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 dis­
- cussion of this topic). A value of 0 means disallow for­
- warding of such datagrams, and a value of 1 means allow
- forwarding.
+ This option specifies whether the client should config­
+ ure 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.
- ooppttiioonn ppoolliiccyy--ffiilltteerr _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
- _i_p_-_a_d_d_r_e_s_s ... ];;
+ ooppttiioonn ppoolliiccyy--ffiilltteerr _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
+ _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.
+ 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.
+ Any source routed datagram whose next-hop address does
+ not match one of the filters should be discarded by the
+ client.
- See STD 3 (RFC1122) for further information.
+ See STD 3 (RFC1122) for further information.
- ooppttiioonn mmaaxx--ddggrraamm--rreeaasssseemmbbllyy _u_i_n_t_1_6;;
+ ooppttiioonn mmaaxx--ddggrraamm--rreeaasssseemmbbllyy _u_i_n_t_1_6;;
+ This option specifies the maximum size datagram that
@@ -268,60 +268,60 @@ dhcpd-options(5) dhcpd-options(5)
dhcpd-options(5) dhcpd-options(5)
- This option specifies the maximum size datagram that the
- client should be prepared to reassemble. The minimum
- value legal value is 576.
-
- ooppttiioonn ddeeffaauulltt--iipp--ttttll _u_i_n_t_8_;
+ the client should be prepared to reassemble. The mini­
+ mum value legal value is 576.
- This option specifies the default time-to-live that the
- client should use on outgoing datagrams.
+ ooppttiioonn ddeeffaauulltt--iipp--ttttll _u_i_n_t_8_;
- ooppttiioonn ppaatthh--mmttuu--aaggiinngg--ttiimmeeoouutt _u_i_n_t_3_2;;
+ This option specifies the default time-to-live that the
+ client should use on outgoing datagrams.
- This option specifies the timeout (in seconds) to use when
- aging Path MTU values discovered by the mechanism defined
- in RFC 1191.
+ ooppttiioonn ppaatthh--mmttuu--aaggiinngg--ttiimmeeoouutt _u_i_n_t_3_2;;
- ooppttiioonn ppaatthh--mmttuu--ppllaatteeaauu--ttaabbllee _u_i_n_t_1_6 [,, _u_i_n_t_1_6 ... ];;
+ This option specifies the timeout (in seconds) to use
+ when aging Path MTU values discovered by the mechanism
+ defined in RFC 1191.
- 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.
+ ooppttiioonn ppaatthh--mmttuu--ppllaatteeaauu--ttaabbllee _u_i_n_t_1_6 [,, _u_i_n_t_1_6... ];;
- ooppttiioonn iinntteerrffaaccee--mmttuu _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 mini­
+ mum MTU value cannot be smaller than 68.
- This option specifies the MTU to use on this interface.
- The minimum legal value for the MTU is 68.
+ ooppttiioonn iinntteerrffaaccee--mmttuu _u_i_n_t_1_6;;
- ooppttiioonn aallll--ssuubbnneettss--llooccaall _f_l_a_g;;
+ This option specifies the MTU to use on this interface.
+ The minimum legal value for the MTU is 68.
- 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.
+ ooppttiioonn aallll--ssuubbnneettss--llooccaall _f_l_a_g;;
- ooppttiioonn bbrrooaaddccaasstt--aaddddrreessss _i_p_-_a_d_d_r_e_s_s;;
+ 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.
- 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).
+ ooppttiioonn bbrrooaaddccaasstt--aaddddrreessss _i_p_-_a_d_d_r_e_s_s;;
- ooppttiioonn ppeerrffoorrmm--mmaasskk--ddiissccoovveerryy _f_l_a_g;;
+ 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).
- This option specifies whether or not the client should
- perform subnet mask discovery using ICMP. A value of 0
- indicates that the client should not perform mask discov­
- ery. A value of 1 means that the client should perform
- mask discovery.
+ ooppttiioonn ppeerrffoorrmm--mmaasskk--ddiissccoovveerryy _f_l_a_g;;
- ooppttiioonn mmaasskk--ssuupppplliieerr _f_l_a_g;;
+ This option specifies whether or not the client should
+ perform subnet mask discovery using ICMP. A value of 0
+ indicates that the client should not perform mask dis­
+ covery. A value of 1 means that the client should per­
+ form mask discovery.
+ ooppttiioonn mmaasskk--ssuupppplliieerr _f_l_a_g;;
@@ -334,60 +334,60 @@ dhcpd-options(5) dhcpd-options(5)
dhcpd-options(5) dhcpd-options(5)
- 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.
+ 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.
- ooppttiioonn rroouutteerr--ddiissccoovveerryy _f_l_a_g;;
+ ooppttiioonn rroouutteerr--ddiissccoovveerryy _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.
+ 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 discov­
+ ery.
- ooppttiioonn rroouutteerr--ssoolliicciittaattiioonn--aaddddrreessss _i_p_-_a_d_d_r_e_s_s;;
+ ooppttiioonn rroouutteerr--ssoolliicciittaattiioonn--aaddddrreessss _i_p_-_a_d_d_r_e_s_s;;
- This option specifies the address to which the client
- should transmit router solicitation requests.
+ This option specifies the address to which the client
+ should transmit router solicitation requests.
- ooppttiioonn ssttaattiicc--rroouutteess _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
- _i_p_-_a_d_d_r_e_s_s ... ];;
+ ooppttiioonn ssttaattiicc--rroouutteess _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
+ _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.
+ This option specifies a list of static routes that the
+ client should install in its routing cache. If multi­
+ ple 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 routes consist of a list of IP address pairs. The
+ first address is the destination address, and the sec­
+ ond 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
- rroouutteerrss option.
+ The default route (0.0.0.0) is an illegal destination
+ for a static route. To specify the default route, use
+ the rroouutteerrss option.
- ooppttiioonn ttrraaiilleerr--eennccaappssuullaattiioonn _f_l_a_g;;
+ ooppttiioonn ttrraaiilleerr--eennccaappssuullaattiioonn _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.
+ 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.
- ooppttiioonn aarrpp--ccaacchhee--ttiimmeeoouutt _u_i_n_t_3_2;;
+ ooppttiioonn aarrpp--ccaacchhee--ttiimmeeoouutt _u_i_n_t_3_2;;
- This option specifies the timeout in seconds for ARP cache
- entries.
+ This option specifies the timeout in seconds for ARP
+ cache entries.
- ooppttiioonn iieeeeee880022--33--eennccaappssuullaattiioonn _f_l_a_g;;
+ ooppttiioonn iieeeeee880022--33--eennccaappssuullaattiioonn _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 encapsula­
- tion. A value of 1 means that the client should use RFC
+ 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
@@ -400,60 +400,60 @@ dhcpd-options(5) dhcpd-options(5)
dhcpd-options(5) dhcpd-options(5)
- 1042 encapsulation.
+ encapsulation. A value of 1 means that the client
+ should use RFC 1042 encapsulation.
- ooppttiioonn ddeeffaauulltt--ttccpp--ttttll _u_i_n_t_8;;
+ ooppttiioonn ddeeffaauulltt--ttccpp--ttttll _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.
+ This option specifies the default TTL that the client
+ should use when sending TCP segments. The minimum
+ value is 1.
- ooppttiioonn ttccpp--kkeeeeppaalliivvee--iinntteerrvvaall _u_i_n_t_3_2;;
+ ooppttiioonn ttccpp--kkeeeeppaalliivvee--iinntteerrvvaall _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 connec­
- tions unless specifically requested by an application.
+ 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.
- ooppttiioonn ttccpp--kkeeeeppaalliivvee--ggaarrbbaaggee _f_l_a_g;;
+ ooppttiioonn ttccpp--kkeeeeppaalliivvee--ggaarrbbaaggee _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.
+ 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.
- ooppttiioonn nniiss--ddoommaaiinn _s_t_r_i_n_g;;
+ ooppttiioonn nniiss--ddoommaaiinn _s_t_r_i_n_g;;
- This option specifies the name of the client's NIS (Sun
- Network Information Services) domain. The domain is for­
- matted as a character string consisting of characters from
- the NVT ASCII character set.
+ 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 charac­
+ ters from the NVT ASCII character set.
- ooppttiioonn nniiss--sseerrvveerrss _i_p_-_a_d_d_r_e_s_s [,, _i_p_-_a_d_d_r_e_s_s ... ];;
+ ooppttiioonn nniiss--sseerrvveerrss _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.
+ This option specifies a list of IP addresses indicating
+ NIS servers available to the client. Servers should be
+ listed in order of preference.
- ooppttiioonn nnttpp--sseerrvveerrss _i_p_-_a_d_d_r_e_s_s [,, _i_p_-_a_d_d_r_e_s_s ... ];;
+ ooppttiioonn nnttpp--sseerrvveerrss _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.
+ 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.
- ooppttiioonn nneettbbiiooss--nnaammee--sseerrvveerrss _i_p_-_a_d_d_r_e_s_s [,, _i_p_-_a_d_d_r_e_s_s ...
+ ooppttiioonn nneettbbiiooss--nnaammee--sseerrvveerrss _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 prefer­
- ence.
-
- ooppttiioonn nneettbbiiooss--dddd--sseerrvveerr _i_p_-_a_d_d_r_e_s_s [,, _i_p_-_a_d_d_r_e_s_s ... ];;
-
- The NetBIOS datagram distribution server (NBDD) option
+ 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
@@ -466,54 +466,81 @@ dhcpd-options(5) dhcpd-options(5)
dhcpd-options(5) dhcpd-options(5)
- specifies a list of RFC 1001/1002 NBDD servers listed in
- order of preference.
+ specified using the netbios-name-servers option.
+
+ ooppttiioonn nneettbbiiooss--dddd--sseerrvveerr _i_p_-_a_d_d_r_e_s_s [,, _i_p_-_a_d_d_r_e_s_s... ];;
+
+ The NetBIOS datagram distribution server (NBDD) option
+ specifies a list of RFC 1001/1002 NBDD servers listed
+ in order of preference.
+
+ ooppttiioonn nneettbbiiooss--nnooddee--ttyyppee _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
+
+ ooppttiioonn nneettbbiiooss--ssccooppee _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.
- ooppttiioonn nneettbbiiooss--nnooddee--ttyyppee _u_i_n_t_8;;
+ ooppttiioonn ffoonntt--sseerrvveerrss _i_p_-_a_d_d_r_e_s_s [,, _i_p_-_a_d_d_r_e_s_s... ];;
- 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. A value of
- 1 corresponds to a NetBIOS B-node; a value of 2 corre­
- sponds to a P-node; a value of 4 corresponds to an M-node;
- a value of 8 corresponds to an H-node.
+ This option specifies a list of X Window System Font
+ servers available to the client. Servers should be
+ listed in order of preference.
- ooppttiioonn nneettbbiiooss--ssccooppee _s_t_r_i_n_g;;
+ ooppttiioonn xx--ddiissppllaayy--mmaannaaggeerr _i_p_-_a_d_d_r_e_s_s [,, _i_p_-_a_d_d_r_e_s_s... ];;
- 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 charac­
- ter-set restrictions.
+ This option specifies a list of systems that are run­
+ ning the X Window System Display Manager and are avail­
+ able to the client. Addresses should be listed in
+ order of preference.
- ooppttiioonn ffoonntt--sseerrvveerrss _i_p_-_a_d_d_r_e_s_s [,, _i_p_-_a_d_d_r_e_s_s ... ];;
+ ooppttiioonn ddhhccpp--cclliieenntt--iiddeennttiiffiieerr _d_a_t_a_-_s_t_r_i_n_g;;
- This option specifies a list of X Window System Font
- servers available to the client. Servers should be listed
- in order of preference.
+ 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.
- ooppttiioonn xx--ddiissppllaayy--mmaannaaggeerr _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 pref­
- erence.
- ooppttiioonn ddhhccpp--cclliieenntt--iiddeennttiiffiieerr _d_a_t_a_-_s_t_r_i_n_g;;
- This option can be used to specify the a DHCP client iden­
- tifier in a host declaration, so that dhcpd can find the
- host record by matching against the client identifier.
+
+ 8
+
+
+
+
+
+dhcpd-options(5) dhcpd-options(5)
+
SSEEEE AALLSSOO
- dhcpd.conf(5), dhcpd.leases(5), dhclient.conf(5),
+ dhcpd.conf(5), dhcpd.leases(5), dhclient.conf(5),
dhcpd(8), dhclient(8), RFC2132, RFC2131.
AAUUTTHHOORR
ddhhccppdd((88)) 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. Informa­
- tion about the Internet Software Consortium can be found
+ contract with Vixie Labs. Funding for this project was
+ provided by the Internet Software Corporation. Informa­
+ tion about the Internet Software Consortium can be found
at hhttttpp::////wwwwww..iisscc..oorrgg//iisscc..
@@ -523,6 +550,45 @@ AAUUTTHHOORR
- 8
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ 9