Just wait for the #2548 resolution (not long: it is in the current
milestone and someone works on it so very likely in the next
development release at the end of the month) which should update
the code to expire released leases instead of to remove them: if you
enable lease affinity (on by default)
Thanks. This is all I've been able to find as well Seems like such a hack - and not something that would work on any
high traffic subnet unless the lease times were quite short to begin with.
Just seems like this should be a simple boolean flag "record any released lease as expired" to get i
On 08/10/2022 04:41, Nathan Neulinger wrote:
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
Have you tried telling the client not to rele
Hi Nathan,
I experienced the same strange behaviour. For me, the only solution
was to prohibit "release" packets at all. In database I inserted:
table: dhcp4_client_class
{"id":"3","name":"DROP","test":"pkt4.msgtype==7","next_server":null,"server_hostname":null,"boot_file_name":null,"only_if_requ
