1 '\" te
   2 .\" Copyright (c) 2001, Sun Microsystems, Inc. All Rights Reserved.
   3 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License").  You may not use this file except in compliance with the License.
   4 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.  See the License for the specific language governing permissions and limitations under the License.
   5 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE.  If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
   6 .TH DHCP 5 "Jan 5, 2007"
   7 .SH NAME
   8 dhcp \- Dynamic Host Configuration Protocol
   9 .SH DESCRIPTION
  10 .sp
  11 .LP
  12 Dynamic Host Configuration Protocol (\fBDHCP\fR) enables host systems in a
  13 \fBTCP/IP\fR network to be configured automatically for the network as they
  14 boot. \fBDHCP\fR uses a client/server mechanism: servers store configuration
  15 information for clients, and provide that information upon a client's request.
  16 The information can include the client's \fBIP\fR address and information about
  17 network services available to the client.
  18 .sp
  19 .LP
  20 This manual page provides a brief summary of the Solaris \fBDHCP\fR
  21 implementation.
  22 .SS "Solaris DHCP Client"
  23 .sp
  24 .LP
  25 The Solaris DHCP client is implemented as background daemon,
  26 \fBdhcpagent\fR(1M).
  27 .sp
  28 .LP
  29 For IPv4, this daemon is started automatically during bootup if there exists at
  30 least one \fBdhcp.\fR\fIinterface\fR file in \fB/etc\fR. Only interfaces with a
  31 corresponding \fB\fR\fB/etc/dhcp.\fR\fB\fIinterface\fR\fR file are
  32 automatically configured during boot.
  33 .sp
  34 .LP
  35 For IPv6, this daemon is started automatically when commanded by \fBin.ndpd\fR
  36 (based on IPv6 Routing Advertisement messages). No
  37 \fB/etc/dhcp\fR.\fIinterface\fR file is necessary, but such a file can be used
  38 to specify an interface as "primary," provided that IPv4 DHCP is also in use.
  39 .sp
  40 .LP
  41 Network parameters needed for system configuration during bootup are extracted
  42 from the information received by the daemon through the use of the
  43 \fBdhcpinfo\fR(1) command. The daemon's default behavior can be altered by
  44 changing the tunables in the \fB/etc/default/dhcpagent\fR file. The daemon is
  45 controlled by the \fBifconfig\fR(1M) utility. Check the status of the daemon
  46 using the \fBnetstat\fR(1M) and \fBifconfig\fR(1M) commands.
  47 .SS "Solaris DHCP Server"
  48 .sp
  49 .LP
  50 The Solaris \fBDHCP\fR server is implemented as a background daemon,
  51 \fBin.dhcpd\fR(1M). This daemon can deliver network configuration information
  52 to either \fBBOOTP\fR or \fBDHCP\fR clients. The Solaris \fBDHCP\fR service can
  53 be managed using the \fBdhcpmgr\fR(1M) \fBGUI\fR or the command line utilities
  54 \fBdhcpconfig\fR(1M), \fBdhtadm\fR(1M), and \fBpntadm\fR(1M).
  55 .SS "DHCP Configuration Tables"
  56 .sp
  57 .LP
  58 The Solaris \fBDHCP\fR server stores client configuration information in the
  59 following two types of tables:
  60 .sp
  61 .ne 2
  62 .na
  63 \fB\fBdhcptab\fR tables\fR
  64 .ad
  65 .RS 23n
  66 Contain macros and options (also known as symbols), used to construct a package
  67 of configuration information to send to each \fBDHCP\fR client. There exists
  68 only one \fBdhcptab\fR for the \fBDHCP\fR service. The \fBdhcptab\fR(4) can be
  69 viewed and modified using the \fBdhtadm\fR(1M) command or \fBdhcpmgr\fR(1M)
  70 graphical utility. See \fBdhcptab\fR(4) for more information about the syntax
  71 of \fBdhcptab\fR records. See \fBdhcp_inittab\fR(4) for more information about
  72 the \fBDHCP\fR options and symbols.
  73 .RE
  74 
  75 .sp
  76 .ne 2
  77 .na
  78 \fB\fBDHCP\fR network tables\fR
  79 .ad
  80 .RS 23n
  81 \fBDHCP\fR network tables, which contain mappings of client \fBID\fRs to
  82 \fBIP\fR addresses and parameters associated with those addresses. Network
  83 tables are named with the \fBIP\fR address of the network, and can be created,
  84 viewed, and modified using the \fBpntadm\fR command or \fBdhcpmgr\fR graphical
  85 utility. See \fBdhcp_network\fR(4) for more information about network tables.
  86 .RE
  87 
  88 .SH SEE ALSO
  89 .sp
  90 .LP
  91 \fBdhcpinfo\fR(1), \fBdhcpagent\fR(1M), \fBdhcpconfig\fR(1M),
  92 \fBdhcpmgr\fR(1M), \fBdhtadm\fR(1M), \fBifconfig\fR(1M), \fBin.dhcpd\fR(1M),
  93 \fBin.ndpd\fR(1M), \fBnetstat\fR(1M), \fBpntadm\fR(1M), \fBsyslog\fR(3C),
  94 \fBdhcp_network\fR(4), \fBdhcptab\fR(4), \fBdhcpsvc.conf\fR(4),
  95 \fBdhcp_inittab\fR(4), \fBndpd.conf\fR(4), \fBdhcp_modules\fR(5)
  96 .sp
  97 .LP
  98 \fISolaris DHCP Service Developer\&'s Guide\fR
  99 .sp
 100 .LP
 101 Alexander, S., and R. Droms. \fIRFC 2132, DHCP Options and BOOTP Vendor
 102 Extensions\fR. Silicon Graphics, Inc. Bucknell University. March 1997.
 103 .sp
 104 .LP
 105 Droms, R. \fIRFC 1534, Interoperation Between DHCP and BOOTP\fR. Bucknell
 106 University. October 1993.
 107 .sp
 108 .LP
 109 Droms, R. \fIRFC 2131, Dynamic Host Configuration Protocol\fR. Bucknell
 110 University. March 1997.
 111 .sp
 112 .LP
 113 Wimer, W. \fIRFC 1542, Clarifications and Extensions for the Bootstrap
 114 Protocol\fR. Carnegie Mellon University. October 1993.
 115 .sp
 116 .LP
 117 Lemon, T. and B. Sommerfeld. \fIRFC 4361, Node-specific Client Identifiers for
 118 Dynamic Host Configuration Protocol Version Four (DHCPv4)\fR. Nominum and Sun
 119 Microsystems. February 2006.
 120 .sp
 121 .LP
 122 Droms, R. \fIRFC 3315, Dynamic Host Configuration Protocol for IPv6
 123 (DHCPv6)\fR. Cisco Systems. July 2003.