+2291. [func] fdupont
+ Added three new API commands: subnet4-select-test and
+ subnet4o6-select-test to kea-dhcp4, and subnet6-select-test
+ to kea-dhcp6. These commands can be used to check which
+ subnet the server will select based on given input paramters.
+ (Gitlab #2794)
+
2290. [bug] razvan
Fixed applying 'output_options' when using the 'config-set'
command. Deprecated 'output_options' which will be removed in
The ``subnet4-select-test`` Command
-----------------------------------
-The :isccmd:`subnet4-select-test` provides a way to test DHCPv4 subnet selection based
+The :isccmd:`subnet4-select-test` provides a way to test DHCPv4 subnet selection based
on a set of input parameters typically supplied in a client packet.
Recognized parameters take strings and are:
-------------------------------------
The :isccmd:`subnet4o6-select-test` provides a way to test DHCPv4-over-DHCPv6 subnet
-selection based on a set of input parameters typically supplied in a client
+selection based on a set of input parameters typically supplied in a client
packet. Recognized parameters take strings and are:
- ``interface`` - the incoming interface name of the DHCPv6 server
- ``classes`` - (list of strings) client classes (allowing to select a guarded subnet)
According to the code only ``remote``, ``interface-id`` and ``interface``
-selectors are used. In DHCPv4-over-DHCPv6 implementation ``interface` and
+selectors are used. In DHCPv4-over-DHCPv6 implementation ``interface` and
``remote`` values are transmitted from the DHCPv6 server, ``interface-id``
and ``link`` are carried in the relay info part of the DHCPv6 packet so
are the same as for the DHCPv6 server.
The ``subnet6-select-test`` Command
-----------------------------------
-The :isccmd:`subnet6-select-test` provides a way to test DHCPv6 subnet selection based
+The :isccmd:`subnet6-select-test` provides a way to test DHCPv6 subnet selection based
on a set of input parameters typically supplied in a client packet.
Recognized parameters take strings and are: