nanog mailing list archives
Re: Cogent IPV6 connectivity to fireball.acr.fi
From: Clinton Work <clinton () scripty com>
Date: Mon, 04 Nov 2013 08:41:28 -0700
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.)
Current thread:
- Cogent IPV6 connectivity to fireball.acr.fi Clinton Work (Nov 03)
- Re: Cogent IPV6 connectivity to fireball.acr.fi JÁKÓ András (Nov 03)
- Re: Cogent IPV6 connectivity to fireball.acr.fi Andrew Fried (Nov 03)
- Re: Cogent IPV6 connectivity to fireball.acr.fi Clinton Work (Nov 03)
- Re: Cogent IPV6 connectivity to fireball.acr.fi Joe Abley (Nov 03)
- Re: Cogent IPV6 connectivity to fireball.acr.fi Clinton Work (Nov 04)
- Re: Cogent IPV6 connectivity to fireball.acr.fi Clinton Work (Nov 03)
- Re: Cogent IPV6 connectivity to fireball.acr.fi Robert Glover (Nov 03)