From: Subrata Modak <subrata@linux.vnet.ibm.com>
To: Daniel Lezcano <dlezcano@fr.ibm.com>
Cc: Michael Kerrisk <mtk.manpages@googlemail.com>,
Pavel Emelyanov <xemul@openvz.org>,
David Miller <davem@davemloft.net>,
"Eric W. Biederman" <ebiederm@xmission.com>,
lkml <linux-kernel@vger.kernel.org>,
linux-man@vger.kernel.org,
Stephen Hemminger <shemminger@linux-foundation.org>,
adobriyan@gmail.com, Patrick McHardy <kaber@trash.net>,
den@openvz.org, ltp-list <ltp-list@lists.sf.net>
Subject: Re: Current state of Network Namespaces (NETNS, CLONE_NEWNET)?
Date: Thu, 20 Nov 2008 13:34:17 +0530 [thread overview]
Message-ID: <1227168257.4978.6.camel@subratamodak.linux.ibm.com> (raw)
In-Reply-To: <492517BC.3050205@fr.ibm.com>
On Thu, 2008-11-20 at 08:54 +0100, Daniel Lezcano wrote:
> Michael Kerrisk wrote:
> > Sorry for the shotgun mail, but in the end, it's
> > not clear who can best answer my question(s).
> >
> > I'm currently trying to add documentation of all of
> > the undocumented CLONE_* flags. One of these is
> > CLONE_NEWNET, and I could use (quite a lot of) help.
> >
> > My questions:
> >
> > What is the current state of the network namespace
> > implementation? Is it complete?
>
> It is not complete but mostly usable for ipv4 and ipv6.
>
> There is a network namespace status I filled at:
>
> http://lxc.sourceforge.net/network/status.php
>
> It should be up-to-date.
>
> > What objects are considered part of the network
> > namespace, and therefore distinct for a new network
> > namespace?
>
> The network namespace brings isolation from the layer-2 to upper layers.
>
> > Is there any documentation for network namespaces
> > already?
>
> http://lxc.sourceforge.net/network.php
> http://lxc.sourceforge.net/doc/sigops/appcr.pdf
>
> > Are there any test programs for network namespaces?
>
> http://sourceforge.net/projects/lxc/
And also at:
http://ltp.cvs.sourceforge.net/viewvc/ltp/ltp/testcases/kernel/containers/
Regards--
Subrata
>
> follow the README page. It is still in development but mainly usable -
> any feedbacks are welcome :)
>
next prev parent reply other threads:[~2008-11-20 8:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-19 21:49 Current state of Network Namespaces (NETNS, CLONE_NEWNET)? Michael Kerrisk
2008-11-20 1:37 ` Eric W. Biederman
2008-11-20 2:50 ` Alexey Dobriyan
2008-11-20 7:54 ` Daniel Lezcano
2008-11-20 8:04 ` Subrata Modak [this message]
2008-11-20 18:20 ` CLONE_NEWNET documentation Michael Kerrisk
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=1227168257.4978.6.camel@subratamodak.linux.ibm.com \
--to=subrata@linux.vnet.ibm.com \
--cc=adobriyan@gmail.com \
--cc=davem@davemloft.net \
--cc=den@openvz.org \
--cc=dlezcano@fr.ibm.com \
--cc=ebiederm@xmission.com \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=ltp-list@lists.sf.net \
--cc=mtk.manpages@googlemail.com \
--cc=shemminger@linux-foundation.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