You would only see 3 duplicate acks prior to the retransmission if the
capture was taken on the interface receiving the dupacks and sending
the retransmissions
or if the end to end latency is very very very very small.
the problem is that speed of light and propagation through devices are not infinitely fast.
i.e. it will take some time before the other end could see your first 3 dupacks and retransmit,
during this time it is very possible that other segments already in flight will generate even more dupacks.
On 10/10/05, fonte fonte <fonte_monte@xxxxxxxxx> wrote:
Hi all,
I had downloaded a file from a FTP server and capture
the transfer using ethereal. I was confused to see
that on my side (client) I had issued 11 dupacks for a
missing segment before the server finally retransmit.
I always thought by default, it will be 3 dupacks to
trigger retransmission? I hope anyone can explain this
to me. The server OS is Windows XP Pro SP2 and client
OS is Windows XP Home SP2.
Best regards.
__________________________________
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
_______________________________________________
Ethereal-users mailing list
Ethereal-users@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-users
