Quoting Matthew Dillon ([EMAIL PROTECTED]):
>
> The question here is... is it actually packet loss that is creating
> this issue for you and John, or is it something else? The only way
> to tell for sure is to run tcpdump on BOTH the client and server
> and then observe whether packet loss is occuring by comparing the dumps.
>
Packet loss is the problem for sure. I am dumping on the server and
client side.
http://www.irbs.net/server-dump.html
http://www.irbs.net/client-dump.html
In 60Ms the server pushed out about 200 segments. My test writes
1 byte at a time on an existing ssh conection so the payload per
segment is small, 48 bytes. (48 + IP + TCP) * 200 is around 17KB
in 60Ms which probably overflowed the frame switch queue. The
client is on a fractional T1, the server is on a 10Mb -> OC3
connection 1200 network miles away.
Jonathan Lemon pointed out in the TCP Anomalies thread that slow
start seems to be broken.
John Capo
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
