netdev - Re: [PATCH 6/6] netns: configurable number of initial network namespaces

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <49075488.8030002@thomson.net>
Date:	Tue, 28 Oct 2008 19:06:00 +0100
From:	Vivien Chappelier <vivien.chappelier@...mson.net>
To:	Patrick McHardy <kaber@...sh.net>
CC:	netdev <netdev@...r.kernel.org>,
	David Miller <davem@...emloft.net>,
	Benjamin Thery <benjamin.thery@...l.net>, jleu@...dspring.com,
	linux-vrf-general@...ts.sourceforge.net
Subject: Re: [PATCH 6/6] netns: configurable number of initial network	namespaces

Hi,

    Yes; the linux-vrf patches had a new netlink message to 
create/remove the equivalent of a network namespace (ip vrf add 1). I've 
not ported this feature yet, so this patch is meant to provide another 
way of setting up networking stacks without the need for a new process 
for each stack. The ability to dynamically create/remove networking 
stacks from userspace would definitely be useful.
    There are also some very minor advantages in creating the namespaces 
statically at boot time, such as increasing the chances that the 
allocation works (though network namespaces are quite small), and 
improving boot time by avoiding a few calls to /sbin/ip on startup. 
Since we are running on embedded devices, that is something that matter 
to us, but it may not be enough to justify the need for this feature. 
Anyway, I do not think it hurts to have the ability to create static 
networking stacks at boot time.

regards,
Vivien.

Patrick McHardy wrote:
> Vivien Chappelier wrote:
>> This allows the creation of more than one network namespace at boot 
>> time.
>
> I'm wondering, what is the advantage over creating them manually?
> They have to be configured by userspace to be useful anyway, don't
> they?
>
>

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html