--- /dev/null
+
+
+
+dhcpd-options(5) dhcpd-options(5)
+
+
+N\bNA\bAM\bME\bE
+ dhcp-options - Dynamic Host Configuration Protocol options
+
+D\bDE\bES\bSC\bCR\bRI\bIP\bPT\bTI\bIO\bON\bN
+ The Dynamic Host Configuration protocol allows the client
+ to receive o\bop\bpt\bti\bio\bon\bns\bs from the DHCP server describing the
+ network configuration and various services that are avail
+ able on the network. When configuring d\bdh\bhc\bcp\bpd\bd(\b(8\b8)\b) or
+ d\bdh\bhc\bcl\bli\bie\ben\bnt\bt(\b(8\b8)\b) ,\b, 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.
+
+R\bRE\bEF\bFE\bER\bRE\bEN\bNC\bCE\bE:\b: O\bOP\bPT\bTI\bIO\bON\bN S\bST\bTA\bAT\bTE\bEM\bME\bEN\bNT\bTS\bS
+ DHCP _\bo_\bp_\bt_\bi_\bo_\bn statements always start with the _\bo_\bp_\bt_\bi_\bo_\bn key
+ word, 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 i\bip\bp-\b-a\bad\bdd\bdr\bre\bes\bss\bs 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 i\bin\bnt\bt3\b32\b2 data type specifies a signed 32-bit integer.
+ The u\bui\bin\bnt\bt3\b32\b2 data type specifies an unsigned 32-bit integer.
+ The i\bin\bnt\bt1\b16\b6 and u\bui\bin\bnt\bt1\b16\b6 data types specify signed and
+ unsigned 16-bit integers. The i\bin\bnt\bt8\b8 and u\bui\bin\bnt\bt8\b8 data types
+ specify signed and unsigned 8-bit integers. Unsigned
+ 8-bit integers are also sometimes referred to as octets.
+
+ The s\bst\btr\bri\bin\bng\bg data type specifies an NVT ASCII string, which
+ must be enclosed in double quotes - for example, to spec
+ ify a domain-name option, the syntax would be
+
+ option domain-name "isc.org";
+
+ The f\bfl\bla\bag\bg 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 d\bda\bat\bta\ba-\b-s\bst\btr\bri\bin\bng\bg data type specifies either an NVT ASCII
+ string enclosed in double quotes, or a series of octets
+ specified in hexadecimal, seperated by colons. For exam
+ ple:
+
+ option client-identifier "CLIENT-FOO";
+ or
+ option client-identifier 43:4c:49:45:54:2d:46:4f:4f;
+
+
+
+ 1
+
+
+
+
+
+dhcpd-options(5) dhcpd-options(5)
+
+
+ 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-_\bn_\bn_\bn, where _\bn_\bn_\bn _\bi_\bs _\bt_\bh_\be _\bd_\be_\bc_\bi_\bm_\ba_\bl
+ _\bn_\bu_\bm_\bb_\be_\br _\bo_\bf _\bt_\bh_\be _\bo_\bp_\bt_\bi_\bo_\bn _\bc_\bo_\bd_\be_\b. _\bT_\bh_\be_\bs_\be _\bo_\bp_\bt_\bi_\bo_\bn_\bs _\bm_\ba_\by _\bb_\be _\bf_\bo_\bl_\bl_\bo_\bw_\be_\bd
+ _\be_\bi_\bt_\bh_\be_\br _\bb_\by _\ba _\bs_\bt_\br_\bi_\bn_\bg_\b, _\be_\bn_\bc_\bl_\bo_\bs_\be_\bd _\bi_\bn _\bq_\bu_\bo_\bt_\be_\bs_\b, _\bo_\br _\bb_\by _\ba _\bs_\be_\br_\bi_\be_\bs _\bo_\bf
+ _\bo_\bc_\bt_\be_\bt_\bs_\b, _\be_\bx_\bp_\br_\be_\bs_\bs_\be_\bd _\ba_\bs _\bt_\bw_\bo_\b-_\bd_\bi_\bg_\bi_\bt _\bh_\be_\bx_\ba_\bd_\be_\bc_\bi_\bm_\ba_\bl _\bn_\bu_\bm_\bb_\be_\br_\bs _\bs_\be_\bp_\be_\br_\b
+ _\ba_\bt_\be_\bd _\bb_\by _\bc_\bo_\bl_\bo_\bn_\bs_\b. _\bF_\bo_\br _\be_\bx_\ba_\bm_\bp_\bl_\be_\b:
+
+ 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 correct
+ ness of the entered data.
+
+ The standard options are:
+
+ o\bop\bpt\bti\bio\bon\bn s\bsu\bub\bbn\bne\bet\bt-\b-m\bma\bas\bsk\bk _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs;\b;
+
+ 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, _\ba_\bn_\by subnet-mask
+ option declaration that is in scope for the address being
+ assigned will override the subnet mask specified in the
+ subnet declaration.
+
+ o\bop\bpt\bti\bio\bon\bn t\bti\bim\bme\be-\b-o\bof\bff\bfs\bse\bet\bt _\bi_\bn_\bt_\b3_\b2;\b;
+
+ The time-offset option specifies the offset of the
+ client's subnet in seconds from Coordinated Universal Time
+ (UTC).
+
+ o\bop\bpt\bti\bio\bon\bn r\bro\bou\but\bte\ber\brs\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs [,\b, _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs ... ];\b;
+
+ The routers option specifies a list of IP addresses for
+ routers on the client's subnet. Routers should be listed
+ in order of preference.
+
+ o\bop\bpt\bti\bio\bon\bn t\bti\bim\bme\be-\b-s\bse\ber\brv\bve\ber\brs\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\b[_\b, _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs ... ];\b;
+
+ The time-server option specifies a list of RFC 868 time
+ servers available to the client. Servers should be listed
+ in order of preference.
+
+ o\bop\bpt\bti\bio\bon\bn i\bie\ben\bn1\b11\b16\b6-\b-n\bna\bam\bme\be-\b-s\bse\ber\brv\bve\ber\brs\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs [,\b, _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs ...
+ ];
+
+ 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.
+
+
+
+
+ 2
+
+
+
+
+
+dhcpd-options(5) dhcpd-options(5)
+
+
+ o\bop\bpt\bti\bio\bon\bn d\bdo\bom\bma\bai\bin\bn-\b-n\bna\bam\bme\be-\b-s\bse\ber\brv\bve\ber\brs\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs [,\b, _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs ...
+ ];\b;
+
+ 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.
+
+ o\bop\bpt\bti\bio\bon\bn l\blo\bog\bg-\b-s\bse\ber\brv\bve\ber\brs\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs [,\b, _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs ... ];\b;
+
+ 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.
+
+ o\bop\bpt\bti\bio\bon\bn c\bco\boo\bok\bki\bie\be-\b-s\bse\ber\brv\bve\ber\brs\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs [,\b, _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs ... ];\b;
+
+ The cookie server option specifies a list of RFC 865
+ cookie servers available to the client. Servers should be
+ listed in order of preference.
+
+ o\bop\bpt\bti\bio\bon\bn l\blp\bpr\br-\b-s\bse\ber\brv\bve\ber\brs\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs [,\b, _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs ... ];\b;
+
+ 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.
+
+ o\bop\bpt\bti\bio\bon\bn i\bim\bmp\bpr\bre\bes\bss\bs-\b-s\bse\ber\brv\bve\ber\brs\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs [,\b, _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs ... ];\b;
+
+ The impress-server option specifies a list of Imagen
+ Impress servers available to the client. Servers should
+ be listed in order of preference.
+
+ o\bop\bpt\bti\bio\bon\bn r\bre\bes\bso\bou\bur\brc\bce\be-\b-l\blo\boc\bca\bat\bti\bio\bon\bn-\b-s\bse\ber\brv\bve\ber\brs\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs [,\b, _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+ ... ];\b;
+
+ This option specifies a list of RFC 887 Resource Location
+ servers available to the client. Servers should be listed
+ in order of preference.
+
+ o\bop\bpt\bti\bio\bon\bn h\bho\bos\bst\bt-\b-n\bna\bam\bme\be _\bs_\bt_\br_\bi_\bn_\bg;\b;
+
+ 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.
+
+ o\bop\bpt\bti\bio\bon\bn b\bbo\boo\bot\bt-\b-s\bsi\biz\bze\be _\bu_\bi_\bn_\bt_\b1_\b6;\b;
+
+ This option specifies the length in 512-octet blocks of
+ the default boot image for the client.
+
+ o\bop\bpt\bti\bio\bon\bn m\bme\ber\bri\bit\bt-\b-d\bdu\bum\bmp\bp _\bs_\bt_\br_\bi_\bn_\bg;\b;
+
+
+
+
+ 3
+
+
+
+
+
+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.
+
+ o\bop\bpt\bti\bio\bon\bn d\bdo\bom\bma\bai\bin\bn-\b-n\bna\bam\bme\be _\bs_\bt_\br_\bi_\bn_\bg;\b;
+
+ This option specifies the domain name that client should
+ use when resolving hostnames via the Domain Name System.
+
+ o\bop\bpt\bti\bio\bon\bn s\bsw\bwa\bap\bp-\b-s\bse\ber\brv\bve\ber\br _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs;\b;
+
+ This specifies the IP address of the client's swap server.
+
+ o\bop\bpt\bti\bio\bon\bn r\bro\boo\bot\bt-\b-p\bpa\bat\bth\bh _\bs_\bt_\br_\bi_\bn_\bg;\b;
+
+ 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.
+
+ o\bop\bpt\bti\bio\bon\bn i\bip\bp-\b-f\bfo\bor\brw\bwa\bar\brd\bdi\bin\bng\bg _\bf_\bl_\ba_\bg;\b;
+
+ 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.
+
+ o\bop\bpt\bti\bio\bon\bn n\bno\bon\bn-\b-l\blo\boc\bca\bal\bl-\b-s\bso\bou\bur\brc\bce\be-\b-r\bro\bou\but\bti\bin\bng\bg _\bf_\bl_\ba_\bg;\b;
+
+ 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.
+
+ o\bop\bpt\bti\bio\bon\bn p\bpo\bol\bli\bic\bcy\by-\b-f\bfi\bil\blt\bte\ber\br _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs [,\b, _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+ _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs ... ];\b;
+
+ 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.
+
+ See STD 3 (RFC1122) for further information.
+
+ o\bop\bpt\bti\bio\bon\bn m\bma\bax\bx-\b-d\bdg\bgr\bra\bam\bm-\b-r\bre\bea\bas\bss\bse\bem\bmb\bbl\bly\by _\bu_\bi_\bn_\bt_\b1_\b6;\b;
+
+
+
+
+ 4
+
+
+
+
+
+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.
+
+ o\bop\bpt\bti\bio\bon\bn d\bde\bef\bfa\bau\bul\blt\bt-\b-i\bip\bp-\b-t\btt\btl\bl _\bu_\bi_\bn_\bt_\b8_\b;
+
+ This option specifies the default time-to-live that the
+ client should use on outgoing datagrams.
+
+ o\bop\bpt\bti\bio\bon\bn p\bpa\bat\bth\bh-\b-m\bmt\btu\bu-\b-a\bag\bgi\bin\bng\bg-\b-t\bti\bim\bme\beo\bou\but\bt _\bu_\bi_\bn_\bt_\b3_\b2;\b;
+
+ This option specifies the timeout (in seconds) to use when
+ aging Path MTU values discovered by the mechanism defined
+ in RFC 1191.
+
+ o\bop\bpt\bti\bio\bon\bn p\bpa\bat\bth\bh-\b-m\bmt\btu\bu-\b-p\bpl\bla\bat\bte\bea\bau\bu-\b-t\bta\bab\bbl\ble\be _\bu_\bi_\bn_\bt_\b1_\b6 [,\b, _\bu_\bi_\bn_\bt_\b1_\b6 ... ];\b;
+
+ 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.
+
+ o\bop\bpt\bti\bio\bon\bn i\bin\bnt\bte\ber\brf\bfa\bac\bce\be-\b-m\bmt\btu\bu _\bu_\bi_\bn_\bt_\b1_\b6;\b;
+
+ This option specifies the MTU to use on this interface.
+ The minimum legal value for the MTU is 68.
+
+ o\bop\bpt\bti\bio\bon\bn a\bal\bll\bl-\b-s\bsu\bub\bbn\bne\bet\bts\bs-\b-l\blo\boc\bca\bal\bl _\bf_\bl_\ba_\bg;\b;
+
+ 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.
+
+ o\bop\bpt\bti\bio\bon\bn b\bbr\bro\boa\bad\bdc\bca\bas\bst\bt-\b-a\bad\bdd\bdr\bre\bes\bss\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs;\b;
+
+ 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).
+
+ o\bop\bpt\bti\bio\bon\bn p\bpe\ber\brf\bfo\bor\brm\bm-\b-m\bma\bas\bsk\bk-\b-d\bdi\bis\bsc\bco\bov\bve\ber\bry\by _\bf_\bl_\ba_\bg;\b;
+
+ 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.
+
+ o\bop\bpt\bti\bio\bon\bn m\bma\bas\bsk\bk-\b-s\bsu\bup\bpp\bpl\bli\bie\ber\br _\bf_\bl_\ba_\bg;\b;
+
+
+
+
+ 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.
+
+ o\bop\bpt\bti\bio\bon\bn r\bro\bou\but\bte\ber\br-\b-d\bdi\bis\bsc\bco\bov\bve\ber\bry\by _\bf_\bl_\ba_\bg;\b;
+
+ 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.
+
+ o\bop\bpt\bti\bio\bon\bn r\bro\bou\but\bte\ber\br-\b-s\bso\bol\bli\bic\bci\bit\bta\bat\bti\bio\bon\bn-\b-a\bad\bdd\bdr\bre\bes\bss\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs;\b;
+
+ This option specifies the address to which the client
+ should transmit router solicitation requests.
+
+ o\bop\bpt\bti\bio\bon\bn s\bst\bta\bat\bti\bic\bc-\b-r\bro\bou\but\bte\bes\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs [,\b, _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+ _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs ... ];\b;
+
+ 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
+ r\bro\bou\but\bte\ber\brs\bs option.
+
+ o\bop\bpt\bti\bio\bon\bn t\btr\bra\bai\bil\ble\ber\br-\b-e\ben\bnc\bca\bap\bps\bsu\bul\bla\bat\bti\bio\bon\bn _\bf_\bl_\ba_\bg;\b;
+
+ 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.
+
+ o\bop\bpt\bti\bio\bon\bn a\bar\brp\bp-\b-c\bca\bac\bch\bhe\be-\b-t\bti\bim\bme\beo\bou\but\bt _\bu_\bi_\bn_\bt_\b3_\b2;\b;
+
+ This option specifies the timeout in seconds for ARP cache
+ entries.
+
+ o\bop\bpt\bti\bio\bon\bn i\bie\bee\bee\be8\b80\b02\b2-\b-3\b3-\b-e\ben\bnc\bca\bap\bps\bsu\bul\bla\bat\bti\bio\bon\bn _\bf_\bl_\ba_\bg;\b;
+
+ 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
+
+
+
+ 6
+
+
+
+
+
+dhcpd-options(5) dhcpd-options(5)
+
+
+ 1042 encapsulation.
+
+ o\bop\bpt\bti\bio\bon\bn d\bde\bef\bfa\bau\bul\blt\bt-\b-t\btc\bcp\bp-\b-t\btt\btl\bl _\bu_\bi_\bn_\bt_\b8;\b;
+
+ This option specifies the default TTL that the client
+ should use when sending TCP segments. The minimum value
+ is 1.
+
+ o\bop\bpt\bti\bio\bon\bn t\btc\bcp\bp-\b-k\bke\bee\bep\bpa\bal\bli\biv\bve\be-\b-i\bin\bnt\bte\ber\brv\bva\bal\bl _\bu_\bi_\bn_\bt_\b3_\b2;\b;
+
+ 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.
+
+ o\bop\bpt\bti\bio\bon\bn t\btc\bcp\bp-\b-k\bke\bee\bep\bpa\bal\bli\biv\bve\be-\b-g\bga\bar\brb\bba\bag\bge\be _\bf_\bl_\ba_\bg;\b;
+
+ 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.
+
+ o\bop\bpt\bti\bio\bon\bn n\bni\bis\bs-\b-d\bdo\bom\bma\bai\bin\bn _\bs_\bt_\br_\bi_\bn_\bg;\b;
+
+ 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.
+
+ o\bop\bpt\bti\bio\bon\bn n\bni\bis\bs-\b-s\bse\ber\brv\bve\ber\brs\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs [,\b, _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs ... ];\b;
+
+ This option specifies a list of IP addresses indicating
+ NIS servers available to the client. Servers should be
+ listed in order of preference.
+
+ o\bop\bpt\bti\bio\bon\bn n\bnt\btp\bp-\b-s\bse\ber\brv\bve\ber\brs\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs [,\b, _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs ... ];\b;
+
+ 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.
+
+ o\bop\bpt\bti\bio\bon\bn n\bne\bet\btb\bbi\bio\bos\bs-\b-n\bna\bam\bme\be-\b-s\bse\ber\brv\bve\ber\brs\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs [,\b, _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs ...
+ ];\b;
+
+ The NetBIOS name server (NBNS) option specifies a list of
+ RFC 1001/1002 NBNS name servers listed in order of prefer
+ ence.
+
+ o\bop\bpt\bti\bio\bon\bn n\bne\bet\btb\bbi\bio\bos\bs-\b-d\bdd\bd-\b-s\bse\ber\brv\bve\ber\br _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs [,\b, _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs ... ];\b;
+
+ The NetBIOS datagram distribution server (NBDD) option
+
+
+
+ 7
+
+
+
+
+
+dhcpd-options(5) dhcpd-options(5)
+
+
+ specifies a list of RFC 1001/1002 NBDD servers listed in
+ order of preference.
+
+ o\bop\bpt\bti\bio\bon\bn n\bne\bet\btb\bbi\bio\bos\bs-\b-n\bno\bod\bde\be-\b-t\bty\byp\bpe\be _\bu_\bi_\bn_\bt_\b8;\b;
+
+ 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.
+
+ o\bop\bpt\bti\bio\bon\bn n\bne\bet\btb\bbi\bio\bos\bs-\b-s\bsc\bco\bop\bpe\be _\bs_\bt_\br_\bi_\bn_\bg;\b;
+
+ 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.
+
+ o\bop\bpt\bti\bio\bon\bn f\bfo\bon\bnt\bt-\b-s\bse\ber\brv\bve\ber\brs\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs [,\b, _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs ... ];\b;
+
+ This option specifies a list of X Window System Font
+ servers available to the client. Servers should be listed
+ in order of preference.
+
+ o\bop\bpt\bti\bio\bon\bn x\bx-\b-d\bdi\bis\bsp\bpl\bla\bay\by-\b-m\bma\ban\bna\bag\bge\ber\br _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs [,\b, _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs ... ];\b;
+
+ 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.
+
+ o\bop\bpt\bti\bio\bon\bn d\bdh\bhc\bcp\bp-\b-c\bcl\bli\bie\ben\bnt\bt-\b-i\bid\bde\ben\bnt\bti\bif\bfi\bie\ber\br _\bd_\ba_\bt_\ba_\b-_\bs_\bt_\br_\bi_\bn_\bg;\b;
+
+ 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.
+
+S\bSE\bEE\bE A\bAL\bLS\bSO\bO
+ dhcpd.conf(5), dhcpd.leases(5), dhclient.conf(5),
+ dhcpd(8), dhclient(8), RFC2132, RFC2131.
+
+A\bAU\bUT\bTH\bHO\bOR\bR
+ d\bdh\bhc\bcp\bpd\bd(\b(8\b8)\b) 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
+ at h\bht\btt\btp\bp:\b:/\b//\b/w\bww\bww\bw.\b.i\bis\bsc\bc.\b.o\bor\brg\bg/\b/i\bis\bsc\bc.\b.
+
+
+
+
+
+
+
+
+ 8
+
+
projects / thirdparty / dhcp.git / commitdiff
