|
Ticket ID: SIXXS #690260 Ticket Status: Resolved PoP: dedus01 - SpeedPartner GmbH (Duesseldorf)
dedus01 ayiya - ping problems (dup!)
![[de]](/s/countries/de.gif) Shadow Hawkins on Monday, 17 March 2008 02:35:03
Hello,
I've just set up my tunnel and wanted to ping sixxs.net:
%ping6 -c4 sixxs.net
PING6(56=40+8+8 bytes) 2a01:198:200:3a::2 --> 2001:838:1:1:210:dcff:fe20:7c7c
16 bytes from 2001:838:1:1:210:dcff:fe20:7c7c, icmp_seq=0 hlim=58 time=63.603 ms
16 bytes from 2001:838:1:1:210:dcff:fe20:7c7c, icmp_seq=0 hlim=58 time=63.930 ms(DUP!)
16 bytes from 2001:838:1:1:210:dcff:fe20:7c7c, icmp_seq=1 hlim=58 time=65.564 ms
16 bytes from 2001:838:1:1:210:dcff:fe20:7c7c, icmp_seq=1 hlim=58 time=66.812 ms(DUP!)
16 bytes from 2001:838:1:1:210:dcff:fe20:7c7c, icmp_seq=2 hlim=58 time=65.650 ms
16 bytes from 2001:838:1:1:210:dcff:fe20:7c7c, icmp_seq=2 hlim=58 time=65.704 ms(DUP!)
16 bytes from 2001:838:1:1:210:dcff:fe20:7c7c, icmp_seq=3 hlim=58 time=65.121 ms
--- sixxs.net ping6 statistics ---
4 packets transmitted, 4 packets received, +3 duplicates, 0.0% packet loss
round-trip min/avg/max/std-dev = 63.603/65.198/66.812/1.025 ms
Is it a client or a server-side problem?
My Operating System is FreeBSD 6.3-Release with AICCU 2007.01.15-console-kame
State change: user
The state of this ticket has been changed to user
dedus01 ayiya - ping problems (dup!)
You will have to provide a lot more information than that, a tcpdump would be very useful. Next to a lot of other information of course, see the "Reporting Problems" checklist.
dedus01 ayiya - ping problems (dup!)
Shadow Hawkins on Monday, 17 March 2008 13:46:26
tcpdump -i tun0 Output:
tcpdump: WARNING: tun0: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on tun0, link-type NULL (BSD loopback), capture size 96 bytes
13:45:11.551694 IP6 cl-59.tunnels-dus-01.de.sixxs.net > noc.sixxs.net: ICMP6, echo request, seq 0, length 16
13:45:11.618312 IP6 noc.sixxs.net > cl-59.tunnels-dus-01.de.sixxs.net: ICMP6, echo reply, seq 0, length 16
13:45:11.618460 IP6 noc.sixxs.net > cl-59.tunnels-dus-01.de.sixxs.net: ICMP6, echo reply, seq 0, length 16
13:45:12.552218 IP6 cl-59.tunnels-dus-01.de.sixxs.net > noc.sixxs.net: ICMP6, echo request, seq 1, length 16
13:45:12.618409 IP6 noc.sixxs.net > cl-59.tunnels-dus-01.de.sixxs.net: ICMP6, echo reply, seq 1, length 16
13:45:12.618619 IP6 noc.sixxs.net > cl-59.tunnels-dus-01.de.sixxs.net: ICMP6, echo reply, seq 1, length 16
13:45:13.552204 IP6 cl-59.tunnels-dus-01.de.sixxs.net > noc.sixxs.net: ICMP6, echo request, seq 2, length 16
13:45:13.617179 IP6 noc.sixxs.net > cl-59.tunnels-dus-01.de.sixxs.net: ICMP6, echo reply, seq 2, length 16
13:45:13.617339 IP6 noc.sixxs.net > cl-59.tunnels-dus-01.de.sixxs.net: ICMP6, echo reply, seq 2, length 16
13:45:14.552199 IP6 cl-59.tunnels-dus-01.de.sixxs.net > noc.sixxs.net: ICMP6, echo request, seq 3, length 16
13:45:14.618675 IP6 noc.sixxs.net > cl-59.tunnels-dus-01.de.sixxs.net: ICMP6, echo reply, seq 3, length 16
13:45:14.618858 IP6 noc.sixxs.net > cl-59.tunnels-dus-01.de.sixxs.net: ICMP6, echo reply, seq 3, length 16
13:45:15.552192 IP6 cl-59.tunnels-dus-01.de.sixxs.net > noc.sixxs.net: ICMP6, echo request, seq 4, length 16
13:45:15.621668 IP6 noc.sixxs.net > cl-59.tunnels-dus-01.de.sixxs.net: ICMP6, echo reply, seq 4, length 16
13:45:15.621957 IP6 noc.sixxs.net > cl-59.tunnels-dus-01.de.sixxs.net: ICMP6, echo reply, seq 4, length 16
13:45:16.552190 IP6 cl-59.tunnels-dus-01.de.sixxs.net > noc.sixxs.net: ICMP6, echo request, seq 5, length 16
13:45:16.617792 IP6 noc.sixxs.net > cl-59.tunnels-dus-01.de.sixxs.net: ICMP6, echo reply, seq 5, length 16
13:45:16.617977 IP6 noc.sixxs.net > cl-59.tunnels-dus-01.de.sixxs.net: ICMP6, echo reply, seq 5, length 16
^C
18 packets captured
18 packets received by filter
0 packets dropped by kernel
%ping6 sixxs.net
PING6(56=40+8+8 bytes) 2a01:198:200:3a::2 --> 2001:838:1:1:210:dcff:fe20:7c7c
16 bytes from 2001:838:1:1:210:dcff:fe20:7c7c, icmp_seq=0 hlim=58 time=66.840 ms
16 bytes from 2001:838:1:1:210:dcff:fe20:7c7c, icmp_seq=0 hlim=58 time=66.902 ms(DUP!)
16 bytes from 2001:838:1:1:210:dcff:fe20:7c7c, icmp_seq=1 hlim=58 time=66.373 ms
16 bytes from 2001:838:1:1:210:dcff:fe20:7c7c, icmp_seq=1 hlim=58 time=66.572 ms(DUP!)
16 bytes from 2001:838:1:1:210:dcff:fe20:7c7c, icmp_seq=2 hlim=58 time=65.075 ms
16 bytes from 2001:838:1:1:210:dcff:fe20:7c7c, icmp_seq=2 hlim=58 time=65.240 ms(DUP!)
16 bytes from 2001:838:1:1:210:dcff:fe20:7c7c, icmp_seq=3 hlim=58 time=66.573 ms
16 bytes from 2001:838:1:1:210:dcff:fe20:7c7c, icmp_seq=3 hlim=58 time=66.738 ms(DUP!)
16 bytes from 2001:838:1:1:210:dcff:fe20:7c7c, icmp_seq=4 hlim=58 time=69.572 ms
16 bytes from 2001:838:1:1:210:dcff:fe20:7c7c, icmp_seq=4 hlim=58 time=69.846 ms(DUP!)
16 bytes from 2001:838:1:1:210:dcff:fe20:7c7c, icmp_seq=5 hlim=58 time=65.697 ms
16 bytes from 2001:838:1:1:210:dcff:fe20:7c7c, icmp_seq=5 hlim=58 time=65.864 ms(DUP!)
dedus01 ayiya - ping problems (dup!)
Shadow Hawkins on Monday, 17 March 2008 13:48:57
Here is also a 'traceroute6' output:
traceroute6 to sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) from 2a01:198:200:3a::2, 64 hops max, 12 byte packets
1 gw-59.tunnels-dus-01.de.sixxs.net 53.995 ms 54.649 ms 53.721 ms
2 edge1.dus1.de.as34225.net 55.973 ms 54.786 ms 55.281 ms
3 speedpartner.r1.dus1.de.opencarrier.eu 54.126 ms 54.782 ms 54.274 ms
4 oc-r1-dus1.r1.fra3.de.opencarrier.eu 60.275 ms 60.000 ms 58.907 ms
5 ge6-0.br0.fra2.de.gbxs.net 62.069 ms 61.810 ms 60.831 ms
6 ge-3-3-4.bb2.bru1.be.gbxs.net 64.597 ms 64.149 ms 63.765 ms
7 ams-ix2.ipv6.concepts.nl 64.109 ms 67.192 ms 69.099 ms
8 2001:838:0:14::2 63.981 ms 69.366 ms 64.275 ms
9 2001:838:0:10::2 584.427 ms 66.107 ms 64.896 ms
10 noc.sixxs.net 65.341 ms 65.259 ms 67.084 ms
dedus01 ayiya - ping problems (dup!)
Shadow Hawkins on Monday, 17 March 2008 14:39:45
Just want to add that the problem also appears on OpenSuSE 10.0 / Kernel 2.6.13-15.18-default, same aiccu version. The duplicates can be seen on the V4 interface also (just to confirm that they are not generated during deencapsulation). My tunnel ID is T14693. Maybe as a side effect, packet loss statistics show 200% packet loss.
14:08:35.348628 IP 192.168.18.1.1090 > 91.184.37.98.5072: UDP, length: 148
14:08:35.385485 IP 91.184.37.98.5072 > 192.168.18.1.1090: UDP, length: 148
14:08:35.385495 IP 91.184.37.98.5072 > 192.168.18.1.1090: UDP, length: 148
14:08:36.354815 IP 192.168.18.1.1090 > 91.184.37.98.5072: UDP, length: 148
14:08:36.392062 IP 91.184.37.98.5072 > 192.168.18.1.1090: UDP, length: 148
14:08:36.392071 IP 91.184.37.98.5072 > 192.168.18.1.1090: UDP, length: 148
ping6 2001:838:1:1:210:dcff:fe20:7c7c
PING 2001:838:1:1:210:dcff:fe20:7c7c(2001:838:1:1:210:dcff:fe20:7c7c) 56 data bytes
64 bytes from 2001:838:1:1:210:dcff:fe20:7c7c: icmp_seq=1 ttl=58 time=38.0 ms
64 bytes from 2001:838:1:1:210:dcff:fe20:7c7c: icmp_seq=1 ttl=58 time=38.1 ms (DUP!)
64 bytes from 2001:838:1:1:210:dcff:fe20:7c7c: icmp_seq=2 ttl=58 time=37.7 ms
64 bytes from 2001:838:1:1:210:dcff:fe20:7c7c: icmp_seq=2 ttl=58 time=37.8 ms (DUP!)
dedus01 ayiya - ping problems (dup!)
Before your tunnel went offline it was actually replying with two identical ICMPv6 packets at a time, thus not so weird that you then, properly, get two back.
Tunnel is down now, thus can't check anything further.
dedus01 ayiya - ping problems (dup!)
Shadow Hawkins on Monday, 17 March 2008 15:38:22
Just to avoid misunderstandings, I am not related to the original poster,
I just wanted to add this information to show that it might not be a problem related to the ticket opener setup but also affects other users on this POP, also with different OSses. My tunnel is still up, it is available for testing.
dedus01 ayiya - ping problems (dup!)
Shadow Hawkins on Monday, 17 March 2008 15:44:06
BTW:
When I ping ipv6.google.com I get duplicates, when I connect to TCP port 80 there are no dups:
15:39:35.154846 IP6 2a01:198:200:35::2.10874 > 2001:4860:0:1001::68.80: S 1182782389:1182782389(0) win 4880 <mss 1220,sackOK,timestamp 5409037 0,nop,wscale 2>
15:39:35.311882 IP6 2001:4860:0:1001::68.80 > 2a01:198:200:35::2.10874: S 3156001770:3156001770(0) ack 1182782390 win 8190 <mss 1212>
15:39:35.311923 IP6 2a01:198:200:35::2.10874 > 2001:4860:0:1001::68.80: . ack 1 win 4880
15:39:35.320419 IP6 2001:4860:0:1001::68.80 > 2a01:198:200:35::2.10874: S 3156001770:3156001770(0) ack 1182782390 win 8190 <mss 1212>
15:39:35.320441 IP6 2a01:198:200:35::2.10874 > 2001:4860:0:1001::68.80: . ack 1 win 4880
15:39:37.745782 IP6 2a01:198:200:35::2.10874 > 2001:4860:0:1001::68.80: F 1:1(0) ack 1 win 4880
15:39:37.879423 IP6 2001:4860:0:1001::68.80 > 2a01:198:200:35::2.10874: F 1:1(0) ack 2 win 8190
15:39:37.879463 IP6 2a01:198:200:35::2.10874 > 2001:4860:0:1001::68.80: . ack 2 win 4880
State change: confirmed
The state of this ticket has been changed to confirmed
dedus01 ayiya - ping problems (dup!)
Latest codedrop has caused this apparently. Resolving the problem now.
State change: resolved
The state of this ticket has been changed to resolved
dedus01 ayiya - ping problems (dup!)
Fixed code drop running on affected PoPs, problem resolved. Thanks for reporting this problem.
dedus01 ayiya - ping problems (dup!)
Shadow Hawkins on Thursday, 23 September 2010 13:26:56
hi,
since this morning the machine get ping duplicates.
ping6 -i 90 www.google.de
PING www.google.de(2a00:1450:4007:800::68) 56 data bytes
64 bytes from 2a00:1450:4007:800::68: icmp_seq=1 ttl=56 time=40.8 ms
64 bytes from 2a00:1450:4007:800::68: icmp_seq=1 ttl=56 time=40.9 ms (DUP!)
64 bytes from 2a00:1450:4007:800::68: icmp_seq=1 ttl=56 time=41.7 ms (DUP!)
64 bytes from 2a00:1450:4007:800::68: icmp_seq=1 ttl=56 time=41.7 ms (DUP!)
The tunnel statistics contains a lot of lost pakets.
dedus01 ayiya - ping problems (dup!)
1 ICMPv6 packet sent to your endpoints causes one IPv4 AYIYA packet to be sent with that ping in it and it replies with 3 packets...
dedus01 ayiya - ping problems (dup!)
Shadow Hawkins on Thursday, 23 September 2010 15:57:55
hi,
thanks for response .. is it a problem or is this behavior OK? never seen such dupe packets before.
dedus01 ayiya - ping problems (dup!)
That behavior is not ok of course. Check your host why it is doing that.
|
![[ch]](/s/countries/ch.gif)
on Monday, 17 March 2008 10:55:28
Posting is only allowed when you are