From: Chris Friesen <chris.friesen@genband.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: shemminger@vyatta.com, netdev@vger.kernel.org,
Linux Containers <containers@lists.osdl.org>
Subject: Re: [PATCH] iproute2: Add processless network namespace support.
Date: Thu, 26 May 2011 15:35:15 -0600 [thread overview]
Message-ID: <4DDEC793.8040502@genband.com> (raw)
In-Reply-To: <m1hb8hyyaj.fsf@fess.ebiederm.org>
On 05/26/2011 02:58 PM, Eric W. Biederman wrote:
>
> The goal of this code change is to implement a mechanism such that it is
> simple to work with a kernel that is using multiple network namespaces
> at once.
>
> This comes in handy for interacting with vpns where there may be rfc1918
> address overlaps, and different policies default routes, name servers
> and the like.
>
> Configuration specific to a network namespace that would ordinarily be
> stored under /etc/ is stored under /etc/netns/<name>. For example if
> the dns server configuration is different for your vpn you would create
> a file /etc/netns/myvpn/resolv.conf.
That would be interesting. Currently I use dnsmasq to keep my DNS
servers straight when connecting in to two different corporate VPNs
simultaneously.
I could see it being interesting trying to remember which shell sessions
were running in which network namespace...
Chris
--
Chris Friesen
Software Developer
GENBAND
chris.friesen@genband.com
www.genband.com
next prev parent reply other threads:[~2011-05-26 21:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 20:58 [PATCH] iproute2: Add processless network namespace support Eric W. Biederman
2011-05-26 20:58 ` Eric W. Biederman
2011-05-26 21:35 ` Chris Friesen [this message]
2011-05-27 0:45 ` Eric W. Biederman
2011-06-29 21:27 ` Eric W. Biederman
2011-06-29 21:27 ` Eric W. Biederman
2011-06-29 21:37 ` Stephen Hemminger
2011-06-29 21:37 ` Stephen Hemminger
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=4DDEC793.8040502@genband.com \
--to=chris.friesen@genband.com \
--cc=containers@lists.osdl.org \
--cc=ebiederm@xmission.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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 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.