Wireshark-users: Re: [Wireshark-users] [TCP Previous segment lost], TCP [TCP Dup ACK 125#1], RTM
Your trace unfortunately doesn't really show the root cause of your packet loss. The main data traffic can be seen by filtering for "tcp.stream eq 7". Using the IO graph and TCP time sequence graph (as well as the details showing retransmissions) doesn't show anything out of the ordinary.
The only thing you can say is that you are seeing about 10% of packets from the server being lost, but they all being retransmitted successfully. So everything is operating correctly.
Your stream is about 200kbps on average - the question is how many concurrent streams or other traffic is running on this pipe? You probably want to correlate your packet loss received with what you are seeing is the utilisation on the link. (And of course the problem may not be at your access - it could be anywhere between your ISP and amazon).
Regards, Martin
MartinVisser99@xxxxxxxxx
On Mon, Sep 7, 2009 at 8:37 PM, Nikolai Longolius
<longolius@xxxxxxxxxxxxxx> wrote:
Hello everyone,
we're in trouble with our website and a german ISP (Hansenet) where it seems that we've got a lot of packet loss. I got some users to use wireshark to capture packets and the dominating colour is red.
Could someone on this list tell me if the problem here is packet loss?
Our Servers are Amazon AWS EC2 instances in the US running Wowza Flash Streaming Server. When using any other ISP than Hansenet (which is No 3 in Germany) the problem doesn't occur.
I raised errors on the ISP side and on AWS side - but as you can imagine nobody realy feels responsible.
I attached the dumpfile.
Any help or comment is appreciated.
Thank you for your time!
Regards,
Nikolai
--
Nikolai Longolius
schnee von morgen webTV GmbH
Manteuffelstr 66
10999 Berlin
___________________________________________________________________________
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
