From: Ben Greear <greearb@candelatech.com>
To: Michal Kazior <michal.kazior@tieto.com>,
s prasad <sprasad.kandregula@gmail.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
Kalle Valo <kvalo@qca.qualcomm.com>
Subject: Re: Ath10 firmware crashing in Monitor mode(Sniffer mode)
Date: Tue, 12 May 2015 07:41:06 -0700 [thread overview]
Message-ID: <55521102.9020306@candelatech.com> (raw)
In-Reply-To: <CA+BoTQmLFGAn2z=E3J1C2qfNP34v57B7-rtALUQhNXrHqJeA6Q@mail.gmail.com>
On 05/12/2015 03:14 AM, Michal Kazior wrote:
> On 12 May 2015 at 11:31, s prasad <sprasad.kandregula@gmail.com> wrote:
>> May I know, is this firmware or driver constraint?
>> If somebody have patch for this, am ready to test it.
>
> Short answer: There's nothing, yet.
>
> Long answer:
>
> From what I know official firmware doesn't support injecting packets
> via monitor vdev. This is a firmware limitation.
>
> A way around this may be creating and using an additional vdev, e.g.
> AP. This will be rather ugly but may work. There's no patch for it.
>
> An alternative would be to ask Ben to modify his CT-firmware branch.
I gave this a decent try a month or two ago, and had no luck. The hardware
(from what I can tell), just will not send a frame to an unknown peer.
I noticed the other day that ANQP will not work on ath10k, and I suspect
similar issues..so I will be in that code again. Maybe I'll learn
how to trick it into sending arbitrary frames.
All that said, there is no way to specify rate-ctrl info on a per-pkt
basis when injecting frames, so I don't know what good injecting frames
on a mgt device will accomplish.
Thanks,
Ben
> Also there's a problem with submitting raw 802.11 frames to firmware.
> There's some work ongoing [1].
>
> [1]: http://lists.infradead.org/pipermail/ath10k/2015-May/005144.html
>
>
> Michał
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2015-05-12 14:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-10 20:56 Ath10 firmware crashing in Monitor mode(Sniffer mode) s prasad
2015-05-11 5:50 ` Michal Kazior
2015-05-11 10:51 ` s prasad
2015-05-11 11:08 ` Michal Kazior
[not found] ` <CAJa-X96KPw6dY0pK1zc8UD4TdQcG0KuA3m6DSueVVyK-VPhn9g@mail.gmail.com>
2015-05-12 5:03 ` Michal Kazior
2015-05-12 9:31 ` s prasad
2015-05-12 10:14 ` Michal Kazior
2015-05-12 14:41 ` Ben Greear [this message]
2015-05-12 15:08 ` s prasad
2015-08-13 20:35 ` s prasad
2015-08-13 20:43 ` Ben Greear
2015-08-13 21:01 ` S Prasad Kandregula
2015-08-14 15:57 ` Ben Greear
2015-05-12 12:19 ` Kalle Valo
2015-05-12 12:34 ` Michal Kazior
2015-05-12 12:53 ` Kalle Valo
2015-05-11 8:52 ` Mário Lopes
2015-05-11 9:14 ` Michal Kazior
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=55521102.9020306@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.com \
--cc=sprasad.kandregula@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;
as well as URLs for NNTP newsgroup(s).