Thank you Simon for the quick reply,
I did indeed miss `interface-name` when skimming through the manual page
and from the looks of it other users on this thread did too.
My suggestion is to have interface-name and dynamic-host mention each
other in the manual page and to modify the error
On 13/03/2023 17:01, Simon Kelley wrote:
Thanks for the bug report, it's definitely not noise.
The history of line 363 is interesting.
When the dynamic-host option was added, it looked like
if (netmask.s_addr == 0x)
and stayed like that until October 2022 when it got changed to the
Thanks for the bug report, it's definitely not noise.
The history of line 363 is interesting.
When the dynamic-host option was added, it looked like
if (netmask.s_addr == 0x)
and stayed like that until October 2022 when it got changed to the
current version
if (netmask.s_addr ==
Hi 0zl and everyone,
I’m writing to add some more information about this issue and my personal
use case that falls on the same problem.
I have being using dnsmasq for a couple of years now, with Pi-Hole project.
In the last year I started using tailscale as a VPN to connect directly to
some
It was proposed to change --conf-file= to have such effect. There were
even patch posted to implement that. I think that would be more useful
than current handling of empty value.
On 3/4/23 22:22, Johnny Utahh wrote:
Is this worth considering?
Proposal: add a `dnsmasq
