<div dir="auto"><div>Thank you Darren. The link you provided describes the problem I am facing very well. Maybe KEA could construct its own UUID based on a defined set of attributes configurable by the customer/user/KEA-Admin and that is used instead.</div><div dir="auto">Anyway, let's see. I basically decided to use different client names/prefixes in the client name to differentiate between v4 and v6 for now. Looking forward to more flexibility regarding hostname settings in KEA with DDNS tuning once I can upgrade to 2.7.7 since this hook has been put into the Open Source category. Thank you for that :)</div><div dir="auto">Regarding lease testing: I shall reduce the lease time then.</div><div dir="auto"><br></div><div dir="auto">Best,</div><div dir="auto">C.</div><div dir="auto"><br><div class="gmail_quote gmail_quote_container" dir="auto"><div dir="ltr" class="gmail_attr">On Mon, 5 May 2025, 00:00 , <<a href="mailto:kea-users-request@lists.isc.org">kea-users-request@lists.isc.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send Kea-users mailing list submissions to<br>
<a href="mailto:kea-users@lists.isc.org" target="_blank" rel="noreferrer">kea-users@lists.isc.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://lists.isc.org/mailman/listinfo/kea-users" rel="noreferrer noreferrer" target="_blank">https://lists.isc.org/mailman/listinfo/kea-users</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:kea-users-request@lists.isc.org" target="_blank" rel="noreferrer">kea-users-request@lists.isc.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:kea-users-owner@lists.isc.org" target="_blank" rel="noreferrer">kea-users-owner@lists.isc.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Kea-users digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Kea-users Digest, Vol 130, Issue 47 (Darren Ankney)<br>
2. Re: Kea-DHCP upgrade 2.4 to 2.6 issues (Darren Ankney)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Sun, 4 May 2025 05:44:32 -0400<br>
From: Darren Ankney <<a href="mailto:darren.ankney@gmail.com" target="_blank" rel="noreferrer">darren.ankney@gmail.com</a>><br>
To: "Kea user's list" <<a href="mailto:kea-users@lists.isc.org" target="_blank" rel="noreferrer">kea-users@lists.isc.org</a>><br>
Subject: Re: [Kea-users] Kea-users Digest, Vol 130, Issue 47<br>
Message-ID:<br>
<<a href="mailto:CAKabWHhU2jAAeugm_NYP6ELSn74Gum585R4mrTTVZ37de%2BoX0A@mail.gmail.com" target="_blank" rel="noreferrer">CAKabWHhU2jAAeugm_NYP6ELSn74Gum585R4mrTTVZ37de+oX0A@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="UTF-8"<br>
<br>
Hi,<br>
<br>
On Tue, Apr 29, 2025 at 3:24?AM Christoph Markert <<a href="mailto:maggiv8@gmail.com" target="_blank" rel="noreferrer">maggiv8@gmail.com</a>> wrote:<br>
><br>
> Hi Darren,<br>
><br>
> thank you for your swift response.<br>
> Here is an update after further investigation:<br>
> A) My reverse zone file for IPv6 had an issue in BIND - it wasn't defined correctly (there was an issue when I typed in the reverse address). I corrected that. I tested it with only requesting a v6 address and consequently the zone files have been updating correctly in BIND.<br>
> B) My DHCP client (in this test case a Windows 11 machine) sends different DHCIDs for v4 and v6 - this seems to be Windows 11 default based on my research. However, according to RFC4701 and RFC4361 the DHCIDs used in v4 and v6 DHCP requests (to KEA) need to<br>
> be identical so that KEA-DDNS can perform a match between the requests. See also '<a href="https://lists.isc.org/pipermail/kea-users/2023-June/004068.html" rel="noreferrer noreferrer" target="_blank">https://lists.isc.org/pipermail/kea-users/2023-June/004068.html</a>'. You can see an excerpt from my DDNS log at the end of my response. In there you can see the DHCIDs are different for v4 and v6 incl. the corresponding error messages (see RCODE '8', which apparently indicates this issue - based on my current understanding).<br>
<br>
Most likely, Kea is creating your DHCID records (unless your clients<br>
are updating DNS directly). See here:<br>
<a href="https://kea.readthedocs.io/en/kea-2.6.2/arm/ddns.html#conflict-resolution" rel="noreferrer noreferrer" target="_blank">https://kea.readthedocs.io/en/kea-2.6.2/arm/ddns.html#conflict-resolution</a><br>
<br>
><br>
> Question 1: since it is very difficult to control each client how they create their DHCID for v4 and v6, is there any setting in KEA (or BIND) to make a matching work between v4 and v6 even though the DHCID may be different. I played around with match-client-ID in KEA v4, but currently I am unsure whether this solves this issue.<br>
<br>
For dual stack environments, see here:<br>
<a href="https://kea.readthedocs.io/en/kea-2.6.2/arm/ddns.html#dual-stack-environments" rel="noreferrer noreferrer" target="_blank">https://kea.readthedocs.io/en/kea-2.6.2/arm/ddns.html#dual-stack-environments</a><br>
but realistically, about all you could try would be to disable<br>
conflict resolution with DHCID records unless you have clients that do<br>
support RFC 4361<br>
<br>
This recent Gitlab issue from another user describes the problem I<br>
think you are encountering:<br>
<a href="https://gitlab.isc.org/isc-projects/kea/-/issues/3780" rel="noreferrer noreferrer" target="_blank">https://gitlab.isc.org/isc-projects/kea/-/issues/3780</a><br>
<br>
> Question 2 - for proper testing: to fully remove a v4 or v6 lease from KEA, is it sufficient to just delete it from the csv-files or is there anything else to do as it seems I get strange behaviours when just removing a lease from the csv-file(s) (since there are 2 files for v4 and 2 files for v6)? How can I flush all or specific v4 / v6 leases properly? I do have a combination of dynamic IP pools and reserved/static IPs in my KEA v4/v6 configuration.<br>
<br>
If you simply delete the lease file, then you'll have orphaned DNS<br>
records hanging around. For testing, I recommend a short lease<br>
(perhaps 5 minutes) so that you can just wait for the lease to expire<br>
and things to happen naturally.<br>
<br>
Thank you,<br>
Darren Ankney<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Sun, 4 May 2025 06:05:01 -0400<br>
From: Darren Ankney <<a href="mailto:darren.ankney@gmail.com" target="_blank" rel="noreferrer">darren.ankney@gmail.com</a>><br>
To: "Kea user's list" <<a href="mailto:kea-users@lists.isc.org" target="_blank" rel="noreferrer">kea-users@lists.isc.org</a>><br>
Subject: Re: [Kea-users] Kea-DHCP upgrade 2.4 to 2.6 issues<br>
Message-ID:<br>
<<a href="mailto:CAKabWHgUrw9OtEQK21SNtAdgdMZ6kad-fCivrqjre9zG_BAVRA@mail.gmail.com" target="_blank" rel="noreferrer">CAKabWHgUrw9OtEQK21SNtAdgdMZ6kad-fCivrqjre9zG_BAVRA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="UTF-8"<br>
<br>
On Fri, May 2, 2025 at 5:30?PM Scott Rakow <<a href="mailto:srsqrd@gmail.com" target="_blank" rel="noreferrer">srsqrd@gmail.com</a>> wrote:<br>
><br>
> Andrei,<br>
> Thanks for the answer. You were correct. I thought I grabbed the el9 files, but they were the el8.<br>
><br>
> I am now getting an error that the CmdHttpListner is not starting because multithreading is disabled. In searching I can not find any reference in the ISC documentation about the cmdhttplistener or how to configure it.<br>
<br>
This likely refers to the HTTP Listener in the HA hook? In 2.6.2,<br>
multithreading should be default on (see here:<br>
<a href="https://kea.readthedocs.io/en/kea-2.6.2/arm/dhcp4-srv.html#multi-threading-settings" rel="noreferrer noreferrer" target="_blank">https://kea.readthedocs.io/en/kea-2.6.2/arm/dhcp4-srv.html#multi-threading-settings</a>)<br>
and the HA Hook should default to multi-threading with dedicated<br>
listener (see here:<br>
<a href="https://kea.readthedocs.io/en/kea-2.6.2/arm/hooks.html#multi-threaded-configuration-ha-mt" rel="noreferrer noreferrer" target="_blank">https://kea.readthedocs.io/en/kea-2.6.2/arm/hooks.html#multi-threaded-configuration-ha-mt</a>).<br>
Perhaps you have disabled multi-threading in your configuration? In<br>
the past (I think earlier than 2.4 though), all of this was default<br>
disabled.<br>
<br>
><br>
> A Google search did come up with this snippet:<br>
><br>
> {<br>
> "dhcp4": {<br>
> "cmdhttplistner": {<br>
> "enabled": true,<br>
> "listen-interface": "eth0",<br>
> "listen-port": 8080,<br>
> "listen-address": "0.0.0.0",<br>
> "auth-key": "your_auth_key"<br>
> }<br>
> }<br>
> }<br>
><br>
> But I can't find any other reference to it.<br>
<br>
This is likely an AI hallucination.<br>
<br>
><br>
> Is there a way to make sure that multithreading is enabled?<br>
><br>
<br>
See above.<br>
<br>
> I see that the kea-ctrl-agent will be merged with the kea-dhcpx service sometime after 2.6. Will all the current curl commands be available once that is in place? The list of commands that I saw left out the ha-maintenance-cancel and start commands.<br>
<br>
You will be able to setup remote API listening directly in the various<br>
daemons in 2.7+ The separate daemon is removed, but the functionality<br>
survives. You are encouraged to setup a test machine of some sort and<br>
start experimenting with the latest 2.7 dev branch. 3.0 will be a big<br>
change, and it is never too early to start testing :)<br>
<br>
<br>
Thank you,<br>
Darren Ankney<br>
<br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
<br>
ISC funds the development of this software with paid support subscriptions. Contact us at <a href="https://www.isc.org/contact/" rel="noreferrer noreferrer" target="_blank">https://www.isc.org/contact/</a> for more information.<br>
<br>
Kea-users mailing list<br>
<a href="mailto:Kea-users@lists.isc.org" target="_blank" rel="noreferrer">Kea-users@lists.isc.org</a><br>
<a href="https://lists.isc.org/mailman/listinfo/kea-users" rel="noreferrer noreferrer" target="_blank">https://lists.isc.org/mailman/listinfo/kea-users</a><br>
<br>
<br>
------------------------------<br>
<br>
End of Kea-users Digest, Vol 131, Issue 5<br>
*****************************************<br>
</blockquote></div></div></div>