linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kilian risse <krisse@student.ethz.ch>
To: Dan Williams <dcbw@redhat.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Virtual Interfaces with iwlwifi
Date: Mon, 9 Mar 2015 20:48:17 +0100	[thread overview]
Message-ID: <54FDF901.8060808@student.ethz.ch> (raw)
In-Reply-To: <1425921599.32409.4.camel@redhat.com>

I think I figured it out - I tried to create two interfaces of the same 
type station - which is not supported according to the "iw phy0 info".

I use a intel 7260 card with a 3.18.7 Kernel.
The command I used was "iw phy phy0 interface add wlan0 type station".
Is this a limitation in hardware or software?

Kilian

On 03/09/2015 06:19 PM, Dan Williams wrote:
> On Mon, 2015-03-09 at 16:53 +0000, Risse Kilian wrote:
>> Hi
>>
>> I tried to create a second interface and connect to another AP. But I was unable to do so. As I tried to enable the second interface I got an error: Device or resource busy. So am I right assuming that this is not possible with the iwlwifi driver?
>
> What specific hardware do you have?
> What kernel version do you have?
> What specific command were you using to create the second interface?
> What are the "software interface modes" and "valid interface
> combinations" sections output from "iw phy0 info"?
>
> It's certainly possible and supported with iwlwifi, but it depends on
> specific hardware, the driver, etc.
>
> Dan
>

  reply	other threads:[~2015-03-09 19:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <C768C63E9A2F584FACC2A65D915E5A2830535956@MBX13.d.ethz.ch>
2015-03-09 16:53 ` Virtual Interfaces with iwlwifi Risse  Kilian
2015-03-09 17:19   ` Dan Williams
2015-03-09 19:48     ` kilian risse [this message]
2015-03-10 14:10       ` Emmanuel Grumbach

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=54FDF901.8060808@student.ethz.ch \
    --to=krisse@student.ethz.ch \
    --cc=dcbw@redhat.com \
    --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).