Hi Ronald, Have a look at the flex_id hook (https://kea.readthedocs.io/en/kea-3.0.1/arm/hooks.html#libdhcp-flex-id-so-flexible-identifier-for-host-reservations). You can combine this with the replace-client-id flag (https://kea.readthedocs.io/en/kea-3.0.1/arm/hooks.html#the-replace-client-id-flag) so that the lease is recorded by option 82 as well (i.e., the client-id in the lease is replaced with the option82 hex). In this way, Kea will effectively be unaware that the client has changed.
Thank you, Darren Ankney On Wed, Sep 3, 2025 at 9:16 AM DDFR | Ronald Blaas <ronald.bl...@ddfr.nl> wrote: > > Hi all > > I was wondering if we could expire a single ip address after 1 hour (or maybe > less) > > > The reason for this is we have a port on which we connect different devices > but the same IP address (is assigned via Option82) > > With the IP address in the database it is locked so the second device gets an > IP from the pool. > > > Ofcourse we can release the IP but I was wondering if this can be automated > so the the IP is Expired sooner > > > Kind regard, > > > Ronald > > > -- > 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@lists.isc.org -- 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@lists.isc.org
