I have read and followed the "Reporting Problems" section on the Contact page. I am removing these five pre-filled lines to demonstrate that I really read it. I am providing the full details as requested on the mentioned Contact page. If I do not remove this, then please ignore this message as I didn't read it anyway. ------------------------------------------------------------------------------>8 I have very high packet loss on my ipv6 connectivity. My nic handle is MH5129-RIPE, the tunnel ID is T8212. My IPv4 connectivity is through T-Online DSL Connected via a speedport W700V router, my local endpoint is an openSUSE 10.2 running the latest AICCU. The output of aiccu autotest follows. --- aiccu autotest output --- kotoko:/etc # aiccu autotest sock_getline() : "200 SixXS TIC Service on noc.sixxs.net ready (http://www.sixxs.net)" sock_printf() : "client TIC/draft-00 AICCU/2007.01.15-gui Linux/2.6.18.8-0.13-default" sock_getline() : "200 Client Identity accepted" sock_printf() : "get unixtime" sock_getline() : "200 1254303435" sock_printf() : "username MH5129-RIPE" sock_getline() : "200 Choose your authentication challenge please" sock_printf() : "challenge md5" sock_getline() : "200 f579979ef33e21fe1078e12a15cc8167" sock_printf() : "authenticate md5 2d5bdf18bc99b1130b700d20c249aab7" sock_getline() : "200 Succesfully logged in using md5 as MH5129-RIPE (Mathias Homann) from 2001:7b8:3:4f:202:b3ff:fe46:bec" sock_printf() : "tunnel show T8212" sock_getline() : "201 Showing tunnel information for T8212" sock_getline() : "TunnelId: T8212" sock_getline() : "Type: 6in4-heartbeat" sock_getline() : "IPv6 Endpoint: 2001:6f8:900:5e9::2" sock_getline() : "IPv6 POP: 2001:6f8:900:5e9::1" sock_getline() : "IPv6 PrefixLength: 64" sock_getline() : "Tunnel MTU: 1280" sock_getline() : "Tunnel Name: home tunnel" sock_getline() : "POP Id: deham01" sock_getline() : "IPv4 Endpoint: heartbeat" sock_getline() : "IPv4 POP: 212.224.0.188" sock_getline() : "UserState: enabled" sock_getline() : "AdminState: enabled" sock_getline() : "Password: xxxxxxxxx" sock_getline() : "Heartbeat_Interval: 60" sock_getline() : "202 Done" Succesfully retrieved tunnel information for T8212 sock_printf() : "QUIT See you later alligator" Tunnel Information for T8212: POP Id : deham01 IPv6 Local : 2001:6f8:900:5e9::2/64 IPv6 Remote : 2001:6f8:900:5e9::1/64 Tunnel Type : 6in4-heartbeat Adminstate : enabled Userstate : enabled heartbeat_socket() - IPv4 : 192.168.238.6 [HB] HEARTBEAT TUNNEL 2001:6f8:900:5e9::2 sender 1254303435 276174e843bf6a3a6bb156e977ed61e9 ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.238.6) ### 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.238.6 (192.168.238.6) 56(84) bytes of data. 64 bytes from 192.168.238.6: icmp_seq=1 ttl=64 time=0.033 ms 64 bytes from 192.168.238.6: icmp_seq=2 ttl=64 time=0.025 ms 64 bytes from 192.168.238.6: icmp_seq=3 ttl=64 time=0.023 ms --- 192.168.238.6 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2001ms rtt min/avg/max/mdev = 0.023/0.027/0.033/0.004 ms ###### ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (212.224.0.188) ### 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 212.224.0.188 (212.224.0.188) 56(84) bytes of data. 64 bytes from 212.224.0.188: icmp_seq=1 ttl=56 time=20.9 ms 64 bytes from 212.224.0.188: icmp_seq=2 ttl=56 time=19.4 ms 64 bytes from 212.224.0.188: icmp_seq=3 ttl=56 time=20.1 ms --- 212.224.0.188 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2006ms rtt min/avg/max/mdev = 19.475/20.194/20.964/0.619 ms ###### ####### [3/8] Traceroute to the PoP (212.224.0.188) 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 212.224.0.188 (212.224.0.188), 30 hops max, 40 byte packets 1 celebrimbor.eregion.home (192.168.238.1) 0.303 ms 0.356 ms 0.369 ms 2 217.0.118.160 (217.0.118.160) 7.885 ms 9.230 ms 7.955 ms 3 87.186.248.50 (87.186.248.50) 8.623 ms 7.546 ms 7.541 ms 4 217.239.40.189 (217.239.40.189) 8.090 ms 217.239.40.193 (217.239.40.193) 9.836 ms 10.320 ms 5 217.243.219.82 (217.243.219.82) 9.152 ms 9.009 ms 8.085 ms 6 te0-0-0.gr10.isham.de.easynet.net (87.86.77.65) 19.730 ms 19.747 ms 19.847 ms 7 ge3-7.br2.isham.de.easynet.net (87.86.71.241) 20.146 ms 19.665 ms 19.463 ms 8 ge7-1.cr20.isham.de.easynet.net (212.224.4.89) 19.684 ms 22.516 ms 22.269 ms 9 deham01.sixxs.net (212.224.0.188) 20.553 ms 21.411 ms 20.664 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=1 ttl=64 time=0.029 ms 64 bytes from ::1: icmp_seq=2 ttl=64 time=0.028 ms 64 bytes from ::1: icmp_seq=3 ttl=64 time=0.102 ms --- ::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 0.028/0.053/0.102/0.034 ms ###### ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:6f8:900:5e9::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2001:6f8:900:5e9::2(2001:6f8:900:5e9::2) 56 data bytes 64 bytes from 2001:6f8:900:5e9::2: icmp_seq=1 ttl=64 time=0.032 ms 64 bytes from 2001:6f8:900:5e9::2: icmp_seq=2 ttl=64 time=0.030 ms 64 bytes from 2001:6f8:900:5e9::2: icmp_seq=3 ttl=64 time=0.032 ms --- 2001:6f8:900:5e9::2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 0.030/0.031/0.032/0.004 ms ###### ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:6f8:900:5e9::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:6f8:900:5e9::1(2001:6f8:900:5e9::1) 56 data bytes --- 2001:6f8:900:5e9::1 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2002ms ###### ###### [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, 40 byte packets 1 * gw-1514.ham-01.de.sixxs.net (2001:6f8:900:5e9::1) 22.253 ms * 2 vl101.cr21.isham.de.easynet.net (2001:6f8:800:1003::209:55) 23.369 ms * 20.797 ms 3 * * ge1-3.br2.isham.de.easynet.net (2001:6f8:800:0:1:0:d4e0:49a) 25.604 ms 4 2001:6f8:1:0:87:86:71:240 (2001:6f8:1:0:87:86:71:240) 22.839 ms * * 5 2001:6f8:1:0:86:87:77:64 (2001:6f8:1:0:86:87:77:64) 35.585 ms * * 6 2001:6f8:1:0:87:82:50:236 (2001:6f8:1:0:87:82:50:236) 33.687 ms * 33.013 ms 7 * 2001:838:5:a::2 (2001:838:5:a::2) 38.991 ms * 8 noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) 36.904 ms * 38.033 ms ###### ###### [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, 40 byte packets 1 * gw-1514.ham-01.de.sixxs.net (2001:6f8:900:5e9::1) 25.559 ms 23.487 ms 2 * * vl101.cr21.isham.de.easynet.net (2001:6f8:800:1003::209:55) 25.229 ms 3 * * ge1-3.br2.isham.de.easynet.net (2001:6f8:800:0:1:0:d4e0:49a) 21.974 ms 4 * * * 5 2001:6f8:1:0:86:87:77:64 (2001:6f8:1:0:86:87:77:64) 35.019 ms * * 6 * * * 7 * * * 8 2001:6f8:1:0:87:86:77:120 (2001:6f8:1:0:87:86:77:120) 42.177 ms * * 9 * 2001:6f8:1:0:87:86:77:111 (2001:6f8:1:0:87:86:77:111) 114.068 ms * 10 2001:6f8:1:0:87:86:77:105 (2001:6f8:1:0:87:86:77:105) 112.223 ms * 111.531 ms 11 * * * 12 2001:48b0:bb00:800b::400b (2001:48b0:bb00:800b::400b) 193.746 ms * 194.662 ms 13 * 2001:48b0:bb00:8004::73 (2001:48b0:bb00:8004::73) 293.514 ms * 14 tky001bb11.IIJ.Net (2001:240:bb00:9008::7e) 296.613 ms 297.252 ms 296.505 ms 15 tky001ix04.IIJ.Net (2001:240:bb01:32::15) 296.462 ms 295.898 ms * 16 2001:200:0:fe00::9c4:11 (2001:200:0:fe00::9c4:11) 294.027 ms 293.752 ms 295.408 ms 17 * * 2001:200:0:1802:20c:dbff:fe1f:7200 (2001:200:0:1802:20c:dbff:fe1f:7200) 288.806 ms 18 * ve42.foundry4.nezu.wide.ad.jp (2001:200:0:11::66) 290.671 ms 290.104 ms 19 ve45.foundry2.yagami.wide.ad.jp (2001:200:0:12::74) 293.450 ms * 294.390 ms 20 * * * 21 orange.kame.net (2001:200:0:8002:203:47ff:fea5:3085) 296.840 ms * 295.045 ms ###### ###### 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.