SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #4662789
Ticket Status: User

PoP: uschi03 - Team Cymru (Chicago, Illinois)

Tunnel T52037 Downtime
[us] Carmen Sandiego on Tuesday, 10 May 2011 14:57:55
Hello, I have received an email from the tunnelrobot stating my endpoint is not pingable. I am able to ping my endpoint from other v6 connected locations. What action do I need to take to make the tunnelrobot happy? As the graphs on my home page also list me as 100% down (even now, while I ping myself from a remote VPS). ** LOCAL END ** root@cinderella:~# ifconfig sixxs sixxs Link encap:IPv6-in-IPv4 inet6 addr: 2604:8800:100:56::2/64 Scope:Global inet6 addr: fe80::c0a8:1a3/64 Scope:Link UP POINTOPOINT RUNNING NOARP PROMISC MTU:1280 Metric:1 RX packets:949 errors:0 dropped:0 overruns:0 frame:0 TX packets:1358 errors:6 dropped:0 overruns:0 carrier:6 collisions:0 txqueuelen:0 RX bytes:176652 (172.5 KiB) TX bytes:136274 (133.0 KiB) root@cinderella:~# tcpdump -v -i sixxs -s 1500 tcpdump: WARNING: sixxs: no IPv4 address assigned tcpdump: listening on sixxs, link-type RAW (Raw IP), capture size 1500 bytes 07:54:28.158991 IP6 (hlim 55, next-header ICMPv6 (58) payload length: 64) 2001:470:21:31::adf5:498c > cl-87.chi-03.us.sixxs.net: [icmp6 sum ok] ICMP6, echo request, length 64, seq 1 07:54:28.158991 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) cl-87.chi-03.us.sixxs.net > 2001:470:21:31::adf5:498c: [icmp6 sum ok] ICMP6, echo reply, length 64, seq 1 07:54:29.158991 IP6 (hlim 55, next-header ICMPv6 (58) payload length: 64) 2001:470:21:31::adf5:498c > cl-87.chi-03.us.sixxs.net: [icmp6 sum ok] ICMP6, echo request, length 64, seq 2 07:54:29.158991 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) cl-87.chi-03.us.sixxs.net > 2001:470:21:31::adf5:498c: [icmp6 sum ok] ICMP6, echo reply, length 64, seq 2 07:54:30.158991 IP6 (hlim 55, next-header ICMPv6 (58) payload length: 64) 2001:470:21:31::adf5:498c > cl-87.chi-03.us.sixxs.net: [icmp6 sum ok] ICMP6, echo request, length 64, seq 3 07:54:30.158991 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) cl-87.chi-03.us.sixxs.net > 2001:470:21:31::adf5:498c: [icmp6 sum ok] ICMP6, echo reply, length 64, seq 3 ** REMOTE VPS ** kline@hosted:~/ackfuss$ ping6 2604:8800:100:56::2 PING 2604:8800:100:56::2(2604:8800:100:56::2) 56 data bytes 64 bytes from 2604:8800:100:56::2: icmp_seq=1 ttl=56 time=77.4 ms 64 bytes from 2604:8800:100:56::2: icmp_seq=2 ttl=56 time=70.3 ms 64 bytes from 2604:8800:100:56::2: icmp_seq=3 ttl=56 time=70.8 ms ^C --- 2604:8800:100:56::2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 70.334/72.891/77.467/3.243 ms Regards, Matt Goff
State change: user Locked
[ch] Jeroen Massar SixXS Staff on Tuesday, 10 May 2011 15:25:05
Message is Locked
The state of this ticket has been changed to user
Tunnel T52037 Downtime
[ch] Jeroen Massar SixXS Staff on Tuesday, 10 May 2011 15:26:05
What action do I need to take to make the tunnelrobot happy?
As stated in the email you got from the robot, start by reading the FAQ. Most likely you are hitting what most people hit and what is mentioned in the FAQ item concerning connection tracking. It is a FAQ for a reason.
Tunnel T52037 Downtime
[us] Carmen Sandiego on Wednesday, 11 May 2011 18:41:59
I enabled v4 ping on my network gateway and the robot still did not like me. I ended up having to move my tunnel off a client on my LAN directly to my gateway; while also leaving the v4 open for ping. It still seems to have some misses in connecting to me, but not the 100% it previously was.
Tunnel T52037 Downtime
[ch] Jeroen Massar SixXS Staff on Wednesday, 11 May 2011 19:01:01
If you would have read the FAQ you would know that the ping test is performed over IPv6. Please actually read the FAQ, it is there for a reason.

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

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