Ticket ID: SIXXS #7966290 Ticket Status: Resolved PoP: sesto01 - Availo (Stockholm)
No ipv6 connectivity past 2001:16d8:1:1352::95 as seen from sesto01
Shadow Hawkins on Saturday, 06 October 2012 10:21:24
------------------------------------------------------------------------------>8
ID JF2268-RIPE
Tunnel T6705
Relevant output from Aiccu test:
###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:16d8:ff00:3a::2)
### This confirms that your tunnel is configured
### If it doesn't reply then check your interface and routing tables
PING 2001:16d8:ff00:3a::2(2001:16d8:ff00:3a::2) 56 data bytes
64 bytes from 2001:16d8:ff00:3a::2: icmp_seq=1 ttl=64 time=0.071 ms
64 bytes from 2001:16d8:ff00:3a::2: icmp_seq=2 ttl=64 time=0.051 ms
64 bytes from 2001:16d8:ff00:3a::2: icmp_seq=3 ttl=64 time=0.052 ms
--- 2001:16d8:ff00:3a::2 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.051/0.058/0.071/0.009 ms
######
Did this work? [Y/n] y
###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:16d8:ff00:3a::1)
### This confirms the reachability of the other side of the tunnel
### If it doesn't reply then check your interface and routing tables
### Don't forget to check your firewall of course
### If the previous test was successful then this could be both
### a firewalling and a routing/interface problem
PING 2001:16d8:ff00:3a::1(2001:16d8:ff00:3a::1) 56 data bytes
64 bytes from 2001:16d8:ff00:3a::1: icmp_seq=1 ttl=64 time=8.35 ms
64 bytes from 2001:16d8:ff00:3a::1: icmp_seq=2 ttl=64 time=7.74 ms
64 bytes from 2001:16d8:ff00:3a::1: icmp_seq=3 ttl=64 time=7.44 ms
--- 2001:16d8:ff00:3a::1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 7.446/7.847/8.353/0.391 ms
######
Did this work? [Y/n] y
###### [7/8] Traceroute6 to the central SixXS machine (noc.sixxs.net)
### This confirms that you can reach the central machine of SixXS
### If that one is reachable you should be able to reach most IPv6 destinations
### Also check http://www.sixxs.net/ipv6calc/ which should show an IPv6 connection
### If your browser supports IPv6 and uses it of course.
traceroute to noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) from 2001:16d8:ff00:3a::2, 30 hops max, 16 byte packets
1 gw-59.sto-01.se.sixxs.net (2001:16d8:ff00:3a::1) 7.826 ms 7.65 ms 7.388 ms
2 sixxs-hy-demarc0.cust.ip6.p80.net (2001:16d8:aaaa:3::2) 7.582 ms 7.679 ms 7.584 ms
3 1890-sixxs.cr0-r87.hy-sto.se.ip6.p80.net (2001:16d8:aaaa:3::1) 7.911 ms 7.867 ms 7.379 ms
4 2001:16d8:1:1352::95 (2001:16d8:1:1352::95) 7.584 ms 7.519 ms 7.397 ms
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
######
Did this work? [Y/n] n
I do not know if this is a problem at the POP or further away, but since I get 4 jumps "out" I have not added more info on local set up (fw tables, routing, etc), as it seems to be working. Let me know if I am wrong.
State change: confirmed
Jeroen Massar on Saturday, 06 October 2012 10:27:43
The state of this ticket has been changed to confirmed
No ipv6 connectivity past 2001:16d8:1:1352::95 as seen from sesto01
Jeroen Massar on Saturday, 06 October 2012 10:28:15
Routes seem to be flapping on and off, not much we can do about (except for the notification which already went out)
State change: resolved
Jeroen Massar on Monday, 08 October 2012 08:15:58
The state of this ticket has been changed to resolved
Posting is only allowed when you are logged in. |