SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #1187512
Ticket Status: User

PoP: usqas01 - OCCAID Inc. (Ashburn, Virginia)

Heartbeat not working?
[ve] Shadow Hawkins on Friday, 28 August 2009 18:58:46
Hi, this is my first problem posting, If there is anything wrong with my report, please say so (gently). Tunnel identification: T22206 [2001:4830:1600:1b4::2] Heartbeat. Tunnel was working for several weeks. After changing it to AYIYA and back to Heartbeat, it doesn't work any longer. Debian lenny system. Aiccu installed and tested. AICCU test works correctly up to step 6. I.E. External IPv6 address. IPv6 local addresses correctly assigned, radvd working. Ping6 on 2001:4830:1600:1b4::2correctly sends a packet on the external facing NIC but no answer back from usqas01. Why usqas01 doesn't answer back?
State change: user Locked
[ch] Jeroen Massar SixXS Staff on Friday, 28 August 2009 23:10:16
Message is Locked
The state of this ticket has been changed to user
Heartbeat not working?
[ch] Jeroen Massar SixXS Staff on Friday, 28 August 2009 23:12:16
Please actually read the contact page and provide the requested details. "It does not work" really does not give us any hints on what could be wrong. Providing the AICCU test output would already be a good thing, providing all the information as clearly requested is way better. The PoP is reporting: Endpoint : 201.211.107.169 Last Beat : 2009-08-29 01:26:44 (2589 seconds ago) Thus heartbeats are coming in sometimes, thus better start checking your configuration.
Heartbeat not working?
[ve] Shadow Hawkins on Saturday, 29 August 2009 03:07:32
No Jeroen but "my configuration" is not the source of the problem.
Heartbeat not working?
[ch] Jeroen Massar SixXS Staff on Saturday, 29 August 2009 12:06:22
You must be right then, as you seem to know everything about it. Enjoy!
Heartbeat not working?
[ve] Shadow Hawkins on Saturday, 29 August 2009 15:01:00
Oh, I am enjoining it a lot, it's an excellent learning experience. The point is: how is it working now without any change on my part?
Heartbeat not working?
[ch] Jeroen Massar SixXS Staff on Saturday, 29 August 2009 15:58:22
The point is: how is it working now without any change on my part?
You seem to know all the answers, you tell us. I suggest that you start reading that big orange box and the texts it references.
Heartbeat not working?
[ve] Shadow Hawkins on Saturday, 29 August 2009 19:04:30
Hoping this is what you want: Tunnel Information for T22206: POP Id : usqas01 IPv6 Local : 2001:4830:1600:1b4::2/64 IPv6 Remote : 2001:4830:1600:1b4::1/64 Tunnel Type : 6in4-heartbeat Adminstate : enabled Userstate : enabled ioctl: No buffer space available RTNETLINK answers: File exists RTNETLINK answers: File exists ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (201.211.107.169) ### 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 201.211.107.169 (201.211.107.169) 56(84) bytes of data. 64 bytes from 201.211.107.169: icmp_seq=1 ttl=64 time=0.075 ms 64 bytes from 201.211.107.169: icmp_seq=2 ttl=64 time=0.054 ms 64 bytes from 201.211.107.169: icmp_seq=3 ttl=64 time=0.042 ms --- 201.211.107.169 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.042/0.057/0.075/0.013 ms ###### Did this work? [Y/n] ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (66.117.47.228) ### 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.117.47.228 (66.117.47.228) 56(84) bytes of data. 64 bytes from 66.117.47.228: icmp_seq=1 ttl=48 time=157 ms 64 bytes from 66.117.47.228: icmp_seq=2 ttl=48 time=156 ms 64 bytes from 66.117.47.228: icmp_seq=3 ttl=48 time=156 ms --- 66.117.47.228 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2007ms rtt min/avg/max/mdev = 156.880/157.075/157.390/0.224 ms ###### Did this work? [Y/n] ####### [3/8] Traceroute to the PoP (66.117.47.228) 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.117.47.228 (66.117.47.228), 30 hops max, 60 byte packets 1 201-211-96-1.genericrev.cantv.net (201.211.96.1) 21.168 ms 23.115 ms 25.057 ms 2 172.16.204.1 (172.16.204.1) 24.035 ms 26.394 ms 27.998 ms 3 10.127.65.77 (10.127.65.77) 33.730 ms 35.579 ms 37.670 ms 4 10.127.65.202 (10.127.65.202) 45.892 ms 47.747 ms 48.685 ms 5 POS2-0-0.GW10.MIA4.ALTER.NET (65.208.86.53) 86.859 ms 87.962 ms 89.758 ms 6 0.ge-6-1-0.XL3.MIA4.ALTER.NET (152.63.82.26) 90.691 ms 69.619 ms 71.901 ms 7 0.so-6-0-0.XT1.ATL4.ALTER.NET (152.63.80.37) 89.856 ms 90.593 ms 92.091 ms 8 0.so-6-0-0.BR1.ATL4.ALTER.NET (152.63.86.169) 90.551 ms 85.627 ms 86.224 ms 9 204.255.169.82 (204.255.169.82) 165.051 ms 160.452 ms 161.988 ms 10 atl-core-02.inet.qwest.net (205.171.21.170) 161.983 ms 159.904 ms 160.517 ms 11 * * * 12 65.119.123.198 (65.119.123.198) 163.354 ms 164.271 ms 166.133 ms 13 209.222.144.164 (209.222.144.164) 168.237 ms 169.171 ms 172.189 ms 14 iad0-sixxs.hotnic.net (66.117.47.228) 176.499 ms 176.560 ms 178.045 ms ###### Did this work? [Y/n] ###### [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=1 ttl=64 time=0.067 ms 64 bytes from ::1: icmp_seq=2 ttl=64 time=0.045 ms 64 bytes from ::1: icmp_seq=3 ttl=64 time=0.044 ms --- ::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.044/0.052/0.067/0.010 ms ###### Did this work? [Y/n] ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:4830:1600:1b4::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2001:4830:1600:1b4::2(2001:4830:1600:1b4::2) 56 data bytes 64 bytes from 2001:4830:1600:1b4::2: icmp_seq=1 ttl=64 time=0.071 ms 64 bytes from 2001:4830:1600:1b4::2: icmp_seq=2 ttl=64 time=0.053 ms 64 bytes from 2001:4830:1600:1b4::2: icmp_seq=3 ttl=64 time=0.051 ms --- 2001:4830:1600:1b4::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.010 ms ###### Did this work? [Y/n] ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:4830:1600:1b4::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:1600:1b4::1(2001:4830:1600:1b4::1) 56 data bytes 64 bytes from 2001:4830:1600:1b4::1: icmp_seq=1 ttl=64 time=157 ms 64 bytes from 2001:4830:1600:1b4::1: icmp_seq=2 ttl=64 time=158 ms 64 bytes from 2001:4830:1600:1b4::1: icmp_seq=3 ttl=64 time=158 ms --- 2001:4830:1600:1b4::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2006ms rtt min/avg/max/mdev = 157.730/157.985/158.209/0.499 ms ###### Did this work? [Y/n] ###### [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), 30 hops max, 80 byte packets 1 gw-437.qas-01.us.sixxs.net (2001:4830:1600:1b4::1) 160.233 ms 162.006 ms 165.020 ms 2 sixxs-gw.hotnic.us.occaid.net (2001:4830:e6:7::1) 166.831 ms 169.911 ms 171.764 ms 3 iad0-b0-ge2.hotnic.net (2001:4810:0:100::1) 174.820 ms 178.760 ms 180.606 ms 4 carpathia-gw.hotnic.net (2001:4810::1:4:2) 183.688 ms 185.539 ms 187.644 ms 5 xe-1-1-0-158.was12.ip6.tinet.net (2001:668:0:3::8000:1) 189.503 ms 193.534 ms 195.564 ms 6 xe-4-1-0.was11.ip6.tinet.net (2001:668:0:2::1:1712) 197.456 ms 159.098 ms 159.833 ms 7 so-1-0-0.nyc22.ip6.tinet.net (2001:668:0:2::1:262) 167.864 ms 165.809 ms 167.642 ms 8 so-0-0-0.dub20.ip6.tinet.net (2001:668:0:2::1:422) 250.618 ms 253.446 ms 257.011 ms 9 so-1-0-0.dub10.ip6.tinet.net (2001:668:0:2::1:811) 257.109 ms 260.479 ms 262.249 ms 10 so-2-0-0.man11.ip6.tinet.net (2001:668:0:2::1:8a1) 265.325 ms 267.184 ms 269.268 ms 11 xe-4-2-0.ams10.ip6.tinet.net (2001:668:0:2::1:11a2) 283.728 ms 283.777 ms 284.787 ms 12 ams-ix.ipv6.concepts.nl (2001:7f8:1::a501:2871:1) 289.537 ms 291.386 ms 295.390 ms 13 2001:838:5:a::2 (2001:838:5:a::2) 256.865 ms 256.328 ms 258.035 ms 14 noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) 259.947 ms 259.385 ms 259.878 ms ###### Did this work? [Y/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), 30 hops max, 80 byte packets 1 gw-437.qas-01.us.sixxs.net (2001:4830:1600:1b4::1) 158.146 ms 162.065 ms 164.177 ms 2 sixxs-gw.hotnic.us.occaid.net (2001:4830:e6:7::1) 165.997 ms 169.068 ms 170.891 ms 3 xe-0.equinix.asbnva01.us.bb.gin.ntt.net (2001:504:0:2::2914:1) 173.974 ms 176.063 ms 178.833 ms 4 as-3.r20.snjsca04.us.bb.gin.ntt.net (2001:418:0:2000::23a) 271.792 ms 268.904 ms 273.299 ms 5 as-1.r20.osakjp01.jp.bb.gin.ntt.net (2001:218:0:2000::7e) 416.703 ms as-2.r20.tokyjp01.jp.bb.gin.ntt.net (2001:218:0:2000::ce) 419.463 ms as-1.r20.osakjp01.jp.bb.gin.ntt.net (2001:218:0:2000::7e) 419.338 ms 6 ae-4.r20.tokyjp01.jp.bb.gin.ntt.net (2001:218:0:2000::d9) 420.610 ms po-1.a15.tokyjp01.jp.ra.gin.ntt.net (2001:218:0:6000::10e) 369.307 ms ae-4.r20.tokyjp01.jp.bb.gin.ntt.net (2001:218:0:2000::d9) 361.040 ms 7 ge-8-2.a15.tokyjp01.jp.ra.gin.ntt.net (2001:218:2000:5000::82) 352.959 ms 374.085 ms 372.836 ms 8 ge-8-2.a15.tokyjp01.jp.ra.gin.ntt.net (2001:218:2000:5000::82) 367.132 ms 366.155 ms ve44.foundry6.otemachi.wide.ad.jp (2001:200:0:10::141) 366.829 ms 9 ve42.foundry4.nezu.wide.ad.jp (2001:200:0:11::66) 374.972 ms ve44.foundry6.otemachi.wide.ad.jp (2001:200:0:10::141) 358.900 ms ve42.foundry4.nezu.wide.ad.jp (2001:200:0:11::66) 369.306 ms 10 ve45.foundry2.yagami.wide.ad.jp (2001:200:0:12::74) 370.630 ms 362.220 ms 362.088 ms 11 2001:200:0:4803:212:e2ff:fe28:1ca2 (2001:200:0:4803:212:e2ff:fe28:1ca2) 379.410 ms * * 12 orange.kame.net (2001:200:0:8002:203:47ff:fea5:3085) 381.824 ms 392.248 ms 385.681 ms ###### Did this work? [Y/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. uname -a Linux apolo.iafcg.priv 2.6.26-2-686 #1 SMP Sun Jun 21 04:57:38 UTC 2009 i686 GNU/Linux ifconfig -a eth0 Link encap:Ethernet HWaddr 00:1b:21:0a:20:2a inet addr:192.168.34.1 Bcast:192.168.34.255 Mask:255.255.255.0 inet6 addr: 2001:4830:16c5:304:1::1/64 Scope:Global inet6 addr: fe80::21b:21ff:fe0a:202a/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2410005 errors:0 dropped:0 overruns:0 frame:0 TX packets:4131583 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:194008272 (185.0 MiB) TX bytes:879578645 (838.8 MiB) eth0:0 Link encap:Ethernet HWaddr 00:1b:21:0a:20:2a inet addr:192.168.34.100 Bcast:192.168.34.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 eth1 Link encap:Ethernet HWaddr 00:11:11:b3:9d:b5 inet addr:201.211.107.169 Bcast:201.211.127.255 Mask:255.255.224.0 inet6 addr: fe80::211:11ff:feb3:9db5/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3109102 errors:0 dropped:0 overruns:0 frame:0 TX packets:2027143 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3777991934 (3.5 GiB) TX bytes:162144384 (154.6 MiB) eth1:azt Link encap:Ethernet HWaddr 00:11:11:b3:9d:b5 inet addr:10.0.0.5 Bcast:10.255.255.255 Mask:255.0.0.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:287071 errors:0 dropped:0 overruns:0 frame:0 TX packets:287071 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:723230892 (689.7 MiB) TX bytes:723230892 (689.7 MiB) sit0 Link encap:IPv6-in-IPv4 NOARP MTU:1480 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) teredo Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet6 addr: fe80::ffff:ffff:ffff/64 Scope:Link inet6 addr: 2001:0:53aa:64c:467:5495:362c:9456/32 Scope:Global UP POINTOPOINT RUNNING NOARP MTU:1280 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) ip -6 route ls 2001::/32 dev teredo metric 256 mtu 1280 advmss 1220 hoplimit 0 2001:4830:16c5:304::/64 dev eth0 metric 256 mtu 1500 advmss 1440 hoplimit 0 fe80::/64 dev eth0 metric 256 mtu 1500 advmss 1440 hoplimit 0 fe80::/64 dev eth1 metric 256 mtu 1500 advmss 1440 hoplimit 0 fe80::/64 dev teredo metric 256 mtu 1280 advmss 1220 hoplimit 0 default dev teredo metric 1029 mtu 1280 advmss 1220 hoplimit 0 traceroute 66.117.47.228 traceroute to 66.117.47.228 (66.117.47.228), 30 hops max, 60 byte packets 1 201-211-96-1.genericrev.cantv.net (201.211.96.1) 22.565 ms 24.580 ms 26.409 ms 2 172.16.204.1 (172.16.204.1) 25.392 ms 27.646 ms 27.700 ms 3 10.127.65.77 (10.127.65.77) 33.921 ms 36.322 ms 40.954 ms 4 10.127.65.202 (10.127.65.202) 46.099 ms 47.296 ms 49.151 ms 5 POS2-0-0.GW10.MIA4.ALTER.NET (65.208.86.53) 85.992 ms 88.079 ms 89.947 ms 6 0.ge-6-1-0.XL3.MIA4.ALTER.NET (152.63.82.26) 90.921 ms 69.400 ms 70.666 ms 7 0.so-6-0-0.XT1.ATL4.ALTER.NET (152.63.80.37) 88.713 ms 89.587 ms 89.533 ms 8 0.so-6-0-0.BR1.ATL4.ALTER.NET (152.63.86.169) 90.360 ms 85.933 ms 85.229 ms 9 204.255.169.82 (204.255.169.82) 163.159 ms 159.087 ms 161.776 ms 10 atl-core-02.inet.qwest.net (205.171.21.170) 161.706 ms 159.402 ms 160.868 ms 11 * * * 12 65.119.123.198 (65.119.123.198) 157.712 ms 155.631 ms 157.189 ms 13 209.222.144.164 (209.222.144.164) 156.377 ms 158.510 ms 158.000 ms 14 iad0-sixxs.hotnic.net (66.117.47.228) 158.690 ms 153.548 ms 155.332 ms traceroute -6 2001:4830:e6:7::2 traceroute to 2001:4830:e6:7::2 (2001:4830:e6:7::2), 30 hops max, 80 byte packets 1 teredo.ameri.ca (2001:418:0:7000::6) 775.960 ms 775.811 ms 775.787 ms 2 fa-6-5.r03.stngva01.us.bb.gin.ntt.net (2001:418:0:5000::41) 779.700 ms 779.690 ms 779.673 ms 3 xe-1-2.r01.stngva01.us.bb.gin.ntt.net (2001:418:0:2000::101) 760.679 ms 760.668 ms 760.619 ms 4 xe-1-3-0.r21.asbnva01.us.bb.gin.ntt.net (2001:418:0:2000::1e5) 753.510 ms 753.511 ms 753.495 ms 5 sixxs-asbnva-gw.customer.occaid.net (2001:4830:e6:7::2) 105.984 ms 101.192 ms 103.994 ms Clock: ntpq -pn remote refid st t when poll reach delay offset jitter ============================================================================== *146.164.48.5 .GPS. 1 u 110 1024 377 191.030 4.550 0.223 +200.55.63.254 200.160.0.8 3 u 888 1024 373 206.468 -11.784 0.467 +190.3.107.187 200.10.140.1 3 u 709 1024 377 287.859 -34.565 3.619 200.11.116.1 146.164.48.5 2 u 728 1024 377 230.462 -64.951 49.059 192.168.34.255 .BCST. 16 u - 64 0 0.000 0.000 0.001
Heartbeat not working?
[ch] Jeroen Massar SixXS Staff on Sunday, 30 August 2009 13:27:53
It is always good to see that 'I read the FAQ' indeed means that you are routing your packets over some other place. Teredo definitely is not the PoP.
Heartbeat not working?
[ve] Shadow Hawkins on Sunday, 30 August 2009 16:28:04
Hmm, Yes, Looks better now? uname -a Linux apolo.iafcg.priv 2.6.26-2-686 #1 SMP Sun Jun 21 04:57:38 UTC 2009 i686 GNU/Linux aiccu test aiccu test Tunnel Information for T22206: POP Id : usqas01 IPv6 Local : 2001:4830:1600:1b4::2/64 IPv6 Remote : 2001:4830:1600:1b4::1/64 Tunnel Type : 6in4-heartbeat Adminstate : enabled Userstate : enabled ioctl: No buffer space available RTNETLINK answers: File exists RTNETLINK answers: File exists ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (201.211.107.169) ### 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 201.211.107.169 (201.211.107.169) 56(84) bytes of data. 64 bytes from 201.211.107.169: icmp_seq=1 ttl=64 time=0.084 ms 64 bytes from 201.211.107.169: icmp_seq=2 ttl=64 time=0.052 ms 64 bytes from 201.211.107.169: icmp_seq=3 ttl=64 time=0.049 ms --- 201.211.107.169 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.049/0.061/0.084/0.018 ms ###### Did this work? [Y/n] y ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (66.117.47.228) ### 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.117.47.228 (66.117.47.228) 56(84) bytes of data. 64 bytes from 66.117.47.228: icmp_seq=1 ttl=51 time=151 ms 64 bytes from 66.117.47.228: icmp_seq=2 ttl=51 time=149 ms 64 bytes from 66.117.47.228: icmp_seq=3 ttl=51 time=154 ms --- 66.117.47.228 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2004ms rtt min/avg/max/mdev = 149.256/151.729/154.122/2.037 ms ###### Did this work? [Y/n] ####### [3/8] Traceroute to the PoP (66.117.47.228) 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.117.47.228 (66.117.47.228), 30 hops max, 60 byte packets 1 201-211-96-1.genericrev.cantv.net (201.211.96.1) 23.154 ms 26.519 ms 28.387 ms 2 172.16.204.1 (172.16.204.1) 25.237 ms 26.495 ms 28.388 ms 3 10.127.65.77 (10.127.65.77) 34.973 ms 35.738 ms 37.672 ms 4 10.127.65.202 (10.127.65.202) 45.896 ms 47.748 ms 49.583 ms 5 POS2-0-0.GW10.MIA4.ALTER.NET (65.208.86.53) 86.719 ms 87.796 ms 89.732 ms 6 0.ge-6-1-0.XL3.MIA4.ALTER.NET (152.63.82.26) 90.857 ms 64.970 ms 65.741 ms 7 0.so-6-0-0.XT1.ATL4.ALTER.NET (152.63.80.37) 84.619 ms 86.627 ms 89.113 ms 8 0.so-6-0-0.BR1.ATL4.ALTER.NET (152.63.86.169) 89.166 ms 90.409 ms 91.317 ms 9 204.255.169.82 (204.255.169.82) 173.427 ms 175.277 ms 177.378 ms 10 atl-core-02.inet.qwest.net (205.171.21.170) 178.322 ms 159.886 ms 161.719 ms 11 * * * 12 65.119.123.198 (65.119.123.198) 156.727 ms 158.540 ms 160.699 ms 13 209.222.144.164 (209.222.144.164) 163.425 ms 164.664 ms 166.485 ms 14 iad0-sixxs.hotnic.net (66.117.47.228) 167.360 ms 171.987 ms 171.876 ms ###### Did this work? [Y/n] ###### [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=1 ttl=64 time=0.066 ms 64 bytes from ::1: icmp_seq=2 ttl=64 time=0.050 ms 64 bytes from ::1: icmp_seq=3 ttl=64 time=0.044 ms --- ::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.044/0.053/0.066/0.011 ms ###### Did this work? [Y/n] ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:4830:1600:1b4::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2001:4830:1600:1b4::2(2001:4830:1600:1b4::2) 56 data bytes 64 bytes from 2001:4830:1600:1b4::2: icmp_seq=1 ttl=64 time=0.069 ms 64 bytes from 2001:4830:1600:1b4::2: icmp_seq=2 ttl=64 time=0.050 ms 64 bytes from 2001:4830:1600:1b4::2: icmp_seq=3 ttl=64 time=0.054 ms --- 2001:4830:1600:1b4::2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.050/0.057/0.069/0.012 ms ###### Did this work? [Y/n] ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:4830:1600:1b4::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:1600:1b4::1(2001:4830:1600:1b4::1) 56 data bytes 64 bytes from 2001:4830:1600:1b4::1: icmp_seq=1 ttl=64 time=153 ms 64 bytes from 2001:4830:1600:1b4::1: icmp_seq=2 ttl=64 time=153 ms 64 bytes from 2001:4830:1600:1b4::1: icmp_seq=3 ttl=64 time=153 ms --- 2001:4830:1600:1b4::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2007ms rtt min/avg/max/mdev = 153.318/153.444/153.679/0.166 ms ###### Did this work? [Y/n] ###### [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), 30 hops max, 80 byte packets 1 gw-437.qas-01.us.sixxs.net (2001:4830:1600:1b4::1) 153.501 ms 157.399 ms 159.482 ms 2 sixxs-gw.hotnic.us.occaid.net (2001:4830:e6:7::1) 162.305 ms 164.417 ms 168.343 ms 3 iad0-b0-ge2.hotnic.net (2001:4810:0:100::1) 170.258 ms 172.052 ms 176.048 ms 4 carpathia-gw.hotnic.net (2001:4810::1:4:2) 178.183 ms 182.159 ms 184.596 ms 5 xe-1-1-0-158.was12.ip6.tinet.net (2001:668:0:3::8000:1) 184.651 ms 187.927 ms 190.972 ms 6 xe-4-1-0.was11.ip6.tinet.net (2001:668:0:2::1:1712) 194.729 ms 153.283 ms 153.930 ms 7 so-1-0-0.nyc22.ip6.tinet.net (2001:668:0:2::1:262) 160.532 ms 161.439 ms 163.839 ms 8 so-0-0-0.dub20.ip6.tinet.net (2001:668:0:2::1:422) 243.878 ms 241.576 ms 243.463 ms 9 so-1-0-0.dub10.ip6.tinet.net (2001:668:0:2::1:811) 246.364 ms * 251.273 ms 10 so-2-0-0.man11.ip6.tinet.net (2001:668:0:2::1:8a1) 253.336 ms 256.122 ms 258.284 ms 11 xe-4-2-0.ams10.ip6.tinet.net (2001:668:0:2::1:11a2) 269.124 ms 272.122 ms 275.231 ms 12 ams-ix.ipv6.concepts.nl (2001:7f8:1::a501:2871:1) 277.979 ms 281.012 ms 282.899 ms 13 2001:838:5:a::2 (2001:838:5:a::2) 288.028 ms 289.896 ms 292.893 ms 14 noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) 258.950 ms 256.593 ms 258.540 ms ###### Did this work? [Y/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), 30 hops max, 80 byte packets 1 gw-437.qas-01.us.sixxs.net (2001:4830:1600:1b4::1) 153.452 ms 157.344 ms 159.238 ms 2 sixxs-gw.hotnic.us.occaid.net (2001:4830:e6:7::1) 161.790 ms 165.199 ms 166.153 ms 3 xe-0.equinix.asbnva01.us.bb.gin.ntt.net (2001:504:0:2::2914:1) 171.684 ms 171.754 ms 175.102 ms 4 as-3.r20.snjsca04.us.bb.gin.ntt.net (2001:418:0:2000::23a) 273.063 ms 277.936 ms 274.878 ms 5 as-1.r20.osakjp01.jp.bb.gin.ntt.net (2001:218:0:2000::7e) 393.394 ms 394.962 ms as-2.r20.tokyjp01.jp.bb.gin.ntt.net (2001:218:0:2000::ce) 393.447 ms 6 po-1.a15.tokyjp01.jp.ra.gin.ntt.net (2001:218:0:6000::10e) 407.653 ms 364.062 ms ae-4.r20.tokyjp01.jp.bb.gin.ntt.net (2001:218:0:2000::d9) 356.750 ms 7 po-1.a15.tokyjp01.jp.ra.gin.ntt.net (2001:218:0:6000::10e) 361.948 ms 450.867 ms 449.780 ms 8 ve44.foundry6.otemachi.wide.ad.jp (2001:200:0:10::141) 441.965 ms 369.331 ms 358.969 ms 9 ve44.foundry6.otemachi.wide.ad.jp (2001:200:0:10::141) 361.723 ms ve42.foundry4.nezu.wide.ad.jp (2001:200:0:11::66) 368.782 ms ve44.foundry6.otemachi.wide.ad.jp (2001:200:0:10::141) 365.666 ms 10 ve42.foundry4.nezu.wide.ad.jp (2001:200:0:11::66) 370.640 ms 371.715 ms 374.559 ms 11 ve45.foundry2.yagami.wide.ad.jp (2001:200:0:12::74) 395.199 ms 2001:200:0:4803:212:e2ff:fe28:1ca2 (2001:200:0:4803:212:e2ff:fe28:1ca2) 399.561 ms ve45.foundry2.yagami.wide.ad.jp (2001:200:0:12::74) 395.215 ms 12 orange.kame.net (2001:200:0:8002:203:47ff:fea5:3085) 402.204 ms 402.262 ms 404.542 ms ###### ip -6 route ls 2001:4830:1600:1b4::/64 via :: dev sixxs metric 256 mtu 1280 advmss 1220 hoplimit 0 2001:4830:16c5:304::/64 dev eth0 metric 256 mtu 1500 advmss 1440 hoplimit 0 fe80::/64 dev eth0 metric 256 mtu 1500 advmss 1440 hoplimit 0 fe80::/64 dev eth1 metric 256 mtu 1500 advmss 1440 hoplimit 0 fe80::/64 via :: dev sixxs metric 256 mtu 1280 advmss 1220 hoplimit 0 default via 2001:4830:1600:1b4::1 dev sixxs metric 1024 mtu 1280 advmss 1220 hoplimit 0 traceroute -4 usqas01.sixxs.net traceroute to usqas01.sixxs.net (66.117.47.228), 30 hops max, 60 byte packets 1 201-211-96-1.genericrev.cantv.net (201.211.96.1) 20.164 ms 23.141 ms 26.293 ms 2 172.16.204.1 (172.16.204.1) 26.351 ms 26.410 ms 27.988 ms 3 10.127.65.77 (10.127.65.77) 32.753 ms 34.847 ms 36.726 ms 4 10.127.65.202 (10.127.65.202) 44.983 ms 46.792 ms 48.898 ms 5 POS2-0-0.GW10.MIA4.ALTER.NET (65.208.86.53) 85.807 ms 87.092 ms 88.914 ms 6 0.ge-6-1-0.XL3.MIA4.ALTER.NET (152.63.82.26) 89.712 ms 72.484 ms 70.885 ms 7 0.so-6-0-0.XT1.ATL4.ALTER.NET (152.63.80.37) 87.851 ms 88.549 ms 90.565 ms 8 0.so-6-0-0.BR1.ATL4.ALTER.NET (152.63.86.169) 89.504 ms 86.809 ms 86.976 ms 9 204.255.169.82 (204.255.169.82) 166.214 ms 160.485 ms 161.042 ms 10 atl-core-02.inet.qwest.net (205.171.21.170) 160.856 ms 160.603 ms 160.740 ms 11 * * * 12 65.119.123.198 (65.119.123.198) 157.053 ms 148.296 ms 149.690 ms 13 209.222.144.164 (209.222.144.164) 151.552 ms 152.848 ms 153.017 ms 14 iad0-sixxs.hotnic.net (66.117.47.228) 152.987 ms 150.540 ms 149.884 ms traceroute -6 usqas01.sixxs.net traceroute to usqas01.sixxs.net (2001:4830:e6:7::2), 30 hops max, 80 byte packets 1 sixxs-asbnva-gw.customer.occaid.net (2001:4830:e6:7::2) 153.361 ms 156.385 ms 159.406 ms ping6 -c5 -A usqas01.sixxs.net PING usqas01.sixxs.net(sixxs-asbnva-gw.customer.occaid.net) 56 data bytes 64 bytes from sixxs-asbnva-gw.customer.occaid.net: icmp_seq=1 ttl=64 time=153 ms 64 bytes from sixxs-asbnva-gw.customer.occaid.net: icmp_seq=2 ttl=64 time=152 ms 64 bytes from sixxs-asbnva-gw.customer.occaid.net: icmp_seq=3 ttl=64 time=152 ms 64 bytes from sixxs-asbnva-gw.customer.occaid.net: icmp_seq=4 ttl=64 time=153 ms 64 bytes from sixxs-asbnva-gw.customer.occaid.net: icmp_seq=5 ttl=64 time=153 ms ifconfig -a eth0 Link encap:Ethernet HWaddr 00:1b:21:0a:20:2a inet addr:192.168.34.1 Bcast:192.168.34.255 Mask:255.255.255.0 inet6 addr: 2001:4830:16c5:304:1::1/64 Scope:Global inet6 addr: fe80::21b:21ff:fe0a:202a/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3089409 errors:0 dropped:0 overruns:0 frame:0 TX packets:5341498 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:258198731 (246.2 MiB) TX bytes:2152716980 (2.0 GiB) eth0:0 Link encap:Ethernet HWaddr 00:1b:21:0a:20:2a inet addr:192.168.34.100 Bcast:192.168.34.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 eth1 Link encap:Ethernet HWaddr 00:11:11:b3:9d:b5 inet addr:201.211.107.169 Bcast:201.211.127.255 Mask:255.255.224.0 inet6 addr: fe80::211:11ff:feb3:9db5/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4727253 errors:0 dropped:0 overruns:0 frame:0 TX packets:3132525 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1317026181 (1.2 GiB) TX bytes:257687917 (245.7 MiB) eth1:azt Link encap:Ethernet HWaddr 00:11:11:b3:9d:b5 inet addr:10.0.0.5 Bcast:10.255.255.255 Mask:255.0.0.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:314511 errors:0 dropped:0 overruns:0 frame:0 TX packets:314511 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:751675455 (716.8 MiB) TX bytes:751675455 (716.8 MiB) sit0 Link encap:IPv6-in-IPv4 NOARP MTU:1480 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) sixxs Link encap:IPv6-in-IPv4 inet6 addr: 2001:4830:1600:1b4::2/64 Scope:Global inet6 addr: fe80::c9d3:6ba9/64 Scope:Link inet6 addr: fe80::c0a8:2264/64 Scope:Link inet6 addr: fe80::a00:5/64 Scope:Link inet6 addr: fe80::c0a8:2201/64 Scope:Link UP POINTOPOINT RUNNING NOARP MTU:1280 Metric:1 RX packets:3525 errors:0 dropped:0 overruns:0 frame:0 TX packets:3617 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1927183 (1.8 MiB) TX bytes:574555 (561.0 KiB) ntpq -pn remote refid st t when poll reach delay offset jitter ============================================================================== *146.164.48.5 .GPS. 1 u 996 1024 377 191.494 15.480 0.973 +200.55.63.254 200.160.0.8 3 u 738 1024 75 207.316 -0.244 1.823 +190.3.107.187 200.10.140.1 3 u 587 1024 377 289.790 -10.526 0.284 200.11.116.1 146.164.48.5 2 u 588 1024 377 229.859 -54.343 0.330 192.168.34.255 .BCST. 16 u - 64 0 0.000 0.000 0.001

Please note Posting is only allowed when you are logged in.
Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker