From: Ben Greear <greearb@candelatech.com>
To: zhj <zhj@topsec.com.cn>, ath10k@lists.infradead.org
Subject: Re: About promis mode
Date: Thu, 28 Dec 2017 12:09:28 -0800 [thread overview]
Message-ID: <5A454F78.8070502@candelatech.com> (raw)
In-Reply-To: <000e01d37fc3$ab4e6bf0$01eb43d0$@topsec.com.cn>
On 12/28/2017 02:07 AM, zhj wrote:
> Hi，
> I used to work on the AR9344+AR9382 platform (using openwrt+ath9k driver) to
> achieve the following functions: setting up Promiscuous mode, scanning all
> channels,capturing radio packets, If finding AP fishing, then sending deauth
> packets to break illegal connections.
>
> Now we use ath10k to drive QCA988X (openwrt platform, QCA956X+QCA988X),
> which can set up promiscuous mode to catch wireless packets, but cannot send
> packets to break connection. However 2.4G wireless network card can achieve
> the above functions(including the switching channel).
>
> Can this be done on QCA988X?
> Where is there a patch to implement this function?
I think this will require modified firmware. I recently tested some improvements
to raw tx on monitor devices with CT firmware...you might give it a try. It is
available in LEDE already, though the new features that allows specifying the rate-code
is only in beta wave-1 firmware and drivers:
http://www.candelatech.com/ath10k.php
Thanks,
Ben
>
>
>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
>
--
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:[~2017-12-28 17:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-28 10:07 About promis mode zhj
2017-12-28 20:09 ` 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=5A454F78.8070502@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=zhj@topsec.com.cn \
/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