[Kea-users] issue with same prefixes with different pools

Francis Dupont fdupont at isc.org
Mon Oct 30 10:54:36 UTC 2017

It does not work on 1.3.0 too (CfgSubnets4::add raises a DuplicateSubnetID
exception, IMHO both not the right exception and it should not raise
as there are different client classes so no possible ambiguity or

BTW if you put them in the same shared network you'll get the same error
and when it will be fixed the semantic will be a bit different because
if one of the pools is exhausted the other one will be used (vs returning
a NAK error saying that no more addresses are available).


Francis Dupont <fdupont at isc.org>

PS: until the bug is fixed I suggest to change the second subnet to use
a greater prefix length: it should work because the check is very
(too as explained by a todo in the code :-) basic.

More information about the Kea-users mailing list