Re: MVP for a DHCP server (was Re: ISC's EoL dhcp suite, including dhcpd)

Roy Marples wrote:

>  ---- On Mon, 14 Jul 2025 19:02:13 +0100  Martin Husemann <[email protected]> wrote --- 
>  > On Mon, Jul 14, 2025 at 05:45:10PM +0100, Roy Marples wrote:
>  > > Would you consider an option to use ethers(5) for this instead?
>  > > This would allow IPv4 mapping, but not IPv6.
>  > 
>  > That is another indirection and quite inconvenient in the diskless
>  > client case. I want the information as close to the root path/next
>  > server option configuration as possible.
>
> Right, but I'm trying to avoid any kind of per host configuration right now.
> If we can achieve static DHCPv4 assignmen via ethers then I think that's MVP for now.

I'm in a similar situation to Martin.  I have a bunch of diskless
clients that boot with dhcp to get their root filesystem location.

For a DHCP server running on NetBSD to support other NetBSD diskless
clients, I think this is the minimal functionality I'd need (from my
existing ISC dhcpd config):

	option  domain-name             "thistledown.com.au";
	option  subnet-mask             255.255.255.0;

	subnet  192.168.0.0 netmask 255.255.255.0 {
		option  routers                 192.168.0.1;
		option  domain-name-servers     192.168.0.42, 192.168.0.1;
		option  ntp-servers             192.168.0.1, 192.168.0.42;
		range                           192.168.0.210 192.168.0.249;
	}

	group {
		host mona {
			hardware ethernet       08:00:2b:2f:d5:58;
			fixed-address           mona;
			server-name             "thoreau";
			filename                "mona.root/netboot";
			option  root-path       "/tftpboot/mona.root";
		}
	}

All my diskless clients have static IP addresses.

Cheers,
Simon.