[Dnsmasq-discuss] Possible lease matching/reuse bug

[Geert Stappers]

On Fri, Sep 11, 2020 at 03:12:34AM +0100, Jerome Vuarand wrote:
> On Wed, 9 Sep 2020 at 17:36, Geert Stappers <stappers at stappers.nl> wrote:

              context,   meanwhile lost


> > > The client sends its hostname "target" which seems to be enough to
> > > identify it and give it the associated ipaddr (either from
> > > dnsmasq.conf or from /etc/hosts).
> >
> > So it seems you either want
> >   dhcp-host=id:target,192.168.4.2
> > or
> >   dhcp-host=id:target,target
> 
> These don't work at all, it gives the following log on first connection:
> 
> dnsmasq-dhcp[583]: DHCPDISCOVER(ap0) b8:27:eb:a6:d4:d6
> dnsmasq-dhcp[583]: DHCPOFFER(ap0) 192.168.4.200 b8:27:eb:a6:d4:d6
> dnsmasq-dhcp[583]: DHCPREQUEST(ap0) 192.168.4.200 b8:27:eb:a6:d4:d6
> dnsmasq-dhcp[583]: DHCPACK(ap0) 192.168.4.200 b8:27:eb:a6:d4:d6 target

I think "existing leases"
but that doesn't match the reported "on first connection"
 
> And unless I remove the entry from /etc/hosts (which is necessary in
> the second case), I get this just after:
> 
> dnsmasq-dhcp[583]: not giving name target.chepstowrifleclub.org.uk to the DHCP lease of 192.168.4.200 because the name exists in /etc/hosts with address 192.168.4.2
> dnsmasq-dhcp[583]: not giving name target to the DHCP lease of 192.168.4.200 because the name exists in /etc/hosts with address 192.168.4.2


OK, sounds good.



Regards
Geert Stappers
Having trooble to read "These don't work at all" as "I still don't understand it"


P.S.
I'm on the mailinglist
-- 
Silence is hard to parse