From: Patrick McHardy <kaber@trash.net>
To: Alexey Dobriyan <adobriyan@parallels.com>
Cc: netfilter-devel@vger.kernel.org, netdev@vger.kernel.org,
devel@openvz.org, den@openvz.org, xemul@openvz.org,
adobriyan@gmail.com
Subject: Re: unlock iptables in netns
Date: Wed, 11 Jun 2008 08:53:23 +0200 [thread overview]
Message-ID: <484F7663.1080408@trash.net> (raw)
In-Reply-To: <200806102127.21093.adobriyan@parallels.com>
Alexey Dobriyan wrote:
> Hi,
>
> Den basically banned iptables in netns via this patch
>
> --- a/net/netfilter/core.c
> +++ b/net/netfilter/core.c
> ...
> , however, at least some of netfilter pieces are ready for usage in netns
> and it would be nice to unlock them before release.
>
> If I'm deciphering chengelog correctly it's all about code which does
> nf_register_hook{,s} but not netns-ready itself:
>
> br_netfilter.c
> iptable_mangle (via ip_route_me_harder)
> conntracking (both IPv4 and IPv6)
> NAT
> arptable_filter
> selinux
> decnet
> ebtable_filter
> ebtable_nat
> ipt_CLUSTERIP
>
> Patch above can be applied and we can mark above list as "depends !NET_NS"
> and move on.
>
> Comments? Den, was there something else you're afraid of?
That might result in some bad surprises for people how have already
turned on NET_NS. I'd prefer a way that doesn't potentially disable
half the netfilter options in existing configs.
next prev parent reply other threads:[~2008-06-11 6:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 17:27 unlock iptables in netns Alexey Dobriyan
2008-06-11 6:53 ` Patrick McHardy [this message]
2008-06-16 10:26 ` Patrick McHardy
2008-06-16 11:04 ` Alexey Dobriyan
2008-06-16 11:16 ` Patrick McHardy
2008-06-16 11:17 ` Pavel Emelyanov
2008-06-16 11:21 ` Patrick McHardy
2008-06-20 17:54 ` Alexey Dobriyan
2008-06-21 8:03 ` Patrick McHardy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=484F7663.1080408@trash.net \
--to=kaber@trash.net \
--cc=adobriyan@gmail.com \
--cc=adobriyan@parallels.com \
--cc=den@openvz.org \
--cc=devel@openvz.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=xemul@openvz.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).