From: Francis Dupont Date: Tue, 2 Jul 2024 18:22:32 +0000 (+0200) Subject: [#1387] Checkpoint: updated doc X-Git-Tag: Kea-2.7.3~60 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=9e208d02489b542a29bb44f5348fc67dfa62f4cb;p=thirdparty%2Fkea.git [#1387] Checkpoint: updated doc --- diff --git a/doc/sphinx/arm/dhcp6-srv.rst b/doc/sphinx/arm/dhcp6-srv.rst index 87cefa6bda..2e42d5ddbb 100644 --- a/doc/sphinx/arm/dhcp6-srv.rst +++ b/doc/sphinx/arm/dhcp6-srv.rst @@ -4271,6 +4271,23 @@ another. host reservation has preference over a global reservation when both exist for the same client. +.. note:: + + Since Kea 2.7.1, a reserved (so delegated) prefix can be associated + with a single prefix to exclude as for prefix delegation pools + :ref:`pd-exclude-option`. The host reservation syntax is extended + by a new entry ``excluded-prefixes`` which when is present must have + the same size as the ``prefixes`` entry: both contains strings + representing IPv6 prefixes (e.g. ``2001:db8::/48``). Each element of + the ``excluded-prefixes`` must be either the empty string or match + the prefix at the same position in the ``prefixes`` list, e.g. + ``2001:db8:0:1::/64`` matches / can be associated with ``2001:db8::/48``. + An empty ``excluded-prefixes`` list or a list with only empty strings + can be omitted (and will be omitted when produced by Kea). + + todo: add something about adding the pd-exclude option to returned + prefixes as done for prefix delegation pools. + .. _reservation6-conflict: Conflicts in DHCPv6 Reservations