svcadm(8)을 검색하려면 섹션에서 8 을 선택하고, 맨 페이지 이름에 svcadm을 입력하고 검색을 누른다.
dhcpagent(8)
dhcpagent(8) System Administration Commands dhcpagent(8)
NAME
dhcpagent - Dynamic Host Configuration Protocol (DHCP) client daemon
SYNOPSIS
/usr/sbin/dhcpagent
DESCRIPTION
dhcpagent implements the client half of the Dynamic Host Configuration
Protocol (DHCP) for machines running Oracle Solaris software.
The dhcpagent daemon obtains configuration parameters for the client
(local) machine's network interfaces from a DHCP server. These parame‐
ters may include a lease on an IP address, which gives the client ma‐
chine use of the address for the period of the lease, which may be in‐
finite. If the client wishes to use the IP address for a period longer
than the lease, it must negotiate an extension using DHCP. For this
reason, dhcpagent must run as a daemon, terminating only when the
client machine powers down.
The dhcpagent daemon is managed by means of the service management fa‐
cility (SMF), by using the fault management resource identifier (FMRI):
svc:/network/dhcp/client:default
For IPv4, the service is started automatically by ipadm or ifconfig
when a DHCP address is created. For IPv6, the service is started auto‐
matically by in.ndpd(8).
When invoked, dhcpagent enters a passive state while it awaits instruc‐
tions from ipadm(8), ifconfig(8) or in.ndpd(8). When it receives a com‐
mand to configure an interface, it brings up the interface (if neces‐
sary) and starts DHCP. Once DHCP is complete, dhcpagent can be queried
for the values of the various network parameters. In addition, if DHCP
was used to obtain a lease on an address for an interface, it config‐
ures the address for use. When a lease is obtained, it is automatically
renewed as necessary. If the lease cannot be renewed, dhcpagent will
unconfigure the address, but the interface will be left up and dhcpa‐
gent will attempt to acquire a new address lease. dhcpagent monitors
system suspend/resume events and will validate any non-permanent leases
with the DHCP server upon resume. Similarly, dhcpagent monitors link
up/down events and will validate any non-permanent leases with the DHCP
server when the downed link is brought back up. The lease validation
mechanism will restart DHCP if the server indicates that the existing
lease is no longer valid. If the server cannot be contacted, then the
existing lease will continue. This behavior can be modified with the
"verified-lease-only" property in ipadm utility. For more information
on this property, see the ipadm(8) man page.
For IPv4, if the configured interface is found to be unplumbed, or to
have a different IP address, subnet mask, or broadcast address from
those obtained from DHCP, the interface is abandoned from DHCP control.
For IPv6, dhcpagent automatically plumbs and unplumbs logical inter‐
faces as necessary for the IPv6 addresses supplied by the server. The
IPv6 prefix length (netmask) is not set by the DHCPv6 protocol, but is
instead set by in.ndpd(8) using prefix information obtained by Router
Advertisements. If any of the logical interfaces created by dhcpagent
is unplumbed, or configured with a different IP address, it will be
abandoned from DHCP control. If the link-local interface is unplumbed,
then all addresses configured by DHCP on that physical interface will
be removed.
In addition to DHCP, dhcpagent also supports BOOTP (IPv4 only). See RFC
951, Bootstrap Protocol. Configuration parameters obtained from a BOOTP
server are treated identically to those received from a DHCP server,
except that the IP address received from a BOOTP server always has an
infinite lease.
DHCP also acts as a mechanism to configure other information needed by
the client, for example, the domain name and addresses of routers.
Aside from the IP address, and for IPv4 alone, the netmask, broadcast
address, and default router, the agent does not directly configure the
workstation, but instead acts as a database which may be interrogated
by other programs, and in particular by dhcpinfo(1).
On clients with a single interface, this is quite straightforward.
Clients with multiple interfaces may present difficulties, as it is
possible that some information arriving on different interfaces may
need to be merged, or may be inconsistent. Furthermore, the configura‐
tion of the interfaces is asynchronous, so requests may arrive while
some or all of the interfaces are still unconfigured. To handle these
cases, one interface may be designated as primary, which makes it the
authoritative source for the values of DHCP parameters in the case
where no specific interface is requested. See dhcpinfo(1) and ifcon‐
fig(8) for details.
All DHCP packets sent by dhcpagent include a vendor class identifier
(RFC 2132, option code 60; RFC 3315, option code 16). This identifier
is the same as the platform name returned by the uname -i command, ex‐
cept:
o Any commas in the platform name are changed to periods.
o If the name does not start with a stock symbol and a comma,
it is automatically prefixed with SUNW.
Address Properties
dhcpagent uses the following ipadm DHCP and addrconf type address ob‐
jects properties:
o verified-lease-only
o offer-wait
o client-id
o param-request-list
o param-ignore-list
Protocol Properties
dhcpagent uses the following ipadm DHCP properties:
o packet-burst-limit (dhcpv4 protocol property)
o packet-burst-limit (dhcpv6 protocol property)
See the ipadm(8) man page for the definition of these properties.
System wide default values for both the above groupings of properties
can be specified by using ipadm DHCPv4 and DHCPv6 protocol properties
of the same names.
Messages
The dhcpagent daemon writes information and error messages in five cat‐
egories:
critical
Critical messages indicate severe conditions that prevent proper
operation.
errors
Error messages are important, sometimes unrecoverable events due to
resource exhaustion and other unexpected failure of system calls;
ignoring errors may lead to degraded functionality.
warnings
Warnings indicate less severe problems, and in most cases, describe
unusual or incorrect datagrams received from servers, or requests
for service that cannot be provided.
informational
Informational messages provide key pieces of information that can
be useful to debugging a DHCP configuration at a site. Informa‐
tional messages are generally controlled by the -v option. However,
certain critical pieces of information, such as the IP address ob‐
tained, are always provided.
debug
Debugging messages, which may be generated at two different levels
of verbosity, are chiefly of benefit to persons having access to
source code, but may be useful as well in debugging difficult DHCP
configuration problems. Debugging messages are only generated when
using the config/debug SMF property is set.
DHCP Events and User-Defined Actions
If an executable (binary or script) is placed at /etc/dhcp/eventhook,
the dhcpagent daemon will automatically run that program when any of
the following events occur:
BOUND and BOUND6
These events occur during interface configuration. The event pro‐
gram is invoked when dhcpagent receives the DHCPv4 ACK or DHCPv6
Reply message from the DHCP server for the lease request of an ad‐
dress, indicating successful initial configuration of the inter‐
face. (See also the INFORM and INFORM6 events, which occur when
configuration parameters are obtained without address leases.)
EXTEND and EXTEND6
These events occur during lease extension. The event program is in‐
voked just after dhcpagent receives the DHCPv4 ACK or DHCPv6 Reply
from the DHCP server for the DHCPv4 REQUEST (renew) message or the
DHCPv6 Renew or Rebind message.
Note that with DHCPv6, the server might choose to remove some ad‐
dresses, add new address leases, and ignore (allow to expire) still
other addresses in a given Reply message. The EXTEND6 event occurs
when a Reply is received that leaves one or more address leases
still valid, even if the Reply message does not extend the lease
for any address. The event program is invoked just before any ad‐
dresses are removed, but just after any new addresses are added.
Those to be removed will be marked with the IFF_DEPRECATED flag.
EXPIRE and EXPIRE6
These events occur during lease expiration. For DHCPv4, the event
program is invoked just before the leased address is removed from
an interface. For DHCPv6, the event program is invoked just before
the last remaining leased addresses are removed from the interface.
DROP and DROP6
These events occur during the period when an interface is dropped.
The event program is invoked just before the interface is removed
from DHCP control. If the interface has been abandoned due to the
user unplumbing the interface, then this event will occur after the
user's action has taken place. The interface might not be present.
INFORM and INFORM6
These events occur when an interface acquires new or updated con‐
figuration information from a DHCP server by means of the DHCPv4
INFORM or the DHCPv6 Information-Request message. These messages
are sent using an ifconfig(8) dhcp inform command or when the
DHCPv6 Router Advertisement O (letter 0) bit is set and the M bit
is not set. Thus, these events occur when the DHCP client does not
obtain an IP address lease from the server, and instead obtains
only configuration parameters.
LOSS6
This event occurs during lease expiration when one or more valid
leases still remain. The event program is invoked just before ex‐
pired addresses are removed. Those being removed will be marked
with the IFF_DEPRECATED flag.
Note that this event is not associated with the receipt of the Re‐
ply message, which occurs only when one or more valid leases re‐
main, and occurs only with DHCPv6. If all leases have expired, then
the EXPIRE6 event occurs instead.
RELEASE and RELEASE6
This event occurs during the period when a leased address is re‐
leased. The event program is invoked just before dhcpagent relin‐
quishes the address on an interface and sends the DHCPv4 RELEASE or
DHCPv6 Release packet to the DHCP server.
The system does not provide a default event program. The file
/etc/dhcp/eventhook is expected to be owned by root and have a mode of
755.
The event program will be passed two arguments, the interface name and
the event name, respectively. For DHCPv6, the interface name is the
name of the physical interface.
The event program can use the dhcpinfo(1) utility to fetch additional
information about the interface. While the event program is invoked on
every event defined above, it can ignore those events in which it is
not interested. The event program runs with the same privileges and en‐
vironment as dhcpagent itself, except that stdin, stdout, and stderr
are redirected to /dev/null. Note that this means that the event pro‐
gram runs with root privileges.
If an invocation of the event program does not exit after 55 seconds,
it is sent a SIGTERM signal. If does not exit within the next three
seconds, it is terminated by a SIGKILL signal.
See EXAMPLES for an example event program.
Service Properties
The following SMF properties are supported by the dhcpagent daemon.
config/debug Sets the debug level to n. Two levels of debugging
are currently available, 1 and 2. The latter is more
verbose.
config/verbose Provide verbose output useful for debugging site con‐
figuration problems.
EXAMPLES
Example 1 Example Event Program
The following script is stored in the file /etc/dhcp/eventhook, owned
by root with a mode of 755. It is invoked upon the occurrence of the
events listed in the file.
#!/bin/sh
(
echo "Interface name: " $1
echo "Event: " $2
case $2 in
"BOUND")
echo "Address acquired from server "\
`/usr/sbin/dhcpinfo -i $1 ServerID`
;;
"BOUND6")
echo "Addresses acquired from server " \
`/usr/sbin/dhcpinfo -v6 -i $1 ServerID`
;;
"EXTEND")
echo "Lease extended for " \
`/usr/sbin/dhcpinfo -i $1 LeaseTime`" seconds"
;;
"EXTEND6")
echo "New lease information obtained on $i"
;;
"EXPIRE" | "DROP" | "RELEASE")
;;
esac
) >/var/run/dhcp_eventhook_output 2>&1
Note the redirection of stdout and stderr to a file.
FILES
/var/dhcp/if.dhc
/var/dhcp/if.dh6
Contains the configuration for interface. The mere existence of
this file does not imply that the configuration is correct, since
the lease might have expired. On start-up, dhcpagent confirms the
validity of the address using REQUEST (for DHCPv4) or Confirm
(DHCPv6).
/var/dhcp/duid
/var/dhcp/iaid
Contains persistent storage for DUID (DHCP Unique Identifier) and
IAID (Identity Association Identifier) values. The format of these
files is undocumented, and applications should not read from or
write to them.
/etc/dhcp/eventhook
Location of a DHCP event program.
ATTRIBUTES
See attributes(7) for descriptions of the following attributes:
tab() box; cw(2.75i) |cw(2.75i) lw(2.75i) |lw(2.75i) ATTRIBUTE TYPEAT‐
TRIBUTE VALUE _ Availabilitysystem/network _ Interface StabilityCommit‐
ted
SEE ALSO
dhcpinfo(1), ipadm(8), syslog(3C), attributes(7), dhcp(7), ifconfig(8),
in.mpathd(8), in.ndpd(8), init(8)
Croft, B. and Gilmore, J.,Bootstrap Protocol (BOOTP)RFC 951, Network
Working Group, September 1985.
Droms, R., Dynamic Host Configuration Protocol, RFC 2131, Network Work‐
ing Group, March 1997.
Lemon, T. and B. Sommerfeld. RFC 4361, Node-specific Client Identifiers
for Dynamic Host Configuration Protocol Version Four (DHCPv4). Nominum
and Sun Microsystems. February 2006.
Droms, R. RFC 3315, Dynamic Host Configuration Protocol for IPv6
(DHCPv6). Cisco Systems. July 2003.
NOTES
The dhcpagent daemon can be used on IPv4 logical interfaces, just as
with physical interfaces. When used on a logical interface, the daemon
automatically constructs a Client ID value based on the DUID and IAID
values, according to RFC 4361. The "client-id" property can be speci‐
fied when the address is created by using ipadm, and if provided, over‐
rides this automatic identifier.
Unlike physical IPv4 interfaces, dhcpagent does not add or remove de‐
fault routes associated with logical interfaces.
DHCP can be performed on IPMP IP interfaces to acquire and maintain
IPMP data addresses. Because an IPMP IP interface has no hardware ad‐
dress, the daemon automatically constructs a Client ID using the same
approach described above for IPv4 logical interfaces. In addition, the
lack of a hardware address means the daemon must set the "broadcast"
flag in all DISCOVER and REQUEST messages on IPMP IP interfaces. Some
DHCP servers may refuse such requests.
DHCP can be performed on IP interfaces that are part of an IPMP group
(to acquire and maintain test addresses). The daemon will automatically
set the NOFAILOVER and DEPRECATED flags on each test address. Addition‐
ally, the daemon will not add or remove default routes in this case.
Note that the actual DHCP packet exchange may be performed over any ac‐
tive IP interface in the IPMP group. It is strongly recommended that
test addresses have infinite leases. Otherwise, an extended network
outage detectable only by probes may cause test address leases to ex‐
pire, causing in.mpathd(8) to revert to link-based failure detection
and trigger an erroneous repair.
Oracle Solaris 11.4 23 Jan 2017 dhcpagent(8)