From: ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org (Eric W. Biederman)
To: Elwin Stelzer Eliazer <stelzere-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org"
<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
Subject: Re: container-to-host virtual or loopback kind of interface support
Date: Mon, 27 Apr 2009 21:19:35 -0700 [thread overview]
Message-ID: <m1iqkpv294.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <638f07d70904271500u1f0a13cbif1c5db64bdb520ab-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> (Elwin Stelzer Eliazer's message of "Mon\, 27 Apr 2009 15\:00\:38 -0700")
Elwin Stelzer Eliazer <stelzere-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> Thanks Eric for your detailed response.
>
> On the PPP interfaces under namespace, how do i configure them under lxc
> config? Are there other types like "veth" and "macvlan" for PPP?
veth and macvlan are created with
ip link add .... type veth ....
ip link add .... type macvlan ...
ppp is created normally.
I have never run lxc and find it's interface inflexible for my needs so I don't
know the specifics there.
> And i believe the container app that opens the /dev/tun gets ownership of the
> file handle, and several container apps can open this in parallel, and they do
> not interfere. Even if the containers do not have separate rootfs, this is the
> case. Please confirm on these.
It is the tun SETIFF ioctl that specifies which interface a tun device connect to.
But yes several tun/tap work just in a container.
Eric
prev parent reply other threads:[~2009-04-28 4:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 22:49 container-to-host virtual or loopback kind of interface support Elwin Stelzer Eliazer
[not found] ` <638f07d70904081549h442c4bb0l401fa08f4980b217-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-04-09 13:57 ` Serge E. Hallyn
[not found] ` <20090409135724.GA26467-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-04-09 16:00 ` Elwin Stelzer Eliazer
[not found] ` <D02204CF-796A-45F5-B9A2-5B581EB52A2F-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-04-09 19:14 ` Serge E. Hallyn
[not found] ` <20090409191402.GA561-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-04-09 23:28 ` Elwin Stelzer Eliazer
[not found] ` <638f07d70904091628o25d11b95oa8614a0585df4cf5-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-04-25 7:27 ` Eric W. Biederman
[not found] ` <m1iqktw5uq.fsf-+imSwln9KH6u2/kzUuoCbdi2O/JbrIOy@public.gmane.org>
2009-04-25 14:38 ` Elwin Stelzer Eliazer
[not found] ` <638f07d70904250738j987ed6j685372651346634a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-04-25 18:51 ` Eric W. Biederman
[not found] ` <m1k558va5u.fsf-+imSwln9KH6u2/kzUuoCbdi2O/JbrIOy@public.gmane.org>
2009-04-26 8:08 ` Elwin Stelzer Eliazer
[not found] ` <638f07d70904260108s3ca2eb5cpcbed37d5ba002d42-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-04-26 21:37 ` Eric W. Biederman
[not found] ` <m1fxfvp04e.fsf-+imSwln9KH6u2/kzUuoCbdi2O/JbrIOy@public.gmane.org>
2009-04-27 22:00 ` Elwin Stelzer Eliazer
[not found] ` <638f07d70904271500u1f0a13cbif1c5db64bdb520ab-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-04-28 4:19 ` Eric W. Biederman [this message]
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=m1iqkpv294.fsf@fess.ebiederm.org \
--to=ebiederm-as9lmozglivwk0htik3j/w@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=stelzere-Re5JQEeQqe8AvxtiuMwx3w@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.