Slashdot Mirror
Comcast Plans IPv6 Trials In 2010
Mortimer.CA writes "In a weblog posting, Jason Livingood, Executive Director of Comcast's Internet Systems has stated that they're beginning public trials of IPv6; Comcast hopes 'that these trials will encourage other stakeholders to make plans to continue, or to begin, work on IPv6 in 2010 so that all stakeholders do their part in ensuring the future of the Internet is as bright and innovative as it has been in the past.' Interested guinea pigs can volunteer at Comcast6.net (FAQ). Those who have IPv6 connectivity via other means can check out their IPv6-only web presence."
I have no ipv6 at this location and it loads just fine here, not exactly 'ipv6 only' like the Dancing Kame ...
Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
I can see it on my ipv6 connection, it's on 2001:558:1002:5:68:87:64:59 and seems to work :)
For those on the UK wanting an ADSL ISP with ipv6 support I recommend Andrews & Arnold (http://www.aaisp.net.uk/) who have been doing this for years now and provide native or tunneled ipv6 and full ipv6 static addresses to their customers on request.
Just a happy customer of theirs :)
ipv6.google.com is IPv6 only, and if you can reach it, you are IPv6 enabled.
We actually used this for the IPv6 test in Netalyzr as the basis of the IPv6 connectivity test. Our servers don't have IPv6, but we have a small amount of javascript on the analysis page that tries to fetch the logo from IPv6.google.com and reports success or failure back to the server.
Test your net with Netalyzr
Pinging ipv6.comcast.net [68.87.64.59]
It works for me.
$ ping6 ipv6.comcast.net
PING6(56=40+8+8 bytes) 2002:1159:44ef::226:48ff:fe12:a9a7 --> 2001:558:1002:5:68:87:64:59
16 bytes from 2001:558:1002:5:68:87:64:59, icmp_seq=0 hlim=52 time=235.216 ms
16 bytes from 2001:558:1002:5:68:87:64:59, icmp_seq=1 hlim=52 time=245.426 ms
This is through an Apple airport base station via whatever tunnel provider it uses for its IPv6 support. No manual setup, just click the buttons to turn IPv6 on and to block incoming connections.
You got trapped by OpenDNS. OpenDNS is VERY agressive at wildcarding network failures:
132.219.67.208.in-addr.arpa. 18794 IN PTR hit-nxdomain.opendns.com.
So even though there is a valid name for ipv6.google.com (the Google DNS servers return a valid reply with a 0-size answer for an A query, and the whole data for an AAA query), OpenDNS instead goes "hey, lets wildcard it and return our server!"
This behavior is why I'm NOT a fan of OpenDNS.
Test your net with Netalyzr
I was part of the team that wrote the IPv6 portion of the DOCSIS 3.0 specs. Although DOCSIS 3.0 added a huge number of features, the two that the cable companies were most desperate for were channel bonding (so they could compete with fiber) and IPv6 support.
IPv6 has been internal testing with major cable operators for several years now. Comcast was always likely to be the first to deploy it (for reasons that I can't go into) but I expect the other major operators to follow suit within a year or two.