* [Cerowrt-devel] IPV6
@ 2013-12-19 2:35 Jim Reisert AD1C
2013-12-19 4:40 ` Dave Taht
0 siblings, 1 reply; 6+ messages in thread
From: Jim Reisert AD1C @ 2013-12-19 2:35 UTC (permalink / raw)
To: cerowrt-devel
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Cerowrt-devel] IPV6
2013-12-19 2:35 [Cerowrt-devel] IPV6 Jim Reisert AD1C
@ 2013-12-19 4:40 ` Dave Taht
2013-12-21 17:13 ` Jim Reisert AD1C
0 siblings, 1 reply; 6+ messages in thread
From: Dave Taht @ 2013-12-19 4:40 UTC (permalink / raw)
To: Jim Reisert AD1C; +Cc: cerowrt-devel
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Cerowrt-devel] IPV6
2013-12-19 4:40 ` Dave Taht
@ 2013-12-21 17:13 ` Jim Reisert AD1C
2013-12-21 17:17 ` Fred Stratton
2013-12-21 17:44 ` Dave Taht
0 siblings, 2 replies; 6+ messages in thread
From: Jim Reisert AD1C @ 2013-12-21 17:13 UTC (permalink / raw)
To: Dave Taht; +Cc: cerowrt-devel
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
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [Cerowrt-devel] IPV6
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
1 sibling, 1 reply; 6+ messages in thread
From: Fred Stratton @ 2013-12-21 17:17 UTC (permalink / raw)
To: Jim Reisert AD1C, cerowrt-devel
You used ping, not ping6, from what you posted.
On 21/12/13 17:13, Jim Reisert AD1C 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.
>
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Cerowrt-devel] IPV6
2013-12-21 17:17 ` Fred Stratton
@ 2013-12-27 2:09 ` Jim Reisert AD1C
0 siblings, 0 replies; 6+ messages in thread
From: Jim Reisert AD1C @ 2013-12-27 2:09 UTC (permalink / raw)
To: Fred Stratton; +Cc: cerowrt-devel
On Sat, Dec 21, 2013 at 10:17 AM, Fred Stratton <fredstratton@imap.cc> wrote:
> You used ping, not ping6, from what you posted.
Right.
root@cerowrt:~# ping6 comcast6.net
PING comcast6.net (2001:558:fe16:7:69:252:216:215): 56 data bytes
^C
--- comcast6.net ping statistics ---
11 packets transmitted, 0 packets received, 100% packet loss
--
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Cerowrt-devel] IPV6
2013-12-21 17:13 ` Jim Reisert AD1C
2013-12-21 17:17 ` Fred Stratton
@ 2013-12-21 17:44 ` Dave Taht
1 sibling, 0 replies; 6+ messages in thread
From: Dave Taht @ 2013-12-21 17:44 UTC (permalink / raw)
To: Jim Reisert AD1C; +Cc: cerowrt-devel
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
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2013-12-27 2:09 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-12-19 2:35 [Cerowrt-devel] IPV6 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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox