|
Ticket ID: SIXXS #4851501 Ticket Status: Remote Problem PoP: simbx01 - Amis (Maribor)
Packet loss to simbx01
![[ru]](/s/countries/ru.gif) Shadow Hawkins on Sunday, 05 June 2011 11:36:51
Dear SixXS support team,
I'm suffering from a packet loss problem for by ipv6 tunnel.
Tunnel number is T67237. My PoP is simbx01.
Traceroute to this PoP from my host looks like this (I have removed first two lines with intranet addresses):
3 b57-2-gw.spb.runnet.ru (194.85.36.221) 1.735 ms 1.613 ms 1.911 ms
4 b57-1-gw.spb.runnet.ru (194.85.40.205) 36.113 ms 37.802 ms 36.072 ms
5 kt12-1-gw.spb.runnet.ru (194.85.40.154) 36.089 ms 36.063 ms 36.075 ms
6 tug11-1-gw.sth.runnet.ru (194.85.40.142) 36.027 ms 36.230 ms 36.083 ms
7 hikhef-1-gw.ams.runnet.ru (194.85.40.241) 36.171 ms 36.470 ms 36.173 ms
8 gi9-10.mpd01.ams04.atlas.cogentco.com (130.117.23.61) 36.156 ms 37.307 ms 36.758 ms
9 te0-0-0-7.ccr21.ams03.atlas.cogentco.com (130.117.49.13) 36.340 ms
te0-4-0-5.ccr21.ams03.atlas.cogentco.com (154.54.39.109) 36.333 ms
te0-4-0-5.mpd21.ams03.atlas.cogentco.com (154.54.39.105) 36.496 ms
10 te0-3-0-1.mpd22.fra03.atlas.cogentco.com (154.54.39.186) 43.526 ms
te0-2-0-1.ccr22.fra03.atlas.cogentco.com (130.117.3.90) 43.209 ms
te0-3-0-3.ccr22.fra03.atlas.cogentco.com (154.54.39.198) 43.123 ms
11 te0-2-0-0.ccr21.muc01.atlas.cogentco.com (130.117.2.206) 55.427 ms
te0-1-0-0.ccr21.muc01.atlas.cogentco.com (130.117.0.66) 55.082 ms
te0-3-0-0.ccr22.muc01.atlas.cogentco.com (154.54.39.18) 48.521 ms
12 te4-1.ccr01.vie01.atlas.cogentco.com (130.117.49.30) 55.079 ms
te2-1.ccr01.vie01.atlas.cogentco.com (130.117.51.233) 55.003 ms
te3-1.ccr01.vie01.atlas.cogentco.com (130.117.3.22) 54.831 ms
13 te1-2.ccr01.lju01.atlas.cogentco.com (130.117.48.82) 60.788 ms 60.683 ms 60.991 ms
14 149.6.52.34 (149.6.52.34) 61.817 ms
149.6.52.38 (149.6.52.38) 61.321 ms 61.807 ms
15 maribor3-te-1-1.amis.net (212.18.35.233) 59.893 ms 59.774 ms 60.193 ms
16 * simbx01.sixxs.net (212.18.63.73) 59.913 ms 59.760 ms
There's no packet loss up to the 15th hop in this list:
# ping -q -i 0.1 -c 100 212.18.35.233
PING 212.18.35.233 (212.18.35.233): 56 data bytes
--- 212.18.35.233 ping statistics ---
100 packets transmitted, 100 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 59.638/60.104/68.962/1.221 ms
However, situation with simbx01 is much worse:
# ping -q -i 0.1 -c 100 212.18.63.73
PING 212.18.63.73 (212.18.63.73): 56 data bytes
--- 212.18.63.73 ping statistics ---
100 packets transmitted, 56 packets received, 44.0% packet loss
round-trip min/avg/max/stddev = 59.732/62.905/227.080/22.138 ms
It affects ipv6 traffic in the tunnel as well and "Loss statistics" graph comfirms that.
State change: remoteproblem
The state of this ticket has been changed to remoteproblem
Packet loss to simbx01
Packet loss can happen in both directions, thus also packets on the way back might be lost. Note also that there might be ICMP ratelimiters at any number of hops. There is not much we can do about this.
As you can see from the traceroute though you are going all the way through Europe which is far from ideal.
Packet loss to simbx01
![[at]](/s/countries/at.gif) Shadow Hawkins on Friday, 10 June 2011 14:38:54
I'm also experiencing packet loss issues (since at least yesterday) and I don't have to route my packets through more than two countries. IPv4 connections generally don't have any issues, only IPv6 connections are intolerably slow.
Are there no other reports of packet losses?
IPv4 Ping
ping -4 -n 10 simbx01.sixxs.net
Ping wird ausgefhrt fr simbx01.sixxs.net [212.18.63.73] mit 32 Bytes Daten:
Zeitberschreitung der Anforderung.
Antwort von 212.18.63.73: Bytes=32 Zeit=16ms TTL=58
Antwort von 212.18.63.73: Bytes=32 Zeit=17ms TTL=58
Zeitberschreitung der Anforderung.
Antwort von 212.18.63.73: Bytes=32 Zeit=16ms TTL=58
Zeitberschreitung der Anforderung.
Antwort von 212.18.63.73: Bytes=32 Zeit=16ms TTL=58
Antwort von 212.18.63.73: Bytes=32 Zeit=1224ms TTL=58
Antwort von 212.18.63.73: Bytes=32 Zeit=16ms TTL=58
Antwort von 212.18.63.73: Bytes=32 Zeit=15ms TTL=58
Ping-Statistik fr 212.18.63.73:
Pakete: Gesendet = 10, Empfangen = 7, Verloren = 3
(30% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 15ms, Maximum = 1224ms, Mittelwert = 188ms
IPv6 Ping
ping -n 10 simbx01.sixxs.net
Ping wird ausgefhrt fr simbx01.sixxs.net [2001:15c0:ffff:7::2] mit 32 Bytes Daten:
Antwort von 2001:15c0:ffff:7::2: Zeit=16ms
Antwort von 2001:15c0:ffff:7::2: Zeit=17ms
Zeitberschreitung der Anforderung.
Antwort von 2001:15c0:ffff:7::2: Zeit=18ms
Zeitberschreitung der Anforderung.
Antwort von 2001:15c0:ffff:7::2: Zeit=18ms
Antwort von 2001:15c0:ffff:7::2: Zeit=17ms
Zeitberschreitung der Anforderung.
Zeitberschreitung der Anforderung.
Antwort von 2001:15c0:ffff:7::2: Zeit=17ms
Ping-Statistik fr 2001:15c0:ffff:7::2:
Pakete: Gesendet = 10, Empfangen = 6, Verloren = 4
(40% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 16ms, Maximum = 18ms, Mittelwert = 17ms
IPv4 Traceroute
tracert -4 simbx01.sixxs.net
Routenverfolgung zu simbx01.sixxs.net [212.18.63.73] ber maximal 30 Abschnitte:
1 12 ms 99 ms 99 ms gateway.---.local [192.168.0.254]
2 14 ms 14 ms 14 ms 079-110-220-077.ascus.at [77.220.110.79]
3 16 ms 14 ms 14 ms 093-082-143-095.as39912.net [95.143.82.93]
4 14 ms 13 ms 14 ms 010-082-143-095.as39912.net [95.143.82.10]
5 29 ms 803 ms 29 ms vix.amis.net [193.203.0.117]
6 32 ms 32 ms 32 ms maribor3-te-1-3.amis.net [212.18.39.213]
7 * 18 ms 18 ms simbx01.sixxs.net [212.18.63.73]
Ablaufverfolgung beendet.
IPv6 Traceroute
tracert simbx01.sixxs.net
Routenverfolgung zu simbx01.sixxs.net [2001:15c0:ffff:7::2] ber maximal 30 Abschnitte:
1 1 ms <1 ms <1 ms ipv6gw.---.local [2001:15c0:66b5::254]
2 * * 18 ms simbx01.sixxs.net [2001:15c0:ffff:7::2]
Ablaufverfolgung beendet.
Pathping
pathping -4 simbx01.sixxs.net
Routenverfolgung zu simbx01.sixxs.net [212.18.63.73]
ber maximal 30 Abschnitte:
0 ---.---local [192.168.0.13]
1 gateway.---.local [192.168.0.254]
2 079-110-220-077.ascus.at [77.220.110.79]
3 093-082-143-095.as39912.net [95.143.82.93]
4 010-082-143-095.as39912.net [95.143.82.10]
5 vix.amis.net [193.203.0.117]
6 maribor3-te-1-3.amis.net [212.18.39.213]
7 simbx01.sixxs.net [212.18.63.73]
Berechnung der Statistiken dauert ca. 175 Sekunden...
Quelle zum Abs. Knoten/Verbindung
Abs. Zeit Verl./Ges.= % Verl./Ges.= % Adresse
0 ---.---.local [192.168.0.13]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% gateway.---.local [192.168.0.254]
0/ 100 = 0% |
2 15ms 0/ 100 = 0% 0/ 100 = 0% 079-110-220-077.ascus.at [77.220.110.79]
0/ 100 = 0% |
3 43ms 0/ 100 = 0% 0/ 100 = 0% 093-082-143-095.as39912.net [95.143.82.93]
0/ 100 = 0% |
4 21ms 0/ 100 = 0% 0/ 100 = 0% 010-082-143-095.as39912.net [95.143.82.10]
0/ 100 = 0% |
5 64ms 0/ 100 = 0% 0/ 100 = 0% vix.amis.net [193.203.0.117]
0/ 100 = 0% |
6 34ms 0/ 100 = 0% 0/ 100 = 0% maribor3-te-1-3.amis.net [212.18.39.213]
41/ 100 = 41% |
7 63ms 41/ 100 = 41% 0/ 100 = 0% simbx01.sixxs.net [212.18.63.73]
Ablaufverfolgung beendet.
Packet loss to simbx01
![[si]](/s/countries/si.gif) Shadow Hawkins on Friday, 10 June 2011 16:50:32
I also have problems with this PoP and I'm in the same country. Packet loss is even on the same network (Amis).
It seems something is wrong at Amis. Would someone look at this as IPv6 is almost unusable last days.
Packet loss to simbx01
Shadow Hawkins on Wednesday, 06 July 2011 11:10:36
Still packet loss to this POP, and this is now for weeks (months). And it seems nobody cares ? It's almost unusable.
ping -c 10 212.18.63.73
PING 212.18.63.73 (212.18.63.73) 56(84) bytes of data.
64 bytes from 212.18.63.73: icmp_req=1 ttl=60 time=39.3 ms
64 bytes from 212.18.63.73: icmp_req=4 ttl=60 time=39.5 ms
64 bytes from 212.18.63.73: icmp_req=7 ttl=60 time=38.3 ms
64 bytes from 212.18.63.73: icmp_req=8 ttl=60 time=38.3 ms
64 bytes from 212.18.63.73: icmp_req=10 ttl=60 time=39.3 ms
--- 212.18.63.73 ping statistics ---
10 packets transmitted, 5 received, 50% packet loss, time 9029ms
rtt min/avg/max/mdev = 38.310/38.982/39.595/0.562 ms
Packet loss to simbx01
![[hr]](/s/countries/hr.gif) Shadow Hawkins on Thursday, 30 June 2011 07:11:35
My NIC handle: VON1-SIXXS
My Tunnel ID: T72701
I just started using the service and am disappointed with the POP.
It is the closest located and the ping time itself is nice.
Sadly I'm suffering a rather large packet loss on IPv4 to the POP itself
Ping statistics for 212.18.63.73:
Packets: Sent = 447, Received = 372, Lost = 75 (16% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 1421ms, Average = 39ms
No wonder my
Packet loss to simbx01
Shadow Hawkins on Thursday, 30 June 2011 07:16:26
Also, here's the IPv4 traceroute:
3 8 ms 8 ms 8 ms 172.29.16.129
4 9 ms 9 ms 9 ms gtr10-gdr10.ip.t-com.hr [195.29.240.105]
5 72 ms 226 ms 219 ms vix.amis.net [193.203.0.117]
6 19 ms 19 ms 20 ms 212.18.44.149
7 32 ms 32 ms 32 ms simbx01.sixxs.net [212.18.63.73]
|
![[ch]](/s/countries/ch.gif)
on Sunday, 05 June 2011 11:39:05
Posting is only allowed when you are