Hi,
I discovered that using dnsmasq as a dhcp (ip4) server on a system with
another nic that has no ip, causes the automatic determination of the
subnet mask to fail, and the server offers leases with a subnet mask of
0.0.0.0. I have worked around it by specifying the subnet mask in the
config.
I've used it for a while on freebsd without issue, configured as per
dnsmasq man page syntax
I would add to docs the risk that this feature can lead to a growing table
of ips that never gets pruned or expired, that could lead to allowing more
ip addrs within a Table over time, than might be antici
Thanks for the clarification and updating the man page too. I'll update my
configuration generating scripts.
Thanks again
Andrew
On Thu 3 Mar 2016 21:26 Simon Kelley wrote:
> On 02/03/16 18:14, Andrew White wrote:
> > Hi,
> >
> > version > 2.65 introduced a bug
Hi,
version > 2.65 introduced a bug where this command gives "bad dhcp-range"
./src/dnsmasq -F dhcp-range=set:tag1,192.168.1.1,192.168.1.254,static
due to how the parsing of options were changed.
adding the subnetmask appears to work around it.
./src/dnsmasq -F
dhcp-range=set:tag1,192.168.1.1,1
