[154320] in North American Network Operators' Group
Re: NANOG Digest, Vol 54, Issue 3 (Comcast's IPv6 Information Site
daemon@ATHENA.MIT.EDU (Brzozowski, John)
Mon Jul 2 07:08:12 2012
From: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
To: "<nanog@nanog.org>" <nanog@nanog.org>
Date: Mon, 2 Jul 2012 11:06:42 +0000
In-Reply-To: <mailman.2409.1341197164.68975.nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Folks,
We will report back shortly with some updates.
Thanks for the mail.
John
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
John Jason Brzozowski
Comcast Cable
m) +1-609-377-6594
e) mailto:john_brzozowski@cable.comcast.com
o) +1-484-962-0060
w) http://www.comcast6.net
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
On Jul 1, 2012, at 10:46 PM, <nanog-request@nanog.org>
<nanog-request@nanog.org> wrote:
> Send NANOG mailing list submissions to
> nanog@nanog.org
>=20
> To subscribe or unsubscribe via the World Wide Web, visit
> https://mailman.nanog.org/mailman/listinfo/nanog
> or, via email, send a message with subject or body 'help' to
> nanog-request@nanog.org
>=20
> You can reach the person managing the list at
> nanog-owner@nanog.org
>=20
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of NANOG digest..."
>=20
>=20
> Today's Topics:
>=20
> 1. Re: Comcast's IPv6 Information Site Unreachable (Sadiq Saif)
> 2. RE: Comcast's IPv6 Information Site Unreachable (Frank Bulk)
> 3. Re: Comcast's IPv6 Information Site Unreachable (Derek Ivey)
> 4. Re: [c-nsp] NTP Servers (Jimmy Hess)
> 5. Re: Comcast's IPv6 Information Site Unreachable (Jimmy Hess)
> 6. Re: FYI Netflix is down (steve pirk [egrep])
> 7. Re: Comcast's IPv6 Information Site Unreachable (Derek Ivey)
>=20
>=20
> ----------------------------------------------------------------------
>=20
> Message: 1
> Date: Sun, 1 Jul 2012 19:37:54 -0400
> From: Sadiq Saif <sadiq@asininetech.com>
> To: Derek Ivey <derek@derekivey.com>
> Cc: nanog@nanog.org
> Subject: Re: Comcast's IPv6 Information Site Unreachable
> Message-ID:
> <CABSLv--jqtdX3eyORRRaWgXtV_UAjFY7jzGEcVRyDo_WmQ60KA@mail.gmail.com>
> Content-Type: text/plain; charset=3DUTF-8
>=20
> Website is reachable here via my HE tunnel. Pings are not going
> through though as you showed.
>=20
> On Sun, Jul 1, 2012 at 7:28 PM, Derek Ivey <derek@derekivey.com> wrote:
>> Anyone else having trouble getting to Comcast's IPv6 Information site? I=
t
>> appears to be unreachable over IPv6.
>>=20
>> [root@server ~]# ping6 comcast6.net
>> PING comcast6.net(speedlab-app05.newcastlerdc.de.panjde.comcast.net) 56 =
data
>> bytes
>> From te-4-1-ur01.newcastlerdc.de.panjde.comcast.net icmp_seq=3D0 Destina=
tion
>> unreachable: Administratively prohibited
>> From te-4-1-ur01.newcastlerdc.de.panjde.comcast.net icmp_seq=3D1 Destina=
tion
>> unreachable: Administratively prohibited
>> From te-4-1-ur01.newcastlerdc.de.panjde.comcast.net icmp_seq=3D2 Destina=
tion
>> unreachable: Administratively prohibited
>> From te-4-1-ur01.newcastlerdc.de.panjde.comcast.net icmp_seq=3D3 Destina=
tion
>> unreachable: Administratively prohibited
>> From te-4-1-ur01.newcastlerdc.de.panjde.comcast.net icmp_seq=3D4 Destina=
tion
>> unreachable: Administratively prohibited
>> ^C
>> --- comcast6.net ping statistics ---
>> 5 packets transmitted, 0 received, +5 errors, 100% packet loss, time 400=
8ms
>>=20
>> [root@server ~]# traceroute6 comcast6.net
>> traceroute to comcast6.net (2001:558:fe16:7:69:252:216:215), 30 hops max=
, 40
>> byte packets
>> 1 pfsense.d3r3k.net (2001:470:8:d15::1) 0.278 ms 0.282 ms 0.317 ms
>> 2 2001:470:7:d15::1 (2001:470:7:d15::1) 20.794 ms 24.746 ms 28.569 ms
>> 3 gige-g4-12.core1.ash1.he.net (2001:470:0:90::1) 28.946 ms 29.124 ms
>> 29.144 ms
>> 4 as6453.gige-g3-16.core1.ash1.he.net (2001:470:0:191::2) 28.917 ms
>> 28.936 ms 28.097 ms
>> 5 if-ae2.2.tcore2.AEQ-Ashburn.ipv6.as6453.net (2001:5a0:600:500::1)
>> 28.059 ms 31.771 ms 57.135 ms
>> 6 2001:5a0:600:500::72 (2001:5a0:600:500::72) 28.959 ms 2001:559::31d
>> (2001:559::31d) 29.041 ms 29.060 ms
>> 7 pos-3-11-0-0-cr01.ashburn.va.ibone.comcast.net (2001:558:0:f5a4::1)
>> 32.553 ms 19.810 ms 16.526 ms
>> 8 2001:558:0:f669::2 (2001:558:0:f669::2) 39.019 ms 37.954 ms 36.368 =
ms
>> 9 2001:558:0:f57f::1 (2001:558:0:f57f::1) 67.134 ms 67.151 ms 67.166 =
ms
>> 10 pos-2-7-0-0-cr01.denver.co.ibone.comcast.net (2001:558:0:f54d::1)
>> 81.571 ms 81.507 ms 81.569 ms
>> 11 2001:558:0:f744::2 (2001:558:0:f744::2) 80.633 ms 80.760 ms 79.825=
ms
>> 12 2001:558:d0:33::1 (2001:558:d0:33::1) 104.686 ms 105.060 ms 105.04=
0 ms
>> 13 te-3-1-ur03.cmc.co.ndcwest.comcast.net (2001:558:d0:5::1) 104.335 ms
>> 103.962 ms 104.068 ms
>> 14 te-3-1-ur03.cmc.co.ndcwest.comcast.net (2001:558:d0:5::1) 104.492 ms=
!X
>> 104.597 ms !X 104.999 ms !X
>>=20
>> Thanks,
>> Derek
>>=20
>=20
>=20
>=20
> --=20
> Sadiq S
> O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
>=20
>=20
>=20
> ------------------------------
>=20
> Message: 2
> Date: Sun, 1 Jul 2012 20:35:24 -0500
> From: "Frank Bulk" <frnkblk@iname.com>
> To: "'Derek Ivey'" <derek@derekivey.com>, <nanog@nanog.org>
> Subject: RE: Comcast's IPv6 Information Site Unreachable
> Message-ID: <000201cd57f2$f3973e90$dac5bbb0$@iname.com>
> Content-Type: text/plain; charset=3D"us-ascii"
>=20
> ICMP to www.comcast6.net has been blocked since 3:16 pm Central on 6/7/20=
12.
> But their site loads fine over port 80.
>=20
> Frank
>=20
> -----Original Message-----
> From: Derek Ivey [mailto:derek@derekivey.com]=20
> Sent: Sunday, July 01, 2012 6:28 PM
> To: nanog@nanog.org
> Subject: Comcast's IPv6 Information Site Unreachable
>=20
> Anyone else having trouble getting to Comcast's IPv6 Information site?=20
> It appears to be unreachable over IPv6.
>=20
> [root@server ~]# ping6 comcast6.net
> PING comcast6.net(speedlab-app05.newcastlerdc.de.panjde.comcast.net) 56=20
> data bytes
> From te-4-1-ur01.newcastlerdc.de.panjde.comcast.net icmp_seq=3D0=20
> Destination unreachable: Administratively prohibited
> From te-4-1-ur01.newcastlerdc.de.panjde.comcast.net icmp_seq=3D1=20
> Destination unreachable: Administratively prohibited
> From te-4-1-ur01.newcastlerdc.de.panjde.comcast.net icmp_seq=3D2=20
> Destination unreachable: Administratively prohibited
> From te-4-1-ur01.newcastlerdc.de.panjde.comcast.net icmp_seq=3D3=20
> Destination unreachable: Administratively prohibited
> From te-4-1-ur01.newcastlerdc.de.panjde.comcast.net icmp_seq=3D4=20
> Destination unreachable: Administratively prohibited
> ^C
> --- comcast6.net ping statistics ---
> 5 packets transmitted, 0 received, +5 errors, 100% packet loss, time 4008=
ms
>=20
> [root@server ~]# traceroute6 comcast6.net
> traceroute to comcast6.net (2001:558:fe16:7:69:252:216:215), 30 hops=20
> max, 40 byte packets
> 1 pfsense.d3r3k.net (2001:470:8:d15::1) 0.278 ms 0.282 ms 0.317 ms
> 2 2001:470:7:d15::1 (2001:470:7:d15::1) 20.794 ms 24.746 ms 28.569 ms
> 3 gige-g4-12.core1.ash1.he.net (2001:470:0:90::1) 28.946 ms 29.124=20
> ms 29.144 ms
> 4 as6453.gige-g3-16.core1.ash1.he.net (2001:470:0:191::2) 28.917 ms =20
> 28.936 ms 28.097 ms
> 5 if-ae2.2.tcore2.AEQ-Ashburn.ipv6.as6453.net (2001:5a0:600:500::1) =20
> 28.059 ms 31.771 ms 57.135 ms
> 6 2001:5a0:600:500::72 (2001:5a0:600:500::72) 28.959 ms=20
> 2001:559::31d (2001:559::31d) 29.041 ms 29.060 ms
> 7 pos-3-11-0-0-cr01.ashburn.va.ibone.comcast.net=20
> (2001:558:0:f5a4::1) 32.553 ms 19.810 ms 16.526 ms
> 8 2001:558:0:f669::2 (2001:558:0:f669::2) 39.019 ms 37.954 ms 36.368 =
ms
> 9 2001:558:0:f57f::1 (2001:558:0:f57f::1) 67.134 ms 67.151 ms 67.166 =
ms
> 10 pos-2-7-0-0-cr01.denver.co.ibone.comcast.net (2001:558:0:f54d::1) =20
> 81.571 ms 81.507 ms 81.569 ms
> 11 2001:558:0:f744::2 (2001:558:0:f744::2) 80.633 ms 80.760 ms 79.825 =
ms
> 12 2001:558:d0:33::1 (2001:558:d0:33::1) 104.686 ms 105.060 ms 105.040=
ms
> 13 te-3-1-ur03.cmc.co.ndcwest.comcast.net (2001:558:d0:5::1) 104.335=20
> ms 103.962 ms 104.068 ms
> 14 te-3-1-ur03.cmc.co.ndcwest.comcast.net (2001:558:d0:5::1) 104.492 ms=
=20
> !X 104.597 ms !X 104.999 ms !X
>=20
> Thanks,
> Derek
>=20
>=20
>=20
>=20
>=20
>=20
> ------------------------------
>=20
> Message: 3
> Date: Sun, 01 Jul 2012 21:44:40 -0400
> From: Derek Ivey <derek@derekivey.com>
> To: Frank Bulk <frnkblk@iname.com>
> Cc: nanog@nanog.org
> Subject: Re: Comcast's IPv6 Information Site Unreachable
> Message-ID: <4FF0FD08.8050706@derekivey.com>
> Content-Type: text/plain; charset=3DISO-8859-1; format=3Dflowed
>=20
> Thanks for the input guys! Sounds like it might be an issue with my=20
> tunnel then. I had problems getting to a few sites last week=20
> (http://www.dslreports.com/forum/r27265527-IPV6-Issues-Facebook-and-Engad=
get)=20
> and HE resolved the issue pretty quickly. I will ask them if they are=20
> aware of it.
>=20
> Thanks,
> Derek
>=20
>=20
> On 7/1/2012 9:35 PM, Frank Bulk wrote:
>> ICMP to www.comcast6.net has been blocked since 3:16 pm Central on 6/7/2=
012.
>> But their site loads fine over port 80.
>>=20
>> Frank
>>=20
>> -----Original Message-----
>> From: Derek Ivey [mailto:derek@derekivey.com]
>> Sent: Sunday, July 01, 2012 6:28 PM
>> To: nanog@nanog.org
>> Subject: Comcast's IPv6 Information Site Unreachable
>>=20
>> Anyone else having trouble getting to Comcast's IPv6 Information site?
>> It appears to be unreachable over IPv6.
>>=20
>> [root@server ~]# ping6 comcast6.net
>> PING comcast6.net(speedlab-app05.newcastlerdc.de.panjde.comcast.net) 56
>> data bytes
>> From te-4-1-ur01.newcastlerdc.de.panjde.comcast.net icmp_seq=3D0
>> Destination unreachable: Administratively prohibited
>> From te-4-1-ur01.newcastlerdc.de.panjde.comcast.net icmp_seq=3D1
>> Destination unreachable: Administratively prohibited
>> From te-4-1-ur01.newcastlerdc.de.panjde.comcast.net icmp_seq=3D2
>> Destination unreachable: Administratively prohibited
>> From te-4-1-ur01.newcastlerdc.de.panjde.comcast.net icmp_seq=3D3
>> Destination unreachable: Administratively prohibited
>> From te-4-1-ur01.newcastlerdc.de.panjde.comcast.net icmp_seq=3D4
>> Destination unreachable: Administratively prohibited
>> ^C
>> --- comcast6.net ping statistics ---
>> 5 packets transmitted, 0 received, +5 errors, 100% packet loss, time 400=
8ms
>>=20
>> [root@server ~]# traceroute6 comcast6.net
>> traceroute to comcast6.net (2001:558:fe16:7:69:252:216:215), 30 hops
>> max, 40 byte packets
>> 1 pfsense.d3r3k.net (2001:470:8:d15::1) 0.278 ms 0.282 ms 0.317 ms
>> 2 2001:470:7:d15::1 (2001:470:7:d15::1) 20.794 ms 24.746 ms 28.569 =
ms
>> 3 gige-g4-12.core1.ash1.he.net (2001:470:0:90::1) 28.946 ms 29.124
>> ms 29.144 ms
>> 4 as6453.gige-g3-16.core1.ash1.he.net (2001:470:0:191::2) 28.917 ms
>> 28.936 ms 28.097 ms
>> 5 if-ae2.2.tcore2.AEQ-Ashburn.ipv6.as6453.net (2001:5a0:600:500::1)
>> 28.059 ms 31.771 ms 57.135 ms
>> 6 2001:5a0:600:500::72 (2001:5a0:600:500::72) 28.959 ms
>> 2001:559::31d (2001:559::31d) 29.041 ms 29.060 ms
>> 7 pos-3-11-0-0-cr01.ashburn.va.ibone.comcast.net
>> (2001:558:0:f5a4::1) 32.553 ms 19.810 ms 16.526 ms
>> 8 2001:558:0:f669::2 (2001:558:0:f669::2) 39.019 ms 37.954 ms 36.36=
8 ms
>> 9 2001:558:0:f57f::1 (2001:558:0:f57f::1) 67.134 ms 67.151 ms 67.16=
6 ms
>> 10 pos-2-7-0-0-cr01.denver.co.ibone.comcast.net (2001:558:0:f54d::1)
>> 81.571 ms 81.507 ms 81.569 ms
>> 11 2001:558:0:f744::2 (2001:558:0:f744::2) 80.633 ms 80.760 ms 79.825=
ms
>> 12 2001:558:d0:33::1 (2001:558:d0:33::1) 104.686 ms 105.060 ms 105.04=
0 ms
>> 13 te-3-1-ur03.cmc.co.ndcwest.comcast.net (2001:558:d0:5::1) 104.335
>> ms 103.962 ms 104.068 ms
>> 14 te-3-1-ur03.cmc.co.ndcwest.comcast.net (2001:558:d0:5::1) 104.492 ms
>> !X 104.597 ms !X 104.999 ms !X
>>=20
>> Thanks,
>> Derek
>>=20
>>=20
>>=20
>=20
>=20
>=20
>=20
>=20
> ------------------------------
>=20
> Message: 4
> Date: Sun, 1 Jul 2012 20:59:42 -0500
> From: Jimmy Hess <mysidia@gmail.com>
> To: PC <paul4004@gmail.com>
> Cc: "nanog@nanog.org" <nanog@nanog.org>
> Subject: Re: [c-nsp] NTP Servers
> Message-ID:
> <CAAAwwbX-fEzaLRPrbrhM4MowFY=3DFJ2aGe=3DT4xFN+TprqKmG_GQ@mail.gmail.com>
> Content-Type: text/plain; charset=3DISO-8859-1
>=20
> On 7/1/12, PC <paul4004@gmail.com> wrote:
>> If your application requires sub-5 second accuracy, (such as end of a
>> banking day), then Windows NTP is unsuitable for the purpose.
> Looks like CYA on Microsoft's part.
>=20
> That i've seen, Windows NTP in physical environments with a hardware
> system clock not having issues consistently provides accuracy better
> than +/- 0.5 against the time source it's synced with, but in
> virtual environments, which have incompatibilities with high
> sub-second RTC accuracy in the first place, neither Windows nor Unix
> NTP services are able to provide that consistently without much
> tinkering.
>=20
> If it's absolutely critical that you have sub-5 second accuracy,
> even Unix NTP is not to be considered good enough, you need highly
> accurate hardware time source, something more accurate than the usual
> system clock you find in a PC or server. Unix NTP can only do so much
> to correct for a broken system clock; although it does do a very
> good job disciplining PC real-time clocks that consistently run a bit
> too fast or too slow, ultimately the
> personal computer clocks can at times be unreliable....
>=20
> If they were perfect, you wouldn't need time sync in the first place;
> just set them once,
> and correct the annual 0.01 seconds worth of error once a year....
>=20
> --
> -JH
>=20
>=20
>=20
> ------------------------------
>=20
> Message: 5
> Date: Sun, 1 Jul 2012 21:20:11 -0500
> From: Jimmy Hess <mysidia@gmail.com>
> To: Derek Ivey <derek@derekivey.com>
> Cc: nanog@nanog.org
> Subject: Re: Comcast's IPv6 Information Site Unreachable
> Message-ID:
> <CAAAwwbVQmcmeGMG44FgSUS6+c9GRTAXBh6DF5P6BEp0rQJVJpA@mail.gmail.com>
> Content-Type: text/plain; charset=3DISO-8859-1
>=20
> On 7/1/12, Derek Ivey <derek@derekivey.com> wrote:
>> Anyone else having trouble getting to Comcast's IPv6 Information site?
>> It appears to be unreachable over IPv6.
>=20
> Looks like just ICMP that's broken.
>=20
> ~# telnet comcast6.net 80
> Trying 2001:558:fe23:2:69:252:208:135...
> Connected to comcast6.net (2001:558:fe23:2:69:252:208:135).
> Escape character is '^]'.
> HEAD / HTTP/1.1
> Host: comcast6.net
> User-Agent: Telnet
>=20
> HTTP/1.1 200 OK
> Date: Mon, 02 Jul 2012 02:21:33 GMT
> Server: Apache/2.2.15 (Red Hat)
> X-Powered-By: PHP/5.3.3
> Set-Cookie: 1a3c31c9847a772452af472ce0afd5f3=3D5hcm2m506se424huah4eo5lvo7=
; path=3D/
> P3P: CP=3D"NOI ADM DEV PSAi COM NAV OUR OTRo STP IND DEM"
> Cache-Control: no-cache
> Pragma: no-cache
> Connection: close
> Content-Type: text/html; charset=3Dutf-8
>=20
> Connection closed by foreign host.
>=20
>=20
>=20
> ~# ping6 comcast6.net
> PING comcast6.net(speedlab-app05.newcastlerdc.de.panjde.comcast.net)
> 56 data bytes
>> From te-4-1-ur01.newcastlerdc.de.panjde.comcast.net icmp_seq=3D0
> Destination unreachable: Administratively prohibited
>> From te-4-1-ur01.newcastlerdc.de.panjde.comcast.net icmp_seq=3D1
> Destination unreachable: Administratively prohibited
>> From te-4-1-ur01.newcastlerdc.de.panjde.comcast.net icmp_seq=3D2
> Destination unreachable: Administratively prohibited
>> From te-4-1-ur01.newcastlerdc.de.panjde.comcast.net icmp_seq=3D3
> Destination unreachable: Administratively prohibited
>> From te-4-1-ur01.newcastlerdc.de.panjde.comcast.net icmp_seq=3D4
> Destination unreachable: Administratively prohibited
>> From te-4-1-ur01.newcastlerdc.de.panjde.comcast.net icmp_seq=3D5
> Destination unreachable: Administratively prohibited
>> From te-4-1-ur01.newcastlerdc.de.panjde.comcast.net icmp_seq=3D6
> Destination unreachable: Administratively prohibited
>> From te-4-1-ur01.newcastlerdc.de.panjde.comcast.net icmp_seq=3D7
> Destination unreachable: Administratively prohibited
>=20
> --- comcast6.net ping statistics ---
> 8 packets transmitted, 0 received, +8 errors, 100% packet loss, time 6999=
ms
>=20
>=20
>=20
> ------------------------------
>=20
> Message: 6
> Date: Sun, 1 Jul 2012 19:38:16 -0700
> From: "steve pirk [egrep]" <steve@pirk.com>
> To: Jay Ashworth <jra@baylink.com>
> Cc: NANOG <nanog@nanog.org>
> Subject: Re: FYI Netflix is down
> Message-ID:
> <CAK4no06996brnEm=3D9117ANePGqrj6_6FDc999KD+ae_kWyWAbA@mail.gmail.com>
> Content-Type: text/plain; charset=3Dwindows-1252
>=20
> On Sun, Jul 1, 2012 at 11:38 AM, Jay Ashworth <jra@baylink.com> wrote:
>=20
>> Not entirely. Datacenters do go down, our best efforts to the contrary
>> notwithstanding. Amazon doesn't guarantee you redundancy on EC2, only
>> the tools to provide it yourself. 25% Amazon; 75% service provider
>> clients;
>> that's my appraisal of the blame.
>>=20
>=20
>> From a Wired article:
>=20
>> That?s what was supposed to happen at Netflix Friday night. But it didn?=
t
>> work out that way. According to Twitter messages from Netflix Director o=
f
>> Cloud Architecture Adrian Cockcroft and Instagram Engineer Rick Branson,=
it
>> looks like an Amazon Elastic Load Balancing service, designed to spread
>> Netflix?s processing loads across data centers, failed during the outage=
.
>> Without that ELB service working properly, the Netflix and Pintrest
>> services hosted by Amazon crashed.
>=20
> http://www.wired.com/wiredenterprise/2012/06/real-clouds-crush-amazon/
>=20
> The GSLB fail-over that was supposed to take place for the affected
> services (that had configured their applications to fail-over) failed.
>=20
> I heard about this the day after Google announced the Compute Engine
> addition to the App Engine product lines they have. The demo was awesome.
> I imagine Google has GSLB down pat by now, so some companies might start
> looking... ;-]
>=20
> --steve
>=20
>=20
> ------------------------------
>=20
> Message: 7
> Date: Sun, 01 Jul 2012 22:45:51 -0400
> From: Derek Ivey <derek@derekivey.com>
> To: Jimmy Hess <mysidia@gmail.com>
> Cc: nanog@nanog.org
> Subject: Re: Comcast's IPv6 Information Site Unreachable
> Message-ID: <4FF10B5F.2090205@derekivey.com>
> Content-Type: text/plain; charset=3DISO-8859-1; format=3Dflowed
>=20
> Someone replied to my DSL Reports thread:=20
> http://www.dslreports.com/forum/r27289866-
>=20
> Apparently there is an ACL issue with their load balancer that is=20
> blocking ICMP and causing PMTU issues for people who use tunnels.
>=20
> http://www.dslreports.com/forum/r27226136-=20
> <http://www.gossamer-threads.com/lists/nsp/ipv6/34197>
>=20
> It looks like it's been going on since June 11. It's strange that=20
> Comcast hasn't resolved the issue by now.
>=20
> Thanks,
> Derek
>=20
> On 7/1/2012 10:20 PM, Jimmy Hess wrote:
>> On 7/1/12, Derek Ivey <derek@derekivey.com> wrote:
>>> Anyone else having trouble getting to Comcast's IPv6 Information site?
>>> It appears to be unreachable over IPv6.
>> Looks like just ICMP that's broken.
>>=20
>> ~# telnet comcast6.net 80
>> Trying 2001:558:fe23:2:69:252:208:135...
>> Connected to comcast6.net (2001:558:fe23:2:69:252:208:135).
>> Escape character is '^]'.
>> HEAD / HTTP/1.1
>> Host: comcast6.net
>> User-Agent: Telnet
>>=20
>> HTTP/1.1 200 OK
>> Date: Mon, 02 Jul 2012 02:21:33 GMT
>> Server: Apache/2.2.15 (Red Hat)
>> X-Powered-By: PHP/5.3.3
>> Set-Cookie: 1a3c31c9847a772452af472ce0afd5f3=3D5hcm2m506se424huah4eo5lvo=
7; path=3D/
>> P3P: CP=3D"NOI ADM DEV PSAi COM NAV OUR OTRo STP IND DEM"
>> Cache-Control: no-cache
>> Pragma: no-cache
>> Connection: close
>> Content-Type: text/html; charset=3Dutf-8
>>=20
>> Connection closed by foreign host.
>>=20
>>=20
>>=20
>> ~# ping6 comcast6.net
>> PING comcast6.net(speedlab-app05.newcastlerdc.de.panjde.comcast.net)
>> 56 data bytes
>> From te-4-1-ur01.newcastlerdc.de.panjde.comcast.net icmp_seq=3D0
>> Destination unreachable: Administratively prohibited
>> From te-4-1-ur01.newcastlerdc.de.panjde.comcast.net icmp_seq=3D1
>> Destination unreachable: Administratively prohibited
>> From te-4-1-ur01.newcastlerdc.de.panjde.comcast.net icmp_seq=3D2
>> Destination unreachable: Administratively prohibited
>> From te-4-1-ur01.newcastlerdc.de.panjde.comcast.net icmp_seq=3D3
>> Destination unreachable: Administratively prohibited
>> From te-4-1-ur01.newcastlerdc.de.panjde.comcast.net icmp_seq=3D4
>> Destination unreachable: Administratively prohibited
>> From te-4-1-ur01.newcastlerdc.de.panjde.comcast.net icmp_seq=3D5
>> Destination unreachable: Administratively prohibited
>> From te-4-1-ur01.newcastlerdc.de.panjde.comcast.net icmp_seq=3D6
>> Destination unreachable: Administratively prohibited
>> From te-4-1-ur01.newcastlerdc.de.panjde.comcast.net icmp_seq=3D7
>> Destination unreachable: Administratively prohibited
>>=20
>> --- comcast6.net ping statistics ---
>> 8 packets transmitted, 0 received, +8 errors, 100% packet loss, time 699=
9ms
>=20
>=20
>=20
>=20
> End of NANOG Digest, Vol 54, Issue 3
> ************************************
