SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #658915
Ticket Status: User

PoP: 

tunnel endpoint not answering
[ee] Shadow Hawkins on Wednesday, 23 January 2008 12:42:25
Well, today I received a letter from tunnelrobot, that my tunnel is not answering.Well my tunnel is in fact replying just fine. My tunnel: T3357 PoP IPv4 : 195.222.0.66 My IPv4 : 84.52.54.139 IPv6 Prefix : 2001:ad0:900:9::1/64 PoP IPv6 : 2001:ad0:900:9::1 Your IPv6 : 2001:ad0:900:9::2 I ping my ipv6 endpoint from http://www.berkom.blazing.de/tools/ping.cgi PING 2001:ad0:900:9::2(2001:ad0:900:9::2) 56 data bytes 64 bytes from 2001:ad0:900:9::2: icmp_seq=1 ttl=52 time=62.3 ms 64 bytes from 2001:ad0:900:9::2: icmp_seq=2 ttl=52 time=66.9 ms 64 bytes from 2001:ad0:900:9::2: icmp_seq=3 ttl=52 time=65.4 ms 64 bytes from 2001:ad0:900:9::2: icmp_seq=4 ttl=52 time=65.9 ms 64 bytes from 2001:ad0:900:9::2: icmp_seq=5 ttl=52 time=64.0 ms --- 2001:ad0:900:9::2 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4040ms rtt min/avg/max/mdev = 62.337/64.963/66.945/1.633 ms and from http://www.ipv6.estpak.ee/?utilities=ping PING 2001:ad0:900:9::2(2001:ad0:900:9::2) 56 data bytes 64 bytes from 2001:ad0:900:9::2: icmp_seq=1 ttl=58 time=14.8 ms 64 bytes from 2001:ad0:900:9::2: icmp_seq=2 ttl=58 time=15.0 ms 64 bytes from 2001:ad0:900:9::2: icmp_seq=3 ttl=58 time=15.2 ms 64 bytes from 2001:ad0:900:9::2: icmp_seq=4 ttl=58 time=14.9 ms --- 2001:ad0:900:9::2 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3000ms rtt min/avg/max/mdev = 14.839/15.040/15.274/0.181 ms Is there maybe something wrong with tunnelrobot? Please check tunnelrobot. THNX.
tunnel endpoint not answering
[ch] Jeroen Massar SixXS Staff on Wednesday, 23 January 2008 12:51:44
Please actually read "Reporting Problems" and the FAQ. The PoP you are using is not located at http://www.berkom.blazing.de/tools/ping.cgi and also not at http://www.ipv6.estpak.ee/?utilities=ping
State change: user Locked
[ch] Jeroen Massar SixXS Staff on Wednesday, 23 January 2008 12:55:25
Message is Locked
The state of this ticket has been changed to user

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker