[Kea-users] How to get kea to reassign same IP after an explicit release (client reboot) if it has not been reused

[Nathan Neulinger]

Scenario:

     Lightly used subnet, reasonably sized pool of addresses, served with an HA pair of Kea v2.2
     Client issues a RELEASE as part of reboot process
     Testing with v4 only at the moment


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.

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.


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?


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.


Reservations are not what I'm looking for, we already have those, this is specifically in regards to 'purely dynamic 
pool' handling.

-- Nathan

------------------------------------------------------------
Nathan Neulingernneul at neulinger.org
Neulinger Consulting                   (573) 612-1412
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20221007/30d54031/attachment.htm>