[166700] in North American Network Operators' Group
Re: Cogent IPV6 connectivity to fireball.acr.fi
daemon@ATHENA.MIT.EDU (Clinton Work)
Mon Nov 4 10:41:40 2013
From: Clinton Work <clinton@scripty.com>
To: nanog@nanog.org
Date: Mon, 04 Nov 2013 08:41:28 -0700
In-Reply-To: <-8241591075349665864@unknownmsgid>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
I should have stated that I tried icmpv6, UDP, and TCP traceroute with
the same results. Looks like Cogent is not returning TTL expired IPV6
packets within their core. I can only guess that this is a result of
using 6PE and propagating the IPV6 TTL into MPLS.
Clinton
On Sun, Nov 3, 2013, at 09:47 PM, Joe Abley wrote:
> "Traceroute packets" is extremely vague. As a general rule, if you
> want to discover a complete path between endpoints that are expected
> to communicate using 80/tcp, trace the route using 80/tcp.
>
> (Not that it's ever expected to see protocol-specific drops in a core
> or across a transit or peering edge.)
