[132254] in North American Network Operators' Group
Re: IPv6
daemon@ATHENA.MIT.EDU (Joel Jaeggli)
Thu Nov 18 18:46:14 2010
Date: Thu, 18 Nov 2010 15:46:04 -0800
From: Joel Jaeggli <joelja@bogus.com>
To: nick@flhsi.com
In-Reply-To: <732392d9$bdf3fc5$7a7b0ede$@com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On 11/18/10 3:00 PM, Nick Olsen wrote:
> That's what I'm hearing. Cogent refuses to peer with HE via IPv6.
> So cogent IPv6 Customers currently can not hit things at HE. And they can't
> do anything about it. Besides 6to4 tunneling and BGP peering with HE (or
> native, If they can).
Wait, a settlement free carrier with less than total reachability?
that never happens, er yeah it does...
I'd get two.
joel
> Nick Olsen
> Network Operations
> (855) FLSPEED x106
>
> ----------------------------------------
>
> From: "Mike Tancsa" <mike@sentex.net>
> Sent: Thursday, November 18, 2010 5:45 PM
> To: "Lee Riemer" <lriemer@bestline.net>
> Subject: Re: IPv6
>
> On 11/18/2010 5:14 PM, Lee Riemer wrote:
>> Try tracerouting to 2001:500:4:13::81 (www.arin.net) or
>> 2001:470:0:76::2 (www.he.net) via Cogent.
>>
>
> Interesting. I noticed a similar issue with ipv6.cnn.com today. I dont
> see it via TATA, but see it via Cogent. So whats the story behind it
> and ARIN not being seen through cogent ? Is it due to no v6 relation
> bewtween he.net and Cogent ?
>
> 2620:0:2200:8:8888:8888:8888:8901 (whats with the crazy 8s?)
>
> see
> http://lg.as6453.net/lg/
>
> Router: gin-mtt-mcore3
> Site: CA, Montreal - MTT, TATA COMM. INT. CENTER
> Command: traceroute ipv6 2620:0:2200:8:8888:8888:8888:8901
>
> Tracing the route to 2620:0:2200:8:8888:8888:8888:8901
>
> 1 * * *
> 2 * * *
> 3 * * *
> 4 * * *
>
> ---Mike
>
>
