From: Stephen Hemminger <shemminger@vyatta.com>
To: Chris Friesen <chris.friesen@genband.com>
Cc: Daniel Wagner <wagi@monom.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Glauber Costa <glommer@parallels.com>,
Linux Containers <containers@lists.osdl.org>,
netdev@vger.kernel.org, David Miller <davem@davemloft.net>,
Pavel Emelyanov <xemul@parallels.com>
Subject: Re: [RFC] per-containers tcp buffer limitation
Date: Thu, 25 Aug 2011 08:44:15 -0700 [thread overview]
Message-ID: <20110825084415.3c3094e8@nehalam.ftrdhcpuser.net> (raw)
In-Reply-To: <4E5664B5.6000806@genband.com>
You seem to have forgotten the work of your forefathers. When appealing
to history you must understand it first.
What about using netfilter (with extensions)? We already have iptables
module to match on uid or gid. It wouldn't be hard to extend this to
other bits of meta data like originating and target containers.
You could also use this to restrict access to ports and hosts on
a per container basis.
next prev parent reply other threads:[~2011-08-25 15:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 22:54 [RFC] per-containers tcp buffer limitation Glauber Costa
2011-08-25 0:35 ` Eric W. Biederman
2011-08-25 1:28 ` Glauber Costa
2011-08-25 1:49 ` KAMEZAWA Hiroyuki
2011-08-25 2:16 ` Eric W. Biederman
[not found] ` <m14o16qlq1.fsf-+imSwln9KH6u2/kzUuoCbdi2O/JbrIOy@public.gmane.org>
2011-08-25 12:55 ` Daniel Wagner
2011-08-25 15:05 ` Chris Friesen
2011-08-25 15:44 ` Stephen Hemminger [this message]
2011-08-25 18:11 ` Glauber Costa
2011-08-25 18:33 ` Daniel Wagner
2011-08-25 18:45 ` Daniel Wagner
2011-08-25 18:27 ` Daniel Wagner
[not found] ` <4E56942A.3080905-kQCPcA+X3s7YtjvyW6yDsg@public.gmane.org>
2011-08-27 23:39 ` Matthew Helsley
2011-08-28 6:09 ` David Miller
2011-08-25 18:02 ` Glauber Costa
2011-08-25 18:05 ` Glauber Costa
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=20110825084415.3c3094e8@nehalam.ftrdhcpuser.net \
--to=shemminger@vyatta.com \
--cc=chris.friesen@genband.com \
--cc=containers@lists.osdl.org \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=glommer@parallels.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=netdev@vger.kernel.org \
--cc=wagi@monom.org \
--cc=xemul@parallels.com \
/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).