> > Are we guaranteed that --dhcp-no-override is supported as far back as
> > the earliest version of dnsmasq that we claim to run with, or do we need
> > to add some --help parsing?
>
> Hmm, good point. The option was added into dnsmasq-2.41 released on
> 12-Feb-2008. I'm not sure what version we
> > It seems some virtual network card ROMs are this old/buggy so let's add
> > --dhcp-no-override as a workaround for them. We don't use extra DHCP
> > options so this should be safe.
>
> Are we guaranteed that --dhcp-no-override is supported as far back as
> the earliest version of dnsmasq that
On 08/11/2010 12:41 PM, Jiri Denemark wrote:
> --dhcp-no-override description from dnsmasq man page:
>
> 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)
--dhcp-no-override description from dnsmasq man page:
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 into DHCP options.
