|
Ticket ID: SIXXS #9688950 Ticket Status: User PoP: deham02 - Easynet (Hamburg)
Cannot reach Pop endpoint
![[de]](/s/countries/de.gif) Carmen Sandiego on Friday, 05 July 2013 07:50:57
Since yesterday (2013-07-04) at around 17:30 UTC I lost my connection to the PoP endpoint at deham02.
My issue is similar to #5956002 and #5873894: I can ping deham02, ping6 my own tunnel address, but not the tunnel endpoint at deham02. Restarting the 6in4 tunnel locally and also trying it with aiccu didn't change the situation.
Tunnel Information for T25507:
PoP Name deham02
PoP IPv4 212.224.0.189
Your IPv4 Static, currently 83.137.98.96
PoP IPv6 2001:6f8:1c00:18a::1
Your IPv6 2001:6f8:1c00:18a::2
Last Alive 2013-07-04 17:30:24 UTC
root@batleth:~# ip -6 ro
2001:6f8:1c00:18a::1 dev sixxs metric 1024 mtu 1480 advmss 1420 hoplimit 4294967295
2001:6f8:1c00:18a::/64 via :: dev sixxs proto kernel metric 256 mtu 1480 advmss 1420 hoplimit 4294967295
2001:6f8:1ccd::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev virbr0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 via :: dev sixxs proto kernel metric 256 mtu 1480 advmss 1420 hoplimit 4294967295
default via 2001:6f8:1c00:18a::1 dev sixxs metric 1024 mtu 1480 advmss 1420 hoplimit 4294967295
root@batleth:~# ip link show sixxs
12: sixxs: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1480 qdisc noqueue state UNKNOWN
link/sit 0.0.0.0 peer 212.224.0.189
Kind regards,
Juri
Cannot reach Pop endpoint
Shadow Hawkins on Friday, 05 July 2013 08:20:14
I've got exactly the same problem. Shortly after 17:00 UTC, the inner tunnel endpoint couldn't be reached anymore. aiccu test failes at the stage, where the inner endpoint gets pinged.
Tunnel Configuration
Tunnel ID T53245
TID 0x394
Tunnel Debugging no
Inner Us 2001:6f8:1c00:394::1
Inner Them 2001:6f8:1c00:394::2
Outer Us 212.224.0.189
Outer Them 85.176.62.109
MTU 1472
Tunnel State up
Tunnel Type heartbeat
# ip -6 ro
2001:6f8:1c00:394::/64 via :: dev sixxs proto kernel metric 256 mtu 1472 advmss 1412 hoplimit 0
2001:6f8:1ddb::/64 dev br-lan proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 0
fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 0
fe80::/64 dev br-lan proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 0
fe80::/64 dev eth0.1 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 0
fe80::/64 dev eth0.2 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 0
fe80::/64 via :: dev sixxs proto kernel metric 256 mtu 1472 advmss 1412 hoplimit 0
default via 2001:6f8:1c00:394::1 dev sixxs metric 1024 mtu 1472 advmss 1412 hoplimit 0
# ip a show sixxs
19: sixxs: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1472 qdisc noqueue state UNKNOWN
link/sit 85.176.62.109 peer 212.224.0.189
inet6 2001:6f8:1c00:394::2/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::55b0:3e6d/64 scope link
valid_lft forever preferred_lft forever
inet6 fe80::a0a:101/64 scope link
valid_lft forever preferred_lft forever
inet6 fe80::c0a8:102/64 scope link
valid_lft forever preferred_lft forever
Thank you for your time,
Dennis
Cannot reach Pop endpoint
From the Live Tunnel Status:
Packet In : 2013-07-04 17:17:22 (1372958242; 0 days 16:18:40 ago)
...
ICMPv4 Errors Received : 188, last: 85.176.62.109 2013-07-05 07:57:08 (1373011028; 0 days 01:38:54 ago)
Check your firewall, though as the other report looks quite similar, maybe time to ask your ISP if they are blocking proto-41?
Cannot reach Pop endpoint
Shadow Hawkins on Friday, 05 July 2013 10:35:32
Hello Jeroen,
since about 10:00 UTC, the tunnel started working again without any change at my end.
For the record, my ISP is Alice.
Cannot reach Pop endpoint
Something must have changed, the question is: where and what.
Cannot reach Pop endpoint
Shadow Hawkins on Friday, 05 July 2013 09:02:09
Hi!
Here's the same problem too.
Ciao, Dominik
Cannot reach Pop endpoint
I think the big orange boxes, in duplicate, are not big enough and not in awful enough color, they clearly state:
"In the event that there is a problem, include a sufficient description as mentioned in the Reporting Problems section of the contact page, we can not handle the problem otherwise."
This is ALSO noted in the pre-filled text in this textfield, to make sure that people read it. Thus please do provide details.
Cannot reach Pop endpoint
2001:6f8:1c00:18a::1 dev sixxs metric 1024 mtu 1480 advmss 1420 hoplimit 4294967295
This route is implicit because of the next one for 2001:6f8:1c00:18a::/64, why is there?
root@batleth:~# ip link show sixxs 12: sixxs: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1480 qdisc noqueue state UNKNOWN link/sit 0.0.0.0 peer 212.224.0.189
That shows the tunnel, which has an unconfigured local address, thus it will pick the 'closest' one etc.
Where is the IPv4 traceroute, the IPv6 traceroute and the tcpdump for this all?
According to the PoP, which you can see under Live PoP Status in the tunnel details:
Packet In : 2013-07-04 17:17:21 (1372958241; 0 days 16:11:18 ago)
Packets In : 0
Octets In : 0
Packet Out : 2013-07-05 09:28:37 (1373016517; 0 days 00:00:02 ago)
Packets Out : 1175
As such, indeed, somewhere yesterday your tunnel quit working. The question now is where and why.
The errors though show what might be the cause:
ICMPv4 Errors Received : 394, last: 83.137.98.96 2013-07-05 07:28:03 (1373009283; 0 days 02:00:36 ago)
That shows your side of the tunnel rejecting IPv6-in-IPv4 (proto-41) packets, which demonstrates that your end is very likely to blame here.
Thus the other thing listed in that list pointed to by the big orange boxes (in duplicate so that you cannot miss it, but clearly people do): what are your firewall rules?
|
![[ch]](/s/countries/ch.gif)
on Friday, 05 July 2013 09:37:01
Posting is only allowed when you are