> On Jul 25, 2018, at 1:35 PM, Simon Kelley wrote:
>
> I think is you specify dhcp boot and dhcp-bo-override and dhcp-option
> fro 66 and 67 then the data will always be sent in the bootp fields, and
> will be sent as options if requested. Experiment needed to be sure.
>
>
> Like a lot of DHCP
On 25/07/18 19:03, Shankar Unni wrote:
> Thanks, Simon!
>
> I did discover this and figured out that we can specify it as —dhcp-boot=…
> and —dhcp-no-override. But then these options will ALWAYS only be sent as
> bootp fields, right?
>
> Will there be an issue the other way, then? (I.e. som
Thanks, Simon!
I did discover this and figured out that we can specify it as —dhcp-boot=… and
—dhcp-no-override. But then these options will ALWAYS only be sent as bootp
fields, right?
Will there be an issue the other way, then? (I.e. some client that sends in
options 66/67 in parameter requ
This dnsmasq configuration is relevant:
--dhcp-no-override
(IPv4 only) Disable re-use of the DHCP servername and filename
fields as extra option space. If it can, dnsmasq moves the boot
server and filename information (from --dhcp-boot) out of their
dedicated fields
