From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Gao feng <gaofeng@cn.fujitsu.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf-next 0/6] Add net namespace support for ipt_CLUSTERIP
Date: Thu, 17 Oct 2013 10:46:45 +0200 [thread overview]
Message-ID: <20131017084645.GA8791@localhost> (raw)
In-Reply-To: <524E819B.1080306@cn.fujitsu.com>
On Fri, Oct 04, 2013 at 04:51:39PM +0800, Gao feng wrote:
> Hi Pablo,
>
> On 10/01/2013 07:05 PM, Pablo Neira Ayuso wrote:
> > Hi Gao,
> >
> > On Wed, Sep 25, 2013 at 03:38:43PM +0800, Gao feng wrote:
> >> This patchset adds net namespace support for ipt_CLUSTERIP,
> >> makes clusterip_configs,clusterip_lock and clusterip_procdir
> >> per net namespace, and allow users in container to operate
> >> the proper pernet resource of CLUSTERIP.
> >>
> >> Gao feng (6):
> >> ipt_CLUSTERIP: make proc directory per net namespace
> >> ipt_CLUSTERIP: make clusterip_list per net namespace
> >> ipt_CLUSTERIP: make clusterip_lock per net namespace
> >> ipt_CLUSTERIP: add parameter net in clusterip_config_find_get
> >> ipt_CLUSTERIP: create proc entry under proper ipt_CLUSTERIP directory
> >> ipt_CLUSTERIP: use proper net namespace to operate CLUSTERIP
> >
> > CLUSTERIP is a subset of the cluster match. The cluster match allows
> > gateway configurations, which are not possible with CLUSTERIP.
>
> Yes, but seems ipt_CLUSTERIP is more popular.(from the result I seach through google)
Fair enough, applied to nf-next.
> > If you really need these, I can take them. But I'd be happy if you can
> > check the cluster match to make sure there are no issue regarding net
> > namespaces.
> >
>
> I looked into the codes of cluster match module, and did some simple test,
> it has no need to do with net namespace. works well in container :)
thanks a lot of checking Gao.
prev parent reply other threads:[~2013-10-17 8:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 7:38 [PATCH nf-next 0/6] Add net namespace support for ipt_CLUSTERIP Gao feng
2013-09-25 7:38 ` [PATCH nf-next 1/6] ipt_CLUSTERIP: make proc directory per net namespace Gao feng
2013-09-25 7:38 ` [PATCH nf-next 2/6] ipt_CLUSTERIP: make clusterip_list " Gao feng
2013-09-25 7:38 ` [PATCH nf-next 3/6] ipt_CLUSTERIP: make clusterip_lock " Gao feng
2013-09-25 7:38 ` [PATCH nf-next 4/6] ipt_CLUSTERIP: add parameter net in clusterip_config_find_get Gao feng
2013-09-25 7:38 ` [PATCH nf-next 5/6] ipt_CLUSTERIP: create proc entry under proper ipt_CLUSTERIP directory Gao feng
2013-09-25 7:38 ` [PATCH nf-next 6/6] ipt_CLUSTERIP: use proper net namespace to operate CLUSTERIP Gao feng
2013-10-01 11:05 ` [PATCH nf-next 0/6] Add net namespace support for ipt_CLUSTERIP Pablo Neira Ayuso
2013-10-04 8:51 ` Gao feng
2013-10-17 8:46 ` Pablo Neira Ayuso [this message]
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=20131017084645.GA8791@localhost \
--to=pablo@netfilter.org \
--cc=gaofeng@cn.fujitsu.com \
--cc=netfilter-devel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.