Tunnel Information for T9622:
POP Id : usewr01
IPv6 Local : 2001:4830:1200:3c::2/64
IPv6 Remote : 2001:4830:1200:3c::1/64
Tunnel Type : ayiya
Adminstate : enabled
Userstate : enabled
#######
####### AICCU Quick Connectivity Test
#######
####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.0.10)
### This should return so called 'echo replies'
### If it doesn't then check your firewall settings
### Your local endpoint should always be pingable
### It could also indicate problems with your IPv4 stack
PING 192.168.0.10 (192.168.0.10) 56(84) bytes of data.
64 bytes from 192.168.0.10: icmp_seq=0 ttl=64 time=0.154 ms
64 bytes from 192.168.0.10: icmp_seq=1 ttl=64 time=0.085 ms
64 bytes from 192.168.0.10: icmp_seq=2 ttl=64 time=0.071 ms
--- 192.168.0.10 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 0.071/0.103/0.154/0.037 ms, pipe 2
######
####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (66.55.128.25)
### These pings should reach the PoP and come back to you
### In case there are problems along the route between your
### host and the PoP this could not return replies
### Check your firewall settings if problems occur
PING 66.55.128.25 (66.55.128.25) 56(84) bytes of data.
64 bytes from 66.55.128.25: icmp_seq=0 ttl=55 time=31.1 ms
64 bytes from 66.55.128.25: icmp_seq=1 ttl=55 time=32.4 ms
64 bytes from 66.55.128.25: icmp_seq=2 ttl=55 time=31.5 ms
--- 66.55.128.25 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 31.154/31.714/32.441/0.538 ms, pipe 2
######
####### [3/8] Traceroute to the PoP (66.55.128.25) over IPv4
### This traceroute should reach the PoP
### In case this traceroute fails then you have no connectivity
### to the PoP and this is most probably the problem
traceroute to 66.55.128.25 (66.55.128.25), 30 hops max, 38 byte packets
1 192.168.0.1 (192.168.0.1) 0.669 ms 0.561 ms 0.537 ms
2 10.132.44.1 (10.132.44.1) 9.491 ms 7.323 ms 7.969 ms
3 66.185.90.209 (66.185.90.209) 7.948 ms 8.347 ms 7.453 ms
4 gw01.nmkt.phub.net.cable.rogers.com (66.185.80.109) 11.962 ms 7.754 ms 7.916 ms
5 gw02.mtnk.phub.net.cable.rogers.com (66.185.81.94) 8.961 ms 10.864 ms 9.383 ms
6 igw01.ny8th.phub.net.cable.rogers.com (66.185.81.13) 102.627 ms 248.406 ms 41.204 ms
7 so-0-0-0.ar2.NYC1.gblx.net (64.209.94.53) 27.419 ms 27.696 ms 24.980 ms
8 * * *
9 NLAYER.ge1-4.ar2.EWR2.gblx.net (64.215.25.238) 29.947 ms 32.248 ms 29.493 ms
10 choopa.tge1-2.ar1.ewr1.us.nlayer.net (69.31.95.90) 76.505 ms 121.557 ms 196.640 ms
11 usewr01.sixxs.net (66.55.128.25) 30.411 ms 30.779 ms 30.058 ms
######
###### [4/8] Checking if we can ping IPv6 localhost (::1)
### This confirms if your IPv6 is working
### If ::1 doesn't reply then something is wrong with your IPv6 stack
PING ::1(::1) 56 data bytes
64 bytes from ::1: icmp_seq=0 ttl=64 time=0.101 ms
64 bytes from ::1: icmp_seq=1 ttl=64 time=0.062 ms
64 bytes from ::1: icmp_seq=2 ttl=64 time=0.055 ms
--- ::1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 0.055/0.072/0.101/0.022 ms, pipe 2
######
###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:4830:1200:3c::2)
### This confirms that your tunnel is configured
### If it doesn't reply then check your interface and routing tables
PING 2001:4830:1200:3c::2(2001:4830:1200:3c::2) 56 data bytes
64 bytes from 2001:4830:1200:3c::2: icmp_seq=0 ttl=64 time=0.109 ms
64 bytes from 2001:4830:1200:3c::2: icmp_seq=1 ttl=64 time=0.063 ms
64 bytes from 2001:4830:1200:3c::2: icmp_seq=2 ttl=64 time=0.059 ms
--- 2001:4830:1200:3c::2 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 0.059/0.077/0.109/0.022 ms, pipe 2
######
###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:4830:1200:3c::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 succesful then this could be both
### a firewalling and a routing/interface problem
PING 2001:4830:1200:3c::1(2001:4830:1200:3c::1) 56 data bytes
64 bytes from 2001:4830:1200:3c::1: icmp_seq=0 ttl=64 time=32.7 ms
64 bytes from 2001:4830:1200:3c::1: icmp_seq=1 ttl=64 time=35.2 ms
64 bytes from 2001:4830:1200:3c::1: icmp_seq=2 ttl=64 time=30.3 ms
--- 2001:4830:1200:3c::1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 30.368/32.790/35.275/2.003 ms, pipe 2
######
###### [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:4830:1200:3c::2, 30 hops max, 16 byte packets
1 2001:4830:1200:3c::1 (2001:4830:1200:3c::1) 32.003 ms 31.005 ms 31.868 ms
2 0.ge0-3.cr1.ewr1.us.occaid.net (2001:4830:e2:29::1) 45.979 ms !N 30.413 ms !N 32.001 ms !N
######
###### [8/8] Traceroute6 to (www.kame.net)
### This confirms that you can reach a Japanese IPv6 destination
### If that one is reachable you should be able to reach most IPv6 destinations
### You should also check http://www.kame.net which should display
### a animated kame (turtle), of course only when your browser supports and uses IPv6
traceroute to www.kame.net (2001:200:0:8002:203:47ff:fea5:3085) from 2001:4830:1200:3c::2, 30 hops max, 16 byte packets
1 gw-61.ewr-01.us.sixxs.net (2001:4830:1200:3c::1) 31.486 ms 32.318 ms 31.981 ms
2 0.ge0-3.cr1.ewr1.us.occaid.net (2001:4830:e2:29::1) 31.462 ms !N 31.412 ms !N 31.935 ms !N
######
###### ACCU Quick Connectivity Test (done)
### Either the above all works and gives no problems
### or it shows you where what goes wrong
### Check the SixXS FAQ (http://www.sixxs.net/faq/
### for more information and possible solutions or hints
### Don't forget to check the Forums (http://www.sixxs.net/forum/)
### for a helping hand.
### Passing the output of 'aiccu autotest >aiccu.log' is a good idea.