On Wed, 2008-02-20 at 15:34 +0700, Mulyadi Santosa wrote:
> Hi...
> 
> The interesting thing about the tcpdump's trace is seems like the
> sending (or receiving) side keep ACK-ing same packet/sequence number.
> Maybe something isn't done correctly?

Don't understand.

This trace is from an HTTP server, where a file is being sent from the
server to a client.

After the "GET" command the client does not send anything else, so why
should the ack sequences be different?

The server sends packets as much as the TCP-window allows.
But here, a packet was sent twice, with no apparent reason.

Also, note my first mail, that packets sent by this server are not sent
through the TCP-stack (using 'send' on a TCP socket), but instead, they
are sent on a raw socket, where the TCP is implemented by my user space
application.

I can most positively say that the user space application called sendto
only once for each packet, whereas one packet was sent twice.



--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to [EMAIL PROTECTED]
Please read the FAQ at http://kernelnewbies.org/FAQ

Reply via email to