| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
| |
circumstances, caused perfectly good connections to be dropped. This
happened for connections over a LAN, where the retransmit timer
calculation TCP_REXMTVAL(tp) returned 0. If sending was blocked by flow
control for long enough, the old code dropped the connection, even
though timely replies were being received for all window probes.
Reviewed by: W. Richard Stevens <rstevens@noao.edu>
|
|
|
|
|
|
|
|
|
| |
1) Set the persist timer to help time-out connections in the CLOSING state.
2) Honor the keep-alive timer in the CLOSING state.
This fixes problems with connections getting "stuck" due to incompletion
of the final connection shutdown which can be a BIG problem on busy WWW
servers.
|
|
|
|
|
|
| |
keepalive on all tcp sessions. Setsockopt(2) cannot override this setting.
Maybe another one is needed that just changes the default for SO_KEEPALIVE ?
Requested by: Joe Greco <jgreco@brasil.moneng.mei.com>
|
|
|
|
| |
changes.
|
|
|
|
|
|
| |
the TF_ACKNOW flag when the REXMT timer goes off to force a
retransmission. In certain situations pulling snd_nxt back to snd_una
is not sufficient.
|
| |
|
| |
|
|
|
|
|
|
|
| |
tcp_output() checks for the condition snd_nxt == snd_una.
Reviewed by: davidg, wollman, olah
Suggested by: Richard Stevens
|
|
|
|
| |
to make ISS-guessing spoofing attacks harder.
|
|
|
|
|
| |
Reviewed by: Andras Olah
Obtained from: 4.4BSD-lite2 via W. Richard Stevens
|
| |
|
|
|
|
| |
macros. Basically, detect 'tp' going away differently.
|
|
|
|
| |
and in_pcblookuphash.
|
| |
|
|
|
|
|
|
|
|
|
| |
Bob Braden <braden@isi.edu>.
NB: This has not had David's TCP ACK hack re-integrated. It is not clear
what the correct solution to this problem is, if any. If a better solution
doesn't pop up in response to this message, I'll put David's code back in
(or he's welcome to do so himself).
|
| |
|
|
|