Kea won't start due to duplicate reservations

[packman2008]

I've had a couple of problems where I've made a typo whilst enterering a reservation in Kea and have created two reservations with the same IP address. The web GUI allows duplicate IPs without any warning but when you next apply/restart the Kea server it fails due to the duplicate addresses, e.g.

<131>1 2024-02-08T11:02:45+00:00 OPNsense.xxxx.com kea-dhcp4 34887 - [meta sequenceId="7"] ERROR [kea-dhcp4.dhcp4.0x8325d8000] DHCP4_CONFIG_LOAD_FAIL configuration error using file: /usr/local/etc/kea/kea-dhcp4.conf, reason: failed to add new host using the HW address 'xx:3a:xx:67:a2:xx and DUID '(null)' to the IPv4 subnet id '1' for the address 10.0.1.64: There's already a reservation for this address

[Ramalama]

Kea is the last crap, like stork, stork is even worse. (Stork is the useless dhcp gui for kea, where you cant even see leases)

Whatever isc is doing, is just money oriented now, the good old days of isc-dhcp are gone.
I would recommend you to stick with the old isc-dhcp.

In short, Kea is not stable and a half working solution.
You cannot do with Kea duplicate ip reservations. But thats a very minor issue if you ask me.

Much worse, is that Kea Raw socket is broken, cause it cannot destinquish from which network the IP address comes from, that means that you cannot use Kea if you have multiple vlans/multiple subnets, unless you have an udp-relay/ip helper/dhcp relay

The UDP-Socket on other hand, is broken either, cause it cannot listen for broadcast dhcp requests.

Thats all a no issue with the old isc-dhcp server, so stick with it as long as possible. At this time, kea has no benefits, not even performance benefits.

Cheers