Thread (2 messages) 2 messages, 2 authors, 2014-12-24

Re: [PATCH net-next] Allow to set net namespace for wireless device via RTM_LINK

From: Vadim Kochan <hidden>
Date: 2014-12-24 09:48:49
Also in: linux-wireless

On Mon, Oct 20, 2014 at 1:52 PM, Johannes Berg
[off-list ref] wrote:
On Mon, 2014-10-20 at 12:46 +0200, Marcel Holtmann wrote:
quoted
Maybe relaxing the check and allow ip link to move a wireless netdev
into a namespace (and having the wiphy follow) could be allowed if it
is the only netdev or the original wlan0 that each wiphy creates. I
really do not know if this is worth it, but for some simpler container
cases it could be beneficial if RTNL can be used instead of having to
go through nl80211.
The thought crossed my mind, but

1) it's relatively complex, though by no means impossible
2) it still moves more than you bargained for, since in theory the wiphy
could be
   used to create new interfaces etc.

That said, I'm much more inclined to believe such a patch would be
worthwhile than the original.

johannes
Hi Johannes,

What about the following thoughts:

    1) Set NETIF_F_NETNS_LOCAL for phy wireless device only if there
is at least one virtual interface which was created on it
    2) What about to inherit netns for newer created interfaces from
the phy device ?

Thanks,
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help