Re: [Dnsmasq-discuss] Got bad packet: bad compression pointer

2017-02-27 Thread Simon Kelley
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Can you easily test newer code? Either git-HEAD or 2.77test3 has a fix for a bug which looks remarkably like this, and it would be good to eliminate that before going further. Cheers, Simon. On 27/02/17 14:08, Igor Lidin wrote: > I'm observing

[Dnsmasq-discuss] Got bad packet: bad compression pointer

2017-02-27 Thread Igor Lidin
I'm observing the following problem with dnsmasq 2.76 on arm7 platform. Dnsmasq is responing with bad packet, but shouldn't. This is somehow related to DNSSEC, ial.ru is signed. this is through local dnsmasq forwarding server: # dig soa guardian.ial.ru @127.0.0.1 ;; Got bad packet: bad

Re: [Dnsmasq-discuss] Got bad packet: bad compression pointer

2017-01-23 Thread Simon Kelley
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 OK, that's a bit difficult to correlate the client and upstream, but I can see in the responses coming back from upstream that the order of the RRs in the Auth section of the "no-such name" replies is NSEC RRSIG (for NSEC) SOA RRSIG (for SOA)

Re: [Dnsmasq-discuss] Got bad packet: bad compression pointer

2017-01-18 Thread Dave Taht
The offputting part of your outline of what to check for was "some hairy pointer code". :) I'm in the middle of some crash bugs elsewhere, and I didn't realize how fast I could get you data without thinking about the "hairy" parts. dnssec and dnssec-check-unsigned are enabled, and I'm using

Re: [Dnsmasq-discuss] Got bad packet: bad compression pointer

2017-01-18 Thread Dave Taht
On Wed, Jan 18, 2017 at 11:48 AM, Simon Kelley wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > I won't have access to a MIPS system 'till the weekend. > > I assume you're using the git head code? No. Lede-project head. package claims to be dnsmasq-2.76-6.

Re: [Dnsmasq-discuss] Got bad packet: bad compression pointer

2017-01-18 Thread Simon Kelley
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I won't have access to a MIPS system 'till the weekend. I assume you're using the git head code? Did you manage to see a dump of the upstream reply? Simon. On 18/01/17 07:31, Dave Taht wrote: > so far I can only make it happen on mips.

Re: [Dnsmasq-discuss] Got bad packet: bad compression pointer

2017-01-18 Thread Dave Taht
so far I can only make it happen on mips. Doesn't happen on arm. Haven't tried harder yet. ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

Re: [Dnsmasq-discuss] Got bad packet: bad compression pointer

2017-01-16 Thread Dave Taht
On Mon, Jan 16, 2017 at 1:11 PM, Simon Kelley wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Host makes A, and MX queries and it's the reply to the MX that's > failing. This all works fine here (dnsmasq and host both running on > the same x86_64

Re: [Dnsmasq-discuss] Got bad packet: bad compression pointer

2017-01-16 Thread Simon Kelley
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Host makes A, and MX queries and it's the reply to the MX that's failing. This all works fine here (dnsmasq and host both running on the same x86_64 host. The reply to the MX query looks like this. ; (1 server found) ;; global options: +cmd

[Dnsmasq-discuss] Got bad packet: bad compression pointer

2017-01-16 Thread Dave Taht
I am testing the dnsmasq-full build on current lede-project head, and enabled dnssec. Then : root@dancer:/# host flent-fremont.bufferbloat.net flent-fremont.bufferbloat.net has address 23.239.20.41 flent-fremont.bufferbloat.net has IPv6 address 2600:3c01::f03c:91ff:fe50:48d4 ;; Got bad packet: