Telling my tunnel is up and running
Shadow Hawkins on Saturday, 03 September 2011 12:10:49
I just received a message from sixxs telling my tunnel cannot be pinged.
On my side, all seem ok.
Online ping6 utility at SubnetOnline.com gives me :
IPv6 Ping Output:
PING 2a01:240:fe00:1a3::2(2a01:240:fe00:1a3::2) 32 data bytes
40 bytes from 2a01:240:fe00:1a3::2: icmp_seq=0 ttl=56 time=77.2 ms
40 bytes from 2a01:240:fe00:1a3::2: icmp_seq=1 ttl=56 time=76.7 ms
40 bytes from 2a01:240:fe00:1a3::2: icmp_seq=2 ttl=56 time=76.9 ms
40 bytes from 2a01:240:fe00:1a3::2: icmp_seq=3 ttl=56 time=77.6 ms
--- 2a01:240:fe00:1a3::2 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3013ms
rtt min/avg/max/mdev = 76.761/77.155/77.669/0.477 ms, pipe 2
So ping seems ok...
Aiccu test all pass.
So... is there anything else I have to do ??
Can there be any sort of timeout bringing the tunnel down when not used ?
Redhat howto suggests so :
Keeping the tunnel up
OK, we're almost there. You now have a working tunnel, and can ping to your heart's content. You can visit IPv6-enabled websites and see all that glorious IPv6 goodness. But if you ignore your tunnel, it will die.
Why that ? Should I really setup a cron job to ping6 somewhere on a regular basis ??
Thanks for your help.
Telling my tunnel is up and running
Jeroen Massar on Saturday, 03 September 2011 12:28:14 Can there be any sort of timeout bringing the tunnel down when not used ? [..]
Why that ? Should I really setup a cron job to ping6 somewhere on a regular basis ??
See the FAQ about connection trackers....
Telling my tunnel is up and running
Shadow Hawkins on Monday, 05 September 2011 12:08:54
Thanks. I fixed my firewall rules, and I think it should work now. I simply had forgotten to allow proto 41 from the other end of the tunnel. So when traffic was going out, the connection was established and traffic was allowed, but after a while it was dropped.
I will wait some time to see if everything is ok...
Posting is only allowed when you are logged in. |