All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: How to configure monitor devices for HT80?
Date: Tue, 06 May 2014 10:56:16 -0700	[thread overview]
Message-ID: <53692240.5010001@candelatech.com> (raw)
In-Reply-To: <1399317771.22235.23.camel@jlt4.sipsolutions.net>

On 05/05/2014 12:22 PM, Johannes Berg wrote:
> On Mon, 2014-05-05 at 12:06 -0700, Ben Greear wrote:
>> I'm trying to sniff using a monitor interface on ath10k, on channel 36.
>>
>> I'm seeing lots of packets, but not all that the AP claims to be sending
>> (when sniffing vap0).  I am not not certain the monitor interface is
>> using HT80 or not.
>>
>> Anyone have a working example of the proper iw commands to create
>> a monitor interface on channel 36 for HT80?
> 
> ...
> iw wlan0 set freq 5180 80 5210

Thanks, this works at least most of the time.

But, it seems if I have another vif up, it will fail, even if that
vif is (should be?) using the exact same frequency.

./local/sbin/iw phy wiphy0 interface add moni0 type monitor
./local/sbin/ip link set dev moni0 up
./local/sbin/iw dev moni0 set freq 5180 80 5210
-> yields error:
command failed: Device or resource busy (-16)


I'm not absolutely certain the monitor device still works
properly or not, but it at least mostly works.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


  reply	other threads:[~2014-05-06 17:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-05 19:06 How to configure monitor devices for HT80? Ben Greear
2014-05-05 19:22 ` Johannes Berg
2014-05-06 17:56   ` Ben Greear [this message]
2014-05-07  9:01     ` Johannes Berg
2014-05-07 12:41       ` Ben Greear
2014-05-07 12:57         ` 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=53692240.5010001@candelatech.com \
    --to=greearb@candelatech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.