Re: Immediate ACK from server

[Martin Visser <martinvisser99 () gmail com>]

More than likely, assuming your measurements are correct,  there is a local
"blackbox" between user and the server. This will possibly be an old-school
application proxy (or a firewall acting as such a proxy), a device like
Packeteer doing traffic-shaping, or a new-age WAN acceleration device (such
as from Riverbed, or a Juniper WX or Cisco WAAS).

These all can fake the ACK, and do so simply to either avoid the problems of
delay on WAN traffic, either trying to serve cached traffic or manage the
sliding Window to improve (or hinder) your throughput.

Regards, Martin

MartinVisser99 () gmail com


On Sun, Mar 28, 2010 at 1:22 PM, vincent paul <amoteluro () yahoo com> wrote:

> Dear All,
>
> I am looking at a trace between user and database server.  And I know for
> sure the RTT between them is 90 ms.
> However, I observe that evertime user sends a request to server,  there is
> one immediate ACK from server to ack this packet (i.e. delta time between
> user's packet and its immediate ACK from the server is much less than RTT.
> For example 0.2 ms compared to RTT of 90 ms).
>
> Please explain how such server's immediate ACK could happen.
>
> regards,
> PV
>
>
> ___________________________________________________________________________
> Sent via:    Wireshark-users mailing list <wireshark-users () wireshark org>
> Archives:    http://www.wireshark.org/lists/wireshark-users
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
>             mailto:wireshark-users-request () wireshark org
> ?subject=unsubscribe
___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
             mailto:wireshark-users-request () wireshark org?subject=unsubscribe