[Dnsmasq-discuss] Boot file name not given (DHCP Option: 67 Bootfile name - is set but not used in PXE clients)

Hi, with dnsmasq (version 2.80 on current OpenWRT 19.07.7) I noticed following (in my opinion wrong) behaviour: when using the setting "dhcp-boot=/pxelinux.0,servername,192.168.1.123" the DHCP Offer/ACK packets sent do not contain the "Boot file name" in the header but "Option: (67) Bootfile

[Dnsmasq-discuss] yaml config file

The config file can be quite complex, with lots of option formats (simple scalar vs CSV vs custom). I wonder if it's not proper time to take a standard format off the shelf and use that. I personally would prefer yaml or toml, hopefully not json. I could also volunteer to conver the whole

[Dnsmasq-discuss] scutil Was: dnsmasq's behaviour with configured static hosts is unintuitive

On Sun, Mar 07, 2021 at 09:35:30AM +0100, Cyberfusion wrote: > Op 7 mrt. 2021 om 00:33 heeft Aaron Jones het volgende geschreven: > > 06/03/2021 19:22, Geert Stappers via Dnsmasq-discuss wrote: > > > Share the challenge you are facing with us. > > > > Put simply, I need dnsmasq to return nothing

[Dnsmasq-discuss] dnsmasq to return NODATA for an A query

On Sat, Mar 06, 2021 at 11:12:31PM +, Aaron Jones wrote: > On 06/03/2021 19:22, Geert Stappers via Dnsmasq-discuss wrote: > > On Thu, Mar 04, 2021 at 06:50:39AM +, Aaron Jones wrote, > > with Subject: dnsmasq's behaviour with configured static hosts is > > unintuitive: > > > Hello. > > >

Re: [Dnsmasq-discuss] dnsmasq's behaviour with configured static hosts is unintuitive

> Op 7 mrt. 2021 om 00:33 heeft Aaron Jones het > volgende geschreven: > > On 06/03/2021 19:22, Geert Stappers via Dnsmasq-discuss wrote: >> Share the challenge you are facing with us. > > Put simply, I need dnsmasq to return nothing for an A query, as the VPN > has no IPv4 routing; I do not