Technical References

Identifies the boot-file to use in the boot process of a client.
The server returns this file name in the 'file' field of its replies.
The packet-file-name cannot be longer than 128 characters.
packet-server-name string
Identifies the host-name of the server to use in a client's boot
process. The server returns this file name in the 'sname' field
of its replies. The packet-server-name field cannot be longer
than 64 characters.
packet-siaddr ipaddr
Identifies the IP address of the next server in the client boot
process. For example, this might be the address of a TFTP server
used by BOOTP clients. The server returns this address in the
'siaddr' field of its replies.
permanent-leases bool default = disabled
Indicates whether leases using this policy are permanently granted
to requesting clients. If leases are permanently granted,
the dhcp-lease-time will be "infinite."
preferred-lifetime time default = 1w
Assigns the default and maximum preferred lifetime for leases to
DHCPv6 client interfaces. Expressed in seconds and relative to
the time the server sent the packet, this attribute sets the
length of time that the address is preferred; that is, its use is
unrestricted. When the preferred lifetime expires, the address
becomes deprecated and its use is restricted.
reconfigure enumint(allow=1, disallow=2, require=3) default = allow
Controls DHCPv6 client reconfiguration support:
1 allow Allows clients to request reconfiguration
support and the server will honor the
request (default).
2 disallow Allows clients to request reconfiguration
support but the server will not honor
the clients' request.
3 require Requires clients to request reconfiguration
support and the server drops client
Solicit and Request messages that do not
include a Reconfigure-Accept option.
This attribute has special handling during the policy hierarchy
processing when checking the Prefix policies (embedded or named)
for the Prefixes on a Link. The Prefixes for the Link are
processed in alphabetic (case blind) order. For each Prefix, the
embedded and then named policy are checked. Only Prefixes to which
the client has access (based on selection tags, etc.) are checked
as follows:
- If any of the prefix policies has this attribute set to
disallow or require, that setting is used.
- Otherwise, if at least one has it set to allow, Reconfigure
is allowed.
- If no prefix policies have this attribute set, the remaining
policies in the hierarchy are checked.
reconfigure-via-relay bool default = false