linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: pavel@suse.cz (Pavel Machek)
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox),
	mblack@csihq.com (Mike Black),
	f.v.heusden@ftr.nl (Heusden Folkert van),
	linux-kernel@vger.kernel.org
Subject: Re: Client receives TCP packets but does not ACK
Date: Sun, 17 Jun 2001 20:32:49 +0100 (BST)	[thread overview]
Message-ID: <E15BiHy-0002xC-00@the-village.bc.nu> (raw)
In-Reply-To: <20010617201727.A1493@bug.ucw.cz> from "Pavel Machek" at Jun 17, 2001 08:17:27 PM

> > Specifically
> > 1.	If the receiver closes and there is unread data many TCP's forget
> > 	to RST the sender to indicate that data was lost.
> 
> Do at least FreeBSD, Solaris and NT sent RST correctly?

I dont believe so

> > 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.
> 
> This is interesting; where are details?

http://www.schooner.com/~loverso/Public/Internet-Drafts/draft-heavens-problems-rsts-00.txt

Yes a 1996 tcp protocol flaw that still hasnt been fixed. 


  reply	other threads:[~2001-06-17 19:34 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-15 12:53 Client receives TCP packets but does not ACK Heusden, Folkert van
2001-06-15 18:27 ` Mike Black
2001-06-15 18:39   ` Gérard Roudier
2001-06-15 19:12   ` Alan Cox
2001-06-17 18:17     ` Pavel Machek
2001-06-17 19:32       ` Alan Cox [this message]
2001-06-17 19:40       ` Dan Podeanu
     [not found]         ` <200106172113.f5HLDhJ377473@saturn.cs.uml.edu>
2001-06-17 22:09           ` Dan Podeanu
2001-06-17 22:35         ` dean gaudet
2001-06-18 11:50 ` Jan Hudec
2001-06-18 16:17   ` dean gaudet
2001-06-18 16:48     ` Jonathan Morton
2001-06-18 22:30       ` dean gaudet
2001-06-18 23:43         ` Jonathan Morton
2001-06-19  2:46           ` dean gaudet
2001-06-20 21:01   ` David Schwartz
  -- strict thread matches above, loose matches on Subject: below --
2001-07-01 21:27 Nivedita Singhvi
2001-07-11  3:43 ` Robert Kleemann
     [not found] <E15BiHy-0002xC-00@the-village.bc.nu.suse.lists.linux.kernel>
2001-06-17 20:21 ` Andi Kleen
     [not found] <Pine.LNX.4.33.0106121720310.1152-100000@localhost.localdomain.suse.lists.linux.kernel>
2001-06-13  8:48 ` Andi Kleen
2001-06-13 16:09   ` Robert Kleemann
2001-06-13  0:26 Robert Kleemann
2001-06-15  3:50 ` Robert Kleemann
2001-06-15 12:44   ` Mike Black
2001-06-15 18:29     ` Albert D. Cahalan
2001-06-15 23:10       ` Robert Kleemann
2001-06-16 11:55       ` Mike Black
2001-06-16 23:56 ` Robert Kleemann
2001-06-27  1:04   ` Robert Kleemann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E15BiHy-0002xC-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=f.v.heusden@ftr.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mblack@csihq.com \
    --cc=pavel@suse.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).