Ticket ID: SIXXS #1087917 Ticket Status: Resolved PoP: deham01 - Easynet (Hamburg)
SixXS's tunnelrobot complains about downtime
![]()
User: PV3595-RIPE
Tunnel-ID: 19396 (2001:6f8:900:c40::1/64)
Tunnel-Type: static
If I could trust in the tunnel statistics the PoP deham01 went down on Thursday 14th May at 5 pm. As far as I know the PoP is up again since around Friday 15th May 09:30 CEST.
Yesterday evening, I wondered that I have not earned 5 ISK for tunnel uptime. OK, this may happen if the PoP was down for a long time. I also wondered that the static graphs didn't get updated.
On Sat, 16 May 2009 01:16:19 +0200 (CEST) I've received an email from the tunnelrobot:
This is the tunnelrobot at SixXS, mailing you to inform you that your
tunnel to Easynet has not been replying to pings for a period of time
Here's the information regarding the tunnel:
...
In the log (https://www.sixxs.net/home/log/) I've found this record:
2009-05-16 01:16:19 | Tunnel endpoint 2001:6f8:900:c40::2 didn't ping for 2 days | -5
For me the tunnel seems to be reachable:
Ping from Tunnel-ID 18558:
~ $ ping6 -c 5 2001:6f8:900:c40::2
PING 2001:6f8:900:c40::2(2001:6f8:900:c40::2) 56 data bytes
64 bytes from 2001:6f8:900:c40::2: icmp_seq=1 ttl=54 time=52.0 ms
64 bytes from 2001:6f8:900:c40::2: icmp_seq=2 ttl=54 time=49.7 ms
64 bytes from 2001:6f8:900:c40::2: icmp_seq=3 ttl=54 time=49.7 ms
64 bytes from 2001:6f8:900:c40::2: icmp_seq=4 ttl=54 time=50.2 ms
64 bytes from 2001:6f8:900:c40::2: icmp_seq=5 ttl=54 time=48.5 ms
--- 2001:6f8:900:c40::2 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 48.558/50.087/52.071/1.151 ms
http://stats.eurorings.net/cgi-bin/lookingglass-v6-new.cgi says:
Query: ping
IP address/Prefix: 2001:6f8:900:c40::2
Location: Amsterdam DC2
Timeout: 20 seconds
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001:6F8:900:C40::2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 20/21/24 ms
Iptables on the tunnel endpoint looks like:
el-negro ~ # iptables -vnL
Chain INPUT (policy ACCEPT 55M packets, 27G bytes)
pkts bytes target prot opt in out source destination
41721 2503K REJECT tcp -- * * 91.xxx.yy.zzz 83.aaa.bb.cc tcp dpt:25 reject-with icmp-host-prohibited
20786 1247K REJECT tcp -- * * 65.xx.yyy.zzz 83.aaa.bb.cc tcp dpt:25 reject-with icmp-host-prohibited
1524 91440 REJECT tcp -- * * 61.xx.yyy.zz 83.aaa.bb.cc tcp dpt:25 reject-with icmp-host-prohibited
567 34020 REJECT tcp -- * * 124.xxx.y.z/15 83.aaa.bb.cc/31 multiport dports 80,443 reject-with icmp-host-prohibited
1066 63960 REJECT tcp -- * * 213.xxx.y.zz/29 83.aaa.bb.cc/31 multiport dports 80,443 reject-with icmp-host-prohibited
2287 137K REJECT tcp -- * * 78.xx.yy.zzz 83.aaa.bb.cc/31 multiport dports 80,443 reject-with icmp-host-prohibited
0 0 REJECT tcp -- * * 78.xx.yy.zzz 83.aaa.bb.cc/31 multiport dports 80,443 reject-with icmp-host-prohibited
122 7320 REJECT tcp -- * * 58.xx.y.z/14 83.aaa.bb.cc/31 multiport dports 80,443 reject-with icmp-host-prohibited
3413 205K REJECT tcp -- * * 122.xxx.y.zz 83.aaa.bb.cc tcp dpt:25 reject-with icmp-host-prohibited
329 19740 REJECT tcp -- * * 221.xx.yyy.zzz 83.aaa.bb.cc tcp dpt:25 reject-with icmp-host-prohibited
549 32940 REJECT tcp -- * * 80.xxx.yyy.zzz 83.aaa.bb.cc tcp dpt:25 reject-with icmp-host-prohibited
302 18120 REJECT tcp -- * * 121.xxx.yy.zz 83.aaa.bb.cc tcp dpt:25 reject-with icmp-host-prohibited
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
Chain OUTPUT (policy ACCEPT 42M packets, 18G bytes)
pkts bytes target prot opt in out source destination
el-negro ~ # ip6tables -vnL
Chain INPUT (policy ACCEPT 4194 packets, 437K 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 3322 packets, 520K bytes)
pkts bytes target prot opt in out source destination
el-negro ~ #
Mhh, where is the problem?
State change: resolved
The state of this ticket has been changed to resolved
SixXS's tunnelrobot complains about downtime
Problem resolved.
(Can't fix things while in an Airplane and having no connectivity unfortunately... other "me too comments" all marked hidden. Really, when a ticket is filed we will see it and act upon it ASAP, which is now that I have connectivity again. Request Queue will be resolved tomorrow after I have had sleep again, ISK will be refunded then too)
SixXS's tunnelrobot complains about downtime
![]()
Same PoP same issue again
Received a mail from the tunnelrobot:
Received: from noc.sixxs.net (noc.sixxs.net [IPv6:2001:838:1:1:210:dcff:fe20:7c7c])
by el-negro.edelhost.de (Postfix) with ESMTP id 03AE8A1007C
for <rcpt@domain.tld>; Wed, 16 Feb 2011 01:17:58 +0100 (CET)
Subject: [SixXS] Tunnel Downtime for PV3595-RIPE's 2001:6f8:900:c40::2
el-negro.edelhost.de[2001:6f8:99b:1:25::1] belongs to 2001:6f8:99b::/48, which is routed to: 2001:6f8:900:c40::2
Pings from Tunnel T18558:
~ $ ping6 -c 5 2001:6f8:900:c40::2
PING 2001:6f8:900:c40::2(2001:6f8:900:c40::2) 56 data bytes
64 bytes from 2001:6f8:900:c40::2: icmp_seq=1 ttl=53 time=55.5 ms
64 bytes from 2001:6f8:900:c40::2: icmp_seq=2 ttl=53 time=54.0 ms
64 bytes from 2001:6f8:900:c40::2: icmp_seq=4 ttl=53 time=53.9 ms
64 bytes from 2001:6f8:900:c40::2: icmp_seq=5 ttl=53 time=54.4 ms
--- 2001:6f8:900:c40::2 ping statistics ---
5 packets transmitted, 4 received, 20% packet loss, time 4003ms
rtt min/avg/max/mdev = 53.930/54.493/55.536/0.668 ms
~ $
Pings from http://www.subnetonline.com/pages/ipv6-network-tools/online-ipv6-ping.php:
PING 2001:6f8:900:c40::2(2001:6f8:900:c40::2) 32 data bytes
40 bytes from 2001:6f8:900:c40::2: icmp_seq=0 ttl=53 time=36.7 ms
40 bytes from 2001:6f8:900:c40::2: icmp_seq=1 ttl=53 time=35.1 ms
40 bytes from 2001:6f8:900:c40::2: icmp_seq=2 ttl=53 time=35.0 ms
40 bytes from 2001:6f8:900:c40::2: icmp_seq=3 ttl=53 time=35.8 ms
40 bytes from 2001:6f8:900:c40::2: icmp_seq=4 ttl=53 time=36.1 ms
--- 2001:6f8:900:c40::2 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4002ms
rtt min/avg/max/mdev = 35.088/35.801/36.799/0.669 ms, pipe 2
IPv6 and IPv4 pings from Tunnel T19396 to the PoP:
~ $ ping6 -c5 2001:6f8:900:c40::1
PING 2001:6f8:900:c40::1(2001:6f8:900:c40::1) 56 data bytes
64 bytes from 2001:6f8:900:c40::1: icmp_seq=1 ttl=64 time=16.4 ms
64 bytes from 2001:6f8:900:c40::1: icmp_seq=2 ttl=64 time=17.1 ms
64 bytes from 2001:6f8:900:c40::1: icmp_seq=3 ttl=64 time=16.9 ms
64 bytes from 2001:6f8:900:c40::1: icmp_seq=4 ttl=64 time=17.2 ms
64 bytes from 2001:6f8:900:c40::1: icmp_seq=5 ttl=64 time=18.2 ms
--- 2001:6f8:900:c40::1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4004ms
rtt min/avg/max/mdev = 16.466/17.203/18.210/0.593 ms
~ $ ping -c5 212.224.0.188
PING 212.224.0.188 (212.224.0.188) 56(84) bytes of data.
64 bytes from 212.224.0.188: icmp_req=1 ttl=53 time=16.5 ms
64 bytes from 212.224.0.188: icmp_req=2 ttl=53 time=17.2 ms
64 bytes from 212.224.0.188: icmp_req=3 ttl=53 time=16.8 ms
64 bytes from 212.224.0.188: icmp_req=4 ttl=53 time=16.2 ms
64 bytes from 212.224.0.188: icmp_req=5 ttl=53 time=15.2 ms
--- 212.224.0.188 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 15.216/16.397/17.201/0.687 ms
~ $
Iptables on the tunnel endpoint looks like:
~ # iptables -vnL
Chain INPUT (policy ACCEPT 31M packets, 21G bytes)
pkts bytes target prot opt in out source destination
65363 3922K REJECT tcp -- * * 91.xxx.yy.zzz 83.aaa.bb.cc tcp dpt:25 reject-with icmp-host-prohibited
20786 1247K REJECT tcp -- * * 65.xx.yyy.zzz 83.aaa.bb.cc tcp dpt:25 reject-with icmp-host-prohibited
3711 223K REJECT tcp -- * * 61.xx.yyy.zz 83.aaa.bb.cc tcp dpt:25 reject-with icmp-host-prohibited
127K 7642K REJECT tcp -- * * 124.xxx.y.z/15 83.aaa.bb.cc/31 multiport dports 80,443 reject-with icmp-host-prohibited
78575 4715K REJECT tcp -- * * 122.xxx.y.zz 83.aaa.bb.cc tcp dpt:25 reject-with icmp-host-prohibited
2498 150K REJECT tcp -- * * 221.xx.yyy.zzz 83.aaa.bb.cc tcp dpt:25 reject-with icmp-host-prohibited
2310 139K REJECT tcp -- * * 80.xxx.yyy.zzz 83.aaa.bb.cc tcp dpt:25 reject-with icmp-host-prohibited
790 47400 REJECT tcp -- * * 121.xxx.yy.zz 83.aaa.bb.cc tcp dpt:25 reject-with icmp-host-prohibited
4672 280K REJECT tcp -- * * 79.xxx.yyy.zzz 83.aaa.bb.cc tcp dpt:25 reject-with icmp-host-prohibited
4607 258K REJECT tcp -- * * 152.xx.yyy.zz 83.aaa.bb.cc tcp dpt:25 reject-with icmp-host-prohibited
160K 9628K REJECT tcp -- * * 168.xxx.yyy.zzz 83.aaa.bb.cc tcp dpt:25 reject-with icmp-host-prohibited
783 46980 REJECT tcp -- * * 206.xxx.yyy.zz 83.aaa.bb.cc tcp dpt:25 reject-with icmp-host-prohibited
216 10168 REJECT tcp -- * * 123.xx.yyy.zzz 83.aaa.bb.cc tcp dpt:25 reject-with icmp-host-prohibited
40588 2435K REJECT tcp -- * * 114.xx.y.z/12 83.aaa.bb.cc/31 multiport dports 80,443 reject-with icmp-host-prohibited
120 7200 REJECT tcp -- * * 211.xxx.yyy.zz 83.aaa.bb.cc tcp dpt:25 reject-with icmp-host-prohibited
3350 201K REJECT tcp -- * * 62.xxx.yyy.z 83.aaa.bb.cc tcp dpt:25 reject-with icmp-host-prohibited
741 44460 REJECT tcp -- * * 77.xxx.yyy.zzz 83.aaa.bb.cc tcp dpt:25 reject-with icmp-host-prohibited
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
Chain OUTPUT (policy ACCEPT 22M packets, 5486M bytes)
pkts bytes target prot opt in out source destination
~ # ip6tables -vnL
Chain INPUT (policy ACCEPT 7063K packets, 3888M bytes)
pkts bytes target prot opt in out source destination
15334 9116K ACCEPT tcp * * ::/0 2001:6f8:99b:ffff:fff:ff:ff:fff/128 tcp dpt:25
21 3072 REJECT all * * 2001:da8:fff::/48 2001:6f8:99b::/48 reject-with icmp6-adm-prohibited
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
Chain OUTPUT (policy ACCEPT 5228K packets, 3514M bytes)
pkts bytes target prot opt in out source destination
~ #
Regards,
Pascal
BTW: ISK from last time wasn't refunded until now.
|