21 For IPv4, this daemon is started automatically during bootup if there
22 exists at least one dhcp.interface file in /etc. Only interfaces with a
23 corresponding /etc/dhcp.interface file are automatically configured
24 during boot.
25
26 For IPv6, this daemon is started automatically when commanded by
27 in.ndpd (based on IPv6 Routing Advertisement messages). No
28 /etc/dhcp.interface file is necessary, but such a file can be used to
29 specify an interface as "primary," provided that IPv4 DHCP is also in
30 use.
31
32 Network parameters needed for system configuration during bootup are
33 extracted from the information received by the daemon through the use
34 of the dhcpinfo(1) command. The daemon's default behavior can be
35 altered by changing the tunables in the /etc/default/dhcpagent file.
36 The daemon is controlled by the ifconfig(1M) utility. Check the status
37 of the daemon using the netstat(1M) and ifconfig(1M) commands.
38
39 SEE ALSO
40 dhcpinfo(1), dhcpagent(1M), ifconfig(1M), in.ndpd(1M), netstat(1M),
41 syslog(3C), dhcp_network(4), dhcptab(4), dhcpsvc.conf(4),
42 dhcp_inittab(4), ndpd.conf(4), dhcp_modules(5)
43
44 Alexander, S., and R. Droms. RFC 2132, DHCP Options and BOOTP Vendor
45 Extensions. Silicon Graphics, Inc. Bucknell University. March 1997.
46
47 Droms, R. RFC 1534, Interoperation Between DHCP and BOOTP. Bucknell
48 University. October 1993.
49
50 Droms, R. RFC 2131, Dynamic Host Configuration Protocol. Bucknell
51 University. March 1997.
52
53 Wimer, W. RFC 1542, Clarifications and Extensions for the Bootstrap
54 Protocol. Carnegie Mellon University. October 1993.
55
56 Lemon, T. and B. Sommerfeld. RFC 4361, Node-specific Client Identifiers
57 for Dynamic Host Configuration Protocol Version Four (DHCPv4). Nominum
58 and Sun Microsystems. February 2006.
59
60 Droms, R. RFC 3315, Dynamic Host Configuration Protocol for IPv6
61 (DHCPv6). Cisco Systems. July 2003.
62
63
64
65 August 15, 2014 DHCP(5)
|
21 For IPv4, this daemon is started automatically during bootup if there
22 exists at least one dhcp.interface file in /etc. Only interfaces with a
23 corresponding /etc/dhcp.interface file are automatically configured
24 during boot.
25
26 For IPv6, this daemon is started automatically when commanded by
27 in.ndpd (based on IPv6 Routing Advertisement messages). No
28 /etc/dhcp.interface file is necessary, but such a file can be used to
29 specify an interface as "primary," provided that IPv4 DHCP is also in
30 use.
31
32 Network parameters needed for system configuration during bootup are
33 extracted from the information received by the daemon through the use
34 of the dhcpinfo(1) command. The daemon's default behavior can be
35 altered by changing the tunables in the /etc/default/dhcpagent file.
36 The daemon is controlled by the ifconfig(1M) utility. Check the status
37 of the daemon using the netstat(1M) and ifconfig(1M) commands.
38
39 SEE ALSO
40 dhcpinfo(1), dhcpagent(1M), ifconfig(1M), in.ndpd(1M), netstat(1M),
41 syslog(3C), dhcp_inittab(4), ndpd.conf(4)
42
43 Alexander, S., and R. Droms. RFC 2132, DHCP Options and BOOTP Vendor
44 Extensions. Silicon Graphics, Inc. Bucknell University. March 1997.
45
46 Droms, R. RFC 1534, Interoperation Between DHCP and BOOTP. Bucknell
47 University. October 1993.
48
49 Droms, R. RFC 2131, Dynamic Host Configuration Protocol. Bucknell
50 University. March 1997.
51
52 Wimer, W. RFC 1542, Clarifications and Extensions for the Bootstrap
53 Protocol. Carnegie Mellon University. October 1993.
54
55 Lemon, T. and B. Sommerfeld. RFC 4361, Node-specific Client Identifiers
56 for Dynamic Host Configuration Protocol Version Four (DHCPv4). Nominum
57 and Sun Microsystems. February 2006.
58
59 Droms, R. RFC 3315, Dynamic Host Configuration Protocol for IPv6
60 (DHCPv6). Cisco Systems. July 2003.
61
62
63
64 February 13, 2020 DHCP(5)
|