[Kea-users] Possible bug with Kea DHCP Server?

[Stephen Dennis (Gmail)]

Hi,

After a client received a lease, the client was rebooting.
It tried to ask for the same IP (Windows machine), but Kea refused with
this error, despite the fact that Kea has a reservation for that client's
MAC:
"2023-09-10 22:38:00.308 WARN
 [kea-dhcp4.alloc-engine/2752.140528795599552]
ALLOC_ENGINE_V4_DISCOVER_ADDRESS_CONFLICT [hwtype=1 xx:xx:xx:xx:xx:xx],
cid=[01:xx:xx:xx:xx:xx:xx], tid=0xb4da0bab: conflicting reservation for
address 192.168.1.11 with existing lease Address:       192.168.1.11"

1. Why would Kea not just answer the client with the same IP already
assigned to that client?
2. Is there no mechanism in place to deal with the case where a client
reboots and has to resend a DHCPREQUEST during an existing lease for that
client?

This, to me, looks like a bug.

Thanks,
Chib

Disclaimer:
If you are not the intended recipient of this message
 (a) you MUST NOT copy, forward, print, save, disclose or otherwise
distribute, make use of or rely upon any of the message content,
 (b) you MUST delete it immediately and notify the Sender of the delivery
error.
The Sender CANNOT guarantee that
 (a) this message has not been corrupted or altered during transmission,
 (b) this message has not been fraudulently produced by an untrusted third
party.
The contents of this message is PRIVATE and
 (a) it MAY NOT necessarily express the views held by the Sender,
 (b) it MAY contain information that is proprietary or confidential to the
Sender,
 (c) SHALL NOT bind the Sender to any contract or order unless explicitly
allowed by prior written agreement or by applicable law.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20230911/18118c27/attachment.htm>