aboutsummaryrefslogtreecommitdiff
path: root/scripts/patch-kernel
diff options
context:
space:
mode:
authorJozsef Kadlecsik <[email protected]>2007-10-11 14:35:52 -0700
committerDavid S. Miller <[email protected]>2007-10-11 14:35:52 -0700
commit17311393f969090ab060540bd9dbe7dc885a76d5 (patch)
treecc8f9a460679870c51b194c8927f998b243a98f7 /scripts/patch-kernel
parentd71fce6b932d83e0a1caa49dfa5a536fd50f07c9 (diff)
[NETFILTER]: nf_conntrack_tcp: fix connection reopening
With your description I could reproduce the bug and actually you were completely right: the code above is incorrect. Somehow I was able to misread RFC1122 and mixed the roles :-(: When a connection is >>closed actively<<, it MUST linger in TIME-WAIT state for a time 2xMSL (Maximum Segment Lifetime). However, it MAY >>accept<< a new SYN from the remote TCP to reopen the connection directly from TIME-WAIT state, if it: [...] The fix is as follows: if the receiver initiated an active close, then the sender may reopen the connection - otherwise try to figure out if we hold a dead connection. Signed-off-by: Jozsef Kadlecsik <[email protected]> Tested-by: Krzysztof Piotr Oledzki <[email protected]> Signed-off-by: Patrick McHardy <[email protected]> Signed-off-by: David S. Miller <[email protected]>
Diffstat (limited to 'scripts/patch-kernel')
0 files changed, 0 insertions, 0 deletions