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 conflict).
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). Thanks Francis Dupont <[email protected]> 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. _______________________________________________ Kea-users mailing list [email protected] https://lists.isc.org/mailman/listinfo/kea-users
