-dhclient.conf(5) dhclient.conf(5)
+Headers, Environments, and Macros dhclient.conf(5)
-N\bNA\bAM\bME\bE
- dhclient.conf - DHCP client configuration file
-D\bDE\bES\bSC\bCR\bRI\bIP\bPT\bTI\bIO\bON\bN
- The dhclient.conf file contains configuration information
- for _\bd_\bh_\bc_\bl_\bi_\be_\bn_\bt_\b, the Internet Software Consortium DHCP
- Client.
+N\bN\bN\bNA\bA\bA\bAM\bM\bM\bME\bE\bE\bE
+ dhclient.conf - DHCP client configuration file
- The dhclient.conf file is a free-form ASCII text file.
- It is parsed by the recursive-descent parser built into
- dhclient. The file may contain extra tabs and newlines
- for formatting purposes. Keywords in the file are case-
- insensitive. Comments may be placed anywhere within the
- file (except within quotes). Comments begin with the #
- character and end at the end of the line.
+D\bD\bD\bDE\bE\bE\bES\bS\bS\bSC\bC\bC\bCR\bR\bR\bRI\bI\bI\bIP\bP\bP\bPT\bT\bT\bTI\bI\bI\bIO\bO\bO\bON\bN\bN\bN
+ The dhclient.conf file contains configuration information
+ for _\bd_\bh_\bc_\bl_\bi_\be_\bn_\bt, the Internet Software Consortium DHCP Client.
- The dhclient.conf file can be used to configure the
- behaviour of the client in a wide variety of ways: proto
- col timing, information requested from the server, infor
- mation required of the server, defaults to use if the
- server does not provide certain information, values with
- which to override information provided by the server, or
- values to prepend or append to information provided by the
- server. The configuration file can also be preinitialized
- with addresses to use on networks that don't have DHCP
- servers.
+ The dhclient.conf file is a free-form ASCII text file. It
+ is parsed by the recursive-descent parser built into
+ dhclient. The file may contain extra tabs and newlines for
+ formatting purposes. Keywords in the file are case-
+ insensitive. Comments may be placed anywhere within the
+ file (except within quotes). Comments begin with the #
+ character and end at the end of the line.
-P\bPR\bRO\bOT\bTO\bOC\bCO\bOL\bL T\bTI\bIM\bMI\bIN\bNG\bG
- The timing behaviour of the client need not be configured
- by the user. If no timing configuration is provided by
- the user, a fairly reasonable timing behaviour will be
- used by default - one which results in fairly timely
- updates without placing an inordinate load on the server.
+ The dhclient.conf file can be used to configure the
+ behaviour of the client in a wide variety of ways: protocol
+ timing, information requested from the server, information
+ required of the server, defaults to use if the server does
+ not provide certain information, values with which to over-
+ ride information provided by the server, or values to
+ prepend or append to information provided by the server.
+ The configuration file can also be preinitialized with
+ addresses to use on networks that don't have DHCP servers.
- The following statements can be used to adjust the timing
- behaviour of the DHCP client if required, however:
+P\bP\bP\bPR\bR\bR\bRO\bO\bO\bOT\bT\bT\bTO\bO\bO\bOC\bC\bC\bCO\bO\bO\bOL\bL\bL\bL T\bT\bT\bTI\bI\bI\bIM\bM\bM\bMI\bI\bI\bIN\bN\bN\bNG\bG\bG\bG
+ The timing behaviour of the client need not be configured by
+ the user. If no timing configuration is provided by the
+ user, a fairly reasonable timing behaviour will be used by
+ default - one which results in fairly timely updates without
+ placing an inordinate load on the server.
- _\bT_\bh_\be t\bti\bim\bme\beo\bou\but\bt _\bs_\bt_\ba_\bt_\be_\bm_\be_\bn_\bt
+ The following statements can be used to adjust the timing
+ behaviour of the DHCP client if required, however:
- t\bti\bim\bme\beo\bou\but\bt _\bt_\bi_\bm_\be ;\b;
+ _\bT_\bh_\be t\bt\bt\bti\bi\bi\bim\bm\bm\bme\be\be\beo\bo\bo\bou\bu\bu\but\bt\bt\bt _\bs_\bt_\ba_\bt_\be_\bm_\be_\bn_\bt
- The _\bt_\bi_\bm_\be_\bo_\bu_\bt statement determines the amount of time that
- must pass between the time that the client begins to try
- to determine its address and the time that it decides that
- it's not going to be able to contact a server. By
- default, this timeout is sixty seconds. After the time
- out has passed, if there are any static leases defined in
- the configuration file, or any leases remaining in the
- lease database that have not yet expired, the client will
- loop through these leases attempting to validate them, and
- if it finds one that appears to be valid, it will use that
- lease's address. If there are no valid static leases or
- unexpired leases in the lease database, the client will
- restart the protocol after the defined retry interval.
+ t\bt\bt\bti\bi\bi\bim\bm\bm\bme\be\be\beo\bo\bo\bou\bu\bu\but\bt\bt\bt _\bt_\bi_\bm_\be ;\b;\b;\b;
+ The _\bt_\bi_\bm_\be_\bo_\bu_\bt statement determines the amount of time that
+ must pass between the time that the client begins to try to
+ determine its address and the time that it decides that it's
+ not going to be able to contact a server. By default, this
+ timeout is sixty seconds. After the timeout has passed, if
+ there are any static leases defined in the configuration
+ file, or any leases remaining in the lease database that
+ have not yet expired, the client will loop through these
+ leases attempting to validate them, and if it finds one that
+ appears to be valid, it will use that lease's address. If
+ there are no valid static leases or unexpired leases in the
+ lease database, the client will restart the protocol after
+ the defined retry interval.
- 1
+SunOS 5.6 Last change: 1
-dhclient.conf(5) dhclient.conf(5)
- _\bT_\bh_\be r\bre\bet\btr\bry\by _\bs_\bt_\ba_\bt_\be_\bm_\be_\bn_\bt
+Headers, Environments, and Macros dhclient.conf(5)
- r\bre\bet\btr\bry\by _\bt_\bi_\bm_\be;\b;
- The _\br_\be_\bt_\br_\by statement determines the time that must pass
- after the client has determined that there is no DHCP
- server present before it tries again to contact a DHCP
- server. By default, this is five minutes.
- _\bT_\bh_\be s\bse\bel\ble\bec\bct\bt-\b-t\bti\bim\bme\beo\bou\but\bt _\bs_\bt_\ba_\bt_\be_\bm_\be_\bn_\bt
+ _\bT_\bh_\be r\br\br\bre\be\be\bet\bt\bt\btr\br\br\bry\by\by\by _\bs_\bt_\ba_\bt_\be_\bm_\be_\bn_\bt
- s\bse\bel\ble\bec\bct\bt-\b-t\bti\bim\bme\beo\bou\but\bt _\bt_\bi_\bm_\be;\b;
+ r\br\br\bre\be\be\bet\bt\bt\btr\br\br\bry\by\by\by _\bt_\bi_\bm_\be;\b;\b;\b;
- It is possible (some might say desirable) for there to be
- more than one DHCP server serving any given network. In
- this case, it is possible that a client may be sent more
- than one offer in response to its initial lease discovery
- message. It may be that one of these offers is prefer
- able to the other (e.g., one offer may have the address
- the client previously used, and the other may not).
+ The _\br_\be_\bt_\br_\by statement determines the time that must pass after
+ the client has determined that there is no DHCP server
+ present before it tries again to contact a DHCP server. By
+ default, this is five minutes.
- The _\bs_\be_\bl_\be_\bc_\bt_\b-_\bt_\bi_\bm_\be_\bo_\bu_\bt is the time after the client sends its
- first lease discovery request at which it stops waiting
- for offers from servers, assuming that it has received at
- least one such offer. If no offers have been received by
- the time the _\bs_\be_\bl_\be_\bc_\bt_\b-_\bt_\bi_\bm_\be_\bo_\bu_\bt has expired, the client will
- accept the first offer that arrives.
+ _\bT_\bh_\be s\bs\bs\bse\be\be\bel\bl\bl\ble\be\be\bec\bc\bc\bct\bt\bt\bt-\b-\b-\b-t\bt\bt\bti\bi\bi\bim\bm\bm\bme\be\be\beo\bo\bo\bou\bu\bu\but\bt\bt\bt _\bs_\bt_\ba_\bt_\be_\bm_\be_\bn_\bt
- By default, the select-timeout is zero seconds - that is,
- the client will take the first offer it sees.
+ s\bs\bs\bse\be\be\bel\bl\bl\ble\be\be\bec\bc\bc\bct\bt\bt\bt-\b-\b-\b-t\bt\bt\bti\bi\bi\bim\bm\bm\bme\be\be\beo\bo\bo\bou\bu\bu\but\bt\bt\bt _\bt_\bi_\bm_\be;\b;\b;\b;
- _\bT_\bh_\be r\bre\beb\bbo\boo\bot\bt _\bs_\bt_\ba_\bt_\be_\bm_\be_\bn_\bt
+ It is possible (some might say desirable) for there to be
+ more than one DHCP server serving any given network. In
+ this case, it is possible that a client may be sent more
+ than one offer in response to its initial lease discovery
+ message. It may be that one of these offers is preferable
+ to the other (e.g., one offer may have the address the
+ client previously used, and the other may not).
- r\bre\beb\bbo\boo\bot\bt _\bt_\bi_\bm_\be;\b;
+ The _\bs_\be_\bl_\be_\bc_\bt-_\bt_\bi_\bm_\be_\bo_\bu_\bt is the time after the client sends its
+ first lease discovery request at which it stops waiting for
+ offers from servers, assuming that it has received at least
+ one such offer. If no offers have been received by the
+ time the _\bs_\be_\bl_\be_\bc_\bt-_\bt_\bi_\bm_\be_\bo_\bu_\bt has expired, the client will accept
+ the first offer that arrives.
- When the client is restarted, it first tries to reacquire
- the last address it had. This is called the INIT-REBOOT
- state. If it is still attached to the same network it
- was attached to when it last ran, this is the quickest way
- to get started. The _\br_\be_\bb_\bo_\bo_\bt statement sets the time that
- must elapse after the client first tries to reacquire its
- old address before it gives up and tries to discover a new
- address. By default, the reboot timeout is ten seconds.
+ By default, the select-timeout is zero seconds - that is,
+ the client will take the first offer it sees.
- _\bT_\bh_\be b\bba\bac\bck\bko\bof\bff\bf-\b-c\bcu\but\bto\bof\bff\bf _\bs_\bt_\ba_\bt_\be_\bm_\be_\bn_\bt
+ _\bT_\bh_\be r\br\br\bre\be\be\beb\bb\bb\bbo\bo\bo\boo\bo\bo\bot\bt\bt\bt _\bs_\bt_\ba_\bt_\be_\bm_\be_\bn_\bt
- b\bba\bac\bck\bko\bof\bff\bf-\b-c\bcu\but\bto\bof\bff\bf _\bt_\bi_\bm_\be;\b;
+ r\br\br\bre\be\be\beb\bb\bb\bbo\bo\bo\boo\bo\bo\bot\bt\bt\bt _\bt_\bi_\bm_\be;\b;\b;\b;
- The client uses an exponential backoff algorithm with some
- randomness, so that if many clients try to configure them
- selves at the same time, they will not make their requests
- in lockstep. The _\bb_\ba_\bc_\bk_\bo_\bf_\bf_\b-_\bc_\bu_\bt_\bo_\bf_\bf statement determines the
- maximum amount of time that the client is allowed to back
- off. It defaults to two minutes.
+ When the client is restarted, it first tries to reacquire
+ the last address it had. This is called the INIT-REBOOT
+ state. If it is still attached to the same network it was
+ attached to when it last ran, this is the quickest way to
+ get started. The _\br_\be_\bb_\bo_\bo_\bt statement sets the time that must
+ elapse after the client first tries to reacquire its old
+ address before it gives up and tries to discover a new
+ address. By default, the reboot timeout is ten seconds.
+ _\bT_\bh_\be b\bb\bb\bba\ba\ba\bac\bc\bc\bck\bk\bk\bko\bo\bo\bof\bf\bf\bff\bf\bf\bf-\b-\b-\b-c\bc\bc\bcu\bu\bu\but\bt\bt\bto\bo\bo\bof\bf\bf\bff\bf\bf\bf _\bs_\bt_\ba_\bt_\be_\bm_\be_\bn_\bt
+ b\bb\bb\bba\ba\ba\bac\bc\bc\bck\bk\bk\bko\bo\bo\bof\bf\bf\bff\bf\bf\bf-\b-\b-\b-c\bc\bc\bcu\bu\bu\but\bt\bt\bto\bo\bo\bof\bf\bf\bff\bf\bf\bf _\bt_\bi_\bm_\be;\b;\b;\b;
- 2
+ The client uses an exponential backoff algorithm with some
+ randomness, so that if many clients try to configure them-
+ selves at the same time, they will not make their requests
+ in lockstep. The _\bb_\ba_\bc_\bk_\bo_\bf_\bf-_\bc_\bu_\bt_\bo_\bf_\bf statement determines the
+SunOS 5.6 Last change: 2
-dhclient.conf(5) dhclient.conf(5)
- _\bT_\bh_\be i\bin\bni\bit\bti\bia\bal\bl-\b-i\bin\bnt\bte\ber\brv\bva\bal\bl _\bs_\bt_\ba_\bt_\be_\bm_\be_\bn_\bt
- i\bin\bni\bit\bti\bia\bal\bl-\b-i\bin\bnt\bte\ber\brv\bva\bal\bl _\bt_\bi_\bm_\be;\b;
- The _\bi_\bn_\bi_\bt_\bi_\ba_\bl_\b-_\bi_\bn_\bt_\be_\br_\bv_\ba_\bl statement sets the amount of time
- between the first attempt to reach a server and the second
- attempt to reach a server. Each time a message is sent,
- the interval between messages is incremented by twice the
- current interval multiplied by a random number between
- zero and one. If it is greater than the backoff-cutoff
- amount, it is set to that amount. It defaults to ten sec
- onds.
+Headers, Environments, and Macros dhclient.conf(5)
-L\bLE\bEA\bAS\bSE\bE R\bRE\bEQ\bQU\bUI\bIR\bRE\bEM\bME\bEN\bNT\bTS\bS A\bAN\bND\bD R\bRE\bEQ\bQU\bUE\bES\bST\bTS\bS
- The DHCP protocol allows the client to request that the
- server send it specific information, and not send it other
- information that it is not prepared to accept. The pro
- tocol also allows the client to reject offers from servers
- if they don't contain information the client needs, or if
- the information provided is not satisfactory.
- There is a variety of data contained in offers that DHCP
- servers send to DHCP clients. The data that can be
- specifically requested is what are called _\bD_\bH_\bC_\bP _\bO_\bp_\bt_\bi_\bo_\bn_\bs.
- DHCP Options are defined in
- d\bdh\bhc\bcp\bp-\b-o\bop\bpt\bti\bio\bon\bns\bs(\b(5\b5)\b).
- _\bT_\bh_\be r\bre\beq\bqu\bue\bes\bst\bt _\bs_\bt_\ba_\bt_\be_\bm_\be_\bn_\bt
+ maximum amount of time that the client is allowed to back
+ off. It defaults to two minutes.
- r\bre\beq\bqu\bue\bes\bst\bt [\b[ _\bo_\bp_\bt_\bi_\bo_\bn ] [,\b, _\b._\b._\b. _\bo_\bp_\bt_\bi_\bo_\bn ];\b;
+ _\bT_\bh_\be i\bi\bi\bin\bn\bn\bni\bi\bi\bit\bt\bt\bti\bi\bi\bia\ba\ba\bal\bl\bl\bl-\b-\b-\b-i\bi\bi\bin\bn\bn\bnt\bt\bt\bte\be\be\ber\br\br\brv\bv\bv\bva\ba\ba\bal\bl\bl\bl _\bs_\bt_\ba_\bt_\be_\bm_\be_\bn_\bt
- The request statement causes the client to request that
- any server responding to the client send the client its
- values for the specified options. Only the option names
- should be specified in the request statement - not option
- parameters.
+ i\bi\bi\bin\bn\bn\bni\bi\bi\bit\bt\bt\bti\bi\bi\bia\ba\ba\bal\bl\bl\bl-\b-\b-\b-i\bi\bi\bin\bn\bn\bnt\bt\bt\bte\be\be\ber\br\br\brv\bv\bv\bva\ba\ba\bal\bl\bl\bl _\bt_\bi_\bm_\be;\b;\b;\b;
- _\bT_\bh_\be r\bre\beq\bqu\bui\bir\bre\be _\bs_\bt_\ba_\bt_\be_\bm_\be_\bn_\bt
+ The _\bi_\bn_\bi_\bt_\bi_\ba_\bl-_\bi_\bn_\bt_\be_\br_\bv_\ba_\bl statement sets the amount of time
+ between the first attempt to reach a server and the second
+ attempt to reach a server. Each time a message is sent, the
+ interval between messages is incremented by twice the
+ current interval multiplied by a random number between zero
+ and one. If it is greater than the backoff-cutoff amount,
+ it is set to that amount. It defaults to ten seconds.
- r\bre\beq\bqu\bui\bir\bre\be [\b[ _\bo_\bp_\bt_\bi_\bo_\bn ] [,\b, _\b._\b._\b. _\bo_\bp_\bt_\bi_\bo_\bn _\b];\b;
+L\bL\bL\bLE\bE\bE\bEA\bA\bA\bAS\bS\bS\bSE\bE\bE\bE R\bR\bR\bRE\bE\bE\bEQ\bQ\bQ\bQU\bU\bU\bUI\bI\bI\bIR\bR\bR\bRE\bE\bE\bEM\bM\bM\bME\bE\bE\bEN\bN\bN\bNT\bT\bT\bTS\bS\bS\bS A\bA\bA\bAN\bN\bN\bND\bD\bD\bD R\bR\bR\bRE\bE\bE\bEQ\bQ\bQ\bQU\bU\bU\bUE\bE\bE\bES\bS\bS\bST\bT\bT\bTS\bS\bS\bS
+ The DHCP protocol allows the client to request that the
+ server send it specific information, and not send it other
+ information that it is not prepared to accept. The proto-
+ col also allows the client to reject offers from servers if
+ they don't contain information the client needs, or if the
+ information provided is not satisfactory.
- The require statement lists options that must be sent in
- order for an offer to be accepted. Offers that do not
- contain all the listed options will be ignored.
+ There is a variety of data contained in offers that DHCP
+ servers send to DHCP clients. The data that can be specifi-
+ cally requested is what are called _\bD_\bH_\bC_\bP _\bO_\bp_\bt_\bi_\bo_\bn_\bs. DHCP
+ Options are defined in
+ d\bd\bd\bdh\bh\bh\bhc\bc\bc\bcp\bp\bp\bp-\b-\b-\b-o\bo\bo\bop\bp\bp\bpt\bt\bt\bti\bi\bi\bio\bo\bo\bon\bn\bn\bns\bs\bs\bs(\b(\b(\b(5\b5\b5\b5)\b)\b)\b).
- _\bT_\bh_\be s\bse\ben\bnd\bd _\bs_\bt_\ba_\bt_\be_\bm_\be_\bn_\bt
+ _\bT_\bh_\be r\br\br\bre\be\be\beq\bq\bq\bqu\bu\bu\bue\be\be\bes\bs\bs\bst\bt\bt\bt _\bs_\bt_\ba_\bt_\be_\bm_\be_\bn_\bt
- s\bse\ben\bnd\bd {\b{ [\b[ _\bo_\bp_\bt_\bi_\bo_\bn _\bd_\be_\bc_\bl_\ba_\br_\ba_\bt_\bi_\bo_\bn ] [,\b, _\b._\b._\b. _\bo_\bp_\bt_\bi_\bo_\bn _\bd_\be_\bc_\bl_\ba_\br_\ba_\bt_\bi_\bo_\bn
- ]}\b}
+ r\br\br\bre\be\be\beq\bq\bq\bqu\bu\bu\bue\be\be\bes\bs\bs\bst\bt\bt\bt [\b[\b[\b[ _\bo_\bp_\bt_\bi_\bo_\bn ] [,\b,\b,\b, ... _\bo_\bp_\bt_\bi_\bo_\bn ];\b;\b;\b;
- The send statement causes the client to send the specified
- options to the server with the specified values. These
- are full option declarations as described in d\bdh\bhc\bcp\bp-\b-
- o\bop\bpt\bti\bio\bon\bns\bs(\b(5\b5)\b). Options that are always sent in the DHCP
+ The request statement causes the client to request that any
+ server responding to the client send the client its values
+ for the specified options. Only the option names should be
+ specified in the request statement - not option parameters.
+ _\bT_\bh_\be r\br\br\bre\be\be\beq\bq\bq\bqu\bu\bu\bui\bi\bi\bir\br\br\bre\be\be\be _\bs_\bt_\ba_\bt_\be_\bm_\be_\bn_\bt
+ r\br\br\bre\be\be\beq\bq\bq\bqu\bu\bu\bui\bi\bi\bir\br\br\bre\be\be\be [\b[\b[\b[ _\bo_\bp_\bt_\bi_\bo_\bn ] [,\b,\b,\b, ... _\bo_\bp_\bt_\bi_\bo_\bn ];\b;\b;\b;
- 3
+ The require statement lists options that must be sent in
+ order for an offer to be accepted. Offers that do not con-
+ tain all the listed options will be ignored.
+ _\bT_\bh_\be s\bs\bs\bse\be\be\ben\bn\bn\bnd\bd\bd\bd _\bs_\bt_\ba_\bt_\be_\bm_\be_\bn_\bt
+ s\bs\bs\bse\be\be\ben\bn\bn\bnd\bd\bd\bd {\b{\b{\b{ [\b[\b[\b[ _\bo_\bp_\bt_\bi_\bo_\bn _\bd_\be_\bc_\bl_\ba_\br_\ba_\bt_\bi_\bo_\bn ] [,\b,\b,\b, ... _\bo_\bp_\bt_\bi_\bo_\bn _\bd_\be_\bc_\bl_\ba_\br_\ba_\bt_\bi_\bo_\bn ]}\b}\b}\b}
+ The send statement causes the client to send the specified
+ options to the server with the specified values. These are
-dhclient.conf(5) dhclient.conf(5)
+SunOS 5.6 Last change: 3
- protocol should not be specified here, except that the
- client can specify a r\bre\beq\bqu\bue\bes\bst\bte\bed\bd-\b-l\ble\bea\bas\bse\be-\b-t\bti\bim\bme\be option other
- than the default requested lease time, which is two hours.
- The other obvious use for this statement is to send infor
- mation to the server that will allow it to differentiate
- between this client and other clients or kinds of clients.
-O\bOP\bPT\bTI\bIO\bON\bN M\bMO\bOD\bDI\bIF\bFI\bIE\bER\bRS\bS
- In some cases, a client may receive option data from the
- server which is not really appropriate for that client, or
- may not receive information that it needs, and for which a
- useful default value exists. It may also receive infor
- mation which is useful, but which needs to be supplemented
- with local information. To handle these needs, several
- option modifiers are available.
- _\bT_\bh_\be d\bde\bef\bfa\bau\bul\blt\bt _\bs_\bt_\ba_\bt_\be_\bm_\be_\bn_\bt
- d\bde\bef\bfa\bau\bul\blt\bt [\b[ _\bo_\bp_\bt_\bi_\bo_\bn _\bd_\be_\bc_\bl_\ba_\br_\ba_\bt_\bi_\bo_\bn ] ;\b;
- If for some option the client should use the value sup
- plied by the server, but needs to use some default value
- if no value was supplied by the server, these values can
- be defined in the d\bde\bef\bfa\bau\bul\blt\bt statement.
- _\bT_\bh_\be s\bsu\bup\bpe\ber\brs\bse\bed\bde\be _\bs_\bt_\ba_\bt_\be_\bm_\be_\bn_\bt
+Headers, Environments, and Macros dhclient.conf(5)
- s\bsu\bup\bpe\ber\brs\bse\bed\bde\be [\b[ _\bo_\bp_\bt_\bi_\bo_\bn _\bd_\be_\bc_\bl_\ba_\br_\ba_\bt_\bi_\bo_\bn ] ;\b;
- If for some option the client should always use a locally-
- configured value or values rather than whatever is sup
- plied by the server, these values can be defined in the
- s\bsu\bup\bpe\ber\brs\bse\bed\bde\be statement.
- _\bT_\bh_\be p\bpr\bre\bep\bpe\ben\bnd\bd _\bs_\bt_\ba_\bt_\be_\bm_\be_\bn_\bt
+ full option declarations as described in d\bd\bd\bdh\bh\bh\bhc\bc\bc\bcp\bp\bp\bp-\b-\b-\b-o\bo\bo\bop\bp\bp\bpt\bt\bt\bti\bi\bi\bio\bo\bo\bon\bn\bn\bns\bs\bs\bs(\b(\b(\b(5\b5\b5\b5)\b)\b)\b).
+ Options that are always sent in the DHCP protocol should not
+ be specified here, except that the client can specify a
+ r\br\br\bre\be\be\beq\bq\bq\bqu\bu\bu\bue\be\be\bes\bs\bs\bst\bt\bt\bte\be\be\bed\bd\bd\bd-\b-\b-\b-l\bl\bl\ble\be\be\bea\ba\ba\bas\bs\bs\bse\be\be\be-\b-\b-\b-t\bt\bt\bti\bi\bi\bim\bm\bm\bme\be\be\be option other than the default requested
+ lease time, which is two hours. The other obvious use for
+ this statement is to send information to the server that
+ will allow it to differentiate between this client and other
+ clients or kinds of clients.
- p\bpr\bre\bep\bpe\ben\bnd\bd [\b[ _\bo_\bp_\bt_\bi_\bo_\bn _\bd_\be_\bc_\bl_\ba_\br_\ba_\bt_\bi_\bo_\bn ] ;\b;
+O\bO\bO\bOP\bP\bP\bPT\bT\bT\bTI\bI\bI\bIO\bO\bO\bON\bN\bN\bN M\bM\bM\bMO\bO\bO\bOD\bD\bD\bDI\bI\bI\bIF\bF\bF\bFI\bI\bI\bIE\bE\bE\bER\bR\bR\bRS\bS\bS\bS
+ In some cases, a client may receive option data from the
+ server which is not really appropriate for that client, or
+ may not receive information that it needs, and for which a
+ useful default value exists. It may also receive informa-
+ tion which is useful, but which needs to be supplemented
+ with local information. To handle these needs, several
+ option modifiers are available.
- If for some option the client should use both a value it
- supplies, and then any values supplied by the server,
- these values can be defined in the p\bpr\bre\bep\bpe\ben\bnd\bd statement.
- The p\bpr\bre\bep\bpe\ben\bnd\bd statement can only be used for options which
- allow more than one value to be given.
+ _\bT_\bh_\be d\bd\bd\bde\be\be\bef\bf\bf\bfa\ba\ba\bau\bu\bu\bul\bl\bl\blt\bt\bt\bt _\bs_\bt_\ba_\bt_\be_\bm_\be_\bn_\bt
- _\bT_\bh_\be a\bap\bpp\bpe\ben\bnd\bd _\bs_\bt_\ba_\bt_\be_\bm_\be_\bn_\bt
+ d\bd\bd\bde\be\be\bef\bf\bf\bfa\ba\ba\bau\bu\bu\bul\bl\bl\blt\bt\bt\bt [\b[\b[\b[ _\bo_\bp_\bt_\bi_\bo_\bn _\bd_\be_\bc_\bl_\ba_\br_\ba_\bt_\bi_\bo_\bn ] ;\b;\b;\b;
- a\bap\bpp\bpe\ben\bnd\bd [\b[ _\bo_\bp_\bt_\bi_\bo_\bn _\bd_\be_\bc_\bl_\ba_\br_\ba_\bt_\bi_\bo_\bn ] ;\b;
+ If for some option the client should use the value supplied
+ by the server, but needs to use some default value if no
+ value was supplied by the server, these values can be
+ defined in the d\bd\bd\bde\be\be\bef\bf\bf\bfa\ba\ba\bau\bu\bu\bul\bl\bl\blt\bt\bt\bt statement.
- If for some option the client should first any values sup
- plied to it by the server, and then some values it sup
- plies, those values should be defined in the a\bap\bpp\bpe\ben\bnd\bd state
- ment. The a\bap\bpp\bpe\ben\bnd\bd statement can only be used for options
- which allow more than one value to be given.
+ _\bT_\bh_\be s\bs\bs\bsu\bu\bu\bup\bp\bp\bpe\be\be\ber\br\br\brs\bs\bs\bse\be\be\bed\bd\bd\bde\be\be\be _\bs_\bt_\ba_\bt_\be_\bm_\be_\bn_\bt
+ s\bs\bs\bsu\bu\bu\bup\bp\bp\bpe\be\be\ber\br\br\brs\bs\bs\bse\be\be\bed\bd\bd\bde\be\be\be [\b[\b[\b[ _\bo_\bp_\bt_\bi_\bo_\bn _\bd_\be_\bc_\bl_\ba_\br_\ba_\bt_\bi_\bo_\bn ] ;\b;\b;\b;
+ If for some option the client should always use a locally-
+ configured value or values rather than whatever is supplied
+ by the server, these values can be defined in the s\bs\bs\bsu\bu\bu\bup\bp\bp\bpe\be\be\ber\br\br\brs\bs\bs\bse\be\be\bed\bd\bd\bde\be\be\be
+ statement.
+ _\bT_\bh_\be p\bp\bp\bpr\br\br\bre\be\be\bep\bp\bp\bpe\be\be\ben\bn\bn\bnd\bd\bd\bd _\bs_\bt_\ba_\bt_\be_\bm_\be_\bn_\bt
- 4
+ p\bp\bp\bpr\br\br\bre\be\be\bep\bp\bp\bpe\be\be\ben\bn\bn\bnd\bd\bd\bd [\b[\b[\b[ _\bo_\bp_\bt_\bi_\bo_\bn _\bd_\be_\bc_\bl_\ba_\br_\ba_\bt_\bi_\bo_\bn ] ;\b;\b;\b;
+ If for some option the client should use both a value it
+ supplies, and then any values supplied by the server, these
+ values can be defined in the p\bp\bp\bpr\br\br\bre\be\be\bep\bp\bp\bpe\be\be\ben\bn\bn\bnd\bd\bd\bd statement. The
+ p\bp\bp\bpr\br\br\bre\be\be\bep\bp\bp\bpe\be\be\ben\bn\bn\bnd\bd\bd\bd statement can only be used for options which allow
+ more than one value to be given.
+ _\bT_\bh_\be a\ba\ba\bap\bp\bp\bpp\bp\bp\bpe\be\be\ben\bn\bn\bnd\bd\bd\bd _\bs_\bt_\ba_\bt_\be_\bm_\be_\bn_\bt
+ a\ba\ba\bap\bp\bp\bpp\bp\bp\bpe\be\be\ben\bn\bn\bnd\bd\bd\bd [\b[\b[\b[ _\bo_\bp_\bt_\bi_\bo_\bn _\bd_\be_\bc_\bl_\ba_\br_\ba_\bt_\bi_\bo_\bn ] ;\b;\b;\b;
+ If for some option the client should first any values sup-
+ plied to it by the server, and then some values it supplies,
-dhclient.conf(5) dhclient.conf(5)
-L\bLE\bEA\bAS\bSE\bE D\bDE\bEC\bCL\bLA\bAR\bRA\bAT\bTI\bIO\bON\bNS\bS
- _\bT_\bh_\be l\ble\bea\bas\bse\be _\bd_\be_\bc_\bl_\ba_\br_\ba_\bt_\bi_\bo_\bn
+SunOS 5.6 Last change: 4
- l\ble\bea\bas\bse\be {\b{ _\bl_\be_\ba_\bs_\be_\b-_\bd_\be_\bc_\bl_\ba_\br_\ba_\bt_\bi_\bo_\bn [ ... _\bl_\be_\ba_\bs_\be_\b-_\bd_\be_\bc_\bl_\ba_\br_\ba_\bt_\bi_\bo_\bn _\b] }\b}
- The DHCP client may decide after some period of time (see
- P\bPR\bRO\bOT\bTO\bOC\bCO\bOL\bL T\bTI\bIM\bMI\bIN\bNG\bG) decide that it is not going to succeed in
- contacting a server. At that time, it consults its own
- database of old leases and tests each one that has not yet
- timed out by pinging the listed router for that lease to
- see if that lease could work. It is possible to define
- one or more _\bf_\bi_\bx_\be_\bd leases in the client configuration file
- for networks where there is no DHCP or BOOTP service, so
- that the client can still automatically configure its
- address. This is done with the l\ble\bea\bas\bse\be statement.
- NOTE: the lease statement is also used in the
- dhclient.leases file in order to record leases that have
- been received from DHCP servers. Some of the syntax for
- leases as described below is only needed in the
- dhclient.leases file. Such syntax is documented here for
- completeness.
- A lease statement consists of the lease keyword, followed
- by a left curly brace, followed by one or more lease dec
- laration statements, followed by a right curly brace.
- The following lease declarations are possible:
- b\bbo\boo\bot\btp\bp;\b;
- The b\bbo\boo\bot\btp\bp statement is used to indicate that the lease was
- acquired using the BOOTP protocol rather than the DHCP
- protocol. It is never necessary to specify this in the
- client configuration file. The client uses this syntax
- in its lease database file.
+Headers, Environments, and Macros dhclient.conf(5)
- i\bin\bnt\bte\ber\brf\bfa\bac\bce\be "\b"_\bs_\bt_\br_\bi_\bn_\bg"\b";\b;
- The i\bin\bnt\bte\ber\brf\bfa\bac\bce\be lease statement is used to indicate the
- interface on which the lease is valid. If set, this
- lease will only be tried on a particular interface. When
- the client receives a lease from a server, it always
- records the interface number on which it received that
- lease. If predefined leases are specified in the
- dhclient.conf file, the interface should also be speci
- fied, although this is not required.
- f\bfi\bix\bxe\bed\bd-\b-a\bad\bdd\bdr\bre\bes\bss\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs;\b;
+ those values should be defined in the a\ba\ba\bap\bp\bp\bpp\bp\bp\bpe\be\be\ben\bn\bn\bnd\bd\bd\bd statement.
+ The a\ba\ba\bap\bp\bp\bpp\bp\bp\bpe\be\be\ben\bn\bn\bnd\bd\bd\bd statement can only be used for options which
+ allow more than one value to be given.
- The f\bfi\bix\bxe\bed\bd-\b-a\bad\bdd\bdr\bre\bes\bss\bs statement is used to set the ip address
- of a particular lease. This is required for all lease
- statements. The IP address must be specified as a dotted
- quad (e.g., 12.34.56.78).
+L\bL\bL\bLE\bE\bE\bEA\bA\bA\bAS\bS\bS\bSE\bE\bE\bE D\bD\bD\bDE\bE\bE\bEC\bC\bC\bCL\bL\bL\bLA\bA\bA\bAR\bR\bR\bRA\bA\bA\bAT\bT\bT\bTI\bI\bI\bIO\bO\bO\bON\bN\bN\bNS\bS\bS\bS
+ _\bT_\bh_\be l\bl\bl\ble\be\be\bea\ba\ba\bas\bs\bs\bse\be\be\be _\bd_\be_\bc_\bl_\ba_\br_\ba_\bt_\bi_\bo_\bn
+ l\bl\bl\ble\be\be\bea\ba\ba\bas\bs\bs\bse\be\be\be {\b{\b{\b{ _\bl_\be_\ba_\bs_\be-_\bd_\be_\bc_\bl_\ba_\br_\ba_\bt_\bi_\bo_\bn [ ... _\bl_\be_\ba_\bs_\be-_\bd_\be_\bc_\bl_\ba_\br_\ba_\bt_\bi_\bo_\bn ] }\b}\b}\b}
+ The DHCP client may decide after some period of time (see
+ P\bP\bP\bPR\bR\bR\bRO\bO\bO\bOT\bT\bT\bTO\bO\bO\bOC\bC\bC\bCO\bO\bO\bOL\bL\bL\bL T\bT\bT\bTI\bI\bI\bIM\bM\bM\bMI\bI\bI\bIN\bN\bN\bNG\bG\bG\bG) decide that it is not going to succeed in
+ contacting a server. At that time, it consults its own
+ database of old leases and tests each one that has not yet
+ timed out by pinging the listed router for that lease to see
+ if that lease could work. It is possible to define one or
+ more _\bf_\bi_\bx_\be_\bd leases in the client configuration file for net-
+ works where there is no DHCP or BOOTP service, so that the
+ client can still automatically configure its address. This
+ is done with the l\bl\bl\ble\be\be\bea\ba\ba\bas\bs\bs\bse\be\be\be statement.
+ NOTE: the lease statement is also used in the
+ dhclient.leases file in order to record leases that have
+ been received from DHCP servers. Some of the syntax for
+ leases as described below is only needed in the
+ dhclient.leases file. Such syntax is documented here for
+ completeness.
- 5
+ A lease statement consists of the lease keyword, followed by
+ a left curly brace, followed by one or more lease declara-
+ tion statements, followed by a right curly brace. The fol-
+ lowing lease declarations are possible:
+ b\bb\bb\bbo\bo\bo\boo\bo\bo\bot\bt\bt\btp\bp\bp\bp;\b;\b;\b;
+ The b\bb\bb\bbo\bo\bo\boo\bo\bo\bot\bt\bt\btp\bp\bp\bp statement is used to indicate that the lease was
+ acquired using the BOOTP protocol rather than the DHCP pro-
+ tocol. It is never necessary to specify this in the client
+ configuration file. The client uses this syntax in its
+ lease database file.
+ i\bi\bi\bin\bn\bn\bnt\bt\bt\bte\be\be\ber\br\br\brf\bf\bf\bfa\ba\ba\bac\bc\bc\bce\be\be\be "\b"\b"\b"_\bs_\bt_\br_\bi_\bn_\bg"\b"\b"\b";\b;\b;\b;
+ The i\bi\bi\bin\bn\bn\bnt\bt\bt\bte\be\be\ber\br\br\brf\bf\bf\bfa\ba\ba\bac\bc\bc\bce\be\be\be lease statement is used to indicate the inter-
+ face on which the lease is valid. If set, this lease will
+ only be tried on a particular interface. When the client
+ receives a lease from a server, it always records the inter-
+ face number on which it received that lease. If predefined
+ leases are specified in the dhclient.conf file, the inter-
+ face should also be specified, although this is not
+ required.
-dhclient.conf(5) dhclient.conf(5)
- f\bfi\bil\ble\ben\bna\bam\bme\be "\b"_\bs_\bt_\br_\bi_\bn_\bg"\b";\b;
- The f\bfi\bil\ble\ben\bna\bam\bme\be statement specifies the name of the boot
- filename to use. This is not used by the standard client
- configuration script, but is included for completeness.
- s\bse\ber\brv\bve\ber\br-\b-n\bna\bam\bme\be "\b"_\bs_\bt_\br_\bi_\bn_\bg"\b";\b;
+SunOS 5.6 Last change: 5
- The s\bse\ber\brv\bve\ber\br-\b-n\bna\bam\bme\be statement specifies the name of the boot
- server name to use. This is also not used by the stan
- dard client configuration script.
- 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;\b;
- The o\bop\bpt\bti\bio\bon\bn statement is used to specify the value of an
- option supplied by the server, or, in the case of prede
- fined leases declared in dhclient.conf, the value that the
- user wishes the client configuration script to use if the
- predefined lease is used.
- s\bsc\bcr\bri\bip\bpt\bt "\b"_\bs_\bc_\br_\bi_\bp_\bt_\b-_\bn_\ba_\bm_\be"\b";\b;
- The s\bsc\bcr\bri\bip\bpt\bt statement is used to specify the pathname of
- the dhcp client configuration script. This script is used
- by the dhcp client to set each interface's initial config
- uration prior to requesting an address, to test the
- address once it has been offered, and to set the inter
- face's final configuration once a lease has been acquired.
- If no lease is acquired, the script is used to test prede
- fined leases, if any, and also called once if no valid
- lease can be identified. For more information, see
- d\bdh\bhc\bcl\bli\bie\ben\bnt\bt-\b-l\ble\bea\bas\bse\be(\b(8\b8)\b).\b.
- m\bme\bed\bdi\biu\bum\bm "\b"_\bm_\be_\bd_\bi_\ba _\bs_\be_\bt_\bu_\bp"\b";\b;
+Headers, Environments, and Macros dhclient.conf(5)
- The m\bme\bed\bdi\biu\bum\bm statement can be used on systems where network
- interfaces cannot automatically determine the type of net
- work to which they are connected. The media setup string
- is a system-dependent parameter which is passed to the
- dhcp client configuration script when initializing the
- interface. On Unix and Unix-like systems, the argument is
- passed on the ifconfig command line when configuring te
- interface.
- The dhcp client automatically declares this parameter if
- it used a media type (see the m\bme\bed\bdi\bia\ba statement) when con
- figuring the interface in order to obtain a lease. This
- statement should be used in predefined leases only if the
- network interface requires media type configuration.
- r\bre\ben\bne\bew\bw _\bd_\ba_\bt_\be;\b;
+ f\bf\bf\bfi\bi\bi\bix\bx\bx\bxe\be\be\bed\bd\bd\bd-\b-\b-\b-a\ba\ba\bad\bd\bd\bdd\bd\bd\bdr\br\br\bre\be\be\bes\bs\bs\bss\bs\bs\bs _\bi_\bp-_\ba_\bd_\bd_\br_\be_\bs_\bs;\b;\b;\b;
- r\bre\beb\bbi\bin\bnd\bd _\bd_\ba_\bt_\be;\b;
+ The f\bf\bf\bfi\bi\bi\bix\bx\bx\bxe\be\be\bed\bd\bd\bd-\b-\b-\b-a\ba\ba\bad\bd\bd\bdd\bd\bd\bdr\br\br\bre\be\be\bes\bs\bs\bss\bs\bs\bs statement is used to set the ip address of
+ a particular lease. This is required for all lease state-
+ ments. The IP address must be specified as a dotted quad
+ (e.g., 12.34.56.78).
+ f\bf\bf\bfi\bi\bi\bil\bl\bl\ble\be\be\ben\bn\bn\bna\ba\ba\bam\bm\bm\bme\be\be\be "\b"\b"\b"_\bs_\bt_\br_\bi_\bn_\bg"\b"\b"\b";\b;\b;\b;
+ The f\bf\bf\bfi\bi\bi\bil\bl\bl\ble\be\be\ben\bn\bn\bna\ba\ba\bam\bm\bm\bme\be\be\be statement specifies the name of the boot
+ filename to use. This is not used by the standard client
+ configuration script, but is included for completeness.
+ s\bs\bs\bse\be\be\ber\br\br\brv\bv\bv\bve\be\be\ber\br\br\br-\b-\b-\b-n\bn\bn\bna\ba\ba\bam\bm\bm\bme\be\be\be "\b"\b"\b"_\bs_\bt_\br_\bi_\bn_\bg"\b"\b"\b";\b;\b;\b;
- 6
+ The s\bs\bs\bse\be\be\ber\br\br\brv\bv\bv\bve\be\be\ber\br\br\br-\b-\b-\b-n\bn\bn\bna\ba\ba\bam\bm\bm\bme\be\be\be statement specifies the name of the boot
+ server name to use. This is also not used by the standard
+ client configuration script.
+ o\bo\bo\bop\bp\bp\bpt\bt\bt\bti\bi\bi\bio\bo\bo\bon\bn\bn\bn _\bo_\bp_\bt_\bi_\bo_\bn-_\bd_\be_\bc_\bl_\ba_\br_\ba_\bt_\bi_\bo_\bn;\b;\b;\b;
+ The o\bo\bo\bop\bp\bp\bpt\bt\bt\bti\bi\bi\bio\bo\bo\bon\bn\bn\bn statement is used to specify the value of an
+ option supplied by the server, or, in the case of predefined
+ leases declared in dhclient.conf, the value that the user
+ wishes the client configuration script to use if the prede-
+ fined lease is used.
+ s\bs\bs\bsc\bc\bc\bcr\br\br\bri\bi\bi\bip\bp\bp\bpt\bt\bt\bt "\b"\b"\b"_\bs_\bc_\br_\bi_\bp_\bt-_\bn_\ba_\bm_\be"\b"\b"\b";\b;\b;\b;
+ The s\bs\bs\bsc\bc\bc\bcr\br\br\bri\bi\bi\bip\bp\bp\bpt\bt\bt\bt statement is used to specify the pathname of the
+ dhcp client configuration script. This script is used by
+ the dhcp client to set each interface's initial configura-
+ tion prior to requesting an address, to test the address
+ once it has been offered, and to set the interface's final
+ configuration once a lease has been acquired. If no lease
+ is acquired, the script is used to test predefined leases,
+ if any, and also called once if no valid lease can be iden-
+ tified. For more information, see d\bd\bd\bdh\bh\bh\bhc\bc\bc\bcl\bl\bl\bli\bi\bi\bie\be\be\ben\bn\bn\bnt\bt\bt\bt-\b-\b-\b-l\bl\bl\ble\be\be\bea\ba\ba\bas\bs\bs\bse\be\be\be(\b(\b(\b(8\b8\b8\b8)\b)\b)\b).\b.\b.\b.
-dhclient.conf(5) dhclient.conf(5)
+ m\bm\bm\bme\be\be\bed\bd\bd\bdi\bi\bi\biu\bu\bu\bum\bm\bm\bm "\b"\b"\b"_\bm_\be_\bd_\bi_\ba _\bs_\be_\bt_\bu_\bp"\b"\b"\b";\b;\b;\b;
+ The m\bm\bm\bme\be\be\bed\bd\bd\bdi\bi\bi\biu\bu\bu\bum\bm\bm\bm statement can be used on systems where network
+ interfaces cannot automatically determine the type of net-
+ work to which they are connected. The media setup string is
+ a system-dependent parameter which is passed to the dhcp
+ client configuration script when initializing the interface.
+ On Unix and Unix-like systems, the argument is passed on the
+ ifconfig command line when configuring te interface.
- e\bex\bxp\bpi\bir\bre\be _\bd_\ba_\bt_\be;\b;
+ The dhcp client automatically declares this parameter if it
+ used a media type (see the m\bm\bm\bme\be\be\bed\bd\bd\bdi\bi\bi\bia\ba\ba\ba statement) when configuring
+ the interface in order to obtain a lease. This statement
- The r\bre\ben\bne\bew\bw statement defines the time at which the dhcp
- client should begin trying to contact its server to renew
- a lease that it is using. The r\bre\beb\bbi\bin\bnd\bd statement defines
- the time at which the dhcp client should begin to try to
- contact _\ba_\bn_\by dhcp server in order to renew its lease. The
- e\bex\bxp\bpi\bir\bre\be statement defines the time at which the dhcp client
- must stop using a lease if it has not been able to contact
- a server in order to renew it.
- These declarations are automatically set in leases
- acquired by the DHCP client, but must also be configured
- in predefined leases - a predefined lease whose expiry
- time has passed will not be used by the DHCP client.
- Dates are specified as follows:
+SunOS 5.6 Last change: 6
- _\b<_\bw_\be_\be_\bk_\bd_\ba_\by_\b> _\b<_\by_\be_\ba_\br_\b>/\b/_\b<_\bm_\bo_\bn_\bt_\bh_\b>/\b/_\b<_\bd_\ba_\by_\b> _\b<_\bh_\bo_\bu_\br_\b>:\b:_\b<_\bm_\bi_\bn_\bu_\bt_\be_\b>:\b:_\b<_\bs_\be_\bc_\bo_\bn_\bd_\b>
- The weekday is present to make it easy for a human to tell
- when a lease expires - it's specified as a number from
- zero to six, with zero being Sunday. When declaring a
- predefined lease, it can always be specified as zero. The
- year is specified with the century, so it should generally
- be four digits except for really long leases. The month
- is specified as a number starting with 1 for January. The
- day of the month is likewise specified starting with 1.
- The hour is a number between 0 and 23, the minute a number
- between 0 and 59, and the second also a number between 0
- and 59.
-A\bAL\bLI\bIA\bAS\bS D\bDE\bEC\bCL\bLA\bAR\bRA\bAT\bTI\bIO\bON\bNS\bS
- a\bal\bli\bia\bas\bs {\b{ _\bd_\be_\bc_\bl_\ba_\br_\ba_\bt_\bi_\bo_\bn_\bs _\b._\b._\b. }\b}
- Some DHCP clients running TCP/IP roaming protocols may
- require that in addition to the lease they may acquire via
- DHCP, their interface also be configured with a predefined
- IP alias so that they can have a permanent IP address even
- while roaming. The Internet Software Consortium DHCP
- client doesn't support roaming with fixed addresses
- directly, but in order to facilitate such experimentation,
- the dhcp client can be set up to configure an IP alias
- using the a\bal\bli\bia\bas\bs declaration.
- The alias declaration resembles a lease declaration,
- except that options other than the subnet-mask option are
- ignored by the standard client configuration script, and
- expiry times are ignored. A typical alias declaration
- includes an interface declaration, a fixed-address decla
- ration for the IP alias address, and a subnet-mask option
- declaration. A medium statement should never be included
- in an alias declaration.
+Headers, Environments, and Macros dhclient.conf(5)
- 7
+ should be used in predefined leases only if the network
+ interface requires media type configuration.
+ r\br\br\bre\be\be\ben\bn\bn\bne\be\be\bew\bw\bw\bw _\bd_\ba_\bt_\be;\b;\b;\b;
+ r\br\br\bre\be\be\beb\bb\bb\bbi\bi\bi\bin\bn\bn\bnd\bd\bd\bd _\bd_\ba_\bt_\be;\b;\b;\b;
+ e\be\be\bex\bx\bx\bxp\bp\bp\bpi\bi\bi\bir\br\br\bre\be\be\be _\bd_\ba_\bt_\be;\b;\b;\b;
+ The r\br\br\bre\be\be\ben\bn\bn\bne\be\be\bew\bw\bw\bw statement defines the time at which the dhcp
+ client should begin trying to contact its server to renew a
+ lease that it is using. The r\br\br\bre\be\be\beb\bb\bb\bbi\bi\bi\bin\bn\bn\bnd\bd\bd\bd statement defines the
+ time at which the dhcp client should begin to try to contact
+ _\ba_\bn_\by dhcp server in order to renew its lease. The e\be\be\bex\bx\bx\bxp\bp\bp\bpi\bi\bi\bir\br\br\bre\be\be\be
+ statement defines the time at which the dhcp client must
+ stop using a lease if it has not been able to contact a
+ server in order to renew it.
-dhclient.conf(5) dhclient.conf(5)
+ These declarations are automatically set in leases acquired
+ by the DHCP client, but must also be configured in prede-
+ fined leases - a predefined lease whose expiry time has
+ passed will not be used by the DHCP client.
+ Dates are specified as follows:
-O\bOT\bTH\bHE\bER\bR D\bDE\bEC\bCL\bLA\bAR\bRA\bAT\bTI\bIO\bON\bNS\bS
- r\bre\bej\bje\bec\bct\bt _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs;\b;
+ <_\bw_\be_\be_\bk_\bd_\ba_\by> <_\by_\be_\ba_\br>/\b/\b/\b/<_\bm_\bo_\bn_\bt_\bh>/\b/\b/\b/<_\bd_\ba_\by> <_\bh_\bo_\bu_\br>:\b:\b:\b:<_\bm_\bi_\bn_\bu_\bt_\be>:\b:\b:\b:<_\bs_\be_\bc_\bo_\bn_\bd>
- The reject statement causes the DHCP client to reject
- offers from servers who use the specified address as a
- server identifier. This can be used to avoid being con
- figured by rogue or misconfigured dhcp servers, although
- it should be a last resort - better to track down the bad
- DHCP server and fix it.
+ The weekday is present to make it easy for a human to tell
+ when a lease expires - it's specified as a number from zero
+ to six, with zero being Sunday. When declaring a predefined
+ lease, it can always be specified as zero. The year is
+ specified with the century, so it should generally be four
+ digits except for really long leases. The month is speci-
+ fied as a number starting with 1 for January. The day of
+ the month is likewise specified starting with 1. The hour
+ is a number between 0 and 23, the minute a number between 0
+ and 59, and the second also a number between 0 and 59.
- i\bin\bnt\bte\ber\brf\bfa\bac\bce\be "\b"_\bn_\ba_\bm_\be"\b" {\b{ _\bd_\be_\bc_\bl_\ba_\br_\ba_\bt_\bi_\bo_\bn_\bs _\b._\b._\b. }\b}
+A\bA\bA\bAL\bL\bL\bLI\bI\bI\bIA\bA\bA\bAS\bS\bS\bS D\bD\bD\bDE\bE\bE\bEC\bC\bC\bCL\bL\bL\bLA\bA\bA\bAR\bR\bR\bRA\bA\bA\bAT\bT\bT\bTI\bI\bI\bIO\bO\bO\bON\bN\bN\bNS\bS\bS\bS
+ a\ba\ba\bal\bl\bl\bli\bi\bi\bia\ba\ba\bas\bs\bs\bs {\b{\b{\b{ _\bd_\be_\bc_\bl_\ba_\br_\ba_\bt_\bi_\bo_\bn_\bs ... }\b}\b}\b}
- A client with more than one network interface may require
- different behaviour depending on which interface is being
- configured. All timing parameters and declarations other
- than lease and alias declarations can be enclosed in an
- interface declaration, and those parameters will then be
- used only for the interface that matches the specified
- name. Interfaces for which there is no interface decla
- ration will use the parameters declared outside of any
- interface declaration, or the default settings.
+ Some DHCP clients running TCP/IP roaming protocols may
+ require that in addition to the lease they may acquire via
+ DHCP, their interface also be configured with a predefined
+ IP alias so that they can have a permanent IP address even
+ while roaming. The Internet Software Consortium DHCP
+ client doesn't support roaming with fixed addresses
+ directly, but in order to facilitate such experimentation,
+ the dhcp client can be set up to configure an IP alias using
+ the a\ba\ba\bal\bl\bl\bli\bi\bi\bia\ba\ba\bas\bs\bs\bs declaration.
- m\bme\bed\bdi\bia\ba "\b"_\bm_\be_\bd_\bi_\ba _\bs_\be_\bt_\bu_\bp"\b" _\b[ ,\b, "\b"_\bm_\be_\bd_\bi_\ba _\bs_\be_\bt_\bu_\bp"\b",\b, _\b._\b._\b. _\b];\b;
- The m\bme\bed\bdi\bia\ba statement defines one or more media configura
- tion parameters which may be tried while attempting to
- acquire an IP address. The dhcp client will cycle
- through each media setup string on the list, configuring
- the interface using that setup and attempting to boot, and
- then trying the next one. This can be used for network
- interfaces which aren't capable of sensing the media type
- unaided - whichever media type succeeds in getting a
- request to the server and hearing the reply is probably
- right (no guarantees).
- The media setup is only used for the initial phase of
- address acquisition (the DHCPDISCOVER and DHCPOFFER pack
- tes). Once an address has been acquired, the dhcp client
- will record it in its lease database and will record the
- media type used to acquire the address. Whenever the
- client tries to renew the lease, it will use that same
- media type. The lease must expire before the client will
- go back to cycling through media types.
-S\bSA\bAM\bMP\bPL\bLE\bE
- The following configuration file is used on a laptop run
- ning NetBSD 1.3. The laptop has an IP alias of
- 192.5.5.213, and has one interface, ep0 (a 3com 3C589C).
- Booting intervals have been shortened somewhat from the
- default, because the client is known to spend most of its
- time on networks with little DHCP activity. The laptop
- does roam to multiple networks.
+SunOS 5.6 Last change: 7
- 8
+Headers, Environments, and Macros dhclient.conf(5)
-dhclient.conf(5) dhclient.conf(5)
+ The alias declaration resembles a lease declaration, except
+ that options other than the subnet-mask option are ignored
+ by the standard client configuration script, and expiry
+ times are ignored. A typical alias declaration includes an
+ interface declaration, a fixed-address declaration for the
+ IP alias address, and a subnet-mask option declaration. A
+ medium statement should never be included in an alias
+ declaration.
+O\bO\bO\bOT\bT\bT\bTH\bH\bH\bHE\bE\bE\bER\bR\bR\bR D\bD\bD\bDE\bE\bE\bEC\bC\bC\bCL\bL\bL\bLA\bA\bA\bAR\bR\bR\bRA\bA\bA\bAT\bT\bT\bTI\bI\bI\bIO\bO\bO\bON\bN\bN\bNS\bS\bS\bS
+ r\br\br\bre\be\be\bej\bj\bj\bje\be\be\bec\bc\bc\bct\bt\bt\bt _\bi_\bp-_\ba_\bd_\bd_\br_\be_\bs_\bs;\b;\b;\b;
- timeout 60;
- retry 60;
- reboot 10;
- select-timeout 5;
- initial-interval 2;
- reject 192.33.137.209;
+ The reject statement causes the DHCP client to reject offers
+ from servers who use the specified address as a server iden-
+ tifier. This can be used to avoid being configured by
+ rogue or misconfigured dhcp servers, although it should be a
+ last resort - better to track down the bad DHCP server and
+ fix it.
- interface "ep0" {
- send host-name "andare.fugue.com";
- send dhcp-client-identifier 1:0:a0:24:ab:fb:9c;
- send dhcp-lease-time 3600;
- supersede domain-name "fugue.com rc.vix.com home.vix.com";
- prepend domain-name-servers 127.0.0.1;
- request subnet-mask, broadcast-address, time-offset, routers,
- domain-name, domain-name-servers, host-name;
- require subnet-mask, domain-name-servers;
- script "/etc/dhclient-script";
- media "media 10baseT/UTP", "media 10base2/BNC";
- }
+ i\bi\bi\bin\bn\bn\bnt\bt\bt\bte\be\be\ber\br\br\brf\bf\bf\bfa\ba\ba\bac\bc\bc\bce\be\be\be "\b"\b"\b"_\bn_\ba_\bm_\be"\b"\b"\b" {\b{\b{\b{ _\bd_\be_\bc_\bl_\ba_\br_\ba_\bt_\bi_\bo_\bn_\bs ... }\b}\b}\b}
- alias {
- interface "ep0";
- fixed-address 192.5.5.213;
- option subnet-mask 255.255.255.255;
- }
- This is a very complicated dhclient.conf file - in gen
- eral, yours should be much simpler. In many cases, it's
- sufficient to just create an empty dhclient.conf file -
- the defaults are usually fine.
+ A client with more than one network interface may require
+ different behaviour depending on which interface is being
+ configured. All timing parameters and declarations other
+ than lease and alias declarations can be enclosed in an
+ interface declaration, and those parameters will then be
+ used only for the interface that matches the specified name.
+ Interfaces for which there is no interface declaration will
+ use the parameters declared outside of any interface
+ declaration, or the default settings.
-S\bSE\bEE\bE A\bAL\bLS\bSO\bO
- dhcp-options(5), dhclient.leases(5), dhcpd(8),
- dhcpd.conf(5), RFC2132, RFC2131.
+ m\bm\bm\bme\be\be\bed\bd\bd\bdi\bi\bi\bia\ba\ba\ba "\b"\b"\b"_\bm_\be_\bd_\bi_\ba _\bs_\be_\bt_\bu_\bp"\b"\b"\b" [ ,\b,\b,\b, "\b"\b"\b"_\bm_\be_\bd_\bi_\ba _\bs_\be_\bt_\bu_\bp"\b"\b"\b",\b,\b,\b, ... ];\b;\b;\b;
-A\bAU\bUT\bTH\bHO\bOR\bR
- d\bdh\bhc\bcl\bli\bie\ben\bnt\bt(\b(8\b8)\b) was written by Ted Lemon <mellon@vix.com>
- under a contract with Vixie Labs. Funding for this pro
- ject was provided by the Internet Software Consortium.
- 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.\b.
+ The m\bm\bm\bme\be\be\bed\bd\bd\bdi\bi\bi\bia\ba\ba\ba statement defines one or more media configuration
+ parameters which may be tried while attempting to acquire an
+ IP address. The dhcp client will cycle through each media
+ setup string on the list, configuring the interface using
+ that setup and attempting to boot, and then trying the next
+ one. This can be used for network interfaces which aren't
+ capable of sensing the media type unaided - whichever media
+ type succeeds in getting a request to the server and hearing
+ the reply is probably right (no guarantees).
+ The media setup is only used for the initial phase of
+ address acquisition (the DHCPDISCOVER and DHCPOFFER
+ packtes). Once an address has been acquired, the dhcp
+ client will record it in its lease database and will record
+ the media type used to acquire the address. Whenever the
+ client tries to renew the lease, it will use that same media
+ type. The lease must expire before the client will go back
+ to cycling through media types.
+SunOS 5.6 Last change: 8
+Headers, Environments, and Macros dhclient.conf(5)
+S\bS\bS\bSA\bA\bA\bAM\bM\bM\bMP\bP\bP\bPL\bL\bL\bLE\bE\bE\bE
+ The following configuration file is used on a laptop running
+ NetBSD 1.3. The laptop has an IP alias of 192.5.5.213, and
+ has one interface, ep0 (a 3com 3C589C). Booting intervals
+ have been shortened somewhat from the default, because the
+ client is known to spend most of its time on networks with
+ little DHCP activity. The laptop does roam to multiple
+ networks.
+ timeout 60;
+ retry 60;
+ reboot 10;
+ select-timeout 5;
+ initial-interval 2;
+ reject 192.33.137.209;
+
+ interface "ep0" {
+ send host-name "andare.fugue.com";
+ send dhcp-client-identifier 1:0:a0:24:ab:fb:9c;
+ send dhcp-lease-time 3600;
+ supersede domain-name "fugue.com rc.vix.com home.vix.com";
+ prepend domain-name-servers 127.0.0.1;
+ request subnet-mask, broadcast-address, time-offset, routers,
+ domain-name, domain-name-servers, host-name;
+ require subnet-mask, domain-name-servers;
+ script "/etc/dhclient-script";
+ media "media 10baseT/UTP", "media 10base2/BNC";
+ }
+
+ alias {
+ interface "ep0";
+ fixed-address 192.5.5.213;
+ option subnet-mask 255.255.255.255;
+ }
+ This is a very complicated dhclient.conf file - in general,
+ yours should be much simpler. In many cases, it's suffi-
+ cient to just create an empty dhclient.conf file - the
+ defaults are usually fine.
+
+S\bS\bS\bSE\bE\bE\bEE\bE\bE\bE A\bA\bA\bAL\bL\bL\bLS\bS\bS\bSO\bO\bO\bO
+ dhcp-options(5), dhclient.leases(5), dhcpd(8),
+ dhcpd.conf(5), RFC2132, RFC2131.
+
+A\bA\bA\bAU\bU\bU\bUT\bT\bT\bTH\bH\bH\bHO\bO\bO\bOR\bR\bR\bR
+ d\bd\bd\bdh\bh\bh\bhc\bc\bc\bcl\bl\bl\bli\bi\bi\bie\be\be\ben\bn\bn\bnt\bt\bt\bt(\b(\b(\b(8\b8\b8\b8)\b)\b)\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 Consortium. Information
+ about the Internet Software Consortium can be found at
+ h\bh\bh\bht\bt\bt\btt\bt\bt\btp\bp\bp\bp:\b:\b:\b:/\b/\b/\b//\b/\b/\b/w\bw\bw\bww\bw\bw\bww\bw\bw\bw.\b.\b.\b.i\bi\bi\bis\bs\bs\bsc\bc\bc\bc.\b.\b.\b.o\bo\bo\bor\br\br\brg\bg\bg\bg/\b/\b/\b/i\bi\bi\bis\bs\bs\bsc\bc\bc\bc.\b.\b.\b.
+
+
+
+
+
+SunOS 5.6 Last change: 9
- 9
projects / thirdparty / dhcp.git / blobdiff