Forum - Sixxs robot keep saying my tunnel is not replying :: SixXS

Sixxs robot keep saying my tunnel is not replying

Shadow Hawkins on Friday, 06 May 2011 09:13:44

Hi, I got a problem and I dont know how to solve it. Sixxs robot keep saying my tunnel is not replying to ping req. The tunnel is up and I can ping 2001:15c0:65ff:553::2 (my ipv6) from the outside:

PING 2001:15c0:65ff:553::2(2001:15c0:65ff:553::2) 56 data bytes 64 bytes from 2001:15c0:65ff:553::2: icmp_seq=1 ttl=54 time=50.8 ms 64 bytes from 2001:15c0:65ff:553::2: icmp_seq=2 ttl=54 time=52.6 ms 64 bytes from 2001:15c0:65ff:553::2: icmp_seq=3 ttl=54 time=52.0 ms 64 bytes from 2001:15c0:65ff:553::2: icmp_seq=4 ttl=54 time=53.3 ms --- 2001:15c0:65ff:553::2 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3004ms rtt min/avg/max/mdev = 50.862/52.250/53.392/0.927 ms

I can ping the sixxs side:

ping6 2001:15c0:65ff:553::1 PING 2001:15c0:65ff:553::1(2001:15c0:65ff:553::1) 56 data bytes 64 bytes from 2001:15c0:65ff:553::1: icmp_seq=1 ttl=64 time=15.1 ms 64 bytes from 2001:15c0:65ff:553::1: icmp_seq=2 ttl=64 time=15.8 ms ^C --- 2001:15c0:65ff:553::1 ping statistics ---] 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 15.148/15.483/15.818/0.335 ms

And I can ping google :D :

PING ipv6.google.com(2a00:1450:4001:c01::63) 56 data bytes 64 bytes from 2a00:1450:4001:c01::63: icmp_seq=1 ttl=58 time=34.3 ms 64 bytes from 2a00:1450:4001:c01::63: icmp_seq=2 ttl=58 time=34.2 ms 64 bytes from 2a00:1450:4001:c01::63: icmp_seq=3 ttl=58 time=34.9 ms ^C --- ipv6.google.com ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2001ms rtt min/avg/max/mdev = 34.268/34.540/34.983/0.381 ms

and the RRDTOOL is showing 100% ping loss for the last 2 days

Sixxs robot keep saying my tunnel is not replying

Shadow Hawkins on Friday, 06 May 2011 11:45:39

Hi Andraz, Seems like your endpoint is running some sort of Linux system. If so do you have any ip6tables rules installed? It would be useful to mention them here. 'ip6tables -L -n' should list all of them. Regards, Sergiusz

Sixxs robot keep saying my tunnel is not replying

Shadow Hawkins on Friday, 06 May 2011 11:48:39

Btw. It would be very useful to be able to ping own tunnel endpoint from the PoP and see what the result is. I will suggest it within "What can be done better?" Regards, Sergiusz

Sixxs robot keep saying my tunnel is not replying

Jeroen Massar SixXS Staff

on Friday, 06 May 2011 14:15:41

First off all see the FAQ about 'my endpoint does not ping'. Secondly, check the FAQ item titled 'connection tracker' for an issue which most likely is causing your troubles.

Sixxs robot keep saying my tunnel is not replying

Shadow Hawkins on Sunday, 08 May 2011 17:37:48

no ip6tables rules set-up

Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination

I fixed the problem. It seems that my tunnel was not responding because there was no/a bit traffic. Now I am running ping6 in screen generating some traffic. I am running gentoo linux on this machine. Is it possible that the interface did not send a response because it was "sleeping"/"not listening"? I don't think I have any special power saving modes compiled in the kernel.

Sixxs robot keep saying my tunnel is not replying

Jeroen Massar SixXS Staff

on Sunday, 08 May 2011 17:50:57

I am running gentoo linux on this machine. Is it possible that the interface did

not send a response because it was "sleeping"/"not listening"?

See my previous reply, it is all about the connection tracking.

Sixxs robot keep saying my tunnel is not replying

Shadow Hawkins on Monday, 09 May 2011 07:55:41

Oh, sorry. Tnx for support. :D

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