+++ /dev/null
-
-
-
-dhclient-script(8) dhclient-script(8)
-
-
-N\bNA\bAM\bME\bE
- dhclient-script - DHCP client network configuration script
-
-D\bDE\bES\bSC\bCR\bRI\bIP\bPT\bTI\bIO\bON\bN
- The DHCP client network configuration script is invoked
- from time to time by d\bdh\bhc\bcl\bli\bie\ben\bnt\bt(\b(8\b8)\b). 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
- identified.
-
- This script is not meant to be customized by the end user.
- If local customizations are needed, they should be possi
- ble using the enter and exit hooks provided (see HOOKS for
- details). These hooks will allow the user to override
- the default behaviour of the client in creating a
- /\b/e\bet\btc\bc/\b/r\bre\bes\bso\bol\blv\bv.\b.c\bco\bon\bnf\bf file.
-
- No standard client script exists for some operating sys
- tems, even though the actual client may work, so a pio
- neering user may well need to create a new script or mod
- ify an existing one. In general, customizations specific
- to a particular computer should be done in the
- /\b/e\bet\btc\bc/\b/d\bdh\bhc\bcl\bli\bie\ben\bnt\bt.\b.c\bco\bon\bnf\bf file. If you find that you can't make
- such a customization without customizing
- /\b/e\bet\btc\bc/\b/d\bdh\bhc\bcl\bli\bie\ben\bnt\bt.\b.c\bco\bon\bnf\bf or using the enter and exit hooks,
- please submit a bug report.
-
-H\bHO\bOO\bOK\bKS\bS
- When it starts, the client script first defines a shell
- function, m\bma\bak\bke\be_\b_r\bre\bes\bso\bol\blv\bv_\b_c\bco\bon\bnf\bf ,\b, which is later used to create
- the /\b/e\bet\btc\bc/\b/r\bre\bes\bso\bol\blv\bv.\b.c\bco\bon\bnf\bf file. To override the default
- behaviour, redefine this function in the enter hook
- script.
-
- On after defining the make_resolv_conf function, the
- client script checks for the presence of an executable
- /\b/e\bet\btc\bc/\b/d\bdh\bhc\bcl\bli\bie\ben\bnt\bt-\b-e\ben\bnt\bte\ber\br-\b-h\bho\boo\bok\bks\bs script, and if present, it
- invokes the script inline, using the Bourne shell '.' com
- mand. The entire environment documented under OPERATION
- is available to this script, which may modify the environ
- ment if needed to change the behaviour of the script. If
- an error occurs during the execution of the script, it can
- set the exit_status variable to a nonzero value, and
- /\b/e\bet\btc\bc/\b/d\bdh\bhc\bcl\bli\bie\ben\bnt\bt-\b-s\bsc\bcr\bri\bip\bpt\bt will exit with that error code imme
- diately after the client script exits.
-
- After all processing has completed, /\b/e\bet\btc\bc/\b/d\bdh\bhc\bcl\bli\bie\ben\bnt\bt-\b-s\bsc\bcr\bri\bip\bpt\bt
- checks for the presence of an executable /\b/e\bet\btc\bc/\b/d\bdh\bhc\bcl\bli\bie\ben\bnt\bt-\b-
- e\bex\bxi\bit\bt-\b-h\bho\boo\bok\bks\bs script, which if present is invoked using the
- '.' command. The exit status is passed in the
-
-
-
- 1
-
-
-
-
-
-dhclient-script(8) dhclient-script(8)
-
-
- exit_status shell variable, and will always be zero if the
- script succeeded at the task for which it was invoked.
-
-O\bOP\bPE\bER\bRA\bAT\bTI\bIO\bON\bN
- When dhclient needs to invoke the client configuration
- script, it writes a shell script into /tmp which defines a
- variety of variables. In all cases, $reason is set to the
- name of the reason why the script has been invoked. The
- following reasons are currently defined: MEDIUM, PREINIT,
- BOUND, RENEW, REBIND, REBOOT, EXPIRE, FAIL and TIMEOUT.
-
-
-M\bME\bED\bDI\bIU\bUM\bM
- The DHCP client is requesting that an interface's media
- type be set. The interface name is passed in $interface,
- and the media type is passed in $medium.
-
-P\bPR\bRE\bEI\bIN\bNI\bIT\bT
- The DHCP client is requesting that an interface be config
- ured as required in order to send packets prior to receiv
- ing an actual address. For clients which use the BSD
- socket library, this means configuring the interface with
- an IP address of 0.0.0.0 and a broadcast address of
- 255.255.255.255. For other clients, it may be possible
- to simply configure the interface up without actually giv
- ing it an IP address at all. The interface name is
- passed in $interface, and the media type in $medium.
-
- If an IP alias has been declared in dhclient.conf, its
- address will be passed in $alias_ip_address, and that ip
- alias should be deleted from the interface, along with any
- routes to it.
-
-B\bBO\bOU\bUN\bND\bD
- The DHCP client has done an initial binding to a new
- address. The new ip address is passed in
- $new_ip_address, and the interface name is passed in
- $interface. The media type is passed in $medium. Any
- options acquired from the server are passed using the
- option name described in d\bdh\bhc\bcp\bp-\b-o\bop\bpt\bti\bio\bon\bns\bs, except that dashes
- ('-') are replaced by underscores ('_') in order to make
- valid shell variables, and the variable names start with
- new_. So for example, the new subnet mask would be
- passed in $new_subnet_mask.
-
- Before actually configuring the address, dhclient-script
- should somehow ARP for it and exit with a nonzero status
- if it receives a reply. In this case, the client will
- send a DHCPDECLINE message to the server and acquire a
- different address. This may also be done in the RENEW,
- REBIND, or REBOOT states, but is not required, and indeed
- may not be desirable.
-
- When a binding has been completed, a lot of network
-
-
-
- 2
-
-
-
-
-
-dhclient-script(8) dhclient-script(8)
-
-
- parameters are likely to need to be set up. A new
- /etc/resolv.conf needs to be created, using the values of
- $new_domain_name and $new_domain_name_servers (which may
- list more than one server, seperated by spaces). A
- default route should be set using $new_routers, and static
- routes may need to be set up using $new_static_routes.
-
- If an IP alias has been declared, it must be set up here.
- The alias IP address will be written as $alias_ip_address,
- and other DHCP options that are set for the alias (e.g.,
- subnet mask) will be passed in variables named as
- described previously except starting with $alias_ instead
- of $new_. Care should be taken that the alias IP address
- not be used if it is identical to the bound IP address
- ($new_ip_address), since the other alias parameters may be
- incorrect in this case.
-
-R\bRE\bEN\bNE\bEW\bW
- When a binding has been renewed, the script is called as
- in BOUND, except that in addition to all the variables
- starting with $new_, there is another set of variables
- starting with $old_. Persistent settings that may have
- changed need to be deleted - for example, if a local route
- to the bound address is being configured, the old local
- route should be deleted. If the default route has
- changed, the old default route should be deleted. If the
- static routes have changed, the old ones should be
- deleted. Otherwise, processing can be done as with BOUND.
-
-R\bRE\bEB\bBI\bIN\bND\bD
- The DHCP client has rebound to a new DHCP server. This
- can be handled as with RENEW, except that if the IP
- address has changed, the ARP table should be cleared.
-
-R\bRE\bEB\bBO\bOO\bOT\bT
- The DHCP client has successfully reacquired its old
- address after a reboot. This can be processed as with
- BOUND.
-
-E\bEX\bXP\bPI\bIR\bRE\bE
- The DHCP client has failed to renew its lease or acquire a
- new one, and the lease has expired. The IP address must
- be relinquished, and all related parameters should be
- deleted, as in RENEW and REBIND.
-
-F\bFA\bAI\bIL\bL
- The DHCP client has been unable to contact any DHCP
- servers, and any leases that have been tested have not
- proved to be valid. The parameters from the last lease
- tested should be deconfigured. This can be handled in
- the same way as EXPIRE.
-
-T\bTI\bIM\bME\bEO\bOU\bUT\bT
- The DHCP client has been unable to contact any DHCP
-
-
-
- 3
-
-
-
-
-
-dhclient-script(8) dhclient-script(8)
-
-
- servers. However, an old lease has been identified, and
- its parameters have been passed in as with BOUND. The
- client configuration script should test these parameters
- and, if it has reason to believe they are valid, should
- exit with a value of zero. If not, it should exit with a
- nonzero value.
-
- The usual way to test a lease is to set up the network as
- with REBIND (since this may be called to test more than
- one lease) and then ping the first router defined in
- $routers. If a response is received, the lease must be
- valid for the network to which the interface is currently
- connected. It would be more complete to try to ping all
- of the routers listed in $new_routers, as well as those
- listed in $new_static_routes, but current scripts do not
- do this.
-
-F\bFI\bIL\bLE\bES\bS
- Each operating system should generally have its own script
- file, although the script files for similar operating sys
- tems may be similar or even identical. The script files
- included in the Internet Software Consortium DHCP distri
- bution appear in the distribution tree under
- client/scripts, and bear the names of the operating sys
- tems on which they are intended to work.
-
-B\bBU\bUG\bGS\bS
- If more than one interface is being used, there's no obvi
- ous way to avoid clashes between server-supplied configu
- ration parameters - for example, the stock dhclient-script
- rewrites /etc/resolv.conf. If more than one interface is
- being configured, /etc/resolv.conf will be repeatedly ini
- tialized to the values provided by one server, and then
- the other. Assuming the information provided by both
- servers is valid, this shouldn't cause any real problems,
- but it could be confusing.
-
-S\bSE\bEE\bE A\bAL\bLS\bSO\bO
- dhclient(8), dhcpd(8), dhcrelay(8), dhclient.conf(5) and
- dhclient.leases(5).
-
-A\bAU\bUT\bTH\bHO\bOR\bR
- d\bdh\bhc\bcl\bli\bie\ben\bnt\bt-\b-s\bsc\bcr\bri\bip\bpt\bt(\b(8\b8)\b) has been written for the Internet Soft
- ware Consortium by Ted Lemon <mellon@fugue.com> in cooper
- ation with Vixie Enterprises. To learn more about the
- Internet Software Consortium, see h\bht\btt\btp\bp:\b:/\b//\b/w\bww\bww\bw.\b.v\bvi\bix\bx.\b.c\bco\bom\bm/\b/i\bis\bsc\bc.\b.
- To learn more about Vixie Enterprises, see
- h\bht\btt\btp\bp:\b:/\b//\b/w\bww\bww\bw.\b.v\bvi\bix\bx.\b.c\bco\bom\bm.\b.
-
-
-
-
-
-
-
-
-
- 4
-
-
+++ /dev/null
-
-
-
-dhclient(8) dhclient(8)
-
-
-N\bNA\bAM\bME\bE
- dhclient - Dynamic Host Configuration Protocol Client
-
-S\bSY\bYN\bNO\bOP\bPS\bSI\bIS\bS
- d\bdh\bhc\bcl\bli\bie\ben\bnt\bt [ -\b-p\bp _\bp_\bo_\br_\bt ] [ -\b-d\bd ] [ -\b-D\bD ] [ -\b-q\bq ] [ -\b-c\bc ] [ -\b-l\blf\bf
- _\bl_\be_\ba_\bs_\be_\b-_\bf_\bi_\bl_\be ] [ -\b-p\bpf\bf _\bp_\bi_\bd_\b-_\bf_\bi_\bl_\be ] [ -\b-c\bcf\bf _\bc_\bo_\bn_\bf_\bi_\bg_\b-_\bf_\bi_\bl_\be ] [ -\b-s\bs
- server ] [ -\b-w\bw ] [ _\bi_\bf_\b0 [ _\b._\b._\b._\bi_\bf_\bN ] ]
-
-D\bDE\bES\bSC\bCR\bRI\bIP\bPT\bTI\bIO\bON\bN
- The Internet Software Consortium DHCP Client, dhclient,
- provides a means for configuring one or more network
- interfaces using the Dynamic Host Configuration Protocol,
- BOOTP protocol, or if these protocols fail, by statically
- assigning an address.
-
-O\bOP\bPE\bER\bRA\bAT\bTI\bIO\bON\bN
- The DHCP protocol allows a host to contact a central
- server which maintains a list of IP addresses which may be
- assigned on one or more subnets. A DHCP client may
- request an address from this pool, and then use it on a
- temporary basis for communication on network. The DHCP
- protocol also provides a mechanism whereby a client can
- learn important details about the network to which it is
- attached, such as the location of a default router, the
- location of a name server, and so on.
-
- On startup, dhclient reads the _\bd_\bh_\bc_\bl_\bi_\be_\bn_\bt_\b._\bc_\bo_\bn_\bf for configu
- ration instructions. It then gets a list of all the net
- work interfaces that are configured in the current system.
- For each interface, it attempts to configure the interface
- using the DHCP protocol.
-
- In order to keep track of leases across system reboots and
- server restarts, dhclient keeps a list of leases it has
- been assigned in the dhclient.leases(5) file. On
- startup, after reading the dhclient.conf file, dhclient
- reads the dhclient.leases file to refresh its memory about
- what leases it has been assigned.
-
- When a new lease is acquired, it is appended to the end of
- the dhclient.leases file. In order to prevent the file
- from becoming arbitrarily large, from time to time
- dhclient creates a new dhclient.leases file from its in-
- core lease database. The old version of the
- dhclient.leases file is retained under the name
- _\bd_\bh_\bc_\bl_\bi_\be_\bn_\bt_\b._\bl_\be_\ba_\bs_\be_\bs_\b~ until the next time dhclient rewrites the
- database.
-
- Old leases are kept around in case the DHCP server is
- unavailable when dhclient is first invoked (generally dur
- ing the initial system boot process). In that event, old
- leases from the dhclient.leases file which have not yet
- expired are tested, and if they are determined to be
- valid, they are used until either they expire or the DHCP
-
-
-
- 1
-
-
-
-
-
-dhclient(8) dhclient(8)
-
-
- server becomes available.
-
- A mobile host which may sometimes need to access a network
- on which no DHCP server exists may be preloaded with a
- lease for a fixed address on that network. When all
- attempts to contact a DHCP server have failed, dhclient
- will try to validate the static lease, and if it succeeds,
- will use that lease until it is restarted.
-
- A mobile host may also travel to some networks on which
- DHCP is not available but BOOTP is. In that case, it may
- be advantageous to arrange with the network administrator
- for an entry on the BOOTP database, so that the host can
- boot quickly on that network rather than cycling through
- the list of old leases.
-
-C\bCO\bOM\bMM\bMA\bAN\bND\bD L\bLI\bIN\bNE\bE
- The names of the network interfaces that dhclient should
- attempt to configure may be specified on the command line.
- If no interface names are specified on the command line
- dhclient will normally identify all network interfaces,
- elimininating non-broadcast interfaces if possible, and
- attempt to configure each interface.
-
- It is also possible to specify interfaces by name in the
- d\bdh\bhc\bcl\bli\bie\ben\bnt\bt.\b.c\bco\bon\bnf\bf(\b(5\b5)\b) file. If interfaces are specified in
- this way, then the client will only configure interfaces
- that are either specified in the configuration file or on
- the command line, and will ignore all other interfaces.
-
- If the DHCP client should listen and transmit on a port
- other than the standard (port 68), the -\b-p\bp flag may used.
- It should be followed by the udp port number that dhclient
- should use. This is mostly useful for debugging purposes.
- If a different port is specified for the client to listen
- on and transmit on, the client will also use a different
- destination port - one greater than the specified destina
- tion port.
-
- The DHCP client normally transmits any protocol messages
- it sends before acquiring an IP address to,
- 255.255.255.255, the IP limited broadcast address. For
- debugging purposes, it may be useful to have the server
- transmit these messages to some other address. This can
- be specified with the -\b-s\bs flag, followed by the IP address
- or domain name of the destination.
-
- The DHCP client will normally run in the foreground until
- it has configured an interface, and then will revert to
- running in the background. To run force dhclient to
- always run as a foreground process, the -\b-d\bd flag should be
- specified. This is useful when running the client under a
- debugger, or when running it out of inittab on System V
- systems.
-
-
-
- 2
-
-
-
-
-
-dhclient(8) dhclient(8)
-
-
- The client writes a temporary shell script whenever it
- invokes dhclient-script. This script is normally deleted
- after the client runs, but it can be helpful when debug
- ging the client script to see what the client wrote. The
- client can be configured not to delete these scripts by
- specifying the -\b-D\bD flag.
-
- The client normally prints a startup message and displays
- the protocol sequence to the standard error descriptor
- until it has acquired an address, and then only logs mes
- sages using the s\bsy\bys\bsl\blo\bog\bg (\b(3\b3)\b) facility. The -\b-q\bq flag pre
- vents any messages other than errors from being printed to
- the standard error descriptor.
-
- The DHCP client normally gets its configuration informa
- tion from /\b/e\bet\btc\bc/\b/d\bdh\bhc\bcl\bli\bie\ben\bnt\bt.\b.c\bco\bon\bnf\bf,\b, its lease database from
- /\b/v\bva\bar\br/\b/d\bdb\bb/\b/d\bdh\bhc\bcl\bli\bie\ben\bnt\bt.\b.l\ble\bea\bas\bse\bes\bs and stores its process ID in a
- file called /\b/v\bva\bar\br/\b/r\bru\bun\bn/\b/d\bdh\bhc\bcl\bli\bie\ben\bnt\bt.\b.p\bpi\bid\bd.\b. To specify different
- names and/or locations for these files, use the -\b-c\bcf\bf,\b, -\b-l\blf\bf
- and -\b-p\bpf\bf flags, respectively, followed by the name of the
- file. This can be particularly useful if, for example,
- /\b/v\bva\bar\br/\b/d\bdb\bb or /\b/v\bva\bar\br/\b/r\bru\bun\bn has not yet been mounted when the DHCP
- client is started.
-
- The DHCP client normally exits if it isn't able to iden
- tify any network interfaces to configure. On laptop com
- puters and other computers with hot-swappable I/O buses,
- it is possible that a broadcast interface may be added
- after system startup. The -\b-w\bw flag can be used to cause
- the client not to exit when it doesn't find any such
- interfaces. The d\bdh\bhc\bcp\bpc\bcc\bcp\bp (\b(8\b8)\b) program can then be used to
- notify the client when a network interface has been added
- or removed, so that the client can configure an IP address
- on that interface.
-
-C\bCO\bON\bNF\bFI\bIG\bGU\bUR\bRA\bAT\bTI\bIO\bON\bN
- The syntax of the dhclient.conf(8) file is discussed
- seperately.
-
-F\bFI\bIL\bLE\bES\bS
- /\b/e\bet\btc\bc/\b/d\bdh\bhc\bcl\bli\bie\ben\bnt\bt.\b.c\bco\bon\bnf\bf,\b, /\b/v\bva\bar\br/\b/d\bdb\bb/\b/d\bdh\bhc\bcl\bli\bie\ben\bnt\bt.\b.l\ble\bea\bas\bse\bes\bs,\b,
- /\b/v\bva\bar\br/\b/r\bru\bun\bn/\b/d\bdh\bhc\bcl\bli\bie\ben\bnt\bt.\b.p\bpi\bid\bd,\b, /\b/v\bva\bar\br/\b/d\bdb\bb/\b/d\bdh\bhc\bcl\bli\bie\ben\bnt\bt.\b.l\ble\bea\bas\bse\bes\bs~\b~.\b.
-
-S\bSE\bEE\bE A\bAL\bLS\bSO\bO
- dhcpd(8), dhcrelay(8), dhclient.conf(5),
- dhclient.leases(5)
-
-A\bAU\bUT\bTH\bHO\bOR\bR
- d\bdh\bhc\bcl\bli\bie\ben\bnt\bt(\b(8\b8)\b) has been written for the Internet Software
- Consortium by Ted Lemon <mellon@fugue.com> in cooperation
- with Vixie Enterprises. To learn more about the Internet
- Software Consortium, see h\bht\btt\btp\bp:\b:/\b//\b/w\bww\bww\bw.\b.v\bvi\bix\bx.\b.c\bco\bom\bm/\b/i\bis\bsc\bc.\b. To learn
- more about Vixie Enterprises, see h\bht\btt\btp\bp:\b:/\b//\b/w\bww\bww\bw.\b.v\bvi\bix\bx.\b.c\bco\bom\bm.\b.
-
-
-
-
- 3
-
-
-
-
-
-dhclient(8) dhclient(8)
-
-
- This client was substantially modified and enhanced by
- Elliot Poger for use on Linux while he was working on the
- MosquitoNet project at Stanford.
-
- The current version owes much to Elliot's Linux enhance
- ments, but was substantially reorganized and partially
- rewritten by Ted Lemon so as to use the same networking
- framework that the Internet Software Consortium DHCP
- server uses. Much system-specific configuration code was
- moved into a shell script so that as support for more
- operating systems is added, it will not be necessary to
- port and maintain system-specific configuration code to
- these operating systems - instead, the shell script can
- invoke the native tools to accomplish the same purpose.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 4
-
-
+++ /dev/null
-
-
-
-dhclient.conf(5) 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.
-
- 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.
-
- 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.
-
-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 following statements can be used to adjust the timing
- behaviour of the DHCP client if required, however:
-
- _\bT_\bh_\be t\bti\bim\bme\beo\bou\but\bt _\bs_\bt_\ba_\bt_\be_\bm_\be_\bn_\bt
-
- t\bti\bim\bme\beo\bou\but\bt _\bt_\bi_\bm_\be ;\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 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.
-
-
-
- 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
-
- 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
-
- s\bse\bel\ble\bec\bct\bt-\b-t\bti\bim\bme\beo\bou\but\bt _\bt_\bi_\bm_\be;\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 _\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.
-
- By default, the select-timeout is zero seconds - that is,
- the client will take the first offer it sees.
-
- _\bT_\bh_\be r\bre\beb\bbo\boo\bot\bt _\bs_\bt_\ba_\bt_\be_\bm_\be_\bn_\bt
-
- r\bre\beb\bbo\boo\bot\bt _\bt_\bi_\bm_\be;\b;
-
- 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\bba\bac\bck\bko\bof\bff\bf-\b-c\bcu\but\bto\bof\bff\bf _\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;
-
- 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.
-
-
-
- 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.
-
-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
-
- 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;
-
- 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. By default, the DHCP server requests the
- subnet-mask, broadcast-address, time-offset, routers,
- domain-name, domain-name-servers and host-name options.
-
- In some cases, it may be desirable to send no parameter
- request list at all. To do this, simply write the
- request statement but specify no parameters:
-
- request;
-
- _\bT_\bh_\be r\bre\beq\bqu\bui\bir\bre\be _\bs_\bt_\ba_\bt_\be_\bm_\be_\bn_\bt
-
- 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;
-
- 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.
-
- _\bT_\bh_\be s\bse\ben\bnd\bd _\bs_\bt_\ba_\bt_\be_\bm_\be_\bn_\bt
-
-
-
- 3
-
-
-
-
-
-dhclient.conf(5) dhclient.conf(5)
-
-
- 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}
-
- 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 pro
- tocol 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 informa
- tion 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
-
- 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
-
- 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;
-
- If for some set of options the client should use a value
- you supply, and then use the values supplied by the
- server, if any, 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.
- This restriction is not enforced - if you ignore it, the
- behaviour will be unpredictable.
-
- _\bT_\bh_\be a\bap\bpp\bpe\ben\bnd\bd _\bs_\bt_\ba_\bt_\be_\bm_\be_\bn_\bt
-
-
-
- 4
-
-
-
-
-
-dhclient.conf(5) dhclient.conf(5)
-
-
- 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 set of options the client should first use the
- values supplied by the server, if any, and then use values
- you supply, these values can be defined in the a\bap\bpp\bpe\ben\bnd\bd
- statement. The a\bap\bpp\bpe\ben\bnd\bd statement can only be used for
- options which allow more than one value to be given.
- This restriction is not enforced - if you ignore it, the
- behaviour will be unpredictable.
-
-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
-
- 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.
-
- 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
-
-
-
- 5
-
-
-
-
-
-dhclient.conf(5) dhclient.conf(5)
-
-
- 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;
-
- 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).
-
- 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;
-
- 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-s\bsc\bcr\bri\bip\bpt\bt(\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;
-
- 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.
-
-
-
-
- 6
-
-
-
-
-
-dhclient.conf(5) dhclient.conf(5)
-
-
- 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;
-
- r\bre\beb\bbi\bin\bnd\bd _\bd_\ba_\bt_\be;\b;
-
- e\bex\bxp\bpi\bir\bre\be _\bd_\ba_\bt_\be;\b;
-
- 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:
-
- _\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.
-
-
-
- 7
-
-
-
-
-
-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 decla
- ration for the IP alias address, and a subnet-mask option
- declaration. A medium statement should never be included
- in an alias declaration.
-
-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;
-
- 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.
-
- 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 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.
-
- p\bps\bse\beu\bud\bdo\bo "\b"_\bn_\ba_\bm_\be" "_\br_\be_\ba_\bl_\b-_\bn_\ba_\bm_\be"\b" {\b{ _\bd_\be_\bc_\bl_\ba_\br_\ba_\bt_\bi_\bo_\bn_\bs _\b._\b._\b. }\b}
-
- Under some circumstances it can be useful to declare a
- pseudo-interface and have the DHCP client acquire a con
- figuration for that interface. Each interface that the
- DHCP client is supporting normally has a DHCP client state
- machine running on it to acquire and maintain its lease.
- A pseudo-interface is just another state machine running
- on the interface named _\br_\be_\ba_\bl_\b-_\bn_\ba_\bm_\be, with its own lease and
- its own state. If you use this feature, you must provide
- a client identifier for both the pseudo-interface and the
- actual interface, and the two identifiers must be differ
- ent. You must also provide a seperate client script for
- the pseudo-interface to do what you want with the IP
- address. For example:
-
- interface "ep0" {
- send dhcp-client-identifier "my-client-ep0";
- }
- pseudo "secondary" "ep0" {
- send dhcp-client-identifier "my-client-ep0-secondary";
- script "/etc/dhclient-secondary";
- }
-
-
-
- 8
-
-
-
-
-
-dhclient.conf(5) dhclient.conf(5)
-
-
- The client script for the pseudo-interface should not con
- figure the interface up or down - essentially, all it
- needs to handle are the states where a lease has been
- acquired or renewed, and the states where a lease has
- expired. See d\bdh\bhc\bcl\bli\bie\ben\bnt\bt-\b-s\bsc\bcr\bri\bip\bpt\bt(\b(8\b8)\b) for more information.
-
- 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.
-
-
- 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;
-
-
-
- 9
-
-
-
-
-
-dhclient.conf(5) dhclient.conf(5)
-
-
- 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 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.
-
-S\bSE\bEE\bE A\bAL\bLS\bSO\bO
- dhcp-options(5), dhclient.leases(5), dhcpd(8),
- dhcpd.conf(5), RFC2132, RFC2131.
-
-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.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 10
-
-
projects / thirdparty / dhcp.git / commitdiff
