|
Ticket ID: SIXXS #7920154 Ticket Status: Resolved PoP: ittrn01 - ITgate (Torino)
Remote IPv6 tunnel endpoint no more reachable
![[it]](/s/countries/it.gif) Shadow Hawkins on Sunday, 30 September 2012 00:40:10
Hi,
I lost IPv6 connectivity about two hours ago.
Run some tests and found that I cannot ping my remote IPv6 tunnel endpoint.
Here last lines of "aiccu test" output:
###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:1418:100:1f4::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:1418:100:1f4::1(2001:1418:100:1f4::1) 56 data bytes
--- 2001:1418:100:1f4::1 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 1999ms
######
Did this work? [Y/n] n
Any help would be appreciated.
Best regards
AZ1329-RIPE
Andrea Zuccherelli
State change: confirmed
The state of this ticket has been changed to confirmed
Remote IPv6 tunnel endpoint no more reachable
The host is unfortunately broken at the moment, seems to hang in some strange state. ITGate is looking into it.
State change: resolved
The state of this ticket has been changed to resolved
Remote IPv6 tunnel endpoint no more reachable
This outage was thanks to the children on the Internet.
At least the children have lost their precious play boxes now.
But it seems we have to tighten those rules again.
Remote IPv6 tunnel endpoint no more reachable
Shadow Hawkins on Sunday, 30 September 2012 18:18:08
Thank you very much for the quick intervention.
However, several hours after resolving this ticket, the connection is still inconstant. Pinging the PoP's sixxs host exhibits an appreciable packet loss, both in IPv4 and in IPv6:
$ ping ittrn01.sixxs.net
PING ittrn01.sixxs.net (213.254.12.34) 56(84) bytes of data.
64 bytes from frejus.ITgate.net (213.254.12.34): icmp_seq=1 ttl=53 time=20.9 ms
64 bytes from frejus.ITgate.net (213.254.12.34): icmp_seq=2 ttl=53 time=21.1 ms
64 bytes from frejus.ITgate.net (213.254.12.34): icmp_seq=3 ttl=53 time=21.0 ms
64 bytes from frejus.ITgate.net (213.254.12.34): icmp_seq=4 ttl=53 time=18.4 ms
64 bytes from frejus.ITgate.net (213.254.12.34): icmp_seq=6 ttl=53 time=20.9 ms
64 bytes from frejus.ITgate.net (213.254.12.34): icmp_seq=8 ttl=53 time=21.0 ms
64 bytes from frejus.ITgate.net (213.254.12.34): icmp_seq=9 ttl=53 time=21.3 ms
64 bytes from frejus.ITgate.net (213.254.12.34): icmp_seq=10 ttl=53 time=14.4 ms
64 bytes from frejus.ITgate.net (213.254.12.34): icmp_seq=11 ttl=53 time=13.7 ms
^C
--- ittrn01.sixxs.net ping statistics ---
11 packets transmitted, 9 received, 18% packet loss, time 10008ms
rtt min/avg/max/mdev = 13.799/19.253/21.330/2.856 ms
$ ping6 ittrn01.sixxs.net
PING ittrn01.sixxs.net(frejus.ITgate.net) 56 data bytes
64 bytes from frejus.ITgate.net: icmp_seq=1 ttl=54 time=21.0 ms
64 bytes from frejus.ITgate.net: icmp_seq=2 ttl=54 time=20.8 ms
64 bytes from frejus.ITgate.net: icmp_seq=3 ttl=54 time=20.3 ms
64 bytes from frejus.ITgate.net: icmp_seq=4 ttl=54 time=21.0 ms
64 bytes from frejus.ITgate.net: icmp_seq=5 ttl=54 time=20.7 ms
64 bytes from frejus.ITgate.net: icmp_seq=8 ttl=54 time=21.0 ms
64 bytes from frejus.ITgate.net: icmp_seq=9 ttl=54 time=20.5 ms
64 bytes from frejus.ITgate.net: icmp_seq=10 ttl=54 time=43.0 ms
64 bytes from frejus.ITgate.net: icmp_seq=11 ttl=54 time=20.7 ms
64 bytes from frejus.ITgate.net: icmp_seq=12 ttl=54 time=18.6 ms
64 bytes from frejus.ITgate.net: icmp_seq=13 ttl=54 time=19.6 ms
^C
--- ittrn01.sixxs.net ping statistics ---
13 packets transmitted, 11 received, 15% packet loss, time 12010ms
IPv4 ping exhibits the same packet loss from 2 hosts located in different cities.
The above IPv6 ping is from a host connected to the native IPv6 GARR network.
An IPv6 ping from this host to the remote (PoP) end of my tunnel exhibits both packet loss and highly oscillating RTTs:
39 packets transmitted, 35 received, 10% packet loss, time 38024ms
rtt min/avg/max/mdev = 13.920/130.541/406.486/116.685 ms
The AYIYA tunnel stays up, but looks suffering and is sometimes hardly usable.
Remote IPv6 tunnel endpoint no more reachable
The problem is not fully resolved as the attacking host is still attacking, we can do little about this though till the upstreams have closed the hosts doing this.
Thank your fellow Italians for causing these issues.
|
![[ch]](/s/countries/ch.gif)
on Sunday, 30 September 2012 08:48:53
Posting is only allowed when you are