Re: Cogent IPV6 connectivity to fireball.acr.fi
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.)
Cogent IPV6 connectivity to fireball.acr.fi
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
Re: Cogent IPV6 connectivity to fireball.acr.fi
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 through Cogent: PING6(56=40+8+8 bytes) 2001:738:2001:2001::c -- 2001:1bc8:100d::2 16 bytes from 2001:1bc8:100d::2, icmp_seq=0 hlim=52 time=57.356 ms 16 bytes from 2001:1bc8:100d::2, icmp_seq=1 hlim=52 time=57.499 ms 16 bytes from 2001:1bc8:100d::2, icmp_seq=2 hlim=52 time=57.889 ms ^C --- fireball.acr.fi ping6 statistics --- 3 packets transmitted, 3 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 57.356/57.581/57.889/0.225 ms traceroute6 to fireball.acr.fi (2001:1bc8:100d::2) from 2001:738:2001:2001::c, 64 hops max, 12 byte packets 1 vl100.taz.net.bme.hu 0.730 ms 0.389 ms 0.369 ms 2 tg0-1-0-1.rtr.bme.hbone.hu 1.116 ms 0.839 ms 0.590 ms 3 * * * 4 2001:978:2:27::7:1 1.227 ms 0.979 ms 0.942 ms 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * 2001:978:2:3f::6 46.962 ms 12 2001:1bc8:1:7:0:d:0:1 47.060 ms * 47.309 ms 13 2001:1bc8:100:100:5::2 55.083 ms !N 54.830 ms !N 62.167 ms !N $ telnet -6 fireball.acr.fi 80 Trying 2001:1bc8:100d::2... Won't send login name and/or authentication information. Connected to fireball.acr.fi. Escape character is '^]'. GET !DOCTYPE HTML public -//W30//DTD W3 HTML 3.0//EN HTML HEAD TITLEThe Home Page of Tero Kivinen/TITLE LINK REL=Up HREF=http://www.iki.fi/; LINK REL=Home HREF=index.html LINK REV=made HREF=mailto:kivi...@iki.fi; /HEAD András
Re: Cogent IPV6 connectivity to fireball.acr.fi
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 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.
Re: Cogent IPV6 connectivity to fireball.acr.fi
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 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.
Re: Cogent IPV6 connectivity to fireball.acr.fi
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 can ping your address but traceroute's aren't making it through. Andrew Andrew Fried andrew.fr...@gmail.com
Re: Cogent IPV6 connectivity to fireball.acr.fi
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 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
