Ticket ID: SIXXS #1154806 Ticket Status: User PoP: deham02 - Easynet (Hamburg)
IPv6 endpoint does not reply do pings (T22467)
Shadow Hawkins on Monday, 27 July 2009 11:50:45
Hello,
I have an IP6-in-IPv4 static tunnel on Debian Lenny (T22467). I tried to configure it manually and using aiccu. Both times I can see IPv6-in-IPv4 packets leaving my interface using tcpdump, but no traffic originating from the deham02 ipv4 endpoint is received. When I first tried to configure the tunnel I accidentally used the IP address (both ipv4 tunnel endpoint and ipv6 address) of a friend of mine because I used cut & paste to copy the config. While I was using the _wrong_ IPv4 endpoint I could see the following:
00:47:48.305184 IP 85.214.52.88 > 212.224.0.188: IP6 2001:6f8:1c00:78::2 > 2001:638:a00:1e:21e:68ff:fe2f:28c4: ICMP6, echo request, seq 1, length 64
00:47:48.335365 IP 212.224.0.188 > 85.214.52.88: ICMP 212.224.0.188 protocol 41 port 0 unreachable, length 132
At the moment I only see the following when trying to ping the endpoint ipv6 adress (packages originating from me but no packages are received back):
11:48:30.305331 IP 85.214.52.88 > 212.224.0.189: IP6 2001:6f8:1c00:78::2 > 2001:6f8:1c00:78::1: ICMP6, echo request, seq 1, length 64
11:48:31.319684 IP 85.214.52.88 > 212.224.0.189: IP6 2001:6f8:1c00:78::2 > 2001:6f8:1c00:78::1: ICMP6, echo request, seq 2, length 64
11:48:32.319684 IP 85.214.52.88 > 212.224.0.189: IP6 2001:6f8:1c00:78::2 > 2001:6f8:1c00:78::1: ICMP6, echo request, seq 3, length 64
Maybe me using the wrong deham02 endpoint ip and ipv6 address lead to being blacklisted.
I disabled my firewall when I ran the following ,,aiccu test''.
(infra) [~] aiccu test
#######
####### AICCU Quick Connectivity Test
#######
####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (85.214.52.88)
### This should return so called 'echo replies'
### If it doesn't then check your firewall settings
### Your local endpoint should always be pingable
### It could also indicate problems with your IPv4 stack
PING 85.214.52.88 (85.214.52.88) 56(84) bytes of data.
64 bytes from 85.214.52.88: icmp_seq=1 ttl=64 time=0.051 ms
64 bytes from 85.214.52.88: icmp_seq=2 ttl=64 time=0.032 ms
64 bytes from 85.214.52.88: icmp_seq=3 ttl=64 time=0.050 ms
--- 85.214.52.88 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.032/0.044/0.051/0.010 ms
######
Did this work? [Y/n] y
####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (212.224.0.189)
### These pings should reach the PoP and come back to you
### In case there are problems along the route between your
### host and the PoP this could not return replies
### Check your firewall settings if problems occur
PING 212.224.0.189 (212.224.0.189) 56(84) bytes of data.
64 bytes from 212.224.0.189: icmp_seq=1 ttl=57 time=29.6 ms
64 bytes from 212.224.0.189: icmp_seq=2 ttl=57 time=29.7 ms
64 bytes from 212.224.0.189: icmp_seq=3 ttl=57 time=29.8 ms
--- 212.224.0.189 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2007ms
rtt min/avg/max/mdev = 29.649/29.732/29.802/0.063 ms
######
Did this work? [Y/n] y
####### [3/8] Traceroute to the PoP (212.224.0.189) over IPv4
### This traceroute should reach the PoP
### In case this traceroute fails then you have no connectivity
### to the PoP and this is most probably the problem
traceroute to 212.224.0.189 (212.224.0.189), 30 hops max, 40 byte packets
1 85.214.1.17 (85.214.1.17) 0.443 ms 0.470 ms 0.544 ms
2 85.214.0.133 (85.214.0.133) 1.418 ms 1.418 ms 1.413 ms
3 85.214.1.254 (85.214.1.254) 13.382 ms 13.453 ms 13.489 ms
4 te0-0-0-5.er10.ixfra.de.easynet.net (80.81.192.14) 14.774 ms 14.765 ms 14.346 ms
5 te0-0-0.gr10.isham.de.easynet.net (87.86.77.65) 29.154 ms 29.446 ms 29.102 ms
6 ge1-11.br2.isham.de.easynet.net (87.86.69.161) 29.535 ms 30.078 ms 30.043 ms
7 ge7-1.cr20.isham.de.easynet.net (212.224.4.89) 29.711 ms 29.434 ms 29.626 ms
8 212.224.0.189 (212.224.0.189) 29.918 ms 29.876 ms 29.989 ms
######
Did this work? [Y/n] y
###### [4/8] Checking if we can ping IPv6 localhost (::1)
### This confirms if your IPv6 is working
### If ::1 doesn't reply then something is wrong with your IPv6 stack
PING ::1(::1) 56 data bytes
64 bytes from ::1: icmp_seq=1 ttl=64 time=0.036 ms
64 bytes from ::1: icmp_seq=2 ttl=64 time=0.038 ms
64 bytes from ::1: icmp_seq=3 ttl=64 time=0.036 ms
--- ::1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.036/0.036/0.038/0.007 ms
######
Did this work? [Y/n] y
###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:6f8:1c00:78::2)
### This confirms that your tunnel is configured
### If it doesn't reply then check your interface and routing tables
PING 2001:6f8:1c00:78::2(2001:6f8:1c00:78::2) 56 data bytes
64 bytes from 2001:6f8:1c00:78::2: icmp_seq=1 ttl=64 time=0.041 ms
64 bytes from 2001:6f8:1c00:78::2: icmp_seq=2 ttl=64 time=0.032 ms
64 bytes from 2001:6f8:1c00:78::2: icmp_seq=3 ttl=64 time=0.027 ms
--- 2001:6f8:1c00:78::2 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.027/0.033/0.041/0.007 ms
######
Did this work? [Y/n] y
###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:6f8:1c00:78::1)
### This confirms the reachability of the other side of the tunnel
### If it doesn't reply then check your interface and routing tables
### Don't forget to check your firewall of course
### If the previous test was succesful then this could be both
### a firewalling and a routing/interface problem
PING 2001:6f8:1c00:78::1(2001:6f8:1c00:78::1) 56 data bytes
--- 2001:6f8:1c00:78::1 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 1999ms
######
Did this work? [Y/n] n
Greetings,
Thomas Glanzmann
--
Thomas Glanzmann <thomas@glanzmann.de> Landline +49 9131 614 -720
Rathsbergerstrasse 28 Facsimile +49 9131 614 -721
D-91054 Erlangen / Burgberg Mobile +49 176 23263284
Germany http://thomas.glanzmann.de/
State change: user
Jeroen Massar on Monday, 27 July 2009 12:32:00
The state of this ticket has been changed to user
IPv6 endpoint does not reply do pings (T22467)
Jeroen Massar on Monday, 27 July 2009 12:32:58
Pings for me:
64 bytes from 2001:6f8:1c00:78::2: icmp_seq=1 ttl=57 time=66.1 ms
Most likely cause is that PoPs do not sync directly when a tunnel is created/allocated.
IPv6 endpoint does not reply do pings (T22467)
Shadow Hawkins on Thursday, 06 August 2009 12:17:00
Hello,
you can close the ticket. The machine was pinging minutes after I created the ticket.
Thomas
Posting is only allowed when you are logged in. |