From: Francis Dupont Date: Wed, 3 Jun 2020 22:00:11 +0000 (+0200) Subject: [#1265] Updated ARM X-Git-Tag: Kea-1.7.10~7^2~7 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=0d006d317810e7d8bb09739f8948353961bac48b;p=thirdparty%2Fkea.git [#1265] Updated ARM --- diff --git a/doc/sphinx/arm/dhcp4-srv.rst b/doc/sphinx/arm/dhcp4-srv.rst index 4fb6bc8127..a366793f57 100644 --- a/doc/sphinx/arm/dhcp4-srv.rst +++ b/doc/sphinx/arm/dhcp4-srv.rst @@ -5166,6 +5166,13 @@ configurations, e.g. shared networks. See :ref:`dhcp4-relay-override` for detail classification mechanism alters the way in which a subnet is selected for the client, depending on the classes to which the client belongs. +.. note:: + + Starting with Kea 1.7.9, the order used to find a subnet which matches + required conditions to be selected is the ascending subnet identifier + order. When the selected subnet is a member of a shared network the + whole shared network is selected. + .. _dhcp4-relay-override: Using a Specific Relay Agent for a Subnet diff --git a/doc/sphinx/arm/dhcp6-srv.rst b/doc/sphinx/arm/dhcp6-srv.rst index bcfbed8db2..073495dd6b 100644 --- a/doc/sphinx/arm/dhcp6-srv.rst +++ b/doc/sphinx/arm/dhcp6-srv.rst @@ -4921,6 +4921,16 @@ DHCPv6 server: Using a Specific Relay Agent for a Subnet ========================================= +The DHCPv6 server follows the same principles than in IPv4 to select +a subnet for the client with noticable differences mainly for relays. + +.. note:: + + Starting with Kea 1.7.9, the order used to find a subnet which matches + required conditions to be selected is the ascending subnet identifier + order. When the selected subnet is a member of a shared network the + whole shared network is selected. + The relay must have an interface connected to the link on which the clients are being configured. Typically the relay has a global IPv6 address configured on that interface, which belongs to the subnet from