------------------------------------------------------------------------------>8 Tunnel is 36797 I've received today an email alert message saying that the tunnel is down from the last 2 days. 2011-02-10 01:15:10 Tunnel endpoint 2001:1620:f00:80::2 didn't ping for 2 days -5 2011-02-05 01:16:06 Tunnel endpoint 2001:1620:f00:80::2 pinged for 27 weeks This is totally wrong. Here the ping6 graph to the endppoint of the tunnel http://dl.dropbox.com/u/13333867/ping6_ns_ioda_net_ch-day.png http://dl.dropbox.com/u/13333867/ping6_ns_ioda_net_ch-week.png Where we can see the same holes due to pop down like in it's own stats (look at between 5 and 6 ) Same firewall rules are in action from months ACCEPT icmpv6 2001:1620:f00:80::1/128 ::/0 ipv6-icmp type 128 /* Ping */ A ping6 works ping6 2001:1620:f00:80::2 PING 2001:1620:f00:80::2(2001:1620:f00:80::2) 56 data bytes 64 bytes from 2001:1620:f00:80::2: icmp_seq=1 ttl=64 time=0.045 ms 64 bytes from 2001:1620:f00:80::2: icmp_seq=2 ttl=64 time=0.046 ms ^C --- 2001:1620:f00:80::2 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 999ms rtt min/avg/max/mdev = 0.045/0.045/0.046/0.006 ms yoda:~ # ping6 2001:1620:f00:80::1 PING 2001:1620:f00:80::1(2001:1620:f00:80::1) 56 data bytes 64 bytes from 2001:1620:f00:80::1: icmp_seq=1 ttl=64 time=12.5 ms 64 bytes from 2001:1620:f00:80::1: icmp_seq=2 ttl=64 time=12.5 ms 64 bytes from 2001:1620:f00:80::1: icmp_seq=3 ttl=64 time=12.2 ms ^C --- 2001:1620:f00:80::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 12.274/12.437/12.526/0.147 ms Routing works too traceroute6 2607:ff38:1:81::3 traceroute to 2607:ff38:1:81::3 (2607:ff38:1:81::3), 30 hops max, 40 byte packets using UDP 1 gw-129.zrh-02.ch.sixxs.net (2001:1620:f00:80::1) 12.395 ms 14.715 ms 15.536 ms 2 2001:1620:2005:4::1 (2001:1620:2005:4::1) 17.107 ms 18.793 ms 20.202 ms 3 r1zur1.core.init7.net (2001:1620:2::49) 28.419 ms 27.745 ms 27.148 ms 4 r1fra1.core.init7.net (2001:1620:2::6) 32.680 ms 36.913 ms 18.978 ms 5 ge-0.de-cix.frnkge03.de.bb.gin.ntt.net (2001:7f8::b62:0:1) 19.795 ms 22.443 ms 23.714 ms 6 ae-0.r21.frnkge04.de.bb.gin.ntt.net (2001:728:0:2000::2) 25.777 ms 27.492 ms 28.551 ms 7 as-1.r23.amstnl02.nl.bb.gin.ntt.net (2001:728:0:2000::13d) 39.054 ms 40.168 ms 41.570 ms 8 ae-7.r21.asbnva02.us.bb.gin.ntt.net (2001:418:0:2000::1b1) 134.438 ms 135.979 ms 137.107 ms 9 ae-0.r20.asbnva02.us.bb.gin.ntt.net (2001:418:0:2000::d) 141.704 ms 141.090 ms 140.504 ms 10 as-2.r21.lsanca03.us.bb.gin.ntt.net (2001:418:0:2000::20d) 216.621 ms 220.922 ms 222.741 ms 11 po-2.r00.lsanca03.us.bb.gin.ntt.net (2001:418:0:2000::2b2) 180.282 ms 181.354 ms 182.932 ms 12 2001:418:4000:5000::2 (2001:418:4000:5000::2) 182.308 ms 184.140 ms 185.521 ms 13 2001:1878:d::3 (2001:1878:d::3) 190.120 ms 190.937 ms 192.315 ms 14 2604:0:b:1::3 (2604:0:b:1::3) 203.494 ms 209.334 ms 210.653 ms traceroute -n ns.ioda.net traceroute to ns.ioda.net (2001:41d0:2:2eb9::2), 30 hops max, 40 byte packets using UDP 1 2001:1620:f00:80::1 (2001:1620:f00:80::1) 12.427 ms 14.040 ms 15.561 ms 2 2001:1620:2005:4::1 (2001:1620:2005:4::1) 17.811 ms 18.670 ms 19.669 ms 3 2001:1620:2::49 (2001:1620:2::49) 25.088 ms 24.417 ms 24.820 ms 4 2001:1620:2::6 (2001:1620:2::6) 32.907 ms 38.225 ms 39.378 ms 5 2001:7f8::1935:0:2 (2001:7f8::1935:0:2) 42.495 ms 44.104 ms 45.725 ms 6 2a01:3e0:ff20::39 (2a01:3e0:ff20::39) 47.763 ms 52.742 ms * 7 2a01:3e0:ff80:100::a (2a01:3e0:ff80:100::a) 67.781 ms 69.643 ms 71.016 ms 8 2a01:3e0:ff80:100::15 (2a01:3e0:ff80:100::15) 68.505 ms 73.513 ms 75.152 ms 9 2001:5a0:1900::a (2001:5a0:1900::a) 72.391 ms * * 10 * 2001:41d0::522 (2001:41d0::522) 63.842 ms * 11 2001:41d0::5b2 (2001:41d0::5b2) 68.253 ms * * 12 2001:41d0::803 (2001:41d0::803) 33.452 ms * * 13 2001:41d0:2:2eb9::2 (2001:41d0:2:2eb9::2) 37.759 ms 39.168 ms 40.563 ms So I don't know what's wrong here. Did you change the tunnel monitor pinger address ? Be kind to restore the 5points wrongly deduced. Thanks