Am 02. Feb 2013 um 15:32 CET schrieb ich: > Am 02. Feb 2013 um 13:52 CET schrieb Marc Haber: > > Mach mal tcpdump auf dem Interface und schau, was passiert, während > > die RTT länger wird. Sieht man ARP-Requests und ARP-Replies in diesem > > Moment? Oder anderen Traffic? > > Immer wenn der ping Verzögerungen zeigt, dann gibt tcpdump folgendes > aus: > > ,----[ tcpdump -i wlan0 ] > | 15:23:54.532744 IP 192.168.52.4 > bk-in-f94.1e100.net: ICMP echo request, id 5843, seq 72, length 64 > | 15:23:54.565156 IP bk-in-f94.1e100.net > 192.168.52.4: ICMP echo reply, id 5843, seq 72, length 64 > | 15:23:55.534434 IP 192.168.52.4 > bk-in-f94.1e100.net: ICMP echo request, id 5843, seq 73, length 64 > | 15:23:55.591607 IP bk-in-f94.1e100.net > 192.168.52.4: ICMP echo reply, id 5843, seq 73, length 64 > | 15:23:56.535829 IP 192.168.52.4 > bk-in-f94.1e100.net: ICMP echo request, id 5843, seq 74, length 64 > | 15:23:56.584991 IP bk-in-f94.1e100.net > 192.168.52.4: ICMP echo reply, id 5843, seq 74, length 64 > | 15:23:57.537220 IP 192.168.52.4 > bk-in-f94.1e100.net: ICMP echo request, id 5843, seq 75, length 64 > | 15:23:57.553020 ARP, Request who-has 192.168.52.4 tell router, length 28 > | 15:23:57.553037 ARP, Reply 192.168.52.4 is-at d8:5d:4c:9f:f0:77 (oui Unknown), length 28 > | 15:23:57.577645 IP bk-in-f94.1e100.net > 192.168.52.4: ICMP echo reply, id 5843, seq 75, length 64 > | 15:23:58.538853 IP 192.168.52.4 > bk-in-f94.1e100.net: ICMP echo request, id 5843, seq 76, length 64 > | 15:23:58.553174 ARP, Request who-has 192.168.52.4 tell router, length 28 > | 15:23:58.553183 ARP, Reply 192.168.52.4 is-at d8:5d:4c:9f:f0:77 (oui Unknown), length 28 > | 15:23:59.545985 IP 192.168.52.4 > bk-in-f94.1e100.net: ICMP echo request, id 5843, seq 77, length 64 > | 15:23:59.553221 ARP, Request who-has 192.168.52.4 tell router, length 28 > | 15:23:59.553237 ARP, Reply 192.168.52.4 is-at d8:5d:4c:9f:f0:77 (oui Unknown), length 28 Ich habe noch mal mit meinem anderen wlan Stick getestet und mit dem liefert der ping Befehl keinerlei Auffälligkeiten, obwohl tcpdump dort ähnliche Meldungen zeigt: ,---- | 17:48:01.738221 IP 192.168.52.4 > bk-in-f160.1e100.net: ICMP echo request, id 11125, seq 40, length 64 | 17:48:01.765627 IP bk-in-f160.1e100.net > 192.168.52.4: ICMP echo reply, id 11125, seq 40, length 64 | 17:48:02.739840 IP 192.168.52.4 > bk-in-f160.1e100.net: ICMP echo request, id 11125, seq 41, length 64 | 17:48:02.768148 IP bk-in-f160.1e100.net > 192.168.52.4: ICMP echo reply, id 11125, seq 41, length 64 | 17:48:03.741348 IP 192.168.52.4 > bk-in-f160.1e100.net: ICMP echo request, id 11125, seq 42, length 64 | 17:48:03.768412 IP bk-in-f160.1e100.net > 192.168.52.4: ICMP echo reply, id 11125, seq 42, length 64 | 17:48:04.742606 IP 192.168.52.4 > bk-in-f160.1e100.net: ICMP echo request, id 11125, seq 43, length 64 | 17:48:04.770303 IP bk-in-f160.1e100.net > 192.168.52.4: ICMP echo reply, id 11125, seq 43, length 64 | 17:48:05.744521 IP 192.168.52.4 > bk-in-f160.1e100.net: ICMP echo request, id 11125, seq 44, length 64 | 17:48:05.771445 IP bk-in-f160.1e100.net > 192.168.52.4: ICMP echo reply, id 11125, seq 44, length 64 | 17:48:06.664458 ARP, Request who-has 192.168.52.4 tell raspi.potato.lan, length 46 | 17:48:06.664470 ARP, Reply 192.168.52.4 is-at 74:ea:3a:8e:e3:84 (oui Unknown), length 28 | 17:48:06.745655 IP 192.168.52.4 > bk-in-f160.1e100.net: ICMP echo request, id 11125, seq 45, length 64 | 17:48:06.773706 IP bk-in-f160.1e100.net > 192.168.52.4: ICMP echo reply, id 11125, seq 45, length 64 | 17:48:07.231289 IP 192.168.52.4.ipp > 192.168.52.255.ipp: UDP, length 222 | 17:48:07.746914 IP 192.168.52.4 > bk-in-f160.1e100.net: ICMP echo request, id 11125, seq 46, length 64 | 17:48:07.759967 ARP, Request who-has 192.168.52.4 tell router, length 28 | 17:48:07.759975 ARP, Reply 192.168.52.4 is-at 74:ea:3a:8e:e3:84 (oui Unknown), length 28 | 17:48:07.774215 IP bk-in-f160.1e100.net > 192.168.52.4: ICMP echo reply, id 11125, seq 46, length 64 | 17:48:08.748412 IP 192.168.52.4 > bk-in-f160.1e100.net: ICMP echo request, id 11125, seq 47, length 64 | 17:48:08.775992 IP bk-in-f160.1e100.net > 192.168.52.4: ICMP echo reply, id 11125, seq 47, length 64 | 17:48:09.750233 IP 192.168.52.4 > bk-in-f160.1e100.net: ICMP echo request, id 11125, seq 48, length 64 | 17:48:09.778002 IP bk-in-f160.1e100.net > 192.168.52.4: ICMP echo reply, id 11125, seq 48, length 64 | 17:48:10.751224 IP 192.168.52.4 > bk-in-f160.1e100.net: ICMP echo request, id 11125, seq 49, length 64 | 17:48:10.777895 IP bk-in-f160.1e100.net > 192.168.52.4: ICMP echo reply, id 11125, seq 49, length 64 | 17:48:11.753096 IP 192.168.52.4 > bk-in-f160.1e100.net: ICMP echo request, id 11125, seq 50, length 64 | 17:48:11.779032 IP bk-in-f160.1e100.net > 192.168.52.4: ICMP echo reply, id 11125, seq 50, length 64 | 17:48:12.754230 IP 192.168.52.4 > bk-in-f160.1e100.net: ICMP echo request, id 11125, seq 51, length 64 | 17:48:12.781930 IP bk-in-f160.1e100.net > 192.168.52.4: ICMP echo reply, id 11125, seq 51, length 64 | 17:48:13.756171 IP 192.168.52.4 > bk-in-f160.1e100.net: ICMP echo request, id 11125, seq 52, length 64 | 17:48:13.783188 IP bk-in-f160.1e100.net > 192.168.52.4: ICMP echo reply, id 11125, seq 52, length 64 | 17:48:14.757386 IP 192.168.52.4 > bk-in-f160.1e100.net: ICMP echo request, id 11125, seq 53, length 64 | 17:48:14.783701 IP bk-in-f160.1e100.net > 192.168.52.4: ICMP echo reply, id 11125, seq 53, length 64 | 17:48:15.758895 IP 192.168.52.4 > bk-in-f160.1e100.net: ICMP echo request, id 11125, seq 54, length 64 | 17:48:15.786719 IP bk-in-f160.1e100.net > 192.168.52.4: ICMP echo reply, id 11125, seq 54, length 64 `---- Gruß Stefan -- ,-----------------------------------------------------------------------------. | Stefan Lütje | "Ich ahne, wovon ich spreche, meine | | stefan.luetje@t-online.de | Damen und Herren." Angela Merkel | `----Key fingerprint = BCB2 48E4 9211 C975 5A3F B192 9B6E CCCF 99CC 44FA-----'
Attachment:
signature.asc
Description: Digital signature