IPv6:netfilter: defrag: Handle sysctls about IPv6 conntrack defragment per-netns
Subsystems (4)
RFC PATCH v2 1/7 IPv6:netfilter: defrag: Handle sysctls about IPv6 conntrack defragment per-netns
Register nf_conntrack_frag6_{timeout,high_thresh,low_thresh} sysctls per-netns. nf_conntrack_frag6_timeout and ip6frag_time, nf_conntrack_frag6_low_thresh and ip6frag_low_thresh, nf_conntrack_frag6_high_thresh and ip6frag_high_thresh, the three sets are equivalent. The former sysctls are just an alias for he latter ones of IPv6.
More discussion about it, see http://marc.info/?l=netfilter-devel&m=126709777922959&w=2.
--- Documentation/feature-removal-schedule.txt | 19 +++++ include/net/netns/ipv6.h | 1 + net/ipv6/netfilter/nf_conntrack_l3proto_ipv6.c | 4 - net/ipv6/netfilter/nf_conntrack_reasm.c | 85 ++++++++++++++++++++++-- 4 files changed, 99 insertions(+), 10 deletions(-)
Documentation/feature-removal-schedule.txt +19 -0
@@ -531,3 +531,22 @@ Why: udev fully replaces this special file system that only contains CAPI NCCI TTY device nodes. User space (pppdcapiplugin) works without noticing the difference. Who: Jan Kiszka <[email protected]> + +--------------------------- + +What: - /proc/sys/net/netfilter/nf_conntrack_frag6_timeout + - /proc/sys/net/netfilter/nf_conntrack_frag6_high_thresh + - /proc/sys/net/netfilter/nf_conntrack_frag6_low_thresh +When: February 2011 + +Why: IPv6 conntrack defragment has introduced network name space, and shares + per-netns_frags with IPv6 stack. ip6frag_low_thresh, ip6frag_time and + ip6frag_high_thresh manage queue numbers and memory thresh size of + both IPv6 conntrack fragment queue and IPv6 stack fragment queue. + So nf_conntrack_frag6_timeout and ip6frag_time have the same effect, + nf_conntrack_frag6_low_thresh and ip6frag_low_thresh also have the same + effect, nf_conntrack_frag6_high_thresh and ip6frag_high_thresh too. + These there sysctls of IPv6 conntrack will be removed in the future, + please use those of IPv6. + +Who: Shan Wei <[email protected]>
include/net/netns/ipv6.h +1 -0
@@ -14,6 +14,7 @@ struct netns_sysctl_ipv6 {#ifdef CONFIG_SYSCTL struct ctl_table_header *table;struct ctl_table_header *frags_hdr; +struct ctl_table_header *nf_ct_frags_hdr;#endif int bindv6only;int flush_delay;
net/ipv6/netfilter/nf_conntrack_l3proto_ipv6.c +0 -4
@@ -387,10 +387,6 @@ struct nf_conntrack_l3proto nf_conntrack_l3proto_ipv6 __read_mostly = { .nlattr_to_tuple = ipv6_nlattr_to_tuple, .nla_policy = ipv6_nla_policy, #endif -#ifdef CONFIG_SYSCTL - .ctl_table_path = nf_net_netfilter_sysctl_path, - .ctl_table = nf_ct_ipv6_sysctl_table, -#endif .me = THIS_MODULE, };
net/ipv6/netfilter/nf_conntrack_reasm.c +79 -6
118 lines not on this page · raw message
Signature · 1 line
1.6.3.3
Hi,
Quoted 6 lines · Shan Wei
Register nf_conntrack_frag6_{timeout,high_thresh,low_thresh} sysctls per-netns.
nf_conntrack_frag6_timeoutandip6frag_time,nf_conntrack_frag6_low_threshandip6frag_low_thresh,nf_conntrack_frag6_high_threshandip6frag_high_thresh, the three sets are equivalent. The former sysctls are just an alias for he latter ones of IPv6.More discussion about it, see http://marc.info/?l=netfilter-devel&m=126709777922959&w=2.
As I mailed in reply to [0/7], I'm not for this,
because the context (including parameters) should be kept separated between defragmentation in core ipv6 and one in netfilter.
--yoshfuji