Hi Geert, Thank you for your response.
I am not sure I fully understand it. Yes, both times the same IP address is passed however test.conf is being overwritten so at any point in time there is at most one entry with this IP address as per the conf files. Yet dnsmasq daemon thinks there is a duplicate. As far as I understand this happens because it does not act on entries deletion: - removing test.conf produces no messages in logs; - emptying it produces "changed file" message in logs however if you re-add even exactly the same entry (with the same id: and same IP) - then dnsmasq says there is a duplicate which is factually wrong - the address is not leased, the address was removed from config, dnsmasq noticed this change, then the address was re-added with exactly same filter, dnsmasq noticed this change and thinks there is a duplicate. Am I missing something? On Sun, 17 May 2020 at 08:10, Geert Stappers <stapp...@stappers.nl> wrote: > On Sat, May 16, 2020 at 05:07:59PM +0100, an0nym wrote: > > Hello, > > > > I hope you are safe and well. > > > > When dnsmasq is configured to monitor hostsdir, I believe there is no > > forgetting logic when you delete and then create or simply overwrite one > of > > the files there with different filter and the same allocated IP. > > > > E. g. > > > > # grep -F dhcp-hostsdir /etc/dnsmasq.conf > > dhcp-hostsdir=/etc/dnsmasq.d/hosts.d > > # echo "id:test,192.168.0.156" >/etc/dnsmasq.d/hosts.d/test.conf > > test .156 > > > > # systemctl status dnsmasq > > ... > > dnsmasq: inotify, new or changed file > > /etc/dnsmasq.d/hosts.d/test.conf > > dnsmasq-dhcp: read /etc/dnsmasq.d/hosts.d/test.conf > > # echo "id:test2,192.168.0.156" >/etc/dnsmasq.d/hosts.d/test.conf > > test2 .156 > > > > # systemctl status dnsmasq > > ... > > dnsmasq: inotify, new or changed file > > /etc/dnsmasq.d/hosts.d/test.conf > > dnsmasq-dhcp: read /etc/dnsmasq.d/hosts.d/test.conf > > dnsmasq: duplicate dhcp-host IP address 192.168.0.156 at line 1 > of /etc/dnsmasq.d/hosts.d/test.conf > > duplicate of .156 > > > > Dnsmasq 2.80. Apologies if this has been fixed in 2.81, > > I did not succeed in compiling from sources to check. > > > > I hope this helps. > > Helpfull is reporting back how helpfull this message was. > > > Groeten > Geert Stappers > -- > Silence is hard to parse > > _______________________________________________ > Dnsmasq-discuss mailing list > Dnsmasqemail@example.com > http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss >
_______________________________________________ Dnsmasq-discuss mailing list Dnsmasqfirstname.lastname@example.org http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss