[166689] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Cogent IPV6 connectivity to fireball.acr.fi

daemon@ATHENA.MIT.EDU (Joe Abley)
Sun Nov 3 23:47:35 2013

From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <1383513757.6384.42414557.011C21EF@webmail.messagingengine.com>
Date: Sun, 3 Nov 2013 20:47:21 -0800
To: Clinton Work <clinton@scripty.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

> On Nov 3, 2013, at 15:38, Clinton Work <clinton@scripty.com> wrote:
>
> I can reach fireball.acr.fi on TCP port 80 so it looks like Cogent is
> just filtering or dropping IPV6 traceroute packets.

"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.)


Joe


home help back first fref pref prev next nref lref last post