From: James Bottomley <James.Bottomley-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>
To: "Sebastián Maruca" <seba-iesXmtczecS4Tu3zPC53fQ@public.gmane.org>,
"Sebastián Maruca"
<juanperiz-/E1597aS9LQMlKAeRRkD2Q@public.gmane.org>,
"containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org"
<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
Subject: Re: Deploy specific iptables ruleset for each container...
Date: Tue, 07 Jun 2016 08:30:02 -0700 [thread overview]
Message-ID: <1465313402.2310.5.camel@HansenPartnership.com> (raw)
In-Reply-To: <1037489545.134365.1465266607461.JavaMail.yahoo-sAHhhX/85wgbqTNvkayDYw@public.gmane.org>
On Tue, 2016-06-07 at 02:30 +0000, Sebastián Maruca via Containers
wrote:
> Hi to everyone!
> Is it possible to deploy a "central" iptables ruleset at a Host,and
> then, deploy several "isolated" iptables rulesets, one for each
> container?
> I'd like to have a this "central" iptables to chain basic rules,and
> each one of them have trivial rulesets, so as to speak of a"multi
> -tenant" IPTables.
It depends what you mean by "deploy". Firewall rule sets are 1:1 with
network namespaces, so it isn't possible to "inherit" rules from the
parent netns. It is, however, perfectly possible to run a veth pair
between two different netns and apply different firewall rules on each
end with each rule set being in its own netns. It sounds like this
could cover your use case.
James
_______________________________________________
Containers mailing list
Containers@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/containers
prev parent reply other threads:[~2016-06-07 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1037489545.134365.1465266607461.JavaMail.yahoo.ref@mail.yahoo.com>
2016-06-07 2:30 ` Deploy specific iptables ruleset for each container Sebastián Maruca via Containers
[not found] ` <1037489545.134365.1465266607461.JavaMail.yahoo-sAHhhX/85wgbqTNvkayDYw@public.gmane.org>
2016-06-07 15:30 ` James Bottomley [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=1465313402.2310.5.camel@HansenPartnership.com \
--to=james.bottomley-d9phhud1jfjcxq6kfmz53/egyhegw8jk@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=juanperiz-/E1597aS9LQMlKAeRRkD2Q@public.gmane.org \
--cc=seba-iesXmtczecS4Tu3zPC53fQ@public.gmane.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.