Ticket ID: SIXXS #1354604 Ticket Status: Resolved PoP: deham01 - Easynet (Hamburg)
Packetloss to deham01.sixxs.net
Shadow Hawkins on Thursday, 11 February 2010 18:37:11
There seems to be an issue with deham01. My tunnels terminated on deham01 are offline due a heavy packetloss. The packetloss occoured to the ipv4 address of deham01:
kraut@dracula:~$ ping -c 100 212.224.0.188
PING 212.224.0.188 (212.224.0.188) 56(84) bytes of data.
64 bytes from 212.224.0.188: icmp_seq=1 ttl=57 time=44.1 ms
64 bytes from 212.224.0.188: icmp_seq=2 ttl=57 time=43.4 ms
64 bytes from 212.224.0.188: icmp_seq=4 ttl=57 time=55.9 ms
64 bytes from 212.224.0.188: icmp_seq=84 ttl=57 time=47.1 ms
64 bytes from 212.224.0.188: icmp_seq=87 ttl=57 time=45.6 ms
64 bytes from 212.224.0.188: icmp_seq=89 ttl=57 time=45.0 ms
--- 212.224.0.188 ping statistics ---
100 packets transmitted, 6 received, 94% packet loss, time 99725ms
rtt min/avg/max/mdev = 43.405/46.883/55.923/4.210 ms
traceroute to 212.224.0.188 (212.224.0.188), 30 hops max, 40 byte packets
1 em0.cygni.hosting-server.cc (194.126.239.65) 0.247 ms 0.221 ms 0.191 ms
2 d-ec1.d.de.net.dtag.de (193.159.226.65) 0.504 ms 0.599 ms 0.690 ms
3 217.239.40.181 (217.239.40.181) 4.904 ms 4.908 ms 4.885 ms
4 217.243.219.82 (217.243.219.82) 4.350 ms 4.362 ms 5.197 ms
5 te0-0-0.gr10.isham.de.easynet.net (87.86.77.65) 15.061 ms 15.061 ms 15.069 ms
6 ge3-7.br2.isham.de.easynet.net (87.86.71.241) 15.295 ms 15.475 ms 15.416 ms
7 ge7-1.cr20.isham.de.easynet.net (212.224.4.89) 14.629 ms 14.085 ms 14.912 ms
8 deham01.sixxs.net (212.224.0.188) 41.829 ms 44.334 ms 43.803 ms
The connection to 212.224.4.89 is fine. Only 212.224.0.188 got that issue.
Regards
Thomas Kuehling
Packetloss to deham01.sixxs.net
Shadow Hawkins on Thursday, 11 February 2010 18:45:46
Same issue via de-cix peering:
tku@kaya:~$ tracepath 212.224.0.188
1: kaya (80.228.126.44) 0.212ms pmtu 1500
1: eins.dd.ewetel.de (80.228.126.1) 0.438ms
1: eins.dd.ewetel.de (80.228.126.1) 0.380ms
2: bbrt.ol-0-ge-7-0-0-23.ewe-ip-backbone.de (213.168.195.2) 0.838ms asymm 3
3: bbrt.hb-2-xe-1-1-0.ewe-ip-backbone.de (80.228.90.34) 1.513ms asymm 4
4: bbrt.ffm-0-10ge-6-0-0.ewe-ip-backbone.de (212.6.114.14) 16.347ms asymm 5
5: te0-0-0-5.er10.ixfra.de.easynet.net (80.81.192.14) 14.490ms
6: te0-1-0.gr11.isham.de.easynet.net (87.86.77.80) 20.839ms asymm 9
7: ge3-7.br3.isham.de.easynet.net (87.86.71.249) 20.837ms asymm 9
8: ge9-15.cr20.isham.de.easynet.net (212.224.4.93) 23.517ms asymm 10
9: deham01.sixxs.net (212.224.0.188) 63.292ms reached
Resume: pmtu 1500 hops 9 back 56
tku@kaya:~$ ping -c 100 212.224.0.188
PING 212.224.0.188 (212.224.0.188) 56(84) bytes of data.
64 bytes from 212.224.0.188: icmp_seq=4 ttl=56 time=61.8 ms
64 bytes from 212.224.0.188: icmp_seq=27 ttl=56 time=62.2 ms
64 bytes from 212.224.0.188: icmp_seq=37 ttl=56 time=61.4 ms
64 bytes from 212.224.0.188: icmp_seq=64 ttl=56 time=62.9 ms
64 bytes from 212.224.0.188: icmp_seq=83 ttl=56 time=61.9 ms
64 bytes from 212.224.0.188: icmp_seq=86 ttl=56 time=60.7 ms
64 bytes from 212.224.0.188: icmp_seq=90 ttl=56 time=62.1 ms
64 bytes from 212.224.0.188: icmp_seq=91 ttl=56 time=60.2 ms
64 bytes from 212.224.0.188: icmp_seq=97 ttl=56 time=62.7 ms
64 bytes from 212.224.0.188: icmp_seq=99 ttl=56 time=61.5 ms
--- 212.224.0.188 ping statistics ---
100 packets transmitted, 10 received, 90% packet loss, time 99179ms
rtt min/avg/max/mdev = 60.201/61.789/62.989/0.810 ms
Packetloss to deham01.sixxs.net
Shadow Hawkins on Thursday, 11 February 2010 19:16:46
--- deham01.sixxs.net ping statistics ---
26 packets transmitted, 7 received, 73% packet loss, time 25045ms
rtt min/avg/max/mdev = 51.790/55.241/58.235/2.579 ms
IPv6 Tunnel is Down due to this excessive Packetloss
deham02 has similar packet loss, other POPs (e.g. dedus01) have no packet loss.
Packetloss to deham01.sixxs.net
Shadow Hawkins on Thursday, 11 February 2010 19:15:06
Same problem here
------------------------------------------
$ ping6 -c 100 sixxs.net
PING sixxs.net(nlede01.sixxs.net) 56 data bytes
64 bytes from nlede01.sixxs.net: icmp_seq=2 ttl=56 time=118 ms
64 bytes from nlede01.sixxs.net: icmp_seq=4 ttl=56 time=116 ms
64 bytes from nlede01.sixxs.net: icmp_seq=6 ttl=56 time=117 ms
64 bytes from nlede01.sixxs.net: icmp_seq=31 ttl=56 time=113 ms
64 bytes from nlede01.sixxs.net: icmp_seq=52 ttl=56 time=118 ms
64 bytes from nlede01.sixxs.net: icmp_seq=53 ttl=56 time=115 ms
64 bytes from nlede01.sixxs.net: icmp_seq=55 ttl=56 time=117 ms
64 bytes from nlede01.sixxs.net: icmp_seq=62 ttl=56 time=110 ms
64 bytes from nlede01.sixxs.net: icmp_seq=85 ttl=56 time=114 ms
64 bytes from nlede01.sixxs.net: icmp_seq=100 ttl=56 time=108 ms
--- sixxs.net ping statistics ---
100 packets transmitted, 10 received, 90% packet loss, time 99014ms
rtt min/avg/max/mdev = 108.994/115.207/118.608/3.027 ms
------------------------------------------
Packetloss to deham01.sixxs.net
Shadow Hawkins on Thursday, 11 February 2010 19:39:22
Hello,
I see packetloss as well, but only on the last hop. Trace via IPv4:
4. workix.ixhbg.de.easynet. .....................................................................................................
5. ge2-0-8.gr10.isham.de.ea .....................................................................................................
6. ge3-8.br2.isham.de.easyn .............................................>................................................>......
7. ge7-1.cr20.isham.de.easy .....................................................................................................
8. deham01.sixxs.net ??????..???.?.??.????.??.??..?...?.??.?....?.?.?.?.??.?.??.??.??????????.???????.??...?.????.??...?.
State change: confirmed
Pim van Pelt on Thursday, 11 February 2010 19:42:44
The state of this ticket has been changed to confirmed
Packetloss to deham01.sixxs.net
Pim van Pelt on Thursday, 11 February 2010 19:43:12
mtr -4 deham01.sixxs.net from AS12859 and AS15169 confirms this packet loss as well. I will bring it up with Easynet folks.
Packetloss to deham01.sixxs.net
Shadow Hawkins on Friday, 12 February 2010 11:48:52
Seems to be fixed. Loss and latency are back to normal!
Packetloss to deham01.sixxs.net
Shadow Hawkins on Friday, 12 February 2010 13:34:29
I can confirm that, too. Everything is working like a charm again. Thanks!
--- 212.224.0.188 ping statistics ---
100 packets transmitted, 100 received, 0% packet loss, time 99344ms
rtt min/avg/max/mdev = 19.920/21.037/23.063/0.557 ms
Packetloss to deham01.sixxs.net
Pim van Pelt on Friday, 12 February 2010 18:45:43
It was a ddos, according to our colleagues at Easynet.
DDoS on deham01 last night from Feb 11 18:03:33 - Feb 12 04:10:02.
State change: resolved
Pim van Pelt on Friday, 12 February 2010 18:45:57
The state of this ticket has been changed to resolved
Posting is only allowed when you are logged in. |