Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-users: Re: [Wireshark-users] Dup ACK #1

From: Martin Visser <martinvisser99@xxxxxxxxx>
Date: Wed, 31 Mar 2010 16:37:14 +1100
Duplicate ACKs are pretty common when you have congested network. If the client is expecting more data and doesn't receive it in time 9maybe 250ms) then it will send another ACK in the hope that the data it is missing/waiting on will be resent.

You haven't indicated what problem you are chasing. If you send a small sample capture that would be useful.

Regards, Martin


On Wed, Mar 31, 2010 at 3:58 PM, vincent paul <amoteluro@xxxxxxxxx> wrote:
Hi All ,
I looked at two traces captured at user's side: one going thru proxy and one bypassing proxy and observed a lot of Dup ACK #1.  Both traces are  traffic of HTTP download's file from server.  I have the following observations and could not find any explanation
1)Traffic going thru proxy:  User always sent double ACKs (one ACK(len=0) and  its Dup ACK #1(len=0) immediately). No Dup ACK problem from server side
2)Traffic bypassing proxy: server, most of the time, sent out double ACK (ACK(len>0) and its Dup ACK #1 (len=0)) with a time period.  This means:
Server---> user: seq=1000 Ack=210 len= 1460
Server----> user (dup Ack #1) seq=2460, Ack =210 len=0
Normal TCP data transfer from server for a while(kind of frequency) , then Server sends out double Acks again.
But there were also some time intervals, the data transfer from server looked normal without any double Acks from server
In this case, no Dup Ack problem from user's side.
I appreciate your help very much.

Sent via:    Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>