Hi, * my tunnel (T54825) stopped working after over a week. * NIC-Handle: MSN16-SIXXS More information: * tunnel is configured using aiccu on pc server (gentoo) in local network (private class-c net) * behind NAT-Router (linux as well, small linksys box with tomato firmware (dnsmasq+iptables)) Info from that gentoo box: lisa ~ # ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: sit0: <NOARP> mtu 1480 qdisc noop state DOWN link/sit 0.0.0.0 brd 0.0.0.0 3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 00:24:8c:5d:61:6c brd ff:ff:ff:ff:ff:ff inet 192.168.1.1/24 brd 192.168.1.255 scope global eth0 inet6 2001:6f8:1ddc::1/64 scope global valid_lft forever preferred_lft forever inet6 fe80::224:8cff:fe5d:616c/64 scope link valid_lft forever preferred_lft forever 19: sixxs: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1280 qdisc pfifo_fast state UNKNOWN qlen 500 link/none inet6 2001:6f8:1c00:3a7::2/64 scope global valid_lft forever preferred_lft forever inet6 fe80::4f8:1c00:3a7:2/64 scope link valid_lft forever preferred_lft forever lisa ~ # ip r 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.1 metric 3 127.0.0.0/8 via 127.0.0.1 dev lo default via 192.168.1.254 dev eth0 metric 3 lisa ~ # ip -6 r 2001:6f8:1c00:3a7::/64 dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 0 2001:6f8:1ddc::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 0 fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 0 fe80::/64 dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 0 default via 2001:6f8:1c00:3a7::1 dev sixxs metric 1024 mtu 1280 advmss 1220 hoplimit 0 iptables is stopped to make sure its not the firewall: lisa ~ # iptables -vnL Chain INPUT (policy ACCEPT 1226 packets, 184K bytes) pkts bytes target prot opt in out source destination Chain FORWARD (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination Chain OUTPUT (policy ACCEPT 1165 packets, 486K bytes) pkts bytes target prot opt in out source destination lisa ~ # ip6tables -vnL Chain INPUT (policy ACCEPT 12 packets, 1248 bytes) pkts bytes target prot opt in out source destination Chain FORWARD (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination Chain OUTPUT (policy ACCEPT 18 packets, 1776 bytes) pkts bytes target prot opt in out source destination lisa ~ # lisa ~ # ntpq -pn remote refid st t when poll reach delay offset jitter ============================================================================== +213.9.73.106 134.34.3.18 2 u 155 1024 377 24.273 1.117 0.228 +85.25.139.186 130.149.17.8 2 u 248 1024 377 28.643 1.267 0.343 -85.31.187.67 131.188.3.222 2 u 730 1024 377 28.283 -2.983 19.730 *46.4.54.78 129.69.1.153 2 u 58 1024 377 28.887 -0.041 0.055 lisa ~ # aiccu autotest Results: lisa ~ # aiccu autotest ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.1.1) ### 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.1.1 (192.168.1.1) 56(84) bytes of data. 64 bytes from 192.168.1.1: icmp_req=1 ttl=64 time=0.089 ms 64 bytes from 192.168.1.1: icmp_req=2 ttl=64 time=0.057 ms 64 bytes from 192.168.1.1: icmp_req=3 ttl=64 time=0.061 ms --- 192.168.1.1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.057/0.069/0.089/0.014 ms ###### ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (212.224.0.189) ### 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.189 (212.224.0.189) 56(84) bytes of data. 64 bytes from 212.224.0.189: icmp_req=1 ttl=57 time=16.7 ms 64 bytes from 212.224.0.189: icmp_req=2 ttl=57 time=16.4 ms 64 bytes from 212.224.0.189: icmp_req=3 ttl=57 time=16.3 ms --- 212.224.0.189 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 16.365/16.526/16.780/0.234 ms ###### ####### [3/8] Traceroute to the PoP (212.224.0.189) 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.189 (212.224.0.189), 30 hops max, 60 byte packets 1 router.schiffbauer.lan (192.168.1.254) 0.708 ms 1.064 ms 2.039 ms 2 lo1.br30.asham.de.hansenet.net (213.191.64.165) 18.438 ms 18.611 ms 19.434 ms 3 ae0-103.cr01.asham.de.hansenet.net (62.109.118.126) 17.846 ms 20.069 ms 20.240 ms 4 ae1-0.pr01.weham.de.hansenet.net (213.191.66.177) 20.439 ms 21.885 ms 29.568 ms 5 workix.ixhbg.de.easynet.net (80.81.203.26) 22.531 ms 22.704 ms 22.920 ms 6 ge2-0-8.gr10.isham.de.easynet.net (87.86.77.126) 23.053 ms 16.055 ms 16.372 ms 7 ge3-8.br2.isham.de.easynet.net (87.86.71.245) 17.447 ms 17.363 ms 16.627 ms 8 ge7-1.cr20.isham.de.easynet.net (212.224.4.89) 17.170 ms 17.484 ms 17.653 ms 9 212.224.0.189 (212.224.0.189) 18.241 ms 19.976 ms 20.515 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.123 ms 64 bytes from ::1: icmp_seq=2 ttl=64 time=0.065 ms 64 bytes from ::1: icmp_seq=3 ttl=64 time=0.077 ms --- ::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.065/0.088/0.123/0.026 ms ###### ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:6f8:1c00:3a7::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2001:6f8:1c00:3a7::2(2001:6f8:1c00:3a7::2) 56 data bytes 64 bytes from 2001:6f8:1c00:3a7::2: icmp_seq=1 ttl=64 time=0.089 ms 64 bytes from 2001:6f8:1c00:3a7::2: icmp_seq=2 ttl=64 time=0.083 ms 64 bytes from 2001:6f8:1c00:3a7::2: icmp_seq=3 ttl=64 time=0.087 ms --- 2001:6f8:1c00:3a7::2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.083/0.086/0.089/0.008 ms ###### ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:6f8:1c00:3a7::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:1c00:3a7::1(2001:6f8:1c00:3a7::1) 56 data bytes --- 2001:6f8:1c00:3a7::1 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2014ms ###### I restarted the router too(to have "clean" internet connection, regarding state tables etc) The setup here did not change i any way since a week. TIA -Marc