The [DHCPv6] section configures the DHCPv6 client, if it is
enabled with the DHCP= setting described above, or invoked by the
IPv6 Router Advertisement:
MUDURL=, IAID=, DUIDType=, DUIDRawData=, RequestOptions=
As in the [DHCPv4] section.
SendOption=
As in the [DHCPv4] section, however because DHCPv6 uses
16-bit fields to store option numbers, the option number is
an integer in the range 1...65536.
SendVendorOption=
Send an arbitrary vendor option in the DHCPv6 request. Takes
an enterprise identifier, DHCP option number, data type, and
data separated with a colon ("enterprise
identifier:option:type:value"). Enterprise identifier is an
unsigned integer in the range 1...4294967294. The option
number must be an integer in the range 1...254. Data type
takes one of "uint8", "uint16", "uint32", "ipv4address",
"ipv6address", or "string". Special characters in the data
string may be escaped using C-style escapes
[18]. This setting
can be specified multiple times. If an empty string is
specified, then all options specified earlier are cleared.
Defaults to unset.
UserClass=
A DHCPv6 client can use User Class option to identify the
type or category of user or applications it represents. The
information contained in this option is a string that
represents the user class of which the client is a member.
Each class sets an identifying string of information to be
used by the DHCP service to classify clients. Special
characters in the data string may be escaped using C-style
escapes
[18]. This setting can be specified multiple times. If
an empty string is specified, then all options specified
earlier are cleared. Takes a whitespace-separated list of
strings. Note that currently NUL
bytes are not allowed.
VendorClass=
A DHCPv6 client can use VendorClass option to identify the
vendor that manufactured the hardware on which the client is
running. The information contained in the data area of this
option is contained in one or more opaque fields that
identify details of the hardware configuration. Takes a
whitespace-separated list of strings.
PrefixDelegationHint=
Takes an IPv6 address with prefix length in the same format
as the Address= in the [Network] section. The DHCPv6 client
will include a prefix hint in the DHCPv6 solicitation sent to
the server. The prefix length must be in the range 1–128.
Defaults to unset.
UseAddress=
When true (the default), the IP addresses provided by the
DHCPv6 server will be assigned.
UseDNS=, UseNTP=, UseHostname=, UseDomains=
As in the [DHCPv4] section.
ForceDHCPv6PDOtherInformation=
Takes a boolean that enforces DHCPv6 stateful mode when the
'Other information' bit is set in Router Advertisement
messages. By default setting only the 'O' bit in Router
Advertisements makes DHCPv6 request network information in a
stateless manner using a two-message Information Request and
Information Reply message exchange. RFC 7084
[19],
requirement WPD-4, updates this behavior for a Customer Edge
router so that stateful DHCPv6 Prefix Delegation is also
requested when only the 'O' bit is set in Router
Advertisements. This option enables such a CE behavior as it
is impossible to automatically distinguish the intention of
the 'O' bit otherwise. By default this option is set to
false, enable it if no prefixes are delegated when the device
should be acting as a CE router.
WithoutRA=
Allows DHCPv6 client to start without router advertisements's
managed or other address configuration flag. Takes one of
"solicit" or "information-request". Defaults to unset.
RapidCommit=
Takes a boolean. The DHCPv6 client can obtain configuration
parameters from a DHCPv6 server through a rapid two-message
exchange (solicit and reply). When the rapid commit option is
enabled by both the DHCPv6 client and the DHCPv6 server, the
two-message exchange is used, rather than the default
four-message exchange (solicit, advertise, request, and
reply). The two-message exchange provides faster client
configuration and is beneficial in environments in which
networks are under a heavy load. See RFC 3315
[20] for
details. Defaults to true.