Date: Fri, 20 Jul 2007 17:39:28 -0500 From: Mike Karels <karels@karels.net> To: Julian Elischer <julian@ironport.com> Cc: FreeBSD Net <freebsd-net@freebsd.org>, Julian Elischer <julian@elischer.org> Subject: Re: Wierd networking. Message-ID: <200707202239.l6KMdSq4035780@redrock.karels.net> In-Reply-To: Your message of Fri, 20 Jul 2007 10:55:18 -0700. <46A0F706.6020701@ironport.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> I think that the possible courses of action are: > 1/ Ignore further incoming data, but ACK it. > (this is basically what the userland code does in this case) This could lead to indefinite data transfer, while misleading the sender into thinking the data are being delivered. > 2/ Stop ACKing the data, and let the other end time out. This seems like a waste of resources on both ends of the connection; both are doomed, but they both have to time out to go away. > 3/ Send a RST This is my choice, literally: I added the code to send a RST in this case sometime in the 1980s, after observing connections that hung with no reader, but with the writer in persist mode indefinitely. (That's choice 4: accept the data, let the receive buffer fill, then advertise a zero window forever.) Mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200707202239.l6KMdSq4035780>