I recently redeployed Kea 2.2.0 in my network; previously it was behind a
router providing relay services, but now it is directly connected to the
subnets it serves. It is running on Linux, kernel is 6.1.<something>.
In the new configuration it has four interfaces enabled, and four subnets (one
per interface). The interfaces are not configured with unicast support (there
is no "/<address>" after the interface name), but the actual underlying
interfaces *do* have GUAs in the matching subnets.
Without an 'interface' specification in the subnet configuration, Kea was
unable to match incoming client requests to subnets. I can understand why this
would be the case if the underlying interface only had a LL address, but it has
both LL and GUA and the GUA matches the subnet. I had expected that kea-dhcp6
would then operate like kea-dhcp4 does, and enumerate the addresses on the
underlying interface to determine if any subnets matched it. I was wrong :-)
My system is working fine with 'interface' in the subnet configuration, but I
thought it might be worthwhile to mention this in case any other users
experience it. I could also suggest that the wording in the ARM be improved to
indicate that 'interface' may be almost-mandatory for common configurations;
right now the wording there makes it seems like 'interface' should not be
needed in common configurations.
--
ISC funds the development of this software with paid support subscriptions.
Contact us at https://www.isc.org/contact/ for more information.
To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users.
Kea-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-users
