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: Wed, 18 Dec 2013 20:40:30 -0800 [thread overview]
Message-ID: <CAA93jw7dQ9LxBkpfhq2ysO9_0q3jmsyp6YPPKKGtKASj0sBexg@mail.gmail.com> (raw)
In-Reply-To: <CAK-n8j4Rr604923TPS1tkmwDpTKGL9XhTwgWDhKrsvPk+eqmpg@mail.gmail.com>
The gui is broken on seeing the wan port. It does look like you got
dns via ipv6.
do an
ip -6 addr show
at the prompt and see if you have ipv6 assigned on the ge00 and se00
devices, at the very least. Of course, the big win would be to see it
on all but the gw11 and gw01 interfaces. Have never got around to
writing the code to assign the /128s on those interfaces/
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.
My ipv6 at one of my main sites arrives soon for comcast (or rather an
ipv6 capable modem). CMTS was upgraded a while back.
I have not had an opportunity to test the odhcpdv6 code since
feburary, but it worked then.
For those of you out there on comcast you can see if your CMTS is ipv6
capable via going to comcast6.net.
Old (non ipv6) modems are common, there are several new ones I liked
that I guess I should document.
On Wed, Dec 18, 2013 at 6:35 PM, Jim Reisert AD1C
<jjreisert@alum.mit.edu> wrote:
> According to Comcast, Colorado is enabled for IPV6:
>
> http://www.comcast6.net/index.php/8-ipv6-trial-news-and-information/134-comcast-ipv6-rollout-expands
>
> "Comcast's IPv6 deployment continues to expand, over 25% of our
> customers are actively provisioned with native dual stack broadband!
> The following areas of the Comcast broadband footprint are now fully
> IPv6 enabled - Colorado, New Mexico, Minnesota, Kansas, Missouri,
> Maryland, Ohio, Pennsylvania, West Virginia, and Houston."
>
> Is there anything I have to do in the router to take advantage of
> this? All I see is the following:
>
> IPV6 WAN Status:
>
> Address: ::
> Gateway: FE80:0:0:0:201:5CFF:FE22:2A01
> DNS 1: 2001:558:feed::1
> DNS 2: 2001:558:feed::2
> Connected: 31d 5h 43m 23s
>
> --
> Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
next prev parent reply other threads:[~2013-12-19 4:40 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 [this message]
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
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=CAA93jw7dQ9LxBkpfhq2ysO9_0q3jmsyp6YPPKKGtKASj0sBexg@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