1 '\" te
2 .\" Copyright 2014 Garrett D'Amore <garrett@damore.org>
3 .\" Copyright (c) 2001, Sun Microsystems, Inc. All Rights Reserved.
4 .\" 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.
5 .\" 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.
6 .\" 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]
7 .TH DHCP 5 "Aug 15, 2014"
8 .SH NAME
9 dhcp \- Dynamic Host Configuration Protocol
10 .SH DESCRIPTION
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 .LP
19 This manual page provides a brief summary of the \fBDHCP\fR
20 implementation.
21 .SS "DHCP Client"
22 .LP
23 The DHCP client is implemented as background daemon,
24 \fBdhcpagent\fR(1M).
25 .LP
26 For IPv4, this daemon is started automatically during bootup if there exists at
27 least one \fBdhcp.\fR\fIinterface\fR file in \fB/etc\fR. Only interfaces with a
28 corresponding \fB\fR\fB/etc/dhcp.\fR\fB\fIinterface\fR\fR file are
29 automatically configured during boot.
30 .LP
31 For IPv6, this daemon is started automatically when commanded by \fBin.ndpd\fR
32 (based on IPv6 Routing Advertisement messages). No
33 \fB/etc/dhcp\fR.\fIinterface\fR file is necessary, but such a file can be used
34 to specify an interface as "primary," provided that IPv4 DHCP is also in use.
35 .LP
36 Network parameters needed for system configuration during bootup are extracted
37 from the information received by the daemon through the use of the
38 \fBdhcpinfo\fR(1) command. The daemon's default behavior can be altered by
39 changing the tunables in the \fB/etc/default/dhcpagent\fR file. The daemon is
40 controlled by the \fBifconfig\fR(1M) utility. Check the status of the daemon
41 using the \fBnetstat\fR(1M) and \fBifconfig\fR(1M) commands.
42 .SH SEE ALSO
43 .LP
44 \fBdhcpinfo\fR(1), \fBdhcpagent\fR(1M),
45 \fBifconfig\fR(1M),
46 \fBin.ndpd\fR(1M), \fBnetstat\fR(1M),
47 \fBsyslog\fR(3C),
48 \fBdhcp_network\fR(4), \fBdhcptab\fR(4), \fBdhcpsvc.conf\fR(4),
49 \fBdhcp_inittab\fR(4), \fBndpd.conf\fR(4), \fBdhcp_modules\fR(5)
50 .LP
51 Alexander, S., and R. Droms. \fIRFC 2132, DHCP Options and BOOTP Vendor
52 Extensions\fR. Silicon Graphics, Inc. Bucknell University. March 1997.
53 .LP
54 Droms, R. \fIRFC 1534, Interoperation Between DHCP and BOOTP\fR. Bucknell
55 University. October 1993.
56 .LP
57 Droms, R. \fIRFC 2131, Dynamic Host Configuration Protocol\fR. Bucknell
58 University. March 1997.
59 .LP
60 Wimer, W. \fIRFC 1542, Clarifications and Extensions for the Bootstrap
61 Protocol\fR. Carnegie Mellon University. October 1993.
62 .LP
63 Lemon, T. and B. Sommerfeld. \fIRFC 4361, Node-specific Client Identifiers for
64 Dynamic Host Configuration Protocol Version Four (DHCPv4)\fR. Nominum and Sun
65 Microsystems. February 2006.
66 .LP
67 Droms, R. \fIRFC 3315, Dynamic Host Configuration Protocol for IPv6
68 (DHCPv6)\fR. Cisco Systems. July 2003.
|
1 '\" te
2 .\" Copyright 2014 Garrett D'Amore <garrett@damore.org>
3 .\" Copyright (c) 2001, Sun Microsystems, Inc. All Rights Reserved.
4 .\" 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.
5 .\" 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.
6 .\" 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]
7 .TH DHCP 5 "Feb 13, 2020"
8 .SH NAME
9 dhcp \- Dynamic Host Configuration Protocol
10 .SH DESCRIPTION
11 Dynamic Host Configuration Protocol (\fBDHCP\fR) enables host systems in a
12 \fBTCP/IP\fR network to be configured automatically for the network as they
13 boot. \fBDHCP\fR uses a client/server mechanism: servers store configuration
14 information for clients, and provide that information upon a client's request.
15 The information can include the client's \fBIP\fR address and information about
16 network services available to the client.
17 .LP
18 This manual page provides a brief summary of the \fBDHCP\fR
19 implementation.
20 .SS "DHCP Client"
21 The DHCP client is implemented as background daemon,
22 \fBdhcpagent\fR(1M).
23 .LP
24 For IPv4, this daemon is started automatically during bootup if there exists at
25 least one \fBdhcp.\fR\fIinterface\fR file in \fB/etc\fR. Only interfaces with a
26 corresponding \fB\fR\fB/etc/dhcp.\fR\fB\fIinterface\fR\fR file are
27 automatically configured during boot.
28 .LP
29 For IPv6, this daemon is started automatically when commanded by \fBin.ndpd\fR
30 (based on IPv6 Routing Advertisement messages). No
31 \fB/etc/dhcp\fR.\fIinterface\fR file is necessary, but such a file can be used
32 to specify an interface as "primary," provided that IPv4 DHCP is also in use.
33 .LP
34 Network parameters needed for system configuration during bootup are extracted
35 from the information received by the daemon through the use of the
36 \fBdhcpinfo\fR(1) command. The daemon's default behavior can be altered by
37 changing the tunables in the \fB/etc/default/dhcpagent\fR file. The daemon is
38 controlled by the \fBifconfig\fR(1M) utility. Check the status of the daemon
39 using the \fBnetstat\fR(1M) and \fBifconfig\fR(1M) commands.
40 .SH SEE ALSO
41 \fBdhcpinfo\fR(1), \fBdhcpagent\fR(1M),
42 \fBifconfig\fR(1M),
43 \fBin.ndpd\fR(1M), \fBnetstat\fR(1M),
44 \fBsyslog\fR(3C),
45 \fBdhcp_inittab\fR(4), \fBndpd.conf\fR(4)
46 .LP
47 Alexander, S., and R. Droms. \fIRFC 2132, DHCP Options and BOOTP Vendor
48 Extensions\fR. Silicon Graphics, Inc. Bucknell University. March 1997.
49 .LP
50 Droms, R. \fIRFC 1534, Interoperation Between DHCP and BOOTP\fR. Bucknell
51 University. October 1993.
52 .LP
53 Droms, R. \fIRFC 2131, Dynamic Host Configuration Protocol\fR. Bucknell
54 University. March 1997.
55 .LP
56 Wimer, W. \fIRFC 1542, Clarifications and Extensions for the Bootstrap
57 Protocol\fR. Carnegie Mellon University. October 1993.
58 .LP
59 Lemon, T. and B. Sommerfeld. \fIRFC 4361, Node-specific Client Identifiers for
60 Dynamic Host Configuration Protocol Version Four (DHCPv4)\fR. Nominum and Sun
61 Microsystems. February 2006.
62 .LP
63 Droms, R. \fIRFC 3315, Dynamic Host Configuration Protocol for IPv6
64 (DHCPv6)\fR. Cisco Systems. July 2003.
|