[PATCH] udhcpd: Per-client boot_file

[David Laight]

From: busybox <busybox-bounces at busybox.net> On Behalf Of Michael Tokarev
> Sent: 25 June 2023 06:58
> 
> 25.06.2023 02:23, Adam Goldman wrote:
> > This patch adds the ability to specify a different boot_file for each
> > client. This is useful if clients have different CPU architectures or if
> > some clients are legacy BIOS and some are EFI.
> >
> > It adds a config file option of the form
> > "for xx:xx:xx:xx:xx:xx boot_file foo" which sets the boot_file to "foo"
> > for the client with the MAC address xx:xx:xx:xx:xx:xx. If no such line
> > exists, the global boot_file will be used. The syntax of the option is
> > intended so that in the future, per-client options other than boot_file
> > could be added.
> 
> I don't think this scales. Instead of per-client, it needs to be per
> group of clients based on some criteria (such as CPU architecture).
> See for example how dnsmasq does this (and maybe it is better suited
> for your usage).

Isn't there are historic precedence for this to do with booting
diskless clients (eg NetBSD) where there are also options for
supplying different first and second level 'boot' files.

A separate (but maybe interesting) case it to use different
address pools for different MAC OUI.
In particular this would allow the crappy Cisco phones that
never renew addresses be given addresses in a different
range from everything else.
(Although since 'dayjob' insist on using the M$ DNS server
we just have to live with the fact that it is completely
broken.)

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)