[Kea-users] Kea 2.6.1 started issuing duplicate IPs after restart
Don Lawrence
dlawrence at lrecok.coop
Tue May 20 12:50:14 UTC 2025
Darren,
Thank you for the response. We have been going over the logs and the configuration files. In this one case, I did not set the configuration change management before making the change since I was removing subnet options that are set globally.
We are moving to a set of new servers running on a non-EOL OS. We will install and use the latest versions and prepare the migration.
I appreciate the help and suggestions. I do not have the files to be able to share otherwise I would. It is definitely a fluke and we are going to upgrade to see if that helps
Don Lawrence
________________________________
From: Kea-users <kea-users-bounces at lists.isc.org> on behalf of Darren Ankney <darren.ankney at gmail.com>
Sent: Friday, May 16, 2025 5:53 PM
To: Kea user's list <kea-users at lists.isc.org>
Subject: Re: [Kea-users] Kea 2.6.1 started issuing duplicate IPs after restart
Caution: [EXTERNAL EMAIL] DO NOT CLICK links, attachments or reply unless you recognize the sender and know the content is safe. When in doubt, contact your IT Department
Hi Don,
My first thought is that something accidentally changed with the lease
storage resulting in Kea having no access to the previously leased
address records when it was restarted. That is just speculation,
however. If you can provide the configuration before and after the
change, and some logs surrounding this time period, something might be
revealed. Please be sure and redact any sensitive information. Also,
the latest stable Stork is 2.0.1 and the latest stable Kea is 2.6.2.
You may want to make plans to upgrade.
Thank you,
Darren Ankney
On Fri, May 16, 2025 at 3:59 PM Don Lawrence <dlawrence at lrecok.coop> wrote:
>
> Hello all,
>
> We are looking to get budget approval for support and sales suggested posting to the user group while we wait.
>
> We are running Kea 2.6.1 running memfile and Stork 1.19.0.
>
> There was a config change on the renew-timer for a subnet to increase the time. The server was restarted with "systemctl restart kea-dhcp4".
>
> Sometime after the restart, Kea started issuing DHCP addresses that were already taken and in the lease file. When looking at the subnet on Stork, the utilization data showed low or 0% utilization on a set of individual subnets under a specific shared network. We noticed it because the client asking for the IP had no connectivity and we could see two entries in the ARP table with different MAC addresses but the same IP.
>
> I know the technical info is light on details. I am asking the group for any tips on troubleshooting or why the server would expire the whole subnet after a restart and start issuing duplicate IPs. I'm thinking a configuration problem but I'm not sure.
>
> Thank you in advance.
> Don
> --
> 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
> Kea-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/kea-users
--
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
Kea-users at lists.isc.org
https://lists.isc.org/mailman/listinfo/kea-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20250520/7933df5a/attachment.htm>
More information about the Kea-users
mailing list