5 # Common Development and Distribution License (the "License").
6 # You may not use this file except in compliance with the License.
7 #
8 # You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
9 # or http://www.opensolaris.org/os/licensing.
10 # See the License for the specific language governing permissions
11 # and limitations under the License.
12 #
13 # When distributing Covered Code, include this CDDL HEADER in each
14 # file and include the License file at usr/src/OPENSOLARIS.LICENSE.
15 # If applicable, add the following below this CDDL HEADER, with the
16 # fields enclosed by brackets "[]" replaced with your own identifying
17 # information: Portions Copyright [yyyy] [name of copyright owner]
18 #
19 # CDDL HEADER END
20 #
21
22 #
23 # Copyright 2009 Sun Microsystems, Inc. All rights reserved.
24 # Use is subject to license terms.
25 #
26
27 #
28 # This file contains tunable parameters for dhcpagent(1M).
29 #
30
31 # All parameters can be tuned for a specific interface by prepending
32 # the interface name to the parameter name. For example, to make
33 # VERIFIED_LEASE_ONLY happen on all interfaces except hme0, specify:
34 #
35 # hme0.VERIFIED_LEASE_ONLY=no
36 # VERIFIED_LEASE_ONLY=yes
37 #
38 # An interface name alone specifies IPv4 DHCP. For DHCPv6, append ".v6".
39 # Some examples:
40 #
41 # hme0.VERIFIED_LEASE_ONLY=no specify hme0 v4 behavior
42 # hme0.v6.VERIFIED_LEASE_ONLY=no specify hme0 v6 behavior
43 # VERIFIED_LEASE_ONLY=no match all v4 interfaces
44 # .v6.VERIFIED_LEASE_ONLY=no match all v6 interfaces
73 # responses to a DISCOVER. If it receives no OFFERs in this time, it
74 # then waits for another 3 seconds, and so forth. To change this
75 # behavior, set and uncomment the following parameter-value pair.
76 # Note: this does not control the retransmission strategy for
77 # DISCOVERs, which is formally specified in RFC 2131. This parameter
78 # is specified in seconds.
79 #
80 # OFFER_WAIT=
81
82 # By default, the DHCP agent does not send out a client identifier
83 # (and hence, the chaddr field is used by the DHCP server as the
84 # client identifier.) To make the DHCP agent send a client
85 # identifier, set and uncomment the following parameter-value pair.
86 # Note that by default this is treated as an NVT ASCII string. To
87 # specify a binary value, prepend "0x" to a sequence of hexadecimal
88 # digits (for example, the value 0xAABBCC11 would set the client
89 # identifier to the 4-byte binary sequence 0xAA 0xBB 0xCC 0x11).
90 #
91 # CLIENT_ID=
92
93 # By default, the DHCP agent will try to request the hostname currently
94 # associated with the interface performing DHCP. If this option is
95 # enabled, the agent will attempt to find a host name in /etc/hostname.<if>,
96 # which must contain a line of the form
97 #
98 # inet name
99 #
100 # where "name" is a single RFC 1101-compliant token. If found, the token
101 # will be used to request that host name from the DHCP server. To prevent
102 # this, uncomment the following line.
103 #
104 # REQUEST_HOSTNAME=no
105
106 # By default, a parameter request list requesting a subnet mask (1),
107 # router (3), DNS server (6), hostname (12), DNS domain (15), broadcast
108 # address (28), and encapsulated vendor options (43), is sent to the DHCP
109 # server when the DHCP agent sends requests. However, if desired, this
110 # can be changed by altering the following parameter-value pair. The
111 # numbers correspond to the values defined in the IANA bootp-dhcp-parameters
112 # registry at the time of this writing. Site and standard option names from
113 # /etc/dhcp/inittab are also accepted.
114 #
115 PARAM_REQUEST_LIST=1,3,6,12,15,28,43
116
117 # The default DHCPv6 parameter request list has preference (7), unicast (12),
118 # DNS addresses (23), DNS search list (24), NIS addresses (27), and
119 # NIS domain (29). This may be changed by altering the following parameter-
120 # value pair. The numbers correspond to the values defined in the IANA
121 # dhcpv6-parameters registry at the time of this writing. Site and standard
122 # option names from /etc/dhcp/inittab6 are also accepted.
|
5 # Common Development and Distribution License (the "License").
6 # You may not use this file except in compliance with the License.
7 #
8 # You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
9 # or http://www.opensolaris.org/os/licensing.
10 # See the License for the specific language governing permissions
11 # and limitations under the License.
12 #
13 # When distributing Covered Code, include this CDDL HEADER in each
14 # file and include the License file at usr/src/OPENSOLARIS.LICENSE.
15 # If applicable, add the following below this CDDL HEADER, with the
16 # fields enclosed by brackets "[]" replaced with your own identifying
17 # information: Portions Copyright [yyyy] [name of copyright owner]
18 #
19 # CDDL HEADER END
20 #
21
22 #
23 # Copyright 2009 Sun Microsystems, Inc. All rights reserved.
24 # Use is subject to license terms.
25 # Copyright (c) 2016, Chris Fraire <cfraire@me.com>.
26 #
27
28 #
29 # This file contains tunable parameters for dhcpagent(1M).
30 #
31
32 # All parameters can be tuned for a specific interface by prepending
33 # the interface name to the parameter name. For example, to make
34 # VERIFIED_LEASE_ONLY happen on all interfaces except hme0, specify:
35 #
36 # hme0.VERIFIED_LEASE_ONLY=no
37 # VERIFIED_LEASE_ONLY=yes
38 #
39 # An interface name alone specifies IPv4 DHCP. For DHCPv6, append ".v6".
40 # Some examples:
41 #
42 # hme0.VERIFIED_LEASE_ONLY=no specify hme0 v4 behavior
43 # hme0.v6.VERIFIED_LEASE_ONLY=no specify hme0 v6 behavior
44 # VERIFIED_LEASE_ONLY=no match all v4 interfaces
45 # .v6.VERIFIED_LEASE_ONLY=no match all v6 interfaces
74 # responses to a DISCOVER. If it receives no OFFERs in this time, it
75 # then waits for another 3 seconds, and so forth. To change this
76 # behavior, set and uncomment the following parameter-value pair.
77 # Note: this does not control the retransmission strategy for
78 # DISCOVERs, which is formally specified in RFC 2131. This parameter
79 # is specified in seconds.
80 #
81 # OFFER_WAIT=
82
83 # By default, the DHCP agent does not send out a client identifier
84 # (and hence, the chaddr field is used by the DHCP server as the
85 # client identifier.) To make the DHCP agent send a client
86 # identifier, set and uncomment the following parameter-value pair.
87 # Note that by default this is treated as an NVT ASCII string. To
88 # specify a binary value, prepend "0x" to a sequence of hexadecimal
89 # digits (for example, the value 0xAABBCC11 would set the client
90 # identifier to the 4-byte binary sequence 0xAA 0xBB 0xCC 0x11).
91 #
92 # CLIENT_ID=
93
94 # By default, for an IPv4 interface that is not in an IP network
95 # multipathing (IPMP) group, that is not IP over InfiniBand (IPoIB), and
96 # that is not a logical interface, the DHCP agent will forgo sending a
97 # client identifier unless CLIENT_ID is defined.
98 #
99 # To use a system-managed, RFC 3315-style (i.e., DHCPv6-style) binding
100 # identifier as documented in RFC 4361, "Node-specific Client Identifiers
101 # for DHCPv4," for all IPv4 interfaces (unless CLIENT_ID is defined),
102 # uncomment the following line.
103 #
104 # V4_DEFAULT_IAID_DUID=yes
105
106 # By default, the DHCP agent will try to request the Fully Qualified Domain
107 # Name (FQDN) currently associated with the interface performing DHCP. The
108 # hostname is defined by using the -h,--reqhost option of ipadm(1M) or the
109 # ncu ip-reqhost property of nwamcfg(1M) or by flagging the interface as
110 # primary so that nodename(4) is used as the hostname.
111 #
112 # A defined hostname will be used as the FQDN if it is "rooted" (i.e., if
113 # it ends with a '.') or if it consists of at least three DNS labels (e.g.,
114 # srv.example.com). If the hostname is not an FQDN, then either a defined
115 # defaultdomain(4) or a defined resolv.conf(4) domain will be appended to
116 # form an FQDN. If no FQDN can be determined, the option will not be used.
117 #
118 # If this REQUEST_FQDN option is enabled, an FQDN will be sent in messages
119 # to the DHCP server along with RFC 4702 options to request that a
120 # collaborating DNS server perform DNS updates for A and PTR resource
121 # records. To prevent sending FQDN and DNS options, uncomment the line
122 # below.
123 #
124 # If an FQDN is sent, REQUEST_HOSTNAME processing will not be done, per RFC
125 # 4702 (3.1): "clients that send the Client FQDN option in their messages
126 # MUST NOT also send the Host Name."
127 #
128 # REQUEST_FQDN=no
129
130 # By default, the DHCP agent will try to request the hostname currently
131 # associated with the interface performing DHCP. If this option is
132 # enabled, the agent will attempt to use an -h,--reqhost option saved with
133 # ipadm(1M) or an ncu ip-reqhost property set with nwamcfg(1M); or else
134 # attempt to find a host name in /etc/hostname.<if>, which must contain a
135 # line of the form
136 #
137 # inet name
138 #
139 # where "name" is a single RFC 1101-compliant token; or else use
140 # nodename(4) for a DHCP interface flagged as primary. If found in any of
141 # these configurations, the token will be used to request that host name
142 # from the DHCP server. To prevent this, uncomment the following line.
143 #
144 # REQUEST_HOSTNAME=no
145
146 # By default, a parameter request list requesting a subnet mask (1),
147 # router (3), DNS server (6), hostname (12), DNS domain (15), broadcast
148 # address (28), and encapsulated vendor options (43), is sent to the DHCP
149 # server when the DHCP agent sends requests. However, if desired, this
150 # can be changed by altering the following parameter-value pair. The
151 # numbers correspond to the values defined in the IANA bootp-dhcp-parameters
152 # registry at the time of this writing. Site and standard option names from
153 # /etc/dhcp/inittab are also accepted.
154 #
155 PARAM_REQUEST_LIST=1,3,6,12,15,28,43
156
157 # The default DHCPv6 parameter request list has preference (7), unicast (12),
158 # DNS addresses (23), DNS search list (24), NIS addresses (27), and
159 # NIS domain (29). This may be changed by altering the following parameter-
160 # value pair. The numbers correspond to the values defined in the IANA
161 # dhcpv6-parameters registry at the time of this writing. Site and standard
162 # option names from /etc/dhcp/inittab6 are also accepted.
|