SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #1113824
Ticket Status: User

PoP: dedus01 - SpeedPartner GmbH (Duesseldorf)

High Latency and Packet Loss on 2a01:198:200::1
[de] Shadow Hawkins on Sunday, 14 June 2009 12:56:23
Incident Description: ping6 shows, that a certain Node at dedus01 raises latency and sometimes drops packets, while my gateway at dedus01 respondes in time. Antwort von 2a01:198:200::1: Zeit=38ms Antwort von 2a01:198:200::1: Zeit=38ms Antwort von 2a01:198:200::1: Zeit=189ms Antwort von 2a01:198:200::1: Zeit=38ms Antwort von 2a01:198:200::1: Zeit=38ms Antwort von 2a01:198:200::1: Zeit=38ms Antwort von 2a01:198:200::1: Zeit=38ms Antwort von 2a01:198:200::1: Zeit=38ms Antwort von 2a01:198:200::1: Zeit=38ms Antwort von 2a01:198:200::1: Zeit=38ms Antwort von 2a01:198:200::1: Zeit=38ms Antwort von 2a01:198:200::1: Zeit=38ms Antwort von 2a01:198:200::1: Zeit=38ms Antwort von 2a01:198:200::1: Zeit=38ms Antwort von 2a01:198:200::1: Zeit=38ms Antwort von 2a01:198:200::1: Zeit=39ms Antwort von 2a01:198:200::1: Zeit=39ms Antwort von 2a01:198:200::1: Zeit=38ms Zeitberschreitung der Anforderung. Antwort von 2a01:198:200::1: Zeit=96ms Antwort von 2a01:198:200::1: Zeit=38ms Antwort von 2a01:198:200:10c::1: Zeit=37ms Antwort von 2a01:198:200:10c::1: Zeit=38ms Antwort von 2a01:198:200:10c::1: Zeit=37ms Antwort von 2a01:198:200:10c::1: Zeit=37ms Antwort von 2a01:198:200:10c::1: Zeit=37ms Antwort von 2a01:198:200:10c::1: Zeit=38ms Antwort von 2a01:198:200:10c::1: Zeit=38ms Antwort von 2a01:198:200:10c::1: Zeit=37ms Antwort von 2a01:198:200:10c::1: Zeit=38ms Antwort von 2a01:198:200:10c::1: Zeit=37ms Antwort von 2a01:198:200:10c::1: Zeit=37ms Antwort von 2a01:198:200:10c::1: Zeit=38ms Antwort von 2a01:198:200:10c::1: Zeit=37ms Antwort von 2a01:198:200:10c::1: Zeit=37ms Antwort von 2a01:198:200:10c::1: Zeit=38ms Antwort von 2a01:198:200:10c::1: Zeit=37ms Antwort von 2a01:198:200:10c::1: Zeit=37ms Antwort von 2a01:198:200:10c::1: Zeit=37ms Antwort von 2a01:198:200:10c::1: Zeit=38ms Antwort von 2a01:198:200:10c::1: Zeit=38ms Antwort von 2a01:198:200:10c::1: Zeit=37ms Antwort von 2a01:198:200:10c::1: Zeit=38ms Antwort von 2a01:198:200:10c::1: Zeit=37ms Antwort von 2a01:198:200:10c::1: Zeit=38ms Antwort von 2a01:198:200:10c::1: Zeit=38ms Antwort von 2a01:198:200:10c::1: Zeit=37ms Antwort von 2a01:198:200:10c::1: Zeit=37ms Result: www.google.com over ipv6 gets slow, as we have packetloss Antwort von 2001:838:1:1:210:dcff:fe20:7c7c: Zeit=158ms Antwort von 2001:838:1:1:210:dcff:fe20:7c7c: Zeit=49ms Antwort von 2001:838:1:1:210:dcff:fe20:7c7c: Zeit=75ms Antwort von 2001:838:1:1:210:dcff:fe20:7c7c: Zeit=48ms Antwort von 2001:838:1:1:210:dcff:fe20:7c7c: Zeit=49ms Antwort von 2001:838:1:1:210:dcff:fe20:7c7c: Zeit=49ms Zeitberschreitung der Anforderung. Antwort von 2001:838:1:1:210:dcff:fe20:7c7c: Zeit=48ms Antwort von 2001:838:1:1:210:dcff:fe20:7c7c: Zeit=49ms Antwort von 2001:838:1:1:210:dcff:fe20:7c7c: Zeit=339ms My connection is a Fritz!Box with IPv6 Patch provided by AVM. Since I have no problem reaching my PoP counterpart, I would dare to say that HW here is faulty. We are talking about this: Tunnel information T15***dedus01 - SpeedPartner GmbH heartbeat2a01:198:200:10c::2AVM FritzBox 7270 wlan Draft-N-RouterEnabled The IPv4 Ping at the same time to the router that drops packets Antwort von 91.184.32.133: Bytes=1400 Zeit=35ms TTL=56 Antwort von 91.184.32.133: Bytes=1400 Zeit=35ms TTL=56 Antwort von 91.184.32.133: Bytes=1400 Zeit=36ms TTL=56 Antwort von 91.184.32.133: Bytes=1400 Zeit=36ms TTL=56 Antwort von 91.184.32.133: Bytes=1400 Zeit=35ms TTL=56 Antwort von 91.184.32.133: Bytes=1400 Zeit=37ms TTL=56 Antwort von 91.184.32.133: Bytes=1400 Zeit=36ms TTL=56 Antwort von 91.184.32.133: Bytes=1400 Zeit=36ms TTL=56 Antwort von 91.184.32.133: Bytes=1400 Zeit=36ms TTL=56 Antwort von 91.184.32.133: Bytes=1400 Zeit=36ms TTL=56 Antwort von 91.184.32.133: Bytes=1400 Zeit=35ms TTL=56 Antwort von 91.184.32.133: Bytes=1400 Zeit=35ms TTL=56 Antwort von 91.184.32.133: Bytes=1400 Zeit=36ms TTL=56 Antwort von 91.184.32.133: Bytes=1400 Zeit=36ms TTL=56 Zero drops Thanks for following up. Remark: Since I have this connection terminated on an embedded device, it's hard to deliver all Interface info. Kind Regards, Martin
State change: user Locked
[ch] Jeroen Massar SixXS Staff on Sunday, 14 June 2009 21:12:44
Message is Locked
The state of this ticket has been changed to user
High Latency and Packet Loss on 2a01:198:200::1
[ch] Jeroen Massar SixXS Staff on Sunday, 14 June 2009 21:15:44
ping6 shows, that a certain Node at dedus01 raises latency and sometimes drops
packets, while my gateway at dedus01 respondes in time.
I am not quite sure what you mean with the above "certain Node at dedus01" but that your "gateway at dedus01" actually works. I am assuming that you mean that there is some kind of latency issue, seeing that you are randomly pinging things. Please actually realize that between you and the PoP there are a lot of hops in the network which might be causing this.

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker