On Thu, Jan 22, 2026 at 10:37 AM Darren Ankney <[email protected]> wrote:
> This is difficult to answer without the configurations for Kea and the
> Debian interface configuration (/etc/network/interfaces) as well as
> the Kea logs (or even better, a pcap file showing the client/server
> dhcp packets obtained with: `tcpdump -i <interface> -w <pcapfile.pcap>
> port 67` while the client is obtaining two addresses).
Hi Darren,
I may look into a pcap in the future. For now I've worked around it by using:
"match-client-id": false
for the subnet and adding
"client-class": "UNKNOWN"
to the pool.
This way I don't have to rely on the client to 'fix' the issue.
When moving to using systemd-networkd the /etc/network/interfaces is
no longer used - it gets renamed or deleted.
The file in question then is /etc/systemd/network/interface.network
and it is pretty straightforward:
===========================
[Match]
Name=eno1
[Network]
DHCP=ipv4
===========================
Adding a new section:
===========================
[DHCPv4]
ClientIdentifier=mac
===========================
is how I fixed in the client. But with the changes in Kea I no longer
need the client side fix.
Thank you,
Chris
--
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.
[email protected]
