[kea-dev] Interface management

Philip Prindeville philipp_subx at redfish-solutions.com
Sat Nov 1 16:55:42 UTC 2025


Hi Zachary.

The two cases of dynamic interfaces on a server that come to mind are (1) tunnels and (2) canned VM images running in the cloud (like Amazon AMI’s).

I don’t see the point of DHCP over a tunnel in the first case (since you’d need an IP already to bring up the tunnel), but it’s certainly potentially useful in the 2nd case.

-Philip



> On Oct 29, 2025, at 1:46 PM, Noble, Zachary C CIV (USA) <zachary.c.noble.civ at us.navy.mil> wrote:
> 
> Sorry, I sent this to the kea-users mail group, but I think it really should have gone here:
>  I haven’t seen any mention of this in any open tickets from what I could see, but I would think it would be nice to have the ability to add/edit/delete interfaces from the interfaces-config interfaces list via the api and/or the kea-ctrl-agent. I am trying to use kea in combination with stork for a dhcp server solution and I want to be able to adjust the list of interfaces through the stork management software, or perhaps have the list generated.  The use case I would imagine is something like this: kea is installed on a server, but it is not known at the time of configuration what all interfaces are installed, and or what IP’s will be assigned to those interfaces yet. Now the server is installed, and I am managing the server’s configuration through the stork interface ( which uses the kea control api) and then I look at the available interfaces with their IPs, and select which ones I want kea to use. Additionally, perhaps later a new interface is installed or an ip is changed, and one of the interfaces in that interfaces list needs to be added or updated.
>  Currently, it requires me to go to that server and manually modify the kea-dhcp configuration file’s list of available interfaces, then assign some of those interfaces to pools/subnets. I would think it would be a good feature to have to be able to manage this through an api interface or through the kea-ctrl-agent ( and then open it up to be configured for stork to manage).  Does this make sense as a feature to have? I would think it would go in either kea-ctrl-agent or stork-agent.
>  Thanks, Zachary Noble
>  -- 
> kea-dev mailing list
> kea-dev at lists.isc.org
> https://lists.isc.org/mailman/listinfo/kea-dev




More information about the kea-dev mailing list