summaryrefslogtreecommitdiffstats
path: root/net/8021q
diff options
context:
space:
mode:
authorFlorian Westphal <fw@strlen.de>2017-07-28 11:22:04 +0200
committerPablo Neira Ayuso <pablo@netfilter.org>2017-07-31 20:42:00 +0200
commit4d3a57f23dec59f0a2362e63540b2d01b37afe0a (patch)
treefa5d6caaf42b7bd0fb2915ac2e725098666b4b0b /net/8021q
parent9b7e26aee7cf27ffb37bb2f17229cecc89a833bd (diff)
downloadlinux-4d3a57f23dec59f0a2362e63540b2d01b37afe0a.tar.gz
linux-4d3a57f23dec59f0a2362e63540b2d01b37afe0a.tar.bz2
linux-4d3a57f23dec59f0a2362e63540b2d01b37afe0a.zip
netfilter: conntrack: do not enable connection tracking unless needed
Discussion during NFWS 2017 in Faro has shown that the current conntrack behaviour is unreasonable. Even if conntrack module is loaded on behalf of a single net namespace, its turned on for all namespaces, which is expensive. Commit 481fa373476 ("netfilter: conntrack: add nf_conntrack_default_on sysctl") attempted to provide an alternative to the 'default on' behaviour by adding a sysctl to change it. However, as Eric points out, the sysctl only becomes available once the module is loaded, and then its too late. So we either have to move the sysctl to the core, or, alternatively, change conntrack to become active only once the rule set requires this. This does the latter, conntrack is only enabled when a rule needs it. Reported-by: Eric Dumazet <edumazet@google.com> Signed-off-by: Florian Westphal <fw@strlen.de> Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
Diffstat (limited to 'net/8021q')
0 files changed, 0 insertions, 0 deletions