Hi, I am having trouble with my tunnel #T11676. According to AICCU, the tunnel comes up, but I can get no traffic to flow over it. I have thought this was a problem with my gateway router, but have recently replaced the router, and still get the problem. I thus installed AICCU on a machine on a different network, with a different OS, and still get exactly the same issue. I also changed the tunnel type to AYIYA to see if this would help, but it has not. In both cases the local enpoint is behind NAT, but with no firewall interfering (i.e in a DMZ zone.). aiccu autotest supplied below. Any pointers will be much appreciated. Kind Regards Anthony Metcalf aiccu autotest Unknown configuration statement on line 78 of /etc/aiccu.conf: "local_ipv4_overrid" 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-console-linux Linux/2.6.29.2" sock_getline() : "200 Client Identity accepted" sock_printf() : "get unixtime" sock_getline() : "200 1273143197" sock_printf() : "starttls" sock_getline() : "400 This service is not SSL enabled (yet)" TIC Server does not support TLS but TLS is not required, continuing sock_printf() : "username AM9427-RIPE" sock_getline() : "200 AM9427-RIPE choose your authentication challenge please" sock_printf() : "challenge md5" sock_getline() : "200 **" sock_printf() : "authenticate md5 **" sock_getline() : "200 Succesfully logged in using md5 as AM9427-RIPE (Anthony Metcalf)" sock_printf() : "tunnel show T11676" sock_getline() : "201 Showing tunnel information for T11676" sock_getline() : "TunnelId: T11676" sock_getline() : "Type: ayiya" sock_getline() : "IPv6 Endpoint: 2001:770:100:e7::2" sock_getline() : "IPv6 POP: 2001:770:100:e7::1" sock_getline() : "IPv6 PrefixLength: 64" sock_getline() : "Tunnel MTU: 1280" sock_getline() : "Tunnel Name: My First Tunnel" sock_getline() : "POP Id: iedub01" sock_getline() : "IPv4 Endpoint: ayiya" sock_getline() : "IPv4 POP: 193.1.31.74" sock_getline() : "UserState: enabled" sock_getline() : "AdminState: enabled" sock_getline() : "Password: **" sock_getline() : "Heartbeat_Interval: 60" sock_getline() : "202 Done" Succesfully retrieved tunnel information for T11676 sock_printf() : "QUIT Zij die gaan, groeten u" Tunnel Information for T11676: POP Id : iedub01 IPv6 Local : 2001:770:100:e7::2/64 IPv6 Remote : 2001:770:100:e7::1/64 Tunnel Type : ayiya Adminstate : enabled Userstate : enabled [AYIYA-start] : Anything in Anything (draft-02) [AYIYA-tun->tundev] : (Socket to TUN) started heartbeat_socket() - IPv4 : 10.1.1.10 ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (10.1.1.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 10.1.1.10 (10.1.1.10) 56(84) bytes of data. 64 bytes from 10.1.1.10: icmp_seq=1 ttl=64 time=0.027 ms 64 bytes from 10.1.1.10: icmp_seq=2 ttl=64 time=0.026 ms 64 bytes from 10.1.1.10: icmp_seq=3 ttl=64 time=0.026 ms --- 10.1.1.10 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.026/0.026/0.027/0.004 ms ###### ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (193.1.31.74) ### 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 193.1.31.74 (193.1.31.74) 56(84) bytes of data. 64 bytes from 193.1.31.74: icmp_seq=1 ttl=55 time=20.8 ms 64 bytes from 193.1.31.74: icmp_seq=2 ttl=55 time=19.1 ms 64 bytes from 193.1.31.74: icmp_seq=3 ttl=55 time=19.7 ms --- 193.1.31.74 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 19.143/19.910/20.825/0.694 ms ###### ####### [3/8] Traceroute to the PoP (193.1.31.74) 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 193.1.31.74 (193.1.31.74), 30 hops max, 40 byte packets 1 10.1.1.1 (10.1.1.1) 1.014 ms 1.068 ms 2.650 ms 2 10.90.24.1 (10.90.24.1) 9.099 ms 9.306 ms 12.048 ms 3 oldh-cam-1a-ge96.network.virginmedia.net (80.5.164.57) 14.682 ms 14.956 ms 15.164 ms 4 manc-core-1a-ae2-0.network.virginmedia.net (195.182.180.37) 17.099 ms 17.350 ms 17.585 ms 5 manc-bb-1a-as0-0.network.virginmedia.net (213.105.175.1) 15.490 ms 15.854 ms 15.685 ms 6 brnt-bb-1b-ae1-0.network.virginmedia.net (212.43.163.86) 21.667 ms 14.265 ms 14.332 ms 7 telc-ic-1-as0-0.network.virginmedia.net (62.253.185.74) 15.880 ms 16.175 ms 15.585 ms 8 ldn-b2-link.telia.net (213.248.100.97) 15.225 ms 19.048 ms 19.593 ms 9 ldn-bb1-link.telia.net (80.91.249.171) 19.903 ms ldn-bb1-link.telia.net (80.91.250.242) 19.655 ms ldn-bb1-link.telia.net (80.91.249.171) 20.416 ms 10 dln-b3-link.telia.net (80.91.249.134) 34.282 ms 34.451 ms 34.344 ms 11 heanet-ic-126792-dln-b3.c.telia.net (213.248.88.10) 33.195 ms 33.617 ms 33.450 ms 12 te5-1-blanch-sr1.services.hea.net (193.1.236.2) 21.399 ms 25.349 ms 25.414 ms 13 sixxs-tb.hea.net (193.1.31.74) 23.899 ms 23.866 ms 26.980 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.030 ms 64 bytes from ::1: icmp_seq=2 ttl=64 time=0.011 ms 64 bytes from ::1: icmp_seq=3 ttl=64 time=0.010 ms --- ::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.010/0.017/0.030/0.009 ms ###### ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:770:100:e7::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2001:770:100:e7::2(2001:770:100:e7::2) 56 data bytes 64 bytes from 2001:770:100:e7::2: icmp_seq=1 ttl=64 time=0.029 ms 64 bytes from 2001:770:100:e7::2: icmp_seq=2 ttl=64 time=0.011 ms 64 bytes from 2001:770:100:e7::2: icmp_seq=3 ttl=64 time=0.012 ms --- 2001:770:100:e7::2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.011/0.017/0.029/0.008 ms ###### ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:770:100:e7::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:770:100:e7::1(2001:770:100:e7::1) 56 data bytes --- 2001:770:100:e7::1 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2016ms ###### ###### [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:770:100:e7::2, 30 hops max, 16 byte packets 1 * * * 2 * * * 3 * *^C ###### ###### [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:770:100:e7::2, 30 hops max, 16 byte packets ^C ###### ###### 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.