lkml.org 
[lkml]   [2001]   [Jun]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Client receives TCP packets but does not ACK
On Sun, Jun 17, 2001 at 08:17:27PM +0200, Pavel Machek wrote:

> > 2. There is a flaw in the TCP protocol itself that is extremely unlikely
> > to bite people but can in theory cause wrong data in some unusual
> > circumstances that Ian Heavans found and has yet to be fixed by
> > the keepers of the protocol.

Bit offtopic.

Is there any logical reason why if, given fd is a connected, AF_INET,
SOCK_STREAM socket, and one does a write(fd, buffer, len); close(fd);
to the peer, over a rather slow network (read modem, satelite link, etc),
the data gets lost (the remote receives the disconnect before the last
packet). According to socket(7), even if SO_LINGER is not set, the data
is flushed in the background.

Is it Linux or TCP specific? Or some obvious techincal detail I'm missing?

Thanks, Dan.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 12:55    [W:0.077 / U:2.900 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site