diff options
author | Florian Westphal <fw@strlen.de> | 2018-08-24 23:22:08 +0200 |
---|---|---|
committer | Pablo Neira Ayuso <pablo@netfilter.org> | 2018-09-11 01:29:24 +0200 |
commit | f94e63801ab2791ed64c409d0f751f6a0c953ead (patch) | |
tree | fc083aac1dde0e5f89e969d14c7ae2adee4b2191 /net/iucv | |
parent | 7acfda539c0b9636a58bfee56abfb3aeee806d96 (diff) | |
download | linux-f94e63801ab2791ed64c409d0f751f6a0c953ead.tar.bz2 |
netfilter: conntrack: reset tcp maxwin on re-register
Doug Smythies says:
Sometimes it is desirable to temporarily disable, or clear,
the iptables rule set on a computer being controlled via a
secure shell session (SSH). While unwise on an internet facing
computer, I also do it often on non-internet accessible computers
while testing. Recently, this has become problematic, with the
SSH session being dropped upon re-load of the rule set.
The problem is that when all rules are deleted, conntrack hooks get
unregistered.
In case the rules are re-added later, its possible that tcp window
has moved far enough so that all packets are considered invalid (out of
window) until entry expires (which can take forever, default
established timeout is 5 days).
Fix this by clearing maxwin of existing tcp connections on register.
v2: don't touch entries on hook removal.
v3: remove obsolete expiry check.
Reported-by: Doug Smythies <dsmythies@telus.net>
Fixes: 4d3a57f23dec59 ("netfilter: conntrack: do not enable connection tracking unless needed")
Signed-off-by: Florian Westphal <fw@strlen.de>
Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
Diffstat (limited to 'net/iucv')
0 files changed, 0 insertions, 0 deletions