<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
Thanks, Darren.</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
Your response is really helpful!</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
Too bad Kea doesn't have an option to tell it not to record the lease for reserved hosts. That would be ideal. </div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
The clients are RHEL8 using NetworkManager, and there's no simple way to release a DHCP lease from that at this point in time.</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
I'll look into the API option - it sounds like that is the solution. </div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
Jason.</div>
<div id="Signature"></div>
<div id="appendonsend"></div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<br>
</div>
<hr style="display: inline-block; width: 98%;">
<div dir="ltr" id="divRplyFwdMsg"><span style="font-family: Calibri, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);"><b>From:</b> Kea-users <kea-users-bounces@lists.isc.org> on behalf of Darren Ankney <darren.ankney@gmail.com><br>
<b>Sent:</b> Thursday, March 7, 2024 5:45 AM<br>
<b>To:</b> Kea user's list <kea-users@lists.isc.org><br>
<b>Subject:</b> Re: [Kea-users] dhcp lease question</span>
<div> </div>
</div>
<div><span style="font-size: 11pt;">Hi Jason,<br>
<br>
This has come up before. The short answer is that ISC DHCP did not<br>
record a lease for addresses reserved with "fixed-address". Kea does<br>
record a lease, and so won't allow assignment to a new client until<br>
the lease is expired. You could send a release from the old computer<br>
before shutting it down, that should end the lease and make available<br>
to the new. You could also use the "lease4-del" API command<br>
(<a href="https://kea.readthedocs.io/en/kea-2.4.1/arm/hooks.html#the-lease4-del-lease6-del-commands" id="OWA8ac2404d-73a6-8956-6709-b334f48a43e5" class="OWAAutoLink" data-auth="NotApplicable" data-loopstyle="linkonly">https://kea.readthedocs.io/en/kea-2.4.1/arm/hooks.html#the-lease4-del-lease6-del-commands</a>)<br>
to remove the lease which would also make it available to the new<br>
client.<br>
<br>
Thank you,<br>
Darren Ankney<br>
<br>
On Wed, Mar 6, 2024 at 5:44 PM Jason Keltz <jas@yorku.ca> wrote:<br>
><br>
> Hi.<br>
><br>
> I have one question with respect to leases with Kea.<br>
><br>
> On a subnet, I have assigned a static IP address for each ethernet address. It works great. Recently, we started replacing the computers in one of our labs. The new computers will be replacing existing computers, so they will take on the same names.
Before we install a new machine, we turn off the old machine, reconfigure the ether address for the host in kea, and have kea re-read it's config file.<br>
><br>
> When the new system comes up, Kea doesn't want to give it the ether address that is reserved for it because it sees a conflict. Of course the IP is already issued to the old computer (that is now off).<br>
><br>
> Is there an option to tell Kea to be "less particular" about leases for reservations? That is, if the config file says that ether address X gets IP address Y, then ether address X is always going to get IP address Y whether the lease database says that
it's in use or not. Obviously we aren't going to have the old and new computer up at the same time.<br>
><br>
> Is this possible?<br>
><br>
> We did these kind of upgrades all the time with ISC DHCPd, and this was never an issue, so hopefully it's just an option that I'm missing.<br>
><br>
> Jason.<br>
><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/" id="OWA24c7b04e-3bdc-8020-6fde-0e2b763b617b" class="OWAAutoLink" data-auth="NotApplicable" data-loopstyle="linkonly">
https://www.isc.org/contact/</a> for more information.<br>
><br>
> To unsubscribe visit <a href="https://lists.isc.org/mailman/listinfo/kea-users" id="OWAf2ae0808-e764-d90c-acb4-5254c5e53b1d" class="OWAAutoLink" data-auth="NotApplicable" data-loopstyle="linkonly">
https://lists.isc.org/mailman/listinfo/kea-users</a>.<br>
><br>
> Kea-users mailing list<br>
> Kea-users@lists.isc.org<br>
> <a href="https://lists.isc.org/mailman/listinfo/kea-users" id="OWA4af5ae45-5366-e76a-e340-3d01a7107cb9" class="OWAAutoLink" data-auth="NotApplicable" data-loopstyle="linkonly">
https://lists.isc.org/mailman/listinfo/kea-users</a><br>
--<br>
ISC funds the development of this software with paid support subscriptions. Contact us at
<a href="https://www.isc.org/contact/" id="OWA20e8387f-80a8-c3fa-d5b2-8516d306edcc" class="OWAAutoLink" data-auth="NotApplicable" data-loopstyle="linkonly">
https://www.isc.org/contact/</a> for more information.<br>
<br>
To unsubscribe visit <a href="https://lists.isc.org/mailman/listinfo/kea-users" id="OWA2b1e74ba-eec0-22ad-a7a8-0a3a62060246" class="OWAAutoLink" data-auth="NotApplicable" data-loopstyle="linkonly">
https://lists.isc.org/mailman/listinfo/kea-users</a>.<br>
<br>
Kea-users mailing list<br>
Kea-users@lists.isc.org<br>
<a href="https://lists.isc.org/mailman/listinfo/kea-users" id="OWA5e39d9f2-a94d-e6dd-eca4-0981755d01d7" class="OWAAutoLink" data-auth="NotApplicable" data-loopstyle="linkonly">https://lists.isc.org/mailman/listinfo/kea-users</a></span></div>
</body>
</html>