ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Question on software-crypt mode.
Date: Wed, 11 Dec 2013 07:07:41 -0800	[thread overview]
Message-ID: <52A87FBD.4000901@candelatech.com> (raw)

Hello!

I am trying to implement software-crypt for ath10k so that it can do crypt
with multiple stations connected to same AP.

I tried using ath9k's approach and just not setting keys, but that does not work at all
(no stations can communicate).

If I basically leave code as is, then secondary stations can associate but never
get DHCP.  I see FCS and hw-crypt errored packets being received from the
ath10k firmware/chip.  This is probably because the chip/firmware decodes the
secondary station's packets with the first station's keys.
Transmitted packets (as sniffed from the AP) do appear fine.

I was thinking to just take all fcs and/or crypt-errored packets in
the receive path and somehow send them up the stack for the software-crypt
layer to (re)decrypt.  I think I have managed to get ath10k to send them
up, but still DHCP does not complete.

Does anyone have any suggestions for things to try or code to look at in
detail?

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

             reply	other threads:[~2013-12-11 15:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-11 15:07 Ben Greear [this message]
2013-12-13 10:53 ` Question on software-crypt mode Michal Kazior
2013-12-13 14:21   ` Ben Greear

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=52A87FBD.4000901@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath10k@lists.infradead.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox