2026-07-24 03:53 UTC
@paul_ipv6@infosec.exchange yeah, that's kind of what it all feels like. I really just want *some* way to have a relatively simple network with redundant DHCPv4 servers. This is all using RFC 1918 space, and I'm in *absolutely* no danger of running out of it. I can grow networks enough to let me have multiple, redundant DHCP pools per network. Except if I actually run 2 independent servers with their own pools then individual systems end up bouncing back and forth between blocks every time they reboot, and that ends up making debugging suck.
Turning on Kea's 2-way replicated DHCP seems to be the *easiest* solution to this, and it was a pain to get right. Honestly, I'd be perfectly fine with running one of them with a "wait 500ms before responding" config or even a "don't respond unless your healthcheck of the master DHCP server fails" setting.
Unfortunately, I've never seen a single DHCP server with either option. Not that either would be *that* hard to throw together, but it's harder than living with Kea, now that it's working.
Fundamentally, there doesn't seem to be much between Kea (very heavy-weight) and things like dnsmasq (mostly aimed at cheap consumer routers and so forth). It's kind of odd that there are a ton of perfectly viable BIND alternatives but no alternatives for ISC's DHCP code.
Replies (1)
-
@paul_ipv6@infosec.exchange 2026-07-24 15:05
@laird@hachyderm.io DHCP does seem to be treated like "i just want ipv4 addr/subnet, def gw, and DNS" or ungodly complicated, as if there's nothing in between. dnsmasq has been a source of broken-ness and evil for years due to neglect and every low end router vendor using way antique versions. i've been involved with DHCP and DHCP RFCs for years and i can't recall anything other than dnsmasq or ISC DHCP for open source implementations in all that time.