Show Posts
1
24.1 Legacy Series / Re: Kea won't start due to duplicate reservations
« on: March 01, 2024, 11:36:47 pm »
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
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