From: Bruce Jones <bruce.jones-cfy2TCaE7SFv+uJa97DSA9BPR1lH4CV8@public.gmane.org>
To: containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org
Cc: Vivien Chappelier
<vivien.chappelier-L+G57L1VLRbR7s880joybQ@public.gmane.org>
Subject: Re: [PATCH 0/6] netns: add linux-vrf features via network namespaces
Date: Wed, 25 Mar 2009 12:21:19 -0600 [thread overview]
Message-ID: <49CA761F.1020006@alcatel-lucent.com> (raw)
In-Reply-To: <4909B10A.8090403-L+G57L1VLRbR7s880joybQ@public.gmane.org>
Vivien Chappelier wrote:
> Hi,
>
> The recently introduced network namespaces allow separate standalone
> network stacks to coexist on the same machine. This is a very useful
> functionality that we have been needing and using in our products
> for some time, through the VRF ptchset
> (http://linux-vrf.sourceforge.net/). The goal of the VRF patchset and
> network namespaces are very similar, yet some features of the VRF are
> missing that these patches intend to provide.
>
>
Hi,
I have been a silent observer of the network namespace work for a few
months. Like a couple of others, I also am interested in the functionality
provided by the linux-vrf patches presented here by Vivien. Eric Biederman
mentioned some sysfs patches that he was working on. Daniel Lezcano
submitted a proposed new socketat syscall. Other than that this thread
seems to have died a few months ago as far as I have been able to find.
I would like to find out if there is any updated status. I offer my help
in this effort. I am a new Linux developer, but I developed similar vrf
features in a BSD-based stack under VxWorks.
Thanks,
Bruce
next prev parent reply other threads:[~2009-03-25 18:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 13:05 [PATCH 0/6] netns: add linux-vrf features via network namespaces Vivien Chappelier
[not found] ` <4909B10A.8090403-L+G57L1VLRbR7s880joybQ@public.gmane.org>
2008-10-30 14:38 ` Andreas B Aaen
[not found] ` <200810301538.08032.andreas.aaen-546VmZ+UeKYX2WXlbB3fKg@public.gmane.org>
2008-10-30 15:03 ` Serge E. Hallyn
2008-10-30 16:20 ` Vivien Chappelier
[not found] ` <4909DEC8.9090102-L+G57L1VLRbR7s880joybQ@public.gmane.org>
2008-10-30 23:07 ` Eric W. Biederman
[not found] ` <m14p2tznoz.fsf-B27657KtZYmhTnVgQlOflh2eb7JE58TQ@public.gmane.org>
2008-10-31 9:46 ` Andreas B Aaen
[not found] ` <200810311046.17506.andreas.aaen-546VmZ+UeKYX2WXlbB3fKg@public.gmane.org>
2008-10-31 14:17 ` Daniel Lezcano
[not found] ` <490B1384.7030001-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2008-10-31 18:59 ` Eric W. Biederman
[not found] ` <m1zlkksi91.fsf-B27657KtZYmhTnVgQlOflh2eb7JE58TQ@public.gmane.org>
2008-10-31 19:32 ` Eric W. Biederman
[not found] ` <m13aicsgr2.fsf-B27657KtZYmhTnVgQlOflh2eb7JE58TQ@public.gmane.org>
2008-10-31 20:48 ` Daniel Lezcano
[not found] ` <490B6F19.4060206-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2008-10-31 23:10 ` Eric W. Biederman
2008-10-31 18:43 ` Eric W. Biederman
2009-03-25 18:21 ` Bruce Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-04-15 3:14 Krishna Vamsi-B22174
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=49CA761F.1020006@alcatel-lucent.com \
--to=bruce.jones-cfy2tcae7sfv+uja97dsa9bpr1lh4cv8@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=vivien.chappelier-L+G57L1VLRbR7s880joybQ@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.