From: Alexey Dobriyan <adobriyan@gmail.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Michael Kerrisk <mtk.manpages@googlemail.com>,
Pavel Emelyanov <xemul@openvz.org>,
David Miller <davem@davemloft.net>,
lkml <linux-kernel@vger.kernel.org>,
linux-man@vger.kernel.org,
Subrata Modak <subrata@linux.vnet.ibm.com>,
Stephen Hemminger <shemminger@linux-foundation.org>,
Patrick McHardy <kaber@trash.net>,
den@openvz.org, Daniel Lezcano <dlezcano@fr.ibm.com>
Subject: Re: Current state of Network Namespaces (NETNS, CLONE_NEWNET)?
Date: Thu, 20 Nov 2008 05:50:19 +0300 [thread overview]
Message-ID: <20081120025019.GA2220@x200.localdomain> (raw)
In-Reply-To: <m1d4grfa8w.fsf@frodo.ebiederm.org>
On Wed, Nov 19, 2008 at 05:37:35PM -0800, Eric W. Biederman wrote:
> Michael Kerrisk <mtk.manpages@googlemail.com> writes:
>
> > 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?
>
> No. It is fairly close though and there is general agreement
> on what it is.
>
> ipv4 and ipv6 are mostly complete and useable.
> ip tables support is in progress.
iptables will be mostly complete in 2.6.28.
next prev parent reply other threads:[~2008-11-20 2:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-19 21:49 Michael Kerrisk
2008-11-20 1:37 ` Eric W. Biederman
2008-11-20 2:50 ` Alexey Dobriyan [this message]
2008-11-20 7:54 ` Daniel Lezcano
2008-11-20 8:04 ` Subrata Modak
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=20081120025019.GA2220@x200.localdomain \
--to=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=mtk.manpages@googlemail.com \
--cc=shemminger@linux-foundation.org \
--cc=subrata@linux.vnet.ibm.com \
--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
all inboxes | Powered by JetHome®