On 09/01/2022 22:27, Simon Kelley wrote: > On 09/01/2022 10:09, Andreas Metzler wrote: >> On 2022-01-06 Andreas Metzler <ametz...@bebt.de> wrote: >>> On 2022-01-05 Simon Kelley wrote: >>>> On 04/01/2022 17:11, Andreas Metzler wrote: >>> [...] >>>>> FWIW this looks similar to https://bugs.debian.org/1001576 which >> [...] >>>> Are you running with the --strict-order config? The backtrace looks, at >>>> least superficially, like the bug fixed in >> >>>> https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=2561f9fe0eb9c0be1df48da1e2bd3d3feaa138c2 >> >>>> Whilst John is not setting --strict order, so that doesn't seem to to be >>>> relevant in his case. >> >>> Hello Simon, >> >>> I have not set strict-order. However I have now rebuilt the Debian >>> package with the abovementioned patch. Let's see whether the problem >>> goes away. >> >> Sadly the patch did not fix the issue. > > OK. > > A few questions, if that's OK. > > 1) I guess you're using DNSSEC, if that correct? > 2) How difficult is that to reproduce? > 3) Could you set --log-queries, maybe with --log-facility set to a file, > if that's easier, and send me the log leading up to a lockup? > >
.. and further, if possible, configure --dumpfile and --dumpmask=0x00ff and send me the packet dump too. > > Cheers, > > Simon. > >> >> cu Andreas >> >> _______________________________________________ >> Dnsmasq-discuss mailing list >> Dnsmasq-discuss@lists.thekelleys.org.uk >> https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss >> > _______________________________________________ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
