Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Jim Gettys <jg@freedesktop.org>
Cc: dnsmasq-discuss <Dnsmasq-discuss@lists.thekelleys.org.uk>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Problems with DNSsec on Comcast, with Cero 3.10.38-1/DNSmasq 4-26-2014
Date: Mon, 28 Apr 2014 11:37:42 -0700	[thread overview]
Message-ID: <CAA93jw4D790r=UD0uKjfWZ2vDGO6u+dQG0GdYXbPXrTeiZWxYw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6ukYcBSEdubFbqoT20MdLLdXHZUbU6Hq+gLWNCaCTY6Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2787 bytes --]

I have put a link up to two of jim's captures going to test-ipv6 via cero,
one with dnssec enabled, captured at the local laptop

http://snapon.lab.bufferbloat.net/~cero2/baddns/

definately a lot of missing responses when captured at this end. the local
laptop is using a local dnsmasq forwarder.

It is falling back to trying a recursive lookup on the default domain (
ipv6.test-ipv6.com.home.lan ) - which it does do a nxdomain for
immediately...



On Mon, Apr 28, 2014 at 10:03 AM, Dave Taht <dave.taht@gmail.com> wrote:

>
>
>
> On Mon, Apr 28, 2014 at 9:55 AM, Jim Gettys <jg@freedesktop.org> wrote:
>
>> ​​Comcast recently lit up IPv6 native dual stack in the Boston area.
>>
>> The http://test-ipv6.com/ web site complains about DNS problems unless
>> dnssec is disabled; if it is, I get various timeouts.
>>
>>
>>
>  Test with IPv4 DNS record
>> ok (4.196s)
>> Test with IPv6 DNS record
>> ok (0.115s) using ipv6
>> Test with Dual Stack DNS record
>> timeout (11.882s)
>>
>
> I  don't  know what this test does. try a local query over ipv6?
>
>  Test for Dual Stack DNS and large packet
>> timeout (11.817s)
>> Test IPv4 without DNS
>> ok (0.214s) using ipv4
>> Test IPv6 without DNS
>> ok (0.204s) using ipv6
>> Test IPv6 large packet
>> ok (0.120s) using ipv6
>> Test if your ISP's DNS server uses IPv6
>> slow (8.752s)
>> Find IPv4 Service Provider
>> timeout (11.968s)
>> Find IPv6 Service Provider
>> ok (0.126s) using ipv6 ASN 7922
>> Test for buggy DNS
>> undefined (5.003s)
>>
>> DNS server addresses look reasonable for Comcast.
>> DNS 1: 75.75.75.75
>> DNS 2: 75.75.76.76
>>
>
> To try to isolate  things a little  bit, you can turn off fetching ipv4
> dns servers
> with
>
> option peerdns  '0'
>
> in the wan (ge00) stanza  of /etc/config/network
>
> and let the wan6 stanza fetch them.
>
> A packet capture of it working vs not working would be good.
>
> tcpdump  -i ge00 -w cap1.cap port 53
>
> Also  capture on the local interface.
>
> DNS 1: 2001:558:feed::1
>> DNS 2: 2001:558:feed::2
>>
>> Today, the problem seems consistent with turning dnssec on and off on the
>> router.  If enabled, I have problems; if disabled, I get a clean bill of
>> health out of test-ipv6.com.
>>                                               - Jim
>>
>>
>> _______________________________________________
>> Cerowrt-devel mailing list
>> Cerowrt-devel@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>>
>>
>
>
> --
> Dave Täht
>
> NSFW:
> https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article
>



-- 
Dave Täht

NSFW:
https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article

[-- Attachment #2: Type: text/html, Size: 8574 bytes --]

  reply	other threads:[~2014-04-28 18:37 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-28 16:55 Jim Gettys
2014-04-28 17:03 ` Dave Taht
2014-04-28 18:37   ` Dave Taht [this message]
2014-04-28 18:56     ` Dave Taht
2014-04-28 19:32       ` [Cerowrt-devel] [Dnsmasq-discuss] " Simon Kelley
2014-04-28 19:45         ` Aaron Wood
2014-04-28 23:24         ` Phil Pennock
2014-04-29 13:22           ` Simon Kelley
2014-04-29 20:57             ` Phil Pennock
2014-04-30 17:26               ` Dave Taht
2014-05-01 18:37                 ` Simon Kelley
2014-05-01 20:26                   ` Rich Brown
2014-05-01 22:27                     ` Dave Taht
2014-05-02 14:30                       ` Sebastian Moeller
2014-05-01 18:35               ` Simon Kelley
2014-05-02 16:40                 ` James Cloos
2014-10-03  9:28             ` [Cerowrt-devel] " Anders Kaseorg
2014-10-03 17:28               ` Valdis.Kletnieks
2014-10-03 21:35                 ` Anders Kaseorg
2014-10-04 21:45               ` Anders Kaseorg
2015-01-08 16:34                 ` Simon Kelley
2015-01-08 17:44                   ` Dave Taht
2015-01-08 18:07                     ` Simon Kelley
2015-01-08 19:52                       ` Dave Taht
2015-01-09  8:52                         ` Dave Taht
2015-01-09 15:36                           ` Simon Kelley
2015-01-09 16:49                           ` Simon Kelley
2015-01-09 21:34                             ` Dave Taht
2015-01-10 15:37                               ` Simon Kelley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAA93jw4D790r=UD0uKjfWZ2vDGO6u+dQG0GdYXbPXrTeiZWxYw@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=Dnsmasq-discuss@lists.thekelleys.org.uk \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=jg@freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox