Elektrine lite

← Feed

@laird@hachyderm.io

2026-07-24 03:12 UTC

In any case, my general opinion of Kea from when I first set it up 3 or 4 years ago hasn't really changed at all. It's massively overengineered for what I need, but *still* isn't actually able to do what I want it to do without jumping through major hoops. Fortunately, most of the hoops that I had to jump through at the time have stayed jumped-through. Other than the static lease issue and the "oops, transient database issue so turning off DHCP" issue I can mostly just ignore it all. I define DHCP pools and static leases in Netbox, and then periodically extract those and write them into a git repo, which gets synced onto my DHCP servers. In theory, this means that if anything breaks it'll just stop updating and it's relatively easy to fix. In practice, it means that I can set up new static reservations by just reserving the IP address for it in Netbox (which is where I manage IPs anyway) and adding a MAC address to the IP via a custom field. Every IPv4 address that has a MAC listed gets added to Kea automatically within a few minutes. This is pretty much the absolute least amount of work needed to accomplish the goal. I just need to paste the MAC into the IP reservation.

Replies (1)

  • @paul_ipv6@infosec.exchange 2026-07-24 03:28

    @laird@hachyderm.io one problem is that the folks that pay ISC for support for DHCP have some of the most insanely complex overly tweaked networks with every knob ever invented twirled and now considered essential. we're talking 10k lines of dhcpd.conf or more to convert to kea. so, the folks paying for kea have the most complicated use cases as essentially table stakes. no one does an open source "this just works for small (sub-10k lease) sites with minimal tweaking". add in that the rabid religious wars between the SLAAC vs DHCPv6 delayed and complicated DHCPv6 for years (f**k you person at google responsible for this). you still can't do any form of address control or auditing with SLAAC, so most enterprise winds up running both. what we really need is a DHCP Lite RFC and a small clean reference implementation but i don't see that happening any time soon.

    Open ##4052950