Please read the "Reporting Problems" section on the contact page as noted in the previous ticket you opened.

The state of this ticket has been changed to duplicate

OK, I'll try to submit the ticket again. I did fail to find the 'Reporting Problems' blurb last time, since I went right to the FAQ and not the Contacts page. Perhaps a link to "Reporting Problems" from the FAQ would be an idea ;) Answers in rough order of what's listed on the contacts page. AICCU: Not in use. Handle: DOJ1-SIXXS Tunnel: T11312 Subnet: R4869 Connections/NAT: IPv4 NAT does take place on this box. IPv6 is not routed anywhere else in my network, all IPv6 connections end up on and are dealt with by this box. OS: Debian 4.0 (Etch) Kernel: Linux 2.6.19.5-grsec route -6 -n: Kernel IPv6 routing table Destination Next Hop Flags Metric Ref Use Iface ::1/128 :: U 0 5302 1 lo 2001:770:100:d2::/128 :: U 0 0 2 lo 2001:770:100:d2::2/128 :: U 0 85216 1 lo 2001:770:100:d2::/64 :: U 256 73730 12 sixxs 2001:770:16b:beef::/128 :: U 0 19 2 lo 2001:770:16b:beef::/128 :: U 0 5789 1 lo 2001:770:16b:beef::1/128 :: U 0 167765 1 lo 2001:770:16b:beef::100/128 :: U 0 14 1 lo 2001:770:16b:beef::/64 :: U 256 0 0 eth0 fe80::/128 :: U 0 0 2 lo fe80::/128 :: U 0 0 2 lo fe80::/128 :: U 0 0 2 lo fe80::c0a8:101/128 :: U 0 0 1 lo fe80::d99b:1b09/128 :: U 0 0 1 lo fe80::d99b:1b0a/128 :: U 0 0 1 lo fe80::d99b:1b0b/128 :: U 0 0 1 lo fe80::211:9ff:fec7:1cfc/128 :: U 0 229 1 lo fe80::211:9ff:fec7:1cfd/128 :: U 0 0 1 lo fe80::/64 :: U 256 0 0 eth0 fe80::/64 :: U 256 0 0 eth1 fe80::/64 :: U 256 0 0 sixxs ff00::/8 :: U 256 0 0 eth0 ff00::/8 :: U 256 0 0 eth1 ff00::/8 :: U 256 0 0 sixxs ::/0 :: U 256 30224 1 sixxs ::/0 2001:770:100:d2::1 UG 1024 2701 0 sixxs ip6tables: Chain INPUT (policy DROP) target prot opt source destination ACCEPT 0 ::/0 ::/0 ACCEPT 0 ::/0 ::/0 ACCEPT 0 2001:770:16b:beef::/64 ::/0 ACCEPT tcp ::/0 ::/0 tcp dpt:113 ACCEPT icmpv6 ::/0 ::/0 ACCEPT 0 ::/0 ::/0 state ESTABLISHED ACCEPT tcp ::/0 ::/0 state RELATED tcp dpts:1024:65535 ACCEPT udp ::/0 ::/0 state RELATED udp dpts:1024:65535 ACCEPT 1 ::/0 ::/0 state RELATED Chain FORWARD (policy DROP) target prot opt source destination ACCEPT 0 ::/0 ::/0 ACCEPT tcp ::/0 ::/0 state RELATED,ESTABLISHED ACCEPT udp ::/0 ::/0 state RELATED,ESTABLISHED ACCEPT 1 ::/0 ::/0 state RELATED,ESTABLISHED ACCEPT 0 2001:770:16b:beef::/64 ::/0 ACCEPT 0 ::/0 2001:770:16b:beef::/64 ACCEPT 0 ::/0 ::/0 state ESTABLISHED ACCEPT tcp ::/0 ::/0 state RELATED tcp dpts:1024:65535 ACCEPT udp ::/0 ::/0 state RELATED udp dpts:1024:65535 ACCEPT 1 ::/0 ::/0 state RELATED Chain OUTPUT (policy DROP) target prot opt source destination ACCEPT 0 ::/0 ::/0 ACCEPT 0 ::/0 2001:770:16b:beef::/64 ACCEPT 0 ::/0 ::/0 state ESTABLISHED Traceroute6: traceroute to 2001:770:100:d2::1 (2001:770:100:d2::1) from 2001:770:100:d2::2, 30 hops max, 24 byte packets 1 gw-211.dub-01.ie.sixxs.net (2001:770:100:d2::1) 39.533 ms 33.607 ms 32.403 ms Traceroute4: traceroute to 193.1.31.74 (193.1.31.74), 30 hops max, 52 byte packets 1 gandhi-dsl1.wh.zen.net.uk (62.3.83.5) 14.627 ms 15.453 ms 14.330 ms 2 gandhi-dsl1.wh.zen.net.uk (62.3.83.5) 18.728 ms 15.542 ms 15.421 ms 3 erazmus-ge-0-0-1-3.wh.zen.net.uk (62.3.80.197) 17.965 ms 15.619 ms 13.870 ms 4 lorenz-so-0-1-0-0.te.zen.net.uk (62.3.80.45) 24.445 ms 16.959 ms 17.278 ms 5 lorenz-ge-0-0-0-0.te.zen.net.uk (62.3.80.41) 16.018 ms 16.264 ms 16.731 ms 6 sl-gw22-lon-2-1.sprintlink.net (213.206.158.57) 16.759 ms 15.915 ms 16.234 ms 7 sl-bb22-lon-9-0.sprintlink.net (213.206.128.104) 16.722 ms 16.193 ms 16.723 ms 8 sl-bb20-lon-12-0.sprintlink.net (213.206.128.52) 17.493 ms 16.603 ms 16.640 ms 9 213.206.131.26 (213.206.131.26) 16.257 ms 17.641 ms 17.716 ms 10 HEAnet-2.so-3-0-0.ar1.dub1.gblx.net (208.48.23.54) 26.609 ms 26.099 ms 26.836 ms 11 gige6-1-ar1-cwt.hea.net (193.1.195.177) 26.345 ms 27.557 ms 26.344 ms 12 blanch-sr1-po1.services.hea.net (193.1.195.139) 27.329 ms 27.555 ms 26.336 ms 13 sixxs-tb.hea.net (193.1.31.74) 32.141 ms 26.769 ms 26.144 ms Hopefully I've not missed anything out there. -- Information from previous ticket. 2 days ago, your status pages started reporting that my tunnel wasn't reachable via ping and I received an email about it today. This is not the case, my tunnel is still working and I can ping it myself from the ping6 utility at http://www.berkom.blazing.de/tools/ping.cgi Nothing has changed in the configuration at my end and the machine has not been rebooted since the tunnel was established (meaning there is no chance that I forgot to add something into the config, rebooted and forgot to add it again). Pinging my machine from the above ping6 utility: PING 2001:770:100:d2::2(2001:770:100:d2::2) 56 data bytes 64 bytes from 2001:770:100:d2::2: icmp_seq=1 ttl=52 time=120 ms 64 bytes from 2001:770:100:d2::2: icmp_seq=2 ttl=52 time=119 ms 64 bytes from 2001:770:100:d2::2: icmp_seq=3 ttl=52 time=126 ms 64 bytes from 2001:770:100:d2::2: icmp_seq=4 ttl=52 time=121 ms 64 bytes from 2001:770:100:d2::2: icmp_seq=5 ttl=52 time=117 ms --- 2001:770:100:d2::2 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4030ms rtt min/avg/max/mdev = 117.578/120.949/126.181/2.941 ms Pinging www.kame.net from my machine: # ping6 www.kame.net PING www.kame.net(orange.kame.net) 56 data bytes 64 bytes from orange.kame.net: icmp_seq=1 ttl=51 time=318 ms 64 bytes from orange.kame.net: icmp_seq=2 ttl=51 time=320 ms 64 bytes from orange.kame.net: icmp_seq=3 ttl=51 time=318 ms 64 bytes from orange.kame.net: icmp_seq=4 ttl=51 time=318 ms 64 bytes from orange.kame.net: icmp_seq=5 ttl=51 time=318 ms --- www.kame.net ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 3998ms rtt min/avg/max/mdev = 318.068/318.822/320.344/0.955 ms