|
lost 5 credits
![[it]](/s/countries/it.gif) Carmen Sandiego on Thursday, 20 January 2005 23:13:17
Hi,
In my log i found this message :
2005-01-20 01:15:11 Tunnel endpoint 2001:1418:100:8a::2 didn't ping for 2 days
Anyway, I don't understend why i get this error, since my box is working correctly and didn't go down. And last week I got some credits, so i don't think there is a problem in the configuration of the box. I would like to know if there is a possibility to get those credits back in any way.
Thanks
lost 5 credits
Carmen Sandiego on Thursday, 20 January 2005 23:26:49
another think , if i ping6 my tunnel from another box , this is result :
PING 2001:1418:100:8a::2 (2001:1418:100:8a::2): 56 data bytes
64 bytes from cl-139.trn-01.it.sixxs.net: icmp_seq=0 ttl=51 time=231.072 ms
64 bytes from cl-139.trn-01.it.sixxs.net: icmp_seq=6 ttl=51 time=233.081 ms
64 bytes from cl-139.trn-01.it.sixxs.net: icmp_seq=7 ttl=51 time=245.007 ms
64 bytes from cl-139.trn-01.it.sixxs.net: icmp_seq=8 ttl=51 time=244.335 ms
64 bytes from cl-139.trn-01.it.sixxs.net: icmp_seq=9 ttl=51 time=246.679 ms
64 bytes from cl-139.trn-01.it.sixxs.net: icmp_seq=11 ttl=51 time=225.006 ms
64 bytes from cl-139.trn-01.it.sixxs.net: icmp_seq=12 ttl=51 time=230.799 ms
64 bytes from cl-139.trn-01.it.sixxs.net: icmp_seq=13 ttl=51 time=229.005 ms
64 bytes from cl-139.trn-01.it.sixxs.net: icmp_seq=14 ttl=51 time=221.366 ms
64 bytes from cl-139.trn-01.it.sixxs.net: icmp_seq=15 ttl=51 time=248.237 ms
--- 2001:1418:100:8a::2 ping statistics ---
34 packets transmitted, 28 packets received, 17% packet loss
round-trip min/avg/max/stddev = 220.445/232.687/248.237/7.102 ms
:/
lost 5 credits
![[fi]](/s/countries/fi.gif) Shadow Hawkins on Friday, 21 January 2005 06:47:06
Can you ping pop end of the tunnel?
lost 5 credits
Carmen Sandiego on Friday, 21 January 2005 11:08:25
Yes :| . My box is ok .. i don't undestand why sixxs addebit me 5 credits .
debian:~# ping6 2001:1418:100::1
PING 2001:1418:100::1(2001:1418:100::1) 56 data bytes
64 bytes from 2001:1418:100::1: icmp_seq=1 ttl=64 time=44.1 ms
64 bytes from 2001:1418:100::1: icmp_seq=2 ttl=64 time=44.2 ms
64 bytes from 2001:1418:100::1: icmp_seq=3 ttl=64 time=43.6 ms
64 bytes from 2001:1418:100::1: icmp_seq=4 ttl=64 time=43.4 ms
64 bytes from 2001:1418:100::1: icmp_seq=5 ttl=64 time=44.8 ms
64 bytes from 2001:1418:100::1: icmp_seq=6 ttl=64 time=44.5 ms
--- 2001:1418:100::1 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5004ms
rtt min/avg/max/mdev = 43.495/44.157/44.881/0.487 ms
debian:~#
and also iv4 pop i can ping :
PING 213.254.12.34 (213.254.12.34) 56(84) bytes of data.
64 bytes from 213.254.12.34: icmp_seq=1 ttl=60 time=43.2 ms
64 bytes from 213.254.12.34: icmp_seq=2 ttl=60 time=41.2 ms
64 bytes from 213.254.12.34: icmp_seq=3 ttl=60 time=43.0 ms
64 bytes from 213.254.12.34: icmp_seq=4 ttl=60 time=41.7 ms
64 bytes from 213.254.12.34: icmp_seq=5 ttl=60 time=41.5 ms
:-|
lost 5 credits
![[gb]](/s/countries/gb.gif) Shadow Hawkins on Tuesday, 25 January 2005 02:21:42
I've just had the same problem. My end-point was down for approx. 20 hours and when I brought it back up and restored the tunnel, sixxs still registers it as not pinging, but yet carrying traffic. Strange!
Suggestions on why this might be happening are very welcome.
Best regards,
-->Gar
from nexus (3ffe:4005:1000:88::2)
[user@nexus tmp]$ ping6 noc.sixxs.net
PING noc.sixxs.net(2001:838:1:1:210:dcff:fe20:7c7c) 56 data bytes
64 bytes from 2001:838:1:1:210:dcff:fe20:7c7c: icmp_seq=1 ttl=57 time=99.0 ms
--- noc.sixxs.net ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 99.030/99.030/99.030/0.000 ms
lost 5 credits
Shadow Hawkins on Tuesday, 25 January 2005 20:26:42
In reply to my own post :-)
Problem is now solved. It was due to me upgrading the kernel to 2.4.29 (from pre 2.4.21) and the IPv6 installing an extra automatic route to the tunnel IP's via the loopback interface.
This meant that I could ping everywhere and everywhere could ping me - EXCEPT the remote tunnel endpoint - which is where the sixxs system runs its ping tests from. This was a PITA to diagnose. Huge thanks to Jeroen for helping me out and pointing me in the right direction.
More information on this in the FAQ at http://www.sixxs.net/faq/connectivity/?faq=ping (which I completely missed until Jeroen pointed it out to me. doh! :-) )
Best regards,
-->Gar
|
Posting is only allowed when you are