From: Daniel Lezcano <daniel.lezcano@free.fr>
To: emil@linux.org.pl
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, ebiederm@maxwell.aristanetworks.com
Subject: Re: Loopback and net namespace
Date: Sat, 25 Apr 2009 21:50:14 +0200 [thread overview]
Message-ID: <49F36976.4090701@free.fr> (raw)
In-Reply-To: <20090424.221923.232357312.davem@davemloft.net>
David Miller wrote:
> From: emil@linux.org.pl
> Date: Fri, 24 Apr 2009 23:55:36 +0200 (CEST)
>
>
>> Currently it is impossible to use both net namespace and sysfs
>> because sysfs does not allow two devices with the same name
>> and each net namespace has to have loopback device.
>>
>> To have this working there must be possibility to
>> create loopback devices with different names.
>>
>> The easiest way to acomplish this seems to be with this patch below.
>>
>> I know the devices will be seen in each namespace, but sometimes
>> the only thing that is needed is network environment separation.
>> For example when I need to run two different services on the same TCP
>> port
>> bound to 0.0.0.0.
>>
>> This patch will not break anything and allow people to test
>> net namespace functionality.
>>
I don't think you have to patch anything if you try a kernel >= 2.6.29.
The sysfs restriction has been solved by disabling the registering of
the kobject when we are not in the initial network namespace.
For more information you can check this commit:
http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6-stable.git;a=commit;h=3891845e1ef6e6807075d4241966b26f6ecb0a5c
Regards,
-- Daniel
next prev parent reply other threads:[~2009-04-25 19:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 21:55 Loopback and net namespace emil
2009-04-25 5:19 ` David Miller
2009-04-25 19:50 ` Daniel Lezcano [this message]
2009-04-25 14:00 ` Serge E. Hallyn
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=49F36976.4090701@free.fr \
--to=daniel.lezcano@free.fr \
--cc=davem@davemloft.net \
--cc=ebiederm@maxwell.aristanetworks.com \
--cc=emil@linux.org.pl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).