From: Ben Greear <greearb@candelatech.com>
To: Yeoh Chun-Yeow <yeohchunyeow@gmail.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: HT80 monitoring using ath10k
Date: Wed, 02 Sep 2015 21:33:17 -0700 [thread overview]
Message-ID: <55E7CD8D.7090003@candelatech.com> (raw)
In-Reply-To: <CAEFj984KSFw6a6kQTMO_80MM+tZqbQo3hq=faKWtS+oxk14zkQ@mail.gmail.com>
On 09/02/2015 08:32 PM, Yeoh Chun-Yeow wrote:
> On Thu, Sep 3, 2015 at 2:46 AM, Ben Greear <greearb@candelatech.com> wrote:
>> On 09/01/2015 06:20 PM, Yeoh Chun-Yeow wrote:
>>>
>>> Hi, all
>>>
>>> Anyone has able to capture the packet sent using HT80 or even higher
>>> putting ath10k in monitor mode?
>>>
>>> Please let me know. Thanks
>>
>>
>> I guess it would require wave-2 hardware to even have a chance of HT160?
>>
>> I thought HT80 capture worked fine on peregrine....I should have a chance to
>> try this for some upcoming IBSS work I have scheduled for my 10.1 firmware.
>
> Did you ever try it before with HT80?
>
> I set using the following after bring up the interface:
> iw moni0 set freq 5180 80 5210
>
> But not seeing any data packet and just those mgmt frame.
To be honest, I normally configure an AP on appropriate channels, and
then just start up a monitor interface. Then, stop the AP interface.
I have poor luck getting a monitor interface to reliably configure the
proper channel & width on its own.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2015-09-03 4:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 1:20 HT80 monitoring using ath10k Yeoh Chun-Yeow
2015-09-02 18:46 ` Ben Greear
2015-09-03 3:32 ` Yeoh Chun-Yeow
2015-09-03 4:33 ` Ben Greear [this message]
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=55E7CD8D.7090003@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=yeohchunyeow@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