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-next>] [day] [month] [year] [list]
Date:   Thu, 14 Jun 2018 16:04:57 +0800
From:   Pamela Mei <pamela.mei@...il.com>
To:     netdev@...r.kernel.org
Subject: Request to enable setting the nested network namespace

In linux, set up 2 network namespaces, ns1 and ns2. "ip netns list"
can view the 2 network namespaces.
Move one network device from linux root namespace to ns1 then from ns1
to ns2, then delete ns2,
expect that network device can move back to ns1,
but actual result is that eth1 is back to linux root network
namespace. I'm not sure whether it's as expected.

Here is the detail test steps:

1.ip netns add ns1

2.ip netns add ns2

3.ip link set eth1 netns ns1

4.ip netns exec ns1 ip link set eth1 netns ns2

5.ip netns del ns2

Expected result: eth1 will be in ns1

Actual result: eth1 is back in linux root namespace 1

Question: is there any method to realize such scenario to make sure
device can be back to ns1 not linux root network namespace 1?

How about if there's a function to enable nest network namespace e.g.
can set ns1 as the parent namespace of ns2, then device can return to
ns1 when ns2 is gone.


Cheers,

Pamela MEI

Powered by blists - more mailing lists