Re: [Dnsmasq-discuss] [PATCH 0/1] Allow configuring filter-A/AAAA via dbus

2023-01-23 Thread Clayton Craft
On Mon, 23 Jan 2023 14:06:56 -0800 Clayton Craft wrote: > There doesn't appear to be a way to change the filter-A or filter- > parameters at runtime, after the config is loaded / cmdline params are parsed. > In some cases[1], I want to conditionally enable/disabling these options at >

[Dnsmasq-discuss] [PATCH 0/1] Allow configuring filter-A/AAAA via dbus

2023-01-23 Thread Clayton Craft
There doesn't appear to be a way to change the filter-A or filter- parameters at runtime, after the config is loaded / cmdline params are parsed. In some cases[1], I want to conditionally enable/disabling these options at runtime. Is this patch to make this configurable via dbus acceptable? Or

[Dnsmasq-discuss] [PATCH 1/1] dbus: allow setting filter-A and filter-AAAA options

2023-01-23 Thread Clayton Craft
--- dbus/DBus-interface | 8 src/dbus.c | 14 ++ 2 files changed, 22 insertions(+) diff --git a/dbus/DBus-interface b/dbus/DBus-interface index 59b41b1..0701971 100644 --- a/dbus/DBus-interface +++ b/dbus/DBus-interface @@ -44,6 +44,14 @@ SetFilterWin2KOption

Re: [Dnsmasq-discuss] dnsmasq: dhcp-server with disabled dns-server: /etc/hosts ignored

2023-01-23 Thread Matus UHLAR - fantomas
Hello, in an addition to an older thread: On 21/10/2022 22:23, Michael Traxler wrote: When you disable the DNS-server via port=0 the /etc/hosts file is ignored and also the addn-hosts= is ignored. If one wants to disable reading /etc/hosts when DNS is disabled, using option "-h" is easy

Re: [Dnsmasq-discuss] DHCP range for hostnames containing string

2023-01-23 Thread Craig Wright via Dnsmasq-discuss
To Buck - My intention for matching !known devices is that I want them in a separate range. So basically any devices that are not tagged mbdevices, and also not in my dhcp-host list (which go in to the top range) would go in to the 'unknown' range.

Re: [Dnsmasq-discuss] DHCP range for hostnames containing string

2023-01-23 Thread Donald Muller
Sorry. Misread and thought they were being assigned to the first range. From: Craig Wright Sent: Monday, January 23, 2023 9:15:39 AM To: Donald Muller Subject: Re: [Dnsmasq-discuss] DHCP range for hostnames containing string Can you explain how this would help?

Re: [Dnsmasq-discuss] DHCP range for hostnames containing string

2023-01-23 Thread Buck Horn
On 23.01.2023 10:28:50, Craig Wright wrote: I have currently: dhcp-range=192.168.0.2,192.168.0.10,255.255.255.0,12h dhcp-range=tag:mbdevices,192.168.0.50,192.168.0.60,255.255.255.0,12h dhcp-range=tag:!known,192.168.0.11,192.168.0.20,255.255.255.0,12h and have tried each of the lines:

Re: [Dnsmasq-discuss] DHCP range for hostnames containing string

2023-01-23 Thread Donald Muller
For your other IP range try this. dhcp-range=tag:!mbdevices,192.168.0.2,192.168.0.10,255.255.255.0,12h From: Dnsmasq-discuss on behalf of Craig Wright via Dnsmasq-discuss Sent: Monday, January 23, 2023 4:28:50 AM To: dnsmasq-discuss@lists.thekelleys.org.uk

Re: [Dnsmasq-discuss] DHCP range for hostnames containing string

2023-01-23 Thread Craig Wright via Dnsmasq-discuss
Update on this issue, but still not fully resolved I received the following advice from Simon: "> To set the mbdevices tag, you need to use dhcp-match to look for MB in > the hostname option (which has number 12). >> dhcp-match=set:mbdevices,12,MB >> Almost works, but it will match MB