netdev - Re: [patch 05/12] net namespace : ioctl to push ifa to net namespace l3

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: <45B2018B.5030807@fr.ibm.com>
Date:	Sat, 20 Jan 2007 12:48:27 +0100
From:	Daniel Lezcano <dlezcano@...ibm.com>
To:	Herbert Poetzl <herbert@...hfloor.at>
CC:	containers@...ts.osdl.org, netdev@...r.kernel.org
Subject: Re: [patch 05/12] net namespace : ioctl to push ifa to net namespace
 l3

Herbert Poetzl wrote:
> On Fri, Jan 19, 2007 at 04:47:19PM +0100, dlezcano@...ibm.com wrote:
>> From: Daniel Lezcano <dlezcano@...ibm.com>
>>
>> New ioctl to "push" ifaddr to a container. Actually, the push is done
>> from the current namespace, so the right word is "pull". That will be
>> changed to move ifaddr from l2 network namespace to l3.
>>
>> Signed-off-by: Daniel Lezcano <dlezcano@...ibm.com>
>>

[ ... ]

>> + * namespace to his l2 network namespace parent.
> 
> hmm, sounds like the address is moved between the
> namespaces? does that mean that the 'parent' will
> not see the 'isolated' ip anymore?

Yes, exact. If the IP address is visible into several namespaces (L2 
parent and L3 child), nothing ensures the two will not use the IP address.

-
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