IPv6

Owen DeLong owen at delong.com
Fri Nov 19 03:19:01 CST 2010


Another option is a static BGP tunnel with HE which can be configured
at http://tunnelbroker.net. It's not ideal and only useful for relatively low
bandwidth. If your needs are greater, we would much rather sell
you transit or peer with you as appropriate. As everyone should know
by now, we have an aggressively open peering policy.

Feel free to direct questions to me off list or to peering at he.net
if you have a peering request.

Owen

On Nov 18, 2010, at 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).
> 
> Nick Olsen
> Network Operations
> (855) FLSPEED  x106
> 
> ----------------------------------------
> 
> From: "Mike Tancsa" <mike at sentex.net>
> Sent: Thursday, November 18, 2010 5:45 PM
> To: "Lee Riemer" <lriemer at 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
> 





More information about the NANOG mailing list