Re: ISC's EoL dhcp suite, including dhcpd

[David Brownlee <abs%netbsd.org@localhost>]

On Fri, 27 Jun 2025 at 07:11, Martin Husemann <martin%duskware.de@localhost> wrote:
>
> On Thu, Jun 26, 2025 at 04:40:09PM -0500, David Young wrote:
> > On Tue, Feb 04, 2025 at 10:57:29PM +0000, Taylor R Campbell wrote:
> > > A DHCP _server_ (or relay) isn't necessary for the kind of system
> > > integration that justifies the maintenance burden of having it in the
> > > base system -- unlike say, a DHCP _client_, which is needed to get
> > > connected to the network and download packages in the first place.
> >
> > Would this change leave NetBSD without a cross-buildable DHCP server?
> >
> > Back when I built routers with NetBSD, it was beautiful how I could
> > cross-build a system image that had a DHCP client and server in it with
> > just one build.sh invocation.  To this day embedded systems do not
> > ordinarily have an "on-line" installation and fetching packages is not
> > part of the flow, so I don't see that as a fallback.
> >
> > Back then, pkgsrc was not cross-buildable.  Maybe it is, now?
>
> I tried to move to something similar simple as the in-tree ISC dhpcd
> by looking at the pkgsrc options for DHCP servers, but besides the
> new ISC variant (which loooked quite huge and a lot more complicated)
> I found nothing that just did a DHCP server and has better support state
> than ISC dhcpd.
>
> I don't need a web frontend and central management for all of my DHCP
> servers. And I don't want a combined DNS/DHCP solution, my DNS setup
> is quite complex and just works, I'd prefer to not touch it.
>
> Maybe I overlooked something.

I've found dnsmasq quite good as a DHCP+DNS server. Setting port=0 in
the config disables all DNS functions, which covers "DHCP only" needs
:)

David