Hello,
I can confirm that we suffered something maybe related on all recent
dnsmasq versions (I never tried with something older), since several
years (first seen in 2021, with a v2.86).
In our scenario, we had a lot of new/removed interfaces, and removing an
interface (and associated subnet) triggered randomly the same behavior
than yours.
However, I was never able to create a stable reproducer. At some point,
dnsmasq started to send bad IP addresses, but I never found something to
trigger it. It looks random.
Our current workaround : always update dnsmasq.conf to not include
removed (or down) interfaces, and restart dnsmasq.
Best regards
--
*Ce message et toutes les pièces jointes (ci-après le "message") sont
établis à l’intention exclusive des destinataires désignés. Il contient des
informations confidentielles et pouvant être protégé par le secret
professionnel. Si vous recevez ce message par erreur, merci d'en avertir
immédiatement l'expéditeur et de détruire le message. Toute utilisation de
ce message non conforme à sa destination, toute diffusion ou toute
publication, totale ou partielle, est interdite, sauf autorisation expresse
de l'émetteur*
_______________________________________________
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
