Wireshark
the world's foremost network protocol analyzer
Wireshark-users: Re: [Wireshark-users] [TCP Previous segment lost], TCP [TCP Dup ACK 125#1]
From: dan meyer <dan@xxxxxxxxxxxxxxxx>
Date: Tue, 8 Sep 2009 09:33:06 -0500
Did you perform your ping test with large (IE 1400 byte) packets? The default payload size for the typical ping utility is 32 bytes. A marginal link can look good passing this smaller packet, and fail when a larger packet is used.
-- Dan Meyer
On Tue, Sep 8, 2009 at 8:23 AM, Nikolai Longolius <longolius@xxxxxxxxxxxxxx> wrote:
Martin + Jeffrey,
thanks for your quick response. In the meantime I am in contact with the ISP who "produces" the packet loss. At least I hope its them. Its pretty hard to find out who's the bad guy in the chain. I did use mtr on my mac to trace + ping all hosts on the route but that didn't turn out any useful information to me.
Am I right, that from Wireshark capturing there is no way to reconstruct on what route a packet got lost?
Regards,
Nikolai
--
Nikolai Longolius
schnee von morgen webTV GmbH
Manteuffelstr 66
10999 Berlin
M +49 170 4777 477
___________________________________________________________________________
Sent via: Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives: http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe
- References:
- Re: [Wireshark-users] [TCP Previous segment lost], TCP [TCP Dup ACK 125#1]
- From: Nikolai Longolius
- Re: [Wireshark-users] [TCP Previous segment lost], TCP [TCP Dup ACK 125#1]
- Prev by Date: Re: [Wireshark-users] RTP Capture filter
- Next by Date: Re: [Wireshark-users] RTP Capture filter
- Previous by thread: Re: [Wireshark-users] [TCP Previous segment lost], TCP [TCP Dup ACK 125#1]
- Next by thread: Re: [Wireshark-users] [TCP Previous segment lost], TCP [TCP Dup ACK 125#1]
- Index(es):