<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Scenario:</p>
<p> Lightly used subnet, reasonably sized pool of addresses,
served with an HA pair of Kea v2.2 <br>
Client issues a RELEASE as part of reboot process<br>
Testing with v4 only at the moment<br>
</p>
<br>
<p>The client appears get a new IP from the pool every time it
reboots. It does this even when no other leases have been granted
to or even requested by other devices in the mean time.<br>
</p>
<p>While this is certainly "valid" behavior - a client can't
_expect_ to get the same IP, especially if network is busy/small
pool/etc. -- it's not particularly user friendly. It's also not at
all what users are used to on a network that was previously using
an ISC DHCPd pair. <br>
</p>
<p><br>
</p>
<p>Is there any way to get Kea to hand out the same IP for a
recently known client identifier if it has not already been given
to another client? i.e. prioritize assignment of LRU priority on
addresses in the pool unless it was the last client to be given a
particular lease?<br>
</p>
<p><br>
</p>
<p>Ideal would be if the above could be time limited. Something like
a "hold time" on a release - where it stays 'assigned but
claimable if necessary' to a given client for some defined number
of minutes after it is released.<br>
</p>
<p><br>
</p>
<p>Reservations are not what I'm looking for, we already have those,
this is specifically in regards to 'purely dynamic pool' handling.
<br>
</p>
<pre class="moz-signature" cols="120">-- Nathan
------------------------------------------------------------
Nathan Neulinger <a class="moz-txt-link-abbreviated" href="mailto:nneul@neulinger.org">nneul@neulinger.org</a>
Neulinger Consulting (573) 612-1412</pre>
</body>
</html>