Re: [SOLVED] Can I run dnsmasq as boot server in my environment

[deloptes <deloptes@gmail.com>]

> 
> 
> The trick was to add following line to the dhcpd.conf
> 
>    option vendor-encapsulated-options
>
6:1:3:a:4:0:50:58:45:9:14:0:0:11:52:61:73:70:62:65:72:72:79:20:50:69:20:42:6f:6f:74:ff;
> 
> This could be added to a class, but I have only one rpi4, so added
> directly to the client config.
> 
> The other trick is to set root-path to the tftp boot directory.
> 
> If there is more curiosity what happens on the network, use this
> 
>         tcpdump -Xvv  udp port 67 or port 68 or port 69
> 
> Amazing!
> 
> I would like to know what vendor-encapsulated-options is. The end of it
> translates to Raspberry Pi Boot\0. But the first part ... ???
> In anycase it does the magic

It is probably not clear what I meant with the message.

It is not necessary to use dnsmasq. Just the proper configuration in
isc-dhcp-server. If the vendor encapsulated option is missing, the boot
process do not continue. When the configuration option is present the boot
sequence continues.

root-path must point to the boot directory, so that Rpi can find the boot
files.

regards