[Dnsmasq-discuss] address=/#/192.168.0.1 - does not work!
nikitan at operamail.com
Mon Dec 9 23:01:47 GMT 2013
Yes, it did the trick, worked at first shot :)
Still remains that "silence" after DHCP "requests" without previous
"discover".. really unpleasant..
Probably its not 100% protocol compliant, but I see also from dhcpd, its
common behaviour to accept DHCP requests from "returning" clients..
Maybe implement a new option also in dnsmasq to enable such
On Mon, Dec 9, 2013, at 09:04 AM, Simon Kelley wrote:
> I think this may be what you need.
> -K, --dhcp-authoritative
> Should be set when dnsmasq is definitely the only
> DHCP server on a network. For DHCPv4, it changes the
> behaviour from strict RFC compliance so that DHCP requests on
> unknown leases from unknown hosts are not ignored.
> This allows new hosts to get a lease without a tedious
> timeout under all circumstances.
> Dnsmasq-discuss mailing list
> Dnsmasq-discuss at lists.thekelleys.org.uk
http://www.fastmail.fm - Access your email from home and the web
More information about the Dnsmasq-discuss