Kea testing observations

Started by MoonbeamFrame, March 06, 2024, 11:45:10 AM

Previous topic - Next topic
March 06, 2024, 11:45:10 AM Last Edit: March 06, 2024, 12:20:20 PM by MoonbeamFrame
I've migrated a couple of firewalls to see how Kea behaves. Both have multiple networks which are using DHCP.  Both migrations were seamless and Kea is working as expected.

Some of the things I experienced I think could be enhanced if they are possible to deploy.

- When creating a subnet I would find it useful to be able to also define a name/label, or pull-in the interface name for the subnet (from a readability perspective).

- When creating a subnet you can enter a pool (as a /29 in my test) which is not in the subnet.

- When creating a reservation there is a check that the IP address is in the displayed subnet. As all the subnets are already defined this could be reversed such that the subnet is set from the entered IP address. Which is another way of saying I frequently did not have the right subnet when manually migrating reservations. That may have also been less of an issue if the subnet selection was name based rather than IP address based.


For the log file

- I miss seeing the DHCP discover, offer, etc. messages.

- ISC DHCPv4 will log a hostname if available, I've not seen them in the Kea logs yet.

While neither of the log messages are required they make it easier to spot a new device trying to connect to a network and if there is an issue with it.