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
IPV6 connectivity to fireball.acr.fi is failing inside Cogent AS174. I
have already contacted the Cogent NOC, but I haven't heard anything back
yet. I'm wondering if somebody else with Cogent IPV6 connectivity can
run some tests. IPV4 connectivity is working fine.
--
Clinton Work
IPV6 connectivity to fireball.acr.fi is failing inside Cogent AS174. I
have already contacted the Cogent NOC, but I haven't heard anything back
yet. I'm wondering if somebody else with Cogent IPV6 connectivity can
run some tests. IPV4 connectivity is working fine.
It works from AS2547
From AS54054 in Ashburn, VA I can ping your address but traceroute's
aren't making it through.
Andrew
Andrew Fried
andrew.fr...@gmail.com
On 11/3/13, 1:30 PM, Clinton Work wrote:
IPV6 connectivity to fireball.acr.fi is failing inside Cogent AS174. I
have already contacted the Cogent NOC, but
All good from AS4307 via Cogent:
Sending 20, 100-byte ICMP Echos to 2001:1BC8:100D::2, timeout is 2 seconds:
Success rate is 100 percent (20/20), round-trip min/avg/max = 200/203/204 ms
Traceroutes fail altogether.
On 11/3/2013 10:30 AM, Clinton Work wrote:
IPV6
I can reach fireball.acr.fi on TCP port 80 so it looks like Cogent is
just filtering or dropping IPV6 traceroute packets.
Thanks for checking connectivity from other locations.
--
Clinton Work
Calgary, AB
On Sun, Nov 3, 2013, at 01:38 PM, Andrew Fried wrote:
From AS54054 in Ashburn, VA I
On Nov 3, 2013, at 15:38, Clinton Work clin...@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
7 matches
Mail list logo
