|
Ticket ID: SIXXS #1064093 Ticket Status: User PoP:
POP refuses SIT-tunnel with ICMP unreachable
![[be]](/s/countries/be.gif) Shadow Hawkins on Saturday, 18 April 2009 14:54:43
I have read and followed the "Reporting Problems" section on the Contact page and am providing the following details for this report based on the list of items stated there:
Description: I'm unable to get my Heartbeat tunnel up. I've used it no more than 4 hours ago. I did no change anything on my side.
Handle: NLM1-SIXXS
Affected IP: 2001:6f8:202:39e::2 and the subnet routed through this tunnel
POP: bebru01, status page says it's UP
OS: Gentoo Linux using AICCU
Time: NTP-synchronized and correct
Debugging already done:
* IPv4 ping to bebru1 (212.100.184.146) - succesful
* IPv6 ping to bebru1, tunnel endpoint (2001:6f8:202:39e::1) - failed
* tcpdump output of my IPv4 connection
14:51:11.112793 IP 91.177.124.182 > 212.100.184.146: IP6 2001:6f8:144c:0:812c:e225:829d:d5b5 > 2001:41d0:1:2ed1::1: ICMP6, echo request, seq 441, length 16
14:51:11.120470 IP 212.100.184.146 > 91.177.124.182: ICMP 212.100.184.146 protocol 41 port 0 unreachable, length 84
It appears that the POP is refusing my IPv6-in-IPv4 packet.
POP refuses SIT-tunnel with ICMP unreachable
Shadow Hawkins on Saturday, 18 April 2009 15:00:14
Additional info:
I just disconnected and reconnected my IPv4 Internet connection, the problem remains.
The UDP heartbeat packets are sent to the POP, and are not refused actively. However, the sixxs.net/home page does NOT show my updated IP in the tunnel information.
14:59:18.733693 IP 87.64.18.123.44419 > 212.100.184.146.3740: UDP, length 87
14:59:18.734892 IP 87.64.18.123.37894 > 212.100.184.146.3740: UDP, length 87
14:59:23.270577 IP 87.64.18.123 > 212.100.184.146: IP6 2001:6f8:144c:0:812c:e225:829d:d5b5 > 2001:41d0:1:2ed1::1: ICMP6, echo request, seq 0, length 16
14:59:23.294359 IP 212.100.184.146 > 87.64.18.123: ICMP 212.100.184.146 protocol 41 port 0 unreachable, length 84
State change: user
The state of this ticket has been changed to user
POP refuses SIT-tunnel with ICMP unreachable
The PoP reports:
Last Beat : 2009-04-18 09:26:42 (24746 seconds ago)
And thus indeed the tunnel is down.
You have to send proper heartbeat packets, otherwise the PoP will not enable the tunnel.
Please read the text in the yellow/orange box and include the output of AICCU in verbose mode.
Next to that, list your routing tables etc etc etc...
POP refuses SIT-tunnel with ICMP unreachable
Shadow Hawkins on Saturday, 18 April 2009 19:24:07
Thank you for the response.
However, I was still sending heartbeat packets, as shown in the TCPdump output in the second post.
As of 2 minutes ago, the tunnel magically came back to life. I am certain that I did not change anything on my side, although I obviously can't prove that.
POP refuses SIT-tunnel with ICMP unreachable
Shadow Hawkins on Saturday, 18 April 2009 19:30:58
The exact same thing happened to me, and when considering the statistics at
POP refuses SIT-tunnel with ICMP unreachable
Shadow Hawkins on Saturday, 18 April 2009 19:35:02
I have read and followed the "Reporting Problems" section on the Contact page and am providing the following details for this report based on the list of items stated there:
The same thing happened to me today, around the same time, so I don't think it was a user mistake in this case. When checking traffic logs here it also shows bebru01 has been handling a lot less traffic than usual this afternoon.
Anyhow, it's back up for me too now it seems, so all's well.
|
![[ch]](/s/countries/ch.gif)
on Saturday, 18 April 2009 19:17:17
Posting is only allowed when you are