3a64270ca6
Back out the change from TCP/IP vol 2, in revision 1.7, which removed TH_FIN
...
from the output flags for CLOSING state. There is no harm in retransmitting
the FIN, and this change has unexpected side effects that break simultaneous
close behaviour.
1998-07-09 05:49:56 +00:00
8cfe8959a6
Fix TCPS_HAVERCVDFIN() to actually catch all TCP states in which a FIN
...
has been received (CLOSE_WAIT, CLOSING, LAST_ACK, and TIME_WAIT).
From David Borman <dab@bsdi.com>.
1998-07-03 05:39:56 +00:00
f73530ba55
add/cleanup multiple inclusion protection.
1998-02-10 01:26:19 +00:00
b8377e5395
As per RFC 793, don't retransmit the FIN during a simultaneous close.
...
From Thorsten Frueauf <frueauf@ira.uka.de> and W. Richard Stevens in PR/3737
and TCP/IP Illustrated, Vol. 2, respectively.
1997-06-18 10:05:44 +00:00
63bb09e6da
Don't return received data to the user until the initial handshake is complete.
...
Also use TCPS_HAVEESTABLISHED() in a few other places.
1994-10-14 16:01:48 +00:00
cf92afd66e
New RCS ID's, take two. they're more aesthecially pleasant, and use 'NetBSD'
1994-06-29 06:29:24 +00:00
07b4f2ab54
Update to 4.4-Lite networking code, with a few local changes.
1994-05-13 06:02:48 +00:00
45a57e79ea
more rcsid additions and file header cleanups
1993-05-20 03:49:51 +00:00
235bd1db44
Add consistent multiple-inclusion protection.
1993-04-19 03:45:34 +00:00
61f282557f
initial import of 386bsd-0.1 sources
1993-03-21 09:45:37 +00:00
mycroft