summaryrefslogtreecommitdiffstats
path: root/sys/netinet/tcp_fsm.h
Commit message (Collapse)AuthorAgeFilesLines
* WARNS=n and lint(1) silencer. Declare an array of (const) stringsmarkm2002-02-031-1/+1
| | | | as const char.
* Undo rev 1.10, which took out TH_FIN from the CLOSING state. Thisjlemon1999-11-071-1/+1
| | | | breaks simultaneous closes.
* KAME related header files additions and merges.shin1999-11-051-1/+15
| | | | | | | (only those which don't affect c source files so much) Reviewed by: cvs-committers Obtained from: KAME project
* $Id$ -> $FreeBSD$peter1999-08-281-1/+1
|
* Two cosmetic changes, one a typo and the other, a clarification.julian1999-04-071-5/+13
|
* Fix all areas of the system (or at least all those in LINT) to avoid storingwollman1997-08-161-2/+2
| | | | | | | | socket addresses in mbufs. (Socket buffers are the one exception.) A number of kernel APIs needed to get fixed in order to make this happen. Also, fix three protocol families which kept PCBs in mbufs to not malloc them instead. Delete some old compatibility cruft while we're at it, and add some new routines in the in_cksum family.
* Back out part 1 of the MCFH that changed $Id$ to $FreeBSD$. We are notpeter1997-02-221-1/+1
| | | | ready for it yet.
* Make the long-awaited change from $Id$ to $FreeBSD$jkh1997-01-141-1/+1
| | | | | | | | This will make a number of things easier in the future, as well as (finally!) avoiding the Id-smashing problem which has plagued developers for so long. Boy, I'm glad we're not using sup anymore. This update would have been insane otherwise.
* New style sysctl & staticize alot of stuff.phk1995-11-141-2/+2
|
* Backed out changes in rev 1.5 that prevent sending FIN if in CLOSINGdg1995-03-301-2/+2
| | | | | state. This causes an infinite loop in some rare cases (probably caused by some other, much more difficult to find bug).
* Don't need to retransmit FIN bit in CLOSING state.wollman1995-02-161-2/+2
| | | | Obtained from: Stevens, vol. 2, exercise 29.5 (solution p. 1090)
* Obey RFC 793, section 3.4:wollman1994-08-261-1/+2
| | | | | | | | | Several examples of connection initiation follow. Although these examples do not show connection synchronization using data-carrying segments, this is perfectly legitimate, so long as the receiving TCP doesn't deliver the data to the user until it is clear the data is valid (i.e., the data must be buffered at the receiver until the connection reaches the ESTABLISHED state).
* Made idempotent.paul1994-08-211-1/+6
| | | | Submitted by: Paul
* Added $Id$dg1994-08-021-0/+1
|
* BSD 4.4 Lite Kernel Sourcesrgrimes1994-05-241-0/+85
OpenPOWER on IntegriCloud