From: Daniel Lezcano <daniel.lezcano@free.fr>
To: "Martín Ferrari" <martin.ferrari@gmail.com>
Cc: netdev <netdev@vger.kernel.org>,
Mathieu Lacage <mathieu.lacage@sophia.inria.fr>
Subject: Re: Namespaces and devices
Date: Sun, 23 May 2010 16:04:38 +0200 [thread overview]
Message-ID: <4BF935F6.2050907@free.fr> (raw)
In-Reply-To: <AANLkTimN8IYQBiot2iBB6XV8dtTGRnHQQ6lKLag5plEm@mail.gmail.com>
On 05/21/2010 06:27 PM, Martín Ferrari wrote:
> Hi,
>
> Sorry if this is a dumb question, but I couldn't find any
> documentation that matches the current behaviour... So I don't know if
> what I see is what is intended, or if it's a bug.
>
> I would like to know what is the exact behaviour re. devices when a
> netns is destroyed, and which kind of devices can be moved.
>
> According to http://lxc.sourceforge.net/network/configuration.php,
> devices assigned to a netns should move to the main netns when the
> former is destroyed. What I see is that the devices are deleted, at
> least for veth and dummy devices. I also see a bug I previously
> reported that caused an oops in some cases.
>
The documentation on this website is a bit out dated. That was the
initial behavior but was changed as the following.
All the virtual devices are destroyed with the network namespace. The
destroyable virtual devices are identified when they have the dellink
ops defined. If you can do the 'ip link del' command on this device,
then this device type will be destroyed by a netns.
About the oops, was the it "kernel panic when using
netns+bridges+tc(netem)" ?
> Also, I have read somewhere (now I cannot find it) that supposedly, I
> should be able to move real devices to a netns, but I always get
> Invalid argument errors.
Yes, that was previously the case with the proof of concept, because
sysfs per namespace was enabled. But this feature is not merged upstream
yet (but is on the way), so physical devices are not movable across
namespaces.
Hope that helps
-- Daniel
next prev parent reply other threads:[~2010-05-23 14:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 16:27 Namespaces and devices Martín Ferrari
2010-05-23 14:04 ` Daniel Lezcano [this message]
2010-05-25 9:56 ` Martín Ferrari
2010-05-25 10:14 ` Daniel Lezcano
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=4BF935F6.2050907@free.fr \
--to=daniel.lezcano@free.fr \
--cc=martin.ferrari@gmail.com \
--cc=mathieu.lacage@sophia.inria.fr \
--cc=netdev@vger.kernel.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.