Ticket ID: SIXXS #852919 Ticket Status: User PoP: fihel01 - DNA Oy (Helsinki)
Odd problem with tunnel monitoring
Shadow Hawkins on Wednesday, 19 November 2008 09:16:03
Your tunnel monitor keeps telling me that my end point is not reachable, however:
]# ping6 2001:14b8:100:204::1
PING 2001:14b8:100:204::1(2001:14b8:100:204::1) 56 data bytes
64 bytes from 2001:14b8:100:204::1: icmp_seq=1 ttl=64 time=1.90 ms
64 bytes from 2001:14b8:100:204::1: icmp_seq=2 ttl=64 time=1.13 ms
64 bytes from 2001:14b8:100:204::1: icmp_seq=3 ttl=64 time=1.12 ms
I can ping *your* end, and there is no IPv6 filtering or firewalling done at my end. The problem has started 16.11.2008 at 8pm.
It would seem that your tunnel monitor is erroring on this. Can you please fix it before it disables my tunnel for no reason whatsoever.
Odd problem with tunnel monitoring
Shadow Hawkins on Monday, 19 July 2010 19:43:07
This problem has ben solved.
Odd problem with tunnel monitoring
Jeroen Massar on Wednesday, 19 November 2008 11:13:47
Read the FAQ and supply a lot more details. That you can ping that endpoint now, doesn't mean the PoP can ping you.
Odd problem with tunnel monitoring
Shadow Hawkins on Wednesday, 19 November 2008 11:34:18
Well. Now it seems to work. The tunnel was marked as being up.
I haven't done anything or changed anything at my end and I know it has worked for the past two days since I've tested quite a lot.
But it seems that the issue is now academic since it has "fixed itself", so ticket can be closed.
Odd problem with tunnel monitoring
Jeroen Massar on Wednesday, 19 November 2008 11:40:38
Most very likely it is My tunnel goes down after some idletime. My tunnelendpoint also is a NAT/Connection Tracker. Indeed, in that case you yourself doesn't change anything, but the kernel does.
Which is why we point you to the FAQ and ask you to provide the information requested in the "Reporting Problems" section on the contact page.
Odd problem with tunnel monitoring
Shadow Hawkins on Monday, 01 December 2008 07:17:56
Ok, I've added coupla rules in the ipv4 firewall. It now passes all traffic thru from the IPv4 endpoint and also any protocol 41 (ipv6) packets. Let's see if this does anything to improve situation.
State change: user
Jeroen Massar on Wednesday, 19 November 2008 11:12:59
The state of this ticket has been changed to user
Posting is only allowed when you are logged in. |