From: Ben Greear <greearb@candelatech.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>,
Michal Kazior <michal.kazior@tieto.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [RFC] ath10k: use raw tx
Date: Thu, 11 Sep 2014 07:17:39 -0700 [thread overview]
Message-ID: <5411AF03.9010008@candelatech.com> (raw)
In-Reply-To: <87ha0e302p.fsf@kamboji.qca.qualcomm.com>
On 09/11/2014 03:47 AM, Kalle Valo wrote:
> Michal Kazior <michal.kazior@tieto.com> writes:
>
>> On 29 August 2014 23:45, Ben Greear <greearb@candelatech.com> wrote:
>>> On 08/22/2014 12:52 AM, Michal Kazior wrote:
>>>> This is just a reference for anyone interested in
>>>> getting injection working with ath10k.
>>>
>>> Did you try this with encryption? I can reproduce the crash
>>> in open mode on my CT firmware, but I couldn't even get
>>> DHCP to complete with wpa2 enabled.
>>
>> Hi,
>>
>> Late reply, sorry.
>>
>> I've just did a quick test on 10.2 (both AP and STA) with WPA2.
>> Apparently the raw tx mode requires IV to be set up on host and packet
>> length (reported in HTT Tx command header) must be re-adjusted
>> differently, otherwise frames are broken (incorrect FCS, too long,
>> somewhat encrypted except LLC/SNAP). The best I could get were
>> FCS-correct undecryptable frames on air. Perhaps someone will figure
>> that out..
>>
>> Another way around this would be to perform software crypto for tx
>> entirely on host.
>
> BTW, it would be nice to get software crypto support to ath10k, for
> example with a nohwcrypt module parameter like ath9k has.
You have to hack the firmware (and patch driver) to make this work. I have patches to make
rx-sw-crypt work with my CT firmware. Been releasing this only for non-commercial
use, but I'd be willing to make it supported without restriction and instead
limit number of stations to < 16 when sw-crypt was enabled. This leaves my
commercial offering worth paying for for the few people that might compete against
our testing products.
I had all sorts of trouble, similar to what you describe trying to get raw tx
to work, and eventually gave up entirely. My method of rx-sw-crypt uses normal tx
(with hardware offload), but decrypts on the host.
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
next prev parent reply other threads:[~2014-09-11 14:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 7:52 [RFC] ath10k: use raw tx Michal Kazior
2014-08-29 7:15 ` Yeoh Chun-Yeow
2014-08-29 7:27 ` Michal Kazior
2014-08-29 8:07 ` Yeoh Chun-Yeow
2014-08-29 21:45 ` Ben Greear
2014-08-30 2:59 ` Ben Greear
2014-09-11 10:35 ` Michal Kazior
2014-09-11 10:47 ` Kalle Valo
2014-09-11 14:17 ` Ben Greear [this message]
2014-09-11 14:19 ` Ben Greear
2014-09-12 10:41 ` Yeoh Chun-Yeow
2014-09-12 11:05 ` Michal Kazior
2014-09-13 1:07 ` Yeoh Chun-Yeow
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=5411AF03.9010008@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.com \
--cc=michal.kazior@tieto.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