|
Ticket ID: SIXXS #4562489 Ticket Status: Resolved PoP: ittrn01 - ITgate (Torino)
Cannot ping remote gateway on T56225 (AYIYA)
![[it]](/s/countries/it.gif) Shadow Hawkins on Wednesday, 04 May 2011 23:23:04
I can't ping my remote gateway 2001:1418:100:3df::1 on tunnel T56225 (AYIYA), all worked until few days ago, now the tunnel seems to set up correctly but I cannot ping anything on IPv6 and all the traffic seem dropped. AICCU is running on my gateway (which is a Debian 6.0); ask me if you need more informations.
## AICCU TEST
# aiccu test
Tunnel Information for T56225:
POP Id : ittrn01
IPv6 Local : 2001:1418:100:3df::2/64
IPv6 Remote : 2001:1418:100:3df::1/64
Tunnel Type : ayiya
Adminstate : enabled
Userstate : enabled
#######
####### AICCU Quick Connectivity Test
#######
####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (79.54.97.115)
### 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 79.54.97.115 (79.54.97.115) 56(84) bytes of data.
64 bytes from 79.54.97.115: icmp_req=1 ttl=64 time=0.175 ms
64 bytes from 79.54.97.115: icmp_req=2 ttl=64 time=0.085 ms
64 bytes from 79.54.97.115: icmp_req=3 ttl=64 time=0.081 ms
--- 79.54.97.115 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 0.081/0.113/0.175/0.045 ms
######
Did this work? [Y/n] y
####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (213.254.12.34)
### 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 213.254.12.34 (213.254.12.34) 56(84) bytes of data.
64 bytes from 213.254.12.34: icmp_req=1 ttl=55 time=44.4 ms
64 bytes from 213.254.12.34: icmp_req=2 ttl=55 time=48.6 ms
64 bytes from 213.254.12.34: icmp_req=3 ttl=55 time=42.6 ms
--- 213.254.12.34 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 42.648/45.244/48.663/2.529 ms
######
Did this work? [Y/n] y
####### [3/8] Traceroute to the PoP (213.254.12.34) 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 213.254.12.34 (213.254.12.34), 30 hops max, 60 byte packets
1 192.168.100.1 (192.168.100.1) 21.718 ms 24.055 ms 28.084 ms
2 host157-182-static.32-88-b.business.telecomitalia.it (88.32.182.157) 28.602 ms 32.640 ms 33.668 ms
3 r-bs47-vl19.opb.interbusiness.it (80.20.178.151) 37.581 ms 38.854 ms 41.242 ms
4 172.17.6.233 (172.17.6.233) 47.859 ms 50.019 ms 52.393 ms
5 172.17.9.137 (172.17.9.137) 58.204 ms 59.858 ms 61.784 ms
6 172.17.7.190 (172.17.7.190) 64.413 ms 62.952 ms 36.946 ms
7 172.17.4.218 (172.17.4.218) 40.527 ms 40.484 ms 42.173 ms
8 itgate-pub.topix.it (194.116.96.4) 45.768 ms 47.917 ms 50.348 ms
9 if-0-1.rumba.edge.TRN.itgate.net (213.254.0.25) 56.945 ms 56.896 ms 56.843 ms
10 frejus.ITgate.net (213.254.12.34) 59.728 ms 62.621 ms 64.274 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.079 ms
64 bytes from ::1: icmp_seq=2 ttl=64 time=0.068 ms
64 bytes from ::1: icmp_seq=3 ttl=64 time=0.068 ms
--- ::1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.068/0.071/0.079/0.011 ms
######
Did this work? [Y/n] Y
###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:1418:100:3df::2)
### This confirms that your tunnel is configured
### If it doesn't reply then check your interface and routing tables
PING 2001:1418:100:3df::2(2001:1418:100:3df::2) 56 data bytes
64 bytes from 2001:1418:100:3df::2: icmp_seq=1 ttl=64 time=0.077 ms
64 bytes from 2001:1418:100:3df::2: icmp_seq=2 ttl=64 time=0.085 ms
64 bytes from 2001:1418:100:3df::2: icmp_seq=3 ttl=64 time=0.085 ms
--- 2001:1418:100:3df::2 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 0.077/0.082/0.085/0.008 ms
######
Did this work? [Y/n] Y
###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:1418:100:3df::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 successful then this could be both
### a firewalling and a routing/interface problem
PING 2001:1418:100:3df::1(2001:1418:100:3df::1) 56 data bytes
--- 2001:1418:100:3df::1 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2016ms
######
Did this work? [Y/n] n
## AICCU VERSION
I'm using aiccu 20070115-14 (the package in the debian stable repository)
## uname -a
Linux cerbero 2.6.32-5-686 #1 SMP Tue Mar 8 21:36:00 UTC 2011 i686 GNU/Linux
## ROUTING TABLE
# ip -6 r
2001:1418:100:3df::/64 dev tun2 proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 0
fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 0
fe80::/64 dev eth1 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 0
fe80::/64 dev eth2 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 0
fe80::/64 dev tun2 proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 0
default via 2001:1418:100:3df::1 dev tun2 metric 1024 mtu 1280 advmss 1220 hoplimit 0
## TCPDUMP
# ping6 -c1 2001:1418:100:3df::1
PING 2001:1418:100:3df::1(2001:1418:100:3df::1) 56 data bytes
--- 2001:1418:100:3df::1 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
# tcpdump -i tun2 -n -s 1500
tcpdump: WARNING: tun2: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on tun2, link-type RAW (Raw IP), capture size 1500 bytes
23:07:10.749743 IP6 2001:1418:100:3df::2 > 2001:1418:100:3df::1: ICMP6, echo request, seq 1, length 64
State change: resolved
The state of this ticket has been changed to resolved
Cannot ping remote gateway on T56225 (AYIYA)
I get replies from your endpoint:
64 bytes from 2001:1418:100:3df::2: icmp_seq=1 ttl=48 time=57.3 ms
Note that tcpdumping a tunnel interface does not make sense, you need to look at the interface below it and not exclude any traffic as it might just be that an ICMP unreachable of whatever form is sent from an intermediate host and there are other packets which might indicate problems.
Cannot ping remote gateway on T56225 (AYIYA)
Shadow Hawkins on Tuesday, 07 June 2011 02:59:37
The same problem happened again:
## AICCU TEST
# aiccu test
Tunnel Information for T56225:
POP Id : ittrn01
IPv6 Local : 2001:1418:100:3df::2/64
IPv6 Remote : 2001:1418:100:3df::1/64
Tunnel Type : ayiya
Adminstate : enabled
Userstate : enabled
#######
####### AICCU Quick Connectivity Test
#######
####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (87.2.99.96)
### 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 87.2.99.96 (87.2.99.96) 56(84) bytes of data.
64 bytes from 87.2.99.96: icmp_req=1 ttl=64 time=0.145 ms
64 bytes from 87.2.99.96: icmp_req=2 ttl=64 time=0.096 ms
64 bytes from 87.2.99.96: icmp_req=3 ttl=64 time=0.104 ms
--- 87.2.99.96 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.096/0.115/0.145/0.021 ms
######
Did this work? [Y/n] y
####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (213.254.12.34)
### 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 213.254.12.34 (213.254.12.34) 56(84) bytes of data.
64 bytes from 213.254.12.34: icmp_req=1 ttl=55 time=29.3 ms
64 bytes from 213.254.12.34: icmp_req=2 ttl=55 time=29.2 ms
64 bytes from 213.254.12.34: icmp_req=3 ttl=55 time=29.0 ms
--- 213.254.12.34 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 29.064/29.219/29.348/0.229 ms
######
Did this work? [Y/n] Y
####### [3/8] Traceroute to the PoP (213.254.12.34) 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 213.254.12.34 (213.254.12.34), 30 hops max, 60 byte packets
####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (213.254.12.34)
### 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 213.254.12.34 (213.254.12.34) 56(84) bytes of data.
64 bytes from 213.254.12.34: icmp_req=1 ttl=55 time=29.3 ms
64 bytes from 213.254.12.34: icmp_req=2 ttl=55 time=29.2 ms
64 bytes from 213.254.12.34: icmp_req=3 ttl=55 time=29.0 ms
--- 213.254.12.34 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 29.064/29.219/29.348/0.229 ms
######
Did this work? [Y/n] Y
####### [3/8] Traceroute to the PoP (213.254.12.34) 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 213.254.12.34 (213.254.12.34), 30 hops max, 60 byte packets
1 192.168.100.1 (192.168.100.1) 23.787 ms 26.347 ms 29.468 ms
2 host29-182-static.32-88-b.business.telecomitalia.it (88.32.182.29) 32.598 ms 35.274 ms 38.153 ms
3 r-bs48-vl19.opb.interbusiness.it (80.20.178.152) 42.052 ms 44.687 ms 47.339 ms
4 172.17.6.133 (172.17.6.133) 54.921 ms 58.306 ms 60.723 ms
5 172.17.9.17 (172.17.9.17) 63.881 ms 66.535 ms 69.656 ms
6 172.17.7.194 (172.17.7.194) 72.320 ms 29.297 ms 30.762 ms
7 172.17.4.226 (172.17.4.226) 32.121 ms 34.758 ms 37.409 ms
8 itgate-pub.topix.it (194.116.96.4) 41.279 ms 43.464 ms 47.313 ms
9 if-0-1.rumba.edge.TRN.itgate.net (213.254.0.25) 49.499 ms 51.655 ms 54.304 ms
10 frejus.ITgate.net (213.254.12.34) 57.475 ms 60.097 ms 63.711 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.083 ms
64 bytes from ::1: icmp_seq=2 ttl=64 time=0.073 ms
64 bytes from ::1: icmp_seq=3 ttl=64 time=0.076 ms
--- ::1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.073/0.077/0.083/0.008 ms
######
Did this work? [Y/n] Y
###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:1418:100:3df::2)
### This confirms that your tunnel is configured
### If it doesn't reply then check your interface and routing tables
PING 2001:1418:100:3df::2(2001:1418:100:3df::2) 56 data bytes
64 bytes from 2001:1418:100:3df::2: icmp_seq=1 ttl=64 time=0.092 ms
64 bytes from 2001:1418:100:3df::2: icmp_seq=2 ttl=64 time=0.097 ms
64 bytes from 2001:1418:100:3df::2: icmp_seq=3 ttl=64 time=0.087 ms
--- 2001:1418:100:3df::2 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.087/0.092/0.097/0.004 ms
######
Did this work? [Y/n] Y
###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:1418:100:3df::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 successful then this could be both
### a firewalling and a routing/interface problem
PING 2001:1418:100:3df::1(2001:1418:100:3df::1) 56 data bytes
--- 2001:1418:100:3df::1 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2014ms
######
Did this work? [Y/n] n
## AICCU VERSION
I'm using aiccu 20070115-14 (the package in the debian stable repository)
## uname -a
Linux cerbero 2.6.32-5-686 #1 SMP Wed May 18 07:08:50 UTC 2011 i686 GNU/Linux
## ROUTING TABLE
# ip -6 r
2001:1418:100:3df::/64 dev tun2 proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 0
fe80::/64 dev eth0 proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 0
fe80::/64 dev eth1 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 0
fe80::/64 dev eth2 proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 0
fe80::/64 dev tun2 proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 0
default via 2001:1418:100:3df::1 dev tun2 metric 1024 mtu 1280 advmss 1220 hoplimit 0
## TCPDUMP
# ping6 -c1 2001:1418:100:3df::1
PING 2001:1418:100:3df::1(2001:1418:100:3df::1) 56 data bytes
--- 2001:1418:100:3df::1 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
# tcpdump -i ppp0 -n -s 1500
# (thanks for the last time)
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on ppp0, link-type LINUX_SLL (Linux cooked), capture size 1500 bytes
00:03:49.723066 IP 87.2.99.96.56122 > 213.254.12.34.5072: UDP, length 148
Cannot ping remote gateway on T56225 (AYIYA)
Shadow Hawkins on Thursday, 09 June 2011 20:10:59
It's working again now, thanks!
|
![[ch]](/s/countries/ch.gif)
on Thursday, 05 May 2011 13:09:56
Posting is only allowed when you are