public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Kevin Wilson <wkevils@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: wireless network interfaces and network namespaces
Date: Sat, 30 Nov 2013 20:35:49 +0100	[thread overview]
Message-ID: <1385840149.4267.1.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CAGXs5wVt3okeE6oA_pNV5WnQLv51+bf+n+52s5d7tQkXq_qvNw@mail.gmail.com> (sfid-20131130_145812_659093_751E3F17)

On Sat, 2013-11-30 at 15:58 +0200, Kevin Wilson wrote:
> Thanks!
> Running:
> iw phy phy0 set netns 3433
> indeed moved wlan0 to the network namespace I created, where process 3433 ran.
> I did not see a way to specify the network namespace name for moving
> wlan0 in this command (at least iw help does not show it and  I am
> using iw 3.4-1 on ubuntu). I did not looked into the source code of iw
> though.

No, that's not supported since all virtual interfaces (e.g. wlan0)
belonging to a device (e.g. phy0) must move namespaces together.
Otherwise you could do

iw wlan0 interface add wlan0b type managed

and then try to move wlan0 while wlan0b stays in the namespace. In
theory that might actually be useful given appropriate resource
reservation and multi-interface/multi-channel capable devices, but it
would require a massive effort to get it right - it's not useful
enough ;)

johannes


  reply	other threads:[~2013-11-30 19:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-30 12:12 wireless network interfaces and network namespaces Kevin Wilson
2013-11-30 12:45 ` Sergey Ryazanov
2013-11-30 13:14 ` Johannes Berg
2013-11-30 13:36   ` Sergey Ryazanov
2013-11-30 13:57     ` Johannes Berg
2013-11-30 13:58   ` Kevin Wilson
2013-11-30 19:35     ` Johannes Berg [this message]
2014-05-22  8:54       ` Hannes Raddatz
2014-05-22 10:46         ` Johannes Berg

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=1385840149.4267.1.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=wkevils@gmail.com \
    /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