linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wilson <wkevils@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: wireless network interfaces and network namespaces
Date: Sat, 30 Nov 2013 15:58:10 +0200	[thread overview]
Message-ID: <CAGXs5wVt3okeE6oA_pNV5WnQLv51+bf+n+52s5d7tQkXq_qvNw@mail.gmail.com> (raw)
In-Reply-To: <1385817282.5056.0.camel@jlt4.sipsolutions.net>

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.




On Sat, Nov 30, 2013 at 3:14 PM, Johannes Berg
<johannes@sipsolutions.net> wrote:
> On Sat, 2013-11-30 at 14:12 +0200, Kevin Wilson wrote:
>> Hello,
>> I am trying to move a wireless interface to a network namespace I
>> created and I get an error:
>>
>> ip link set wlan0 netns ns1
>> RTNETLINK answers: Invalid argument
>>
>> I do it with latest iproute2 git sources,  on 3.8 kernel.
>>
>> I want to verify this: all wireless interfaces do no support
>> network namespace. Is this true ? what in fact is the reason for this ?
>
> At least mac80211-based wireless interfaces *do* support namespaces, but
> you have to change the entire wireless NIC's namespace using iw --
> having different virtual interfaces of the same NIC in different
> namespaces is not supported.
>
> johannes
>

  parent reply	other threads:[~2013-11-30 13:58 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 [this message]
2013-11-30 19:35     ` Johannes Berg
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=CAGXs5wVt3okeE6oA_pNV5WnQLv51+bf+n+52s5d7tQkXq_qvNw@mail.gmail.com \
    --to=wkevils@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).