-dhcpd.conf(5) NetBSD Programmer's Manual dhcpd.conf(5)
+
+
+
+dhcpd.conf(5)() dhcpd.conf(5)()
+
N\bNA\bAM\bME\bE
- d\bdh\bhc\bcp\bpd\bd.\b.c\bco\bon\bnf\bf - dhcpd configuration file
+ dhcpd.conf - dhcpd configuration file
D\bDE\bES\bSC\bCR\bRI\bIP\bPT\bTI\bIO\bON\bN
- The dhcpd.conf(5) file contains configuration information for dhcpd(8),
- the Dynamic Host Configuration Protocol daemon. A primer on configuring
- d\bdh\bhc\bcp\bpd\bd is included in dhcpd(8). This document describes the format of the
- file in detail, and is probably a better reference than a primer.
+ The dhcpd.conf file contains configuration information for
+ _\bd_\bh_\bc_\bp_\bd_\b(_\b8_\b)_\b, the Dynamic Host Configuration Protocol daemon.
+ A primer on configuring dhcpd is included in dhcpd(8).
+ This document describes the format of the file in detail,
+ and is probably a better reference than a primer.
+
+ The dhcpd.conf file is a free-form ASCII text file. It
+ is parsed by a recursive-descent parser. Statements in
+ the file may contain extra tabs and newlines for format-
+ ting purposes. Each statement in the file is terminated
+ by a semicolon. Keywords in the file are case-
+ insensitive.
+
+ There are currently two statements that can meaningfully
+ appear in the file--the _\bs_\bu_\bb_\bn_\be_\bt statement, and the _\bh_\bo_\bs_\bt
+ statement.
- The d\bdh\bhc\bcp\bpd\bd.\b.c\bco\bon\bnf\bf file is a free-form ASCII text file. It is parsed by a
- recursive-descent parser. Statements in the file may contain extra tabs
- and newlines for formatting purposes. Each statement in the file is
- terminated by a semicolon. Keywords in the file are case-insensitive.
+T\bTh\bhe\be S\bSU\bUB\bBN\bNE\bET\bT s\bst\bta\bat\bte\bem\bme\ben\bnt\bt
+ s\bsu\bub\bbn\bne\bet\bt _\bs_\bu_\bb_\bn_\be_\bt_\b-_\bn_\bu_\bm_\bb_\be_\br n\bne\bet\btm\bma\bas\bsk\bk _\bn_\be_\bt_\bm_\ba_\bs_\bk [ _\bc_\bl_\ba_\bu_\bs_\be_\bs ];
- There are currently two statements that can meaningfully appear in the
- file--the s\bsu\bub\bbn\bne\bet\bt statement, and the h\bho\bos\bst\bt statement.
+ _\bs_\bu_\bb_\bn_\be_\bt_\b-_\bn_\bu_\bm_\bb_\be_\br should be an IP address or DNS name which
+ resolves to the subnet number of the subnet being
+ described. _\bn_\be_\bt_\bm_\ba_\bs_\bk should be an IP address or DNS name
+ which resolves to the subnet mask of the subnet being
+ described. These are the only required fields in a subnet
+ declaration, although it may be desirable to add one or
+ more of the following clauses.
+
+ Subnets for which addresses will be dynamically allocated
+ must have one or more addresses reserved for future allo-
+ cation by dhcpd. These addresses are allocated using the
+ _\br_\ba_\bn_\bg_\be clause.
+
+ r\bra\ban\bng\bge\be _\bl_\bo_\bw_\be_\bs_\bt_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\bh_\bi_\bg_\bh_\be_\bs_\bt_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+
+ _\bl_\bo_\bw_\be_\bs_\bt_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs should be the lowest address in the range
+ that may be assigned by dhcpd to a DHCP client. _\bh_\bi_\bg_\bh_\be_\bs_\bt_\b-
+ _\ba_\bd_\bd_\br_\be_\bs_\bs should be the highest address in the range that
+ may be assigned by dhcpd. If there is only one address
+ in a range, it must be specified as both the lowest and
+ highest addresses. As many r\bra\ban\bng\bge\be clauses as are needed
+ may be specified in any given s\bsu\bub\bbn\bne\bet\bt statement.
+
+ d\bde\bef\bfa\bau\bul\blt\bt-\b-l\ble\bea\bas\bse\be-\b-t\bti\bim\bme\be _\bt_\bi_\bm_\be
+
+ _\bt_\bi_\bm_\be should be the expiration time in seconds that will be
+ assigned to a lease if the client requesting the lease
+ does not ask for a specific expiration time. This clause
+ may only appear once in each s\bsu\bub\bbn\bne\bet\bt statement.
-T\bTh\bhe\be S\bSU\bUB\bBN\bNE\bET\bT s\bst\bta\bat\bte\bem\bme\ben\bnt\bt
- s\bsu\bub\bbn\bne\bet\bt _\bs_\bu_\bb_\bn_\be_\bt_\b-_\bn_\bu_\bm_\bb_\be_\br n\bne\bet\btm\bma\bas\bsk\bk _\bn_\be_\bt_\bm_\ba_\bs_\bk [_\bc_\bl_\ba_\bu_\bs_\be_\bs];
- _\bs_\bu_\bb_\bn_\be_\bt_\b-_\bn_\bu_\bm_\bb_\be_\br should be an IP address or DNS name which resolves to the
- subnet number of the subnet being described. _\bn_\be_\bt_\bm_\ba_\bs_\bk should be an IP ad-
- dress or DNS name which resolves to the subnet mask of the subnet being
- described. These are the only required fields in a subnet declaration,
- although it may be desirable to add one or more of the following clauses.
- Subnets for which addresses will be dynamically allocated must have one
- or more addresses reserved for future allocation by d\bdh\bhc\bcp\bpd\bd. These address-
- es are allocated using the r\bra\ban\bng\bge\be clause.
- r\bra\ban\bng\bge\be _\bl_\bo_\bw_\be_\bs_\bt_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\bh_\bi_\bg_\bh_\be_\bs_\bt_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+ 1
- _\bL_\bo_\bw_\be_\bs_\bt_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs should be the lowest address in the range that may be as-
- signed by d\bdh\bhc\bcp\bpd\bd to a DHCP client. _\bH_\bi_\bg_\bh_\be_\bs_\bt_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs should be the highest
- address in the range that may be assigned by d\bdh\bhc\bcp\bpd\bd. If there is only one
- address in a range, it must be specified as both the lowest and highest
- addresses. As many r\bra\ban\bng\bge\be clauses as are needed may be specified in any
- given s\bsu\bub\bbn\bne\bet\bt statement.
- d\bde\bef\bfa\bau\bul\blt\bt-\b-l\ble\bea\bas\bse\be-\b-t\bti\bim\bme\be _\bt_\bi_\bm_\be
- _\bT_\bi_\bm_\be should be the expiration time in seconds that will be assigned to a
- lease if the client requesting the lease does not ask for a specific ex-
- piration time. This clause may only appear once in each s\bsu\bub\bbn\bne\bet\bt state-
- ment.
- m\bma\bax\bx-\b-l\ble\bea\bas\bse\be-\b-t\bti\bim\bme\be _\bt_\bi_\bm_\be
- _\bT_\bi_\bm_\be should be the maximum expiration time in seconds that will be as-
- signed to a lease if the client requesting the lease asks for a specific
- expiration time. This clause may only appear once in each s\bsu\bub\bbn\bne\bet\bt state-
- ment.
+dhcpd.conf(5)() dhcpd.conf(5)()
- o\bop\bpt\bti\bio\bon\bn _\bo_\bp_\bt_\bi_\bo_\bn_\b-_\bd_\be_\bc_\bl_\ba_\br_\ba_\bt_\bi_\bo_\bn
- Any number of d\bdh\bhc\bcp\bpd\bd.\b.c\bco\bon\bnf\bf option clauses may appear in a subnet statement.
- The syntax of option declarations is described later in this document.
+ m\bma\bax\bx-\b-l\ble\bea\bas\bse\be-\b-t\bti\bim\bme\be _\bt_\bi_\bm_\be
+
+ _\bt_\bi_\bm_\be should be the maximum expiration time in seconds that
+ will be assigned to a lease if the client requesting the
+ lease asks for a specific expiration time. This clause
+ may only appear once in each s\bsu\bub\bbn\bne\bet\bt statement.
+
+ o\bop\bpt\bti\bio\bon\bn _\bo_\bp_\bt_\bi_\bo_\bn_\b-_\bd_\be_\bc_\bl_\ba_\br_\ba_\bt_\bi_\bo_\bn
+
+ Any number of o\bop\bpt\bti\bio\bon\bn clauses may appear in a subnet state-
+ ment. The syntax of option declarations is described
+ later in this document.
T\bTh\bhe\be H\bHO\bOS\bST\bT s\bst\bta\bat\bte\bem\bme\ben\bnt\bt
- h\bho\bos\bst\bt _\bh_\bo_\bs_\bt_\bn_\ba_\bm_\be [_\bc_\bl_\ba_\bu_\bs_\be_\bs];
+ h\bho\bos\bst\bt _\bh_\bo_\bs_\bt_\bn_\ba_\bm_\be
+
+ There must be at least one h\bho\bos\bst\bt statement for every BOOTP
+ client that is to be served. h\bho\bos\bst\bt statements may also be
+ specified for DHCP clients, although this is not required.
+ If it is desirable to be able to boot a DHCP or BOOTP
+ client on more than one subnet with fixed addresses, more
+ than one address may be specified in the f\bfi\bix\bxe\bed\bd-\b-a\bad\bdd\bdr\bre\bes\bss\bs
+ clause, or more than one h\bho\bos\bst\bt statement may be specified.
+ If client-specific boot parameters must change based on
+ the network to which the client is attached, then multiple
+ h\bho\bos\bst\bt statements should be used. If a client is to be
+ booted using a fixed address if it's possible, but should
+ be allocated a dynamic address otherwise, then a h\bho\bos\bst\bt
+ statement must be specified without a f\bfi\bix\bxe\bed\bd-\b-a\bad\bdd\bdr\bre\bes\bss\bs
+ clause. _\bh_\bo_\bs_\bt_\bn_\ba_\bm_\be should be a name identifying the host.
+ It is for labelling purposes only, and is not used in the
+ BOOTP protocol.
+
+ h\bha\bar\brd\bdw\bwa\bar\bre\be _\bh_\ba_\br_\bd_\bw_\ba_\br_\be_\b-_\bt_\by_\bp_\be _\bh_\ba_\br_\bd_\bw_\ba_\br_\be_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+
+ In order for a BOOTP client to be recognized, its network
+ hardware address must be declared using a h\bha\bar\brd\bdw\bwa\bar\bre\be clause
+ in the h\bho\bos\bst\bt statement. Only one such clause can appear
+ in any host statement. _\bh_\ba_\br_\bd_\bw_\ba_\br_\be_\b-_\bt_\by_\bp_\be must be the name of
+ a physical hardware interface type. Currently, only the
+ e\bet\bth\bhe\ber\brn\bne\bet\bt type is recognized, although support for t\bto\bok\bke\ben\bn-\b-
+ r\bri\bin\bng\bg and f\bfd\bdd\bdi\bi hardware types will be added soon. The
+ _\bh_\ba_\br_\bd_\bw_\ba_\br_\be_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs should be a set of hexadecimal octets
+ (numbers from 0 through ff) seperated by colons.
+
+ f\bfi\bil\ble\ben\bna\bam\bme\be _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be
+
+ If the BOOTP client needs to load a boot file (for exam-
+ ple, a kernel or configuration file), the name of this
+ file may be provided to the client using the f\bfi\bil\ble\ben\bna\bam\bme\be
+ clause. The _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be should be a filename recognizable
+ to whatever file transfer protocol the client can be
+ expected to use to load the file.
+
+
+
- There must be at least one h\bho\bos\bst\bt statement for every BOOTP client that is
- to be served. _\bh_\bo_\bs_\bt_\bn_\ba_\bm_\be should be a name identifying the host. It is
- for labelling purposes only, and is not used in the BOOTP protocol.
+ 2
- h\bha\bar\brd\bdw\bwa\bar\bre\be _\bh_\ba_\br_\bd_\bw_\ba_\br_\be_\b-_\bt_\by_\bp_\be _\bh_\ba_\br_\bd_\bw_\ba_\br_\be_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
- In order for a BOOTP client to be recognized, its network hardware ad-
- dress must be declared using a h\bha\bar\brd\bdw\bwa\bar\bre\be clause in the h\bho\bos\bst\bt statement.
- Only one such clause can appear in any host statement. _\bh_\ba_\br_\bd_\bw_\ba_\br_\be_\b-_\bt_\by_\bp_\be
- must be the name of a physical hardware interface type. Currently, only
- the e\bet\bth\bhe\ber\brn\bne\bet\bt type is recognized, although support for t\bto\bok\bke\ben\bn-\b-r\bri\bin\bng\bg and f\bfd\bdd\bdi\bi
- hardware types will be added soon. The _\bh_\ba_\br_\bd_\bw_\ba_\br_\be_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs should be a set
- of hexadecimal octets (numbers from 0 through ff) seperated by colons.
- f\bfi\bil\ble\ben\bna\bam\bme\be _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be
- If the BOOTP client needs to load a boot file (for example, a kernel or
- configuration file), the name of this file may be provided to the client
- using the f\bfi\bil\ble\ben\bna\bam\bme\be clause. The _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be should be a filename recogniz-
- able to whatever file transfer protocol the client can be expected to use
- to load the file.
- f\bfi\bix\bxe\bed\bd-\b-a\bad\bdd\bdr\bre\bes\bss\bs _\ba_\bd_\bd_\br_\be_\bs_\bs
+dhcpd.conf(5)() dhcpd.conf(5)()
- BOOTP clients must be assigned fixed IP addresses. The f\bfi\bix\bxe\bed\bd-\b-a\bad\bdd\bdr\bre\bes\bss\bs
- clause is used to associate a fixed IP address with a BOOTP client.
- _\bA_\bd_\bd_\br_\be_\bs_\bs should be either an IP address or a DNS name which resolves to a
- single IP address.
- o\bop\bpt\bti\bio\bon\bn _\bo_\bp_\bt_\bi_\bo_\bn_\b-_\bd_\be_\bc_\bl_\ba_\br_\ba_\bt_\bi_\bo_\bn
+ f\bfi\bix\bxe\bed\bd-\b-a\bad\bdd\bdr\bre\bes\bss\bs _\ba_\bd_\bd_\br_\be_\bs_\bs [, _\ba_\bd_\bd_\br_\be_\bs_\bs ]
+
+ BOOTP clients must be assigned fixed IP addresses. DHCP
+ clients may optionally be assigned a fixed address. The
+ f\bfi\bix\bxe\bed\bd-\b-a\bad\bdd\bdr\bre\bes\bss\bs clause is used to associate one or more
+ fixed IP address with a BOOTP or DHCP client. If more
+ than one address is supplied, the client may be booted on
+ each network for which an address is specified. Multiple
+ addresses on the same network should not be specified.
+ _\ba_\bd_\bd_\br_\be_\bs_\bs should be either an IP address or a DNS name which
+ resolves to a single IP address.
+
+ o\bop\bpt\bti\bio\bon\bn _\bo_\bp_\bt_\bi_\bo_\bn_\b-_\bd_\be_\bc_\bl_\ba_\br_\ba_\bt_\bi_\bo_\bn
+
+ Any number of o\bop\bpt\bti\bio\bon\bn c\bcl\bla\bau\bus\bse\bes\bs m\bma\bay\by a\bap\bpp\bpe\bea\bar\br i\bin\bn a\ba h\bho\bos\bst\bt s\bst\bta\bat\bte\be-\b-
+ m\bme\ben\bnt\bt.\b. T\bTh\bhe\be s\bsy\byn\bnt\bta\bax\bx o\bof\bf option declarations is described
+ later in this document. If an option clause in a h\bho\bos\bst\bt
+ statement conflicts with an option clause in the s\bsu\bub\bbn\bne\bet\bt
+ statement for the subnet containing that host, the option
+ clause in the h\bho\bos\bst\bt statement is used.
- Any number of d\bdh\bhc\bcp\bpd\bd.\b.c\bco\bon\bnf\bf option clauses may appear in a host statement.
- The syntax of option declarations is described later in this document.
- If an option clause in a h\bho\bos\bst\bt statement conflicts with an option clause
- in the s\bsu\bub\bbn\bne\bet\bt statement for the subnet containing that host, the option
- clause in the h\bho\bos\bst\bt statement is used.
O\bOp\bpt\bti\bio\bon\bn D\bDe\bec\bcl\bla\bar\bra\bat\bti\bio\bon\bns\bs
- Option declarations always start with the o\bop\bpt\bti\bio\bon\bn keyword, followed by an
- option name, followed by option data. The option names and data formats
- are described below. Many of the options described below which set IP
- or TCP parameters have default values which will generally work perfectly
- well, so only those options whose values must be set explicitly should be
- included in s\bsu\bub\bbn\bne\bet\bt or h\bho\bos\bst\bt statements.
+ Option declarations always start with the o\bop\bpt\bti\bio\bon\bn keyword,
+ followed by an option name, followed by option data. The
+ option names and data formats are described below. Many
+ of the options described below which set IP or TCP parame-
+ ters have default values which will generally work per-
+ fectly well, so only those options whose values must be
+ set explicitly should be included in. B subnet or h\bho\bos\bst\bt
+ statements.
+
+ Option data comes in a variety of formats. In order to
+ avoid having to explain the formats along with each option
+ definition below, a number of data types have been
+ defined.
+
+ The ip-address 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 int32 data type specifies a signed 32-bit integer.
+ The uint32 data type specifies an unsigned 32-bit integer.
+ The int16 and uint16 data types specify signed and
+ unsigned 16-bit integers. The int8 and uint8 data types
+ specify signed and unsigned 8-bit integers. Unsigned
+ 8-bit integers are also sometimes referred to as octets.
+
+ The string 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
+
+
+
+
+ 3
+
+
+
+
+
+dhcpd.conf(5)() dhcpd.conf(5)()
+
+
+ option domain-name "isc.org"
+
+ The flag data type specifies a one-bit (boolean) number.
+
+ The data-string 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
+
+ The documentation for the various options mentioned below is taken
+ from the latest IETF draft document on DHCP options.
+
+ 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
+
+ The subnet mask option specifies the client's subnet mask as per RFC
+ 950.
+
+ 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
+
+ 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
+ [,
+ _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+ _\b._\b._\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
+ [,
+ _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+ _\b._\b._\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
+
+
+
+ 4
+
+
+
+
+
+dhcpd.conf(5)() dhcpd.conf(5)()
+
+
+ n\bna\bam\bme\be-\b-s\bse\ber\brv\bve\ber\brs\bs
+ _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+ [,
+ _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+ _\b._\b._\b.
+ ]
+
+ The name-servers option specifies a list of IEN 116 name servers
+ available to the client. Servers should be listed in order of
+ preference.
+
+ 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
+ [,
+ _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+ _\b._\b._\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 preference.
+
+ 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
+ [,
+ _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+ _\b._\b._\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
+ [,
+ _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+ _\b._\b._\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
+ [,
+ _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+ _\b._\b._\b.
+ ]
+
+
+
+ 5
+
+
+
+
+
+dhcpd.conf(5)() dhcpd.conf(5)()
+
+
+ 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
+ [,
+ _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+ _\b._\b._\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
+ [,
+ _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+ _\b._\b._\b.
+ ]
+
+ This option specifies a list of RFC 887 Resource Location
+ servers available to the client. Servers should be listed in order
+ of preference.
- Option data comes in a variety of formats. In order to avoid having to
- explain the formats along with each option definition below, a number of
- data types have been defined.
+ o\bop\bpt\bti\bio\bon\bn
+ h\bho\bos\bst\bt-\b-n\bna\bam\bme\be
+ _\bs_\bt_\br_\bi_\bn_\bg
- The ip-address 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 sin-
- gle IP address.
+ 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.
- The int32 data type specifies a signed 32-bit integer. The uint32 data
- type specifies an unsigned 32-bit integer. The int16 and uint16 data
- types specify signed and unsigned 16-bit integers. The int8 and uint8
- data types specify signed and unsigned 8-bit integers. Unsigned 8-bit
- integers are also sometimes referred to as octets.
+ o\bop\bpt\bti\bio\bon\bn
+ b\bbo\boo\bot\bt-\b-s\bsi\biz\bze\be
+ _\bu_\bi_\bn_\bt_\b1_\b6
- The string data type specifies an NVT ASCII string, which must be en-
- closed in double quotes - for example, to specify a domain-name option,
- the syntax would be
+ This option specifies the length in 512-octet blocks of the default
+ boot image for the client.
- option domain-name "isc.org"
+ 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
- The flag data type specifies a one-bit (boolean) number.
+ 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.
+ o\bop\bpt\bti\bio\bon\bn
- The documentation for the various options mentioned below is taken from
- the latest IETF draft document on DHCP options.
- 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
- The subnet mask option specifies the client's subnet mask as per RFC 950.
+ 6
- 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
- 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 [ , _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\b._\b._\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 [ , _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\b._\b._\b.]
+dhcpd.conf(5)() dhcpd.conf(5)()
- 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 n\bna\bam\bme\be-\b-s\bse\ber\brv\bve\ber\brs\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs [ , _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\b._\b._\b.]
+ d\bdo\bom\bma\bai\bin\bn-\b-n\bna\bam\bme\be
+ _\bs_\bt_\br_\bi_\bn_\bg
- The name-servers option specifies a list of IEN 116 name servers avail-
- able to the client. Servers should be listed in order of preference.
+ 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 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 [ , _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\b._\b._\b.]
+ 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
- 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.
+ This specifies the IP address of the client's swap server.
- 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 [ , _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\b._\b._\b.]
+ o\bop\bpt\bti\bio\bon\bn
+ r\bro\boo\bot\bt-\b-p\bpa\bat\bth\bh
+ _\bs_\bt_\br_\bi_\bn_\bg
- The log-server option specifies a list of MIT-LCS UDP log servers avail-
- able to the client. Servers should be listed in order of preference.
+ 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.
- 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 [ , _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\b._\b._\b.]
+ 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
- The cookie server option specifies a list of RFC 865 cookie servers
- available to the client. Servers should be listed in order of prefer-
- ence.
+ 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 l\blp\bpr\br-\b-s\bse\ber\brv\bve\ber\brs\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs [ , _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\b._\b._\b.]
+ 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
- The LPR server option specifies a list of RFC 1179 line printer servers
- available to the client. Servers should be listed in order of prefer-
- ence.
+ 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.
- 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 [ , _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\b._\b._\b.]
+ 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
+ [,
+ _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+ _\b._\b._\b.
+ ]
- The impress-server option specifies a list of Imagen Impress servers
- available to the client. Servers should be listed in order of prefer-
- ence.
+ 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.
- 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 [ , _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\b._\b._\b.]
+ Any source routed datagram whose next-hop address does not match one
+ of the filters should be discarded by the client.
- This option specifies a list of RFC 887 Resource Location servers avail-
- able to the client. Servers should be listed in order of preference.
+ See STD 3 (RFC1122) for further information.
- o\bop\bpt\bti\bio\bon\bn h\bho\bos\bst\bt-\b-n\bna\bam\bme\be _\bs_\bt_\br_\bi_\bn_\bg
- 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.
- o\bop\bpt\bti\bio\bon\bn b\bbo\boo\bot\bt-\b-s\bsi\biz\bze\be _\bu_\bi_\bn_\bt_\b1_\b6
+ 7
- 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
- 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 for-
- matted as a character string consisting of characters from the NVT ASCII
- character 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
- This option specifies the domain name that client should use when resolv-
- ing hostnames via the Domain Name System.
+dhcpd.conf(5)() dhcpd.conf(5)()
- 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
- This specifies the IP address of the client's swap server.
+ 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
- o\bop\bpt\bti\bio\bon\bn r\bro\boo\bot\bt-\b-p\bpa\bat\bth\bh _\bs_\bt_\br_\bi_\bn_\bg
+ This option specifies the maximum size datagram that the client
+ should be prepared to reassemble. The minimum value legal value is
+ 576.
- 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.
+ 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
- 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
+ This option specifies the default time-to-live that the client should
+ use on outgoing datagrams.
- 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
+ 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
- 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
+ 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 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 disal-
- low forwarding of such datagrams, and a value of 1 means allow forward-
- ing.
+ 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
+ [,
+ _\bu_\bi_\bn_\bt_\b1_\b6
+ _\b._\b._\b.
+ ]
- 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 [ , _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\b._\b._\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.
- This option specifies policy filters for non-local source routing. The
- filters consist of a list of IP addresses and masks which specify desti-
- nation/mask pairs with which to filter incoming source routes.
+ 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
- Any source routed datagram whose next-hop address does not match one of
- the filters should be discarded by the client.
+ This option specifies the MTU to use on this interface. The minimum
+ legal value for the MTU is 68.
- See STD 3 (RFC1122) for further information.
+ 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
+ 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 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
+ 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
- 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
- This option specifies the default time-to-live that the client should use
- on outgoing datagrams.
+ 8
- 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
- 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 [ , _\bu_\bi_\bn_\bt_\b1_\b6 _\b._\b._\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 mini-
- mum MTU value cannot be smaller than 68.
+dhcpd.conf(5)() dhcpd.conf(5)()
- 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
- This option specifies the MTU to use on this interface. The minimum le-
- gal value for the MTU is 68.
+ _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
- 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 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).
- 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
+ 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
- This option specifies the broadcast address in use on the client's sub-
- net. 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 discovery. A value of 1 means that the
+ client should perform mask discovery.
- 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
+ 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
- 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 discovery. A value of 1 means that the client should
- perform mask discovery.
+ 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 m\bma\bas\bsk\bk-\b-s\bsu\bup\bpp\bpl\bli\bie\ber\br _\bf_\bl_\ba_\bg
+ 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
- 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 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-d\bdi\bis\bsc\bco\bov\bve\ber\bry\by _\bf_\bl_\ba_\bg
+ 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
- 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 the address to which the client should transmit
+ router solicitation requests.
- 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
+ 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
+ [,
+ _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+ _\b._\b._\b.
+ ]
- This option specifies the address to which the client should transmit
- router solicitation requests.
+ 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.
- 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 [ , _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\b._\b._\b.]
- This option specifies a list of static routes that the client should in-
- stall 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.
+ 9
- 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
- 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 in-
- dicates 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
- This option specifies the timeout in seconds for ARP cache entries.
+dhcpd.conf(5)() dhcpd.conf(5)()
- 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
- This option specifies whether or not the client should use Ethernet Ver-
- sion 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.
+ 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.
- 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
+ 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.
- 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\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
- 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
+ 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 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 indi-
- cates that the client should not generate keepalive messages on connec-
- tions unless specifically requested by an application.
+ 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
- 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
+ This option specifies the timeout in seconds for ARP cache entries.
- 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
+ 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
- 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
+ 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.
- This option specifies the name of the client's NIS (Sun Network Informa-
- tion Services) domain. The domain is formatted as a character string
- consisting of characters from the NVT ASCII character set.
+ 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
- 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 [ , _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\b._\b._\b.]
+ This option specifies the default TTL that the client should use when
+ sending TCP segments. The minimum value is 1.
- This option specifies a list of IP addresses indicating NIS servers
- available to the client. Servers should be listed in order of prefer-
- ence.
+ 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
- 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 [ , _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\b._\b._\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
+ connections unless specifically requested by an application.
- 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
+ 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
- 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 [ , _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\b._\b._\b.]
- The NetBIOS name server (NBNS) option specifies a list of RFC 1001/1002
- NBNS name servers listed in order of preference.
+ 10
- 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 [ , _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\b._\b._\b.]
- The NetBIOS datagram distribution server (NBDD) option 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
- 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 corresponds 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
+dhcpd.conf(5)() dhcpd.conf(5)()
- The NetBIOS scope option specifies the NetBIOS over TCP/IP scope parame-
- ter for the client as specified in RFC 1001/1002. See RFC1001, RFC1002,
- and RFC1035 for character-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 [ , _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\b._\b._\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.
- 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
+ n\bni\bis\bs-\b-d\bdo\bom\bma\bai\bin\bn
+ _\bs_\bt_\br_\bi_\bn_\bg
- 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 [ , _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\b._\b._\b.]
+ 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.
- 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.
+ 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
+ [,
+ _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+ _\b._\b._\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
+ [,
+ _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+ _\b._\b._\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
+ [,
+ _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+ _\b._\b._\b.
+ ]
+
+ The NetBIOS name server (NBNS) option specifies a list of RFC
+ 1001/1002 NBNS name servers listed in order of preference.
+
+ 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
+ [,
+ _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+
+
+
+ 11
+
+
+
+
+
+dhcpd.conf(5)() dhcpd.conf(5)()
+
+
+ _\b._\b._\b.
+ ]
+
+ The NetBIOS datagram distribution server (NBDD) option 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
+
+ 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 corresponds
+ 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
+
+ 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.
+
+ 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
+ [,
+ _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+ _\b._\b._\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
+ [,
+ _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+ _\b._\b._\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 preference.
+
+ 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
+
+ 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
+
+
+
+ 12
+
+
+
+
+
+dhcpd.conf(5)() dhcpd.conf(5)()
+
+
+ against the client identifier.
S\bSE\bEE\bE A\bAL\bLS\bSO\bO
- dhcpd.conf(5), dhcpd.leases(5)
+ dhcpd.conf(5), dhcpd.leases(5)
A\bAU\bUT\bTH\bHO\bOR\bR
- dhcpd(8) was written by Ted Lemon <\b<m\bme\bel\bll\blo\bon\bn@\b@v\bvi\bix\bx.\b.c\bco\bom\bm>\b> under a contract with
- Vixie Labs. Funding for this project was provided by the Internet Soft-
- ware Corporation. Information 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.
+ 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.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ 13
+
- March 6, 1996 7
-dhcpd.conf(5) NetBSD Programmer's Manual dhcpd.conf(5)
+
+
+
+dhcpd.conf(5)() dhcpd.conf(5)()
+
N\bNA\bAM\bME\bE
- d\bdh\bhc\bcp\bpd\bd.\b.c\bco\bon\bnf\bf - dhcpd configuration file
+ dhcpd.conf - dhcpd configuration file
D\bDE\bES\bSC\bCR\bRI\bIP\bPT\bTI\bIO\bON\bN
- The dhcpd.conf(5) file contains configuration information for dhcpd(8),
- the Dynamic Host Configuration Protocol daemon. A primer on configuring
- d\bdh\bhc\bcp\bpd\bd is included in dhcpd(8). This document describes the format of the
- file in detail, and is probably a better reference than a primer.
+ The dhcpd.conf file contains configuration information for
+ _\bd_\bh_\bc_\bp_\bd_\b(_\b8_\b)_\b, the Dynamic Host Configuration Protocol daemon.
+ A primer on configuring dhcpd is included in dhcpd(8).
+ This document describes the format of the file in detail,
+ and is probably a better reference than a primer.
+
+ The dhcpd.conf file is a free-form ASCII text file. It
+ is parsed by a recursive-descent parser. Statements in
+ the file may contain extra tabs and newlines for format-
+ ting purposes. Each statement in the file is terminated
+ by a semicolon. Keywords in the file are case-
+ insensitive.
+
+ There are currently two statements that can meaningfully
+ appear in the file--the _\bs_\bu_\bb_\bn_\be_\bt statement, and the _\bh_\bo_\bs_\bt
+ statement.
- The d\bdh\bhc\bcp\bpd\bd.\b.c\bco\bon\bnf\bf file is a free-form ASCII text file. It is parsed by a
- recursive-descent parser. Statements in the file may contain extra tabs
- and newlines for formatting purposes. Each statement in the file is
- terminated by a semicolon. Keywords in the file are case-insensitive.
+T\bTh\bhe\be S\bSU\bUB\bBN\bNE\bET\bT s\bst\bta\bat\bte\bem\bme\ben\bnt\bt
+ s\bsu\bub\bbn\bne\bet\bt _\bs_\bu_\bb_\bn_\be_\bt_\b-_\bn_\bu_\bm_\bb_\be_\br n\bne\bet\btm\bma\bas\bsk\bk _\bn_\be_\bt_\bm_\ba_\bs_\bk [ _\bc_\bl_\ba_\bu_\bs_\be_\bs ];
- There are currently two statements that can meaningfully appear in the
- file--the s\bsu\bub\bbn\bne\bet\bt statement, and the h\bho\bos\bst\bt statement.
+ _\bs_\bu_\bb_\bn_\be_\bt_\b-_\bn_\bu_\bm_\bb_\be_\br should be an IP address or DNS name which
+ resolves to the subnet number of the subnet being
+ described. _\bn_\be_\bt_\bm_\ba_\bs_\bk should be an IP address or DNS name
+ which resolves to the subnet mask of the subnet being
+ described. These are the only required fields in a subnet
+ declaration, although it may be desirable to add one or
+ more of the following clauses.
+
+ Subnets for which addresses will be dynamically allocated
+ must have one or more addresses reserved for future allo-
+ cation by dhcpd. These addresses are allocated using the
+ _\br_\ba_\bn_\bg_\be clause.
+
+ r\bra\ban\bng\bge\be _\bl_\bo_\bw_\be_\bs_\bt_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\bh_\bi_\bg_\bh_\be_\bs_\bt_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+
+ _\bl_\bo_\bw_\be_\bs_\bt_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs should be the lowest address in the range
+ that may be assigned by dhcpd to a DHCP client. _\bh_\bi_\bg_\bh_\be_\bs_\bt_\b-
+ _\ba_\bd_\bd_\br_\be_\bs_\bs should be the highest address in the range that
+ may be assigned by dhcpd. If there is only one address
+ in a range, it must be specified as both the lowest and
+ highest addresses. As many r\bra\ban\bng\bge\be clauses as are needed
+ may be specified in any given s\bsu\bub\bbn\bne\bet\bt statement.
+
+ d\bde\bef\bfa\bau\bul\blt\bt-\b-l\ble\bea\bas\bse\be-\b-t\bti\bim\bme\be _\bt_\bi_\bm_\be
+
+ _\bt_\bi_\bm_\be should be the expiration time in seconds that will be
+ assigned to a lease if the client requesting the lease
+ does not ask for a specific expiration time. This clause
+ may only appear once in each s\bsu\bub\bbn\bne\bet\bt statement.
-T\bTh\bhe\be S\bSU\bUB\bBN\bNE\bET\bT s\bst\bta\bat\bte\bem\bme\ben\bnt\bt
- s\bsu\bub\bbn\bne\bet\bt _\bs_\bu_\bb_\bn_\be_\bt_\b-_\bn_\bu_\bm_\bb_\be_\br n\bne\bet\btm\bma\bas\bsk\bk _\bn_\be_\bt_\bm_\ba_\bs_\bk [_\bc_\bl_\ba_\bu_\bs_\be_\bs];
- _\bs_\bu_\bb_\bn_\be_\bt_\b-_\bn_\bu_\bm_\bb_\be_\br should be an IP address or DNS name which resolves to the
- subnet number of the subnet being described. _\bn_\be_\bt_\bm_\ba_\bs_\bk should be an IP ad-
- dress or DNS name which resolves to the subnet mask of the subnet being
- described. These are the only required fields in a subnet declaration,
- although it may be desirable to add one or more of the following clauses.
- Subnets for which addresses will be dynamically allocated must have one
- or more addresses reserved for future allocation by d\bdh\bhc\bcp\bpd\bd. These address-
- es are allocated using the r\bra\ban\bng\bge\be clause.
- r\bra\ban\bng\bge\be _\bl_\bo_\bw_\be_\bs_\bt_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\bh_\bi_\bg_\bh_\be_\bs_\bt_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+ 1
- _\bL_\bo_\bw_\be_\bs_\bt_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs should be the lowest address in the range that may be as-
- signed by d\bdh\bhc\bcp\bpd\bd to a DHCP client. _\bH_\bi_\bg_\bh_\be_\bs_\bt_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs should be the highest
- address in the range that may be assigned by d\bdh\bhc\bcp\bpd\bd. If there is only one
- address in a range, it must be specified as both the lowest and highest
- addresses. As many r\bra\ban\bng\bge\be clauses as are needed may be specified in any
- given s\bsu\bub\bbn\bne\bet\bt statement.
- d\bde\bef\bfa\bau\bul\blt\bt-\b-l\ble\bea\bas\bse\be-\b-t\bti\bim\bme\be _\bt_\bi_\bm_\be
- _\bT_\bi_\bm_\be should be the expiration time in seconds that will be assigned to a
- lease if the client requesting the lease does not ask for a specific ex-
- piration time. This clause may only appear once in each s\bsu\bub\bbn\bne\bet\bt state-
- ment.
- m\bma\bax\bx-\b-l\ble\bea\bas\bse\be-\b-t\bti\bim\bme\be _\bt_\bi_\bm_\be
- _\bT_\bi_\bm_\be should be the maximum expiration time in seconds that will be as-
- signed to a lease if the client requesting the lease asks for a specific
- expiration time. This clause may only appear once in each s\bsu\bub\bbn\bne\bet\bt state-
- ment.
+dhcpd.conf(5)() dhcpd.conf(5)()
- o\bop\bpt\bti\bio\bon\bn _\bo_\bp_\bt_\bi_\bo_\bn_\b-_\bd_\be_\bc_\bl_\ba_\br_\ba_\bt_\bi_\bo_\bn
- Any number of d\bdh\bhc\bcp\bpd\bd.\b.c\bco\bon\bnf\bf option clauses may appear in a subnet statement.
- The syntax of option declarations is described later in this document.
+ m\bma\bax\bx-\b-l\ble\bea\bas\bse\be-\b-t\bti\bim\bme\be _\bt_\bi_\bm_\be
+
+ _\bt_\bi_\bm_\be should be the maximum expiration time in seconds that
+ will be assigned to a lease if the client requesting the
+ lease asks for a specific expiration time. This clause
+ may only appear once in each s\bsu\bub\bbn\bne\bet\bt statement.
+
+ o\bop\bpt\bti\bio\bon\bn _\bo_\bp_\bt_\bi_\bo_\bn_\b-_\bd_\be_\bc_\bl_\ba_\br_\ba_\bt_\bi_\bo_\bn
+
+ Any number of o\bop\bpt\bti\bio\bon\bn clauses may appear in a subnet state-
+ ment. The syntax of option declarations is described
+ later in this document.
T\bTh\bhe\be H\bHO\bOS\bST\bT s\bst\bta\bat\bte\bem\bme\ben\bnt\bt
- h\bho\bos\bst\bt _\bh_\bo_\bs_\bt_\bn_\ba_\bm_\be [_\bc_\bl_\ba_\bu_\bs_\be_\bs];
+ h\bho\bos\bst\bt _\bh_\bo_\bs_\bt_\bn_\ba_\bm_\be
+
+ There must be at least one h\bho\bos\bst\bt statement for every BOOTP
+ client that is to be served. h\bho\bos\bst\bt statements may also be
+ specified for DHCP clients, although this is not required.
+ If it is desirable to be able to boot a DHCP or BOOTP
+ client on more than one subnet with fixed addresses, more
+ than one address may be specified in the f\bfi\bix\bxe\bed\bd-\b-a\bad\bdd\bdr\bre\bes\bss\bs
+ clause, or more than one h\bho\bos\bst\bt statement may be specified.
+ If client-specific boot parameters must change based on
+ the network to which the client is attached, then multiple
+ h\bho\bos\bst\bt statements should be used. If a client is to be
+ booted using a fixed address if it's possible, but should
+ be allocated a dynamic address otherwise, then a h\bho\bos\bst\bt
+ statement must be specified without a f\bfi\bix\bxe\bed\bd-\b-a\bad\bdd\bdr\bre\bes\bss\bs
+ clause. _\bh_\bo_\bs_\bt_\bn_\ba_\bm_\be should be a name identifying the host.
+ It is for labelling purposes only, and is not used in the
+ BOOTP protocol.
+
+ h\bha\bar\brd\bdw\bwa\bar\bre\be _\bh_\ba_\br_\bd_\bw_\ba_\br_\be_\b-_\bt_\by_\bp_\be _\bh_\ba_\br_\bd_\bw_\ba_\br_\be_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+
+ In order for a BOOTP client to be recognized, its network
+ hardware address must be declared using a h\bha\bar\brd\bdw\bwa\bar\bre\be clause
+ in the h\bho\bos\bst\bt statement. Only one such clause can appear
+ in any host statement. _\bh_\ba_\br_\bd_\bw_\ba_\br_\be_\b-_\bt_\by_\bp_\be must be the name of
+ a physical hardware interface type. Currently, only the
+ e\bet\bth\bhe\ber\brn\bne\bet\bt type is recognized, although support for t\bto\bok\bke\ben\bn-\b-
+ r\bri\bin\bng\bg and f\bfd\bdd\bdi\bi hardware types will be added soon. The
+ _\bh_\ba_\br_\bd_\bw_\ba_\br_\be_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs should be a set of hexadecimal octets
+ (numbers from 0 through ff) seperated by colons.
+
+ f\bfi\bil\ble\ben\bna\bam\bme\be _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be
+
+ If the BOOTP client needs to load a boot file (for exam-
+ ple, a kernel or configuration file), the name of this
+ file may be provided to the client using the f\bfi\bil\ble\ben\bna\bam\bme\be
+ clause. The _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be should be a filename recognizable
+ to whatever file transfer protocol the client can be
+ expected to use to load the file.
+
+
+
- There must be at least one h\bho\bos\bst\bt statement for every BOOTP client that is
- to be served. _\bh_\bo_\bs_\bt_\bn_\ba_\bm_\be should be a name identifying the host. It is
- for labelling purposes only, and is not used in the BOOTP protocol.
+ 2
- h\bha\bar\brd\bdw\bwa\bar\bre\be _\bh_\ba_\br_\bd_\bw_\ba_\br_\be_\b-_\bt_\by_\bp_\be _\bh_\ba_\br_\bd_\bw_\ba_\br_\be_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
- In order for a BOOTP client to be recognized, its network hardware ad-
- dress must be declared using a h\bha\bar\brd\bdw\bwa\bar\bre\be clause in the h\bho\bos\bst\bt statement.
- Only one such clause can appear in any host statement. _\bh_\ba_\br_\bd_\bw_\ba_\br_\be_\b-_\bt_\by_\bp_\be
- must be the name of a physical hardware interface type. Currently, only
- the e\bet\bth\bhe\ber\brn\bne\bet\bt type is recognized, although support for t\bto\bok\bke\ben\bn-\b-r\bri\bin\bng\bg and f\bfd\bdd\bdi\bi
- hardware types will be added soon. The _\bh_\ba_\br_\bd_\bw_\ba_\br_\be_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs should be a set
- of hexadecimal octets (numbers from 0 through ff) seperated by colons.
- f\bfi\bil\ble\ben\bna\bam\bme\be _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be
- If the BOOTP client needs to load a boot file (for example, a kernel or
- configuration file), the name of this file may be provided to the client
- using the f\bfi\bil\ble\ben\bna\bam\bme\be clause. The _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be should be a filename recogniz-
- able to whatever file transfer protocol the client can be expected to use
- to load the file.
- f\bfi\bix\bxe\bed\bd-\b-a\bad\bdd\bdr\bre\bes\bss\bs _\ba_\bd_\bd_\br_\be_\bs_\bs
+dhcpd.conf(5)() dhcpd.conf(5)()
- BOOTP clients must be assigned fixed IP addresses. The f\bfi\bix\bxe\bed\bd-\b-a\bad\bdd\bdr\bre\bes\bss\bs
- clause is used to associate a fixed IP address with a BOOTP client.
- _\bA_\bd_\bd_\br_\be_\bs_\bs should be either an IP address or a DNS name which resolves to a
- single IP address.
- o\bop\bpt\bti\bio\bon\bn _\bo_\bp_\bt_\bi_\bo_\bn_\b-_\bd_\be_\bc_\bl_\ba_\br_\ba_\bt_\bi_\bo_\bn
+ f\bfi\bix\bxe\bed\bd-\b-a\bad\bdd\bdr\bre\bes\bss\bs _\ba_\bd_\bd_\br_\be_\bs_\bs [, _\ba_\bd_\bd_\br_\be_\bs_\bs ]
+
+ BOOTP clients must be assigned fixed IP addresses. DHCP
+ clients may optionally be assigned a fixed address. The
+ f\bfi\bix\bxe\bed\bd-\b-a\bad\bdd\bdr\bre\bes\bss\bs clause is used to associate one or more
+ fixed IP address with a BOOTP or DHCP client. If more
+ than one address is supplied, the client may be booted on
+ each network for which an address is specified. Multiple
+ addresses on the same network should not be specified.
+ _\ba_\bd_\bd_\br_\be_\bs_\bs should be either an IP address or a DNS name which
+ resolves to a single IP address.
+
+ o\bop\bpt\bti\bio\bon\bn _\bo_\bp_\bt_\bi_\bo_\bn_\b-_\bd_\be_\bc_\bl_\ba_\br_\ba_\bt_\bi_\bo_\bn
+
+ Any number of o\bop\bpt\bti\bio\bon\bn c\bcl\bla\bau\bus\bse\bes\bs m\bma\bay\by a\bap\bpp\bpe\bea\bar\br i\bin\bn a\ba h\bho\bos\bst\bt s\bst\bta\bat\bte\be-\b-
+ m\bme\ben\bnt\bt.\b. T\bTh\bhe\be s\bsy\byn\bnt\bta\bax\bx o\bof\bf option declarations is described
+ later in this document. If an option clause in a h\bho\bos\bst\bt
+ statement conflicts with an option clause in the s\bsu\bub\bbn\bne\bet\bt
+ statement for the subnet containing that host, the option
+ clause in the h\bho\bos\bst\bt statement is used.
- Any number of d\bdh\bhc\bcp\bpd\bd.\b.c\bco\bon\bnf\bf option clauses may appear in a host statement.
- The syntax of option declarations is described later in this document.
- If an option clause in a h\bho\bos\bst\bt statement conflicts with an option clause
- in the s\bsu\bub\bbn\bne\bet\bt statement for the subnet containing that host, the option
- clause in the h\bho\bos\bst\bt statement is used.
O\bOp\bpt\bti\bio\bon\bn D\bDe\bec\bcl\bla\bar\bra\bat\bti\bio\bon\bns\bs
- Option declarations always start with the o\bop\bpt\bti\bio\bon\bn keyword, followed by an
- option name, followed by option data. The option names and data formats
- are described below. Many of the options described below which set IP
- or TCP parameters have default values which will generally work perfectly
- well, so only those options whose values must be set explicitly should be
- included in s\bsu\bub\bbn\bne\bet\bt or h\bho\bos\bst\bt statements.
+ Option declarations always start with the o\bop\bpt\bti\bio\bon\bn keyword,
+ followed by an option name, followed by option data. The
+ option names and data formats are described below. Many
+ of the options described below which set IP or TCP parame-
+ ters have default values which will generally work per-
+ fectly well, so only those options whose values must be
+ set explicitly should be included in. B subnet or h\bho\bos\bst\bt
+ statements.
+
+ Option data comes in a variety of formats. In order to
+ avoid having to explain the formats along with each option
+ definition below, a number of data types have been
+ defined.
+
+ The ip-address 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 int32 data type specifies a signed 32-bit integer.
+ The uint32 data type specifies an unsigned 32-bit integer.
+ The int16 and uint16 data types specify signed and
+ unsigned 16-bit integers. The int8 and uint8 data types
+ specify signed and unsigned 8-bit integers. Unsigned
+ 8-bit integers are also sometimes referred to as octets.
+
+ The string 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
+
+
+
+
+ 3
+
+
+
+
+
+dhcpd.conf(5)() dhcpd.conf(5)()
+
+
+ option domain-name "isc.org"
+
+ The flag data type specifies a one-bit (boolean) number.
+
+ The data-string 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
+
+ The documentation for the various options mentioned below is taken
+ from the latest IETF draft document on DHCP options.
+
+ 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
+
+ The subnet mask option specifies the client's subnet mask as per RFC
+ 950.
+
+ 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
+
+ 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
+ [,
+ _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+ _\b._\b._\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
+ [,
+ _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+ _\b._\b._\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
+
+
+
+ 4
+
+
+
+
+
+dhcpd.conf(5)() dhcpd.conf(5)()
+
+
+ n\bna\bam\bme\be-\b-s\bse\ber\brv\bve\ber\brs\bs
+ _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+ [,
+ _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+ _\b._\b._\b.
+ ]
+
+ The name-servers option specifies a list of IEN 116 name servers
+ available to the client. Servers should be listed in order of
+ preference.
+
+ 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
+ [,
+ _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+ _\b._\b._\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 preference.
+
+ 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
+ [,
+ _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+ _\b._\b._\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
+ [,
+ _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+ _\b._\b._\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
+ [,
+ _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+ _\b._\b._\b.
+ ]
+
+
+
+ 5
+
+
+
+
+
+dhcpd.conf(5)() dhcpd.conf(5)()
+
+
+ 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
+ [,
+ _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+ _\b._\b._\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
+ [,
+ _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+ _\b._\b._\b.
+ ]
+
+ This option specifies a list of RFC 887 Resource Location
+ servers available to the client. Servers should be listed in order
+ of preference.
- Option data comes in a variety of formats. In order to avoid having to
- explain the formats along with each option definition below, a number of
- data types have been defined.
+ o\bop\bpt\bti\bio\bon\bn
+ h\bho\bos\bst\bt-\b-n\bna\bam\bme\be
+ _\bs_\bt_\br_\bi_\bn_\bg
- The ip-address 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 sin-
- gle IP address.
+ 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.
- The int32 data type specifies a signed 32-bit integer. The uint32 data
- type specifies an unsigned 32-bit integer. The int16 and uint16 data
- types specify signed and unsigned 16-bit integers. The int8 and uint8
- data types specify signed and unsigned 8-bit integers. Unsigned 8-bit
- integers are also sometimes referred to as octets.
+ o\bop\bpt\bti\bio\bon\bn
+ b\bbo\boo\bot\bt-\b-s\bsi\biz\bze\be
+ _\bu_\bi_\bn_\bt_\b1_\b6
- The string data type specifies an NVT ASCII string, which must be en-
- closed in double quotes - for example, to specify a domain-name option,
- the syntax would be
+ This option specifies the length in 512-octet blocks of the default
+ boot image for the client.
- option domain-name "isc.org"
+ 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
- The flag data type specifies a one-bit (boolean) number.
+ 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.
+ o\bop\bpt\bti\bio\bon\bn
- The documentation for the various options mentioned below is taken from
- the latest IETF draft document on DHCP options.
- 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
- The subnet mask option specifies the client's subnet mask as per RFC 950.
+ 6
- 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
- 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 [ , _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\b._\b._\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 [ , _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\b._\b._\b.]
+dhcpd.conf(5)() dhcpd.conf(5)()
- 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 n\bna\bam\bme\be-\b-s\bse\ber\brv\bve\ber\brs\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs [ , _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\b._\b._\b.]
+ d\bdo\bom\bma\bai\bin\bn-\b-n\bna\bam\bme\be
+ _\bs_\bt_\br_\bi_\bn_\bg
- The name-servers option specifies a list of IEN 116 name servers avail-
- able to the client. Servers should be listed in order of preference.
+ 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 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 [ , _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\b._\b._\b.]
+ 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
- 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.
+ This specifies the IP address of the client's swap server.
- 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 [ , _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\b._\b._\b.]
+ o\bop\bpt\bti\bio\bon\bn
+ r\bro\boo\bot\bt-\b-p\bpa\bat\bth\bh
+ _\bs_\bt_\br_\bi_\bn_\bg
- The log-server option specifies a list of MIT-LCS UDP log servers avail-
- able to the client. Servers should be listed in order of preference.
+ 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.
- 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 [ , _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\b._\b._\b.]
+ 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
- The cookie server option specifies a list of RFC 865 cookie servers
- available to the client. Servers should be listed in order of prefer-
- ence.
+ 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 l\blp\bpr\br-\b-s\bse\ber\brv\bve\ber\brs\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs [ , _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\b._\b._\b.]
+ 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
- The LPR server option specifies a list of RFC 1179 line printer servers
- available to the client. Servers should be listed in order of prefer-
- ence.
+ 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.
- 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 [ , _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\b._\b._\b.]
+ 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
+ [,
+ _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+ _\b._\b._\b.
+ ]
- The impress-server option specifies a list of Imagen Impress servers
- available to the client. Servers should be listed in order of prefer-
- ence.
+ 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.
- 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 [ , _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\b._\b._\b.]
+ Any source routed datagram whose next-hop address does not match one
+ of the filters should be discarded by the client.
- This option specifies a list of RFC 887 Resource Location servers avail-
- able to the client. Servers should be listed in order of preference.
+ See STD 3 (RFC1122) for further information.
- o\bop\bpt\bti\bio\bon\bn h\bho\bos\bst\bt-\b-n\bna\bam\bme\be _\bs_\bt_\br_\bi_\bn_\bg
- 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.
- o\bop\bpt\bti\bio\bon\bn b\bbo\boo\bot\bt-\b-s\bsi\biz\bze\be _\bu_\bi_\bn_\bt_\b1_\b6
+ 7
- 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
- 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 for-
- matted as a character string consisting of characters from the NVT ASCII
- character 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
- This option specifies the domain name that client should use when resolv-
- ing hostnames via the Domain Name System.
+dhcpd.conf(5)() dhcpd.conf(5)()
- 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
- This specifies the IP address of the client's swap server.
+ 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
- o\bop\bpt\bti\bio\bon\bn r\bro\boo\bot\bt-\b-p\bpa\bat\bth\bh _\bs_\bt_\br_\bi_\bn_\bg
+ This option specifies the maximum size datagram that the client
+ should be prepared to reassemble. The minimum value legal value is
+ 576.
- 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.
+ 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
- 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
+ This option specifies the default time-to-live that the client should
+ use on outgoing datagrams.
- 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
+ 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
- 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
+ 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 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 disal-
- low forwarding of such datagrams, and a value of 1 means allow forward-
- ing.
+ 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
+ [,
+ _\bu_\bi_\bn_\bt_\b1_\b6
+ _\b._\b._\b.
+ ]
- 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 [ , _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\b._\b._\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.
- This option specifies policy filters for non-local source routing. The
- filters consist of a list of IP addresses and masks which specify desti-
- nation/mask pairs with which to filter incoming source routes.
+ 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
- Any source routed datagram whose next-hop address does not match one of
- the filters should be discarded by the client.
+ This option specifies the MTU to use on this interface. The minimum
+ legal value for the MTU is 68.
- See STD 3 (RFC1122) for further information.
+ 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
+ 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 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
+ 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
- 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
- This option specifies the default time-to-live that the client should use
- on outgoing datagrams.
+ 8
- 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
- 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 [ , _\bu_\bi_\bn_\bt_\b1_\b6 _\b._\b._\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 mini-
- mum MTU value cannot be smaller than 68.
+dhcpd.conf(5)() dhcpd.conf(5)()
- 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
- This option specifies the MTU to use on this interface. The minimum le-
- gal value for the MTU is 68.
+ _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
- 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 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).
- 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
+ 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
- This option specifies the broadcast address in use on the client's sub-
- net. 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 discovery. A value of 1 means that the
+ client should perform mask discovery.
- 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
+ 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
- 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 discovery. A value of 1 means that the client should
- perform mask discovery.
+ 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 m\bma\bas\bsk\bk-\b-s\bsu\bup\bpp\bpl\bli\bie\ber\br _\bf_\bl_\ba_\bg
+ 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
- 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 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-d\bdi\bis\bsc\bco\bov\bve\ber\bry\by _\bf_\bl_\ba_\bg
+ 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
- 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 the address to which the client should transmit
+ router solicitation requests.
- 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
+ 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
+ [,
+ _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+ _\b._\b._\b.
+ ]
- This option specifies the address to which the client should transmit
- router solicitation requests.
+ 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.
- 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 [ , _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\b._\b._\b.]
- This option specifies a list of static routes that the client should in-
- stall 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.
+ 9
- 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
- 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 in-
- dicates 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
- This option specifies the timeout in seconds for ARP cache entries.
+dhcpd.conf(5)() dhcpd.conf(5)()
- 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
- This option specifies whether or not the client should use Ethernet Ver-
- sion 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.
+ 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.
- 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
+ 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.
- 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\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
- 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
+ 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 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 indi-
- cates that the client should not generate keepalive messages on connec-
- tions unless specifically requested by an application.
+ 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
- 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
+ This option specifies the timeout in seconds for ARP cache entries.
- 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
+ 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
- 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
+ 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.
- This option specifies the name of the client's NIS (Sun Network Informa-
- tion Services) domain. The domain is formatted as a character string
- consisting of characters from the NVT ASCII character set.
+ 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
- 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 [ , _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\b._\b._\b.]
+ This option specifies the default TTL that the client should use when
+ sending TCP segments. The minimum value is 1.
- This option specifies a list of IP addresses indicating NIS servers
- available to the client. Servers should be listed in order of prefer-
- ence.
+ 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
- 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 [ , _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\b._\b._\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
+ connections unless specifically requested by an application.
- 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
+ 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
- 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 [ , _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\b._\b._\b.]
- The NetBIOS name server (NBNS) option specifies a list of RFC 1001/1002
- NBNS name servers listed in order of preference.
+ 10
- 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 [ , _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\b._\b._\b.]
- The NetBIOS datagram distribution server (NBDD) option 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
- 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 corresponds 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
+dhcpd.conf(5)() dhcpd.conf(5)()
- The NetBIOS scope option specifies the NetBIOS over TCP/IP scope parame-
- ter for the client as specified in RFC 1001/1002. See RFC1001, RFC1002,
- and RFC1035 for character-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 [ , _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\b._\b._\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.
- 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
+ n\bni\bis\bs-\b-d\bdo\bom\bma\bai\bin\bn
+ _\bs_\bt_\br_\bi_\bn_\bg
- 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 [ , _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\b._\b._\b.]
+ 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.
- 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.
+ 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
+ [,
+ _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+ _\b._\b._\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
+ [,
+ _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+ _\b._\b._\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
+ [,
+ _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+ _\b._\b._\b.
+ ]
+
+ The NetBIOS name server (NBNS) option specifies a list of RFC
+ 1001/1002 NBNS name servers listed in order of preference.
+
+ 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
+ [,
+ _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+
+
+
+ 11
+
+
+
+
+
+dhcpd.conf(5)() dhcpd.conf(5)()
+
+
+ _\b._\b._\b.
+ ]
+
+ The NetBIOS datagram distribution server (NBDD) option 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
+
+ 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 corresponds
+ 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
+
+ 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.
+
+ 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
+ [,
+ _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+ _\b._\b._\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
+ [,
+ _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
+ _\b._\b._\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 preference.
+
+ 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
+
+ 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
+
+
+
+ 12
+
+
+
+
+
+dhcpd.conf(5)() dhcpd.conf(5)()
+
+
+ against the client identifier.
S\bSE\bEE\bE A\bAL\bLS\bSO\bO
- dhcpd.conf(5), dhcpd.leases(5)
+ dhcpd.conf(5), dhcpd.leases(5)
A\bAU\bUT\bTH\bHO\bOR\bR
- dhcpd(8) was written by Ted Lemon <\b<m\bme\bel\bll\blo\bon\bn@\b@v\bvi\bix\bx.\b.c\bco\bom\bm>\b> under a contract with
- Vixie Labs. Funding for this project was provided by the Internet Soft-
- ware Corporation. Information 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.
+ 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.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ 13
+
- March 6, 1996 7
projects / thirdparty / dhcp.git / commitdiff
