From: Dave Taht <dave.taht@gmail.com>
To: Jim Reisert AD1C <jjreisert@alum.mit.edu>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] IPV6
Date: Sat, 21 Dec 2013 09:44:33 -0800 [thread overview]
Message-ID: <CAA93jw5t=42qMuN2j_AZDAKMd+Rzpzv9giGJeaRLiGWh-v_xmg@mail.gmail.com> (raw)
In-Reply-To: <CAK-n8j6d8W1KuaWXYLZxyvHX6QcFMw5=9oqPNn1+GknJn8xB=A@mail.gmail.com>
No, you did not managed to get ipv6 addrs assigned on even the
gateway. How you got an addr assigned for ipv6 dns is puzzling.
grump. Well, something broke between last feburary (when this worked
in comcast's lab), and today (deployment). I am trying to get ipv6 at
a location here in california that ostensibly supports it...
(but oy, do I not want to talk about the disaster I had with customer
service yesterday trying to get bridge mode to work and also saw no
sign of an ipv6 address assignment. I want to maintain the holiday
spirit)
But we'll get there.
Merely getting to comcast6.net is not a good test. That is on both
ipv4 and ipv6.
On Sat, Dec 21, 2013 at 9:13 AM, Jim Reisert AD1C
<jjreisert@alum.mit.edu> wrote:
> On Wed, Dec 18, 2013 at 9:40 PM, Dave Taht <dave.taht@gmail.com> wrote:
>
>> The gui is broken on seeing the wan port. It does look like you got
>> dns via ipv6.
>>
>> do an
>>
>> ip -6 addr show
>
> 2: se00: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
> inet6 fe80::100d:7fff:fe64:c60c/64 scope link
> valid_lft forever preferred_lft forever
>
> 3: ge00: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
> inet6 fe80::120d:7fff:fe64:c60d/64 scope link
> valid_lft forever preferred_lft forever
>
>> if you do see ipv6 addrs, hopefully dnsmasq is doing ipv6 dns queries
>> at the very least. Try also a ping6 of a ipv6 enabled website.
>
> root@cerowrt:~# ping comcast6.net
> PING comcast6.net (69.252.216.215): 56 data bytes
> --- comcast6.net ping statistics ---
> 6 packets transmitted, 0 packets received, 100% packet loss
>
> I can get to http://comcast6.net however.
>
>
> --
> Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
prev parent reply other threads:[~2013-12-21 17:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 2:35 Jim Reisert AD1C
2013-12-19 4:40 ` Dave Taht
2013-12-21 17:13 ` Jim Reisert AD1C
2013-12-21 17:17 ` Fred Stratton
2013-12-27 2:09 ` Jim Reisert AD1C
2013-12-21 17:44 ` Dave Taht [this message]
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='CAA93jw5t=42qMuN2j_AZDAKMd+Rzpzv9giGJeaRLiGWh-v_xmg@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=jjreisert@alum.mit.edu \
/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