![]() |
![]()
| ![]() |
![]()
NAMEdhclient —
Dynamic Host Configuration Protocol (DHCP) client
SYNOPSIS
DESCRIPTIONThedhclient utility provides a means for configuring
network interfaces using DHCP, BOOTP, or if these protocols fail, by
statically assigning an address.
The name of the network interface that
The options are as follows:
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 the 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, In order to keep track of leases across system reboots and server
restarts, Old leases are kept around in case the DHCP server is unavailable
when 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, 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. NOTESYou must have the Berkeley Packet Filter (BPF) configured in your kernel. Thedhclient utility requires at least one
/dev/bpf* device for each broadcast network interface
that is attached to your system. See
bpf(4) for
more information.
FILES
SEE ALSOdhclient.conf(5), dhclient.leases(5), dhclient-script(8)AUTHORSThedhclient utility was written by Ted
Lemon
<mellon@fugue.com> and
Elliot Poger
<elliot@poger.com>.
The current implementation was reworked by Henning Brauer <henning@openbsd.org>. BUGSThedhclient utility uses
capsicum(4)
to sandbox the main process. If the requisite kernel support is not available,
the main process will attempt to run in a
chroot(2)
sandbox instead. This will fail if the process is jailed or the
kern.chroot_allow_open_directories sysctl is set to 0.
|