From: Christian Lamparter <chunkeey@googlemail.com>
To: Ignacy Gawedzki <i@lri.fr>
Cc: linux-wireless@vger.kernel.org
Subject: Re: WPA in ad-hoc mode with carl9170
Date: Fri, 13 May 2011 22:31:47 +0200 [thread overview]
Message-ID: <201105132231.48232.chunkeey@googlemail.com> (raw)
In-Reply-To: <20110513174041.GA4690@zenon.in.qult.net>
On Friday 13 May 2011 19:40:41 Ignacy Gawedzki wrote:
> On Fri, May 13, 2011 at 12:39:53PM -0400, thus spake Brian Prodoehl:
> > Have you tested only with hw crypto? Try passing the nohwcrypt param
> > to the module while loading.
>
> I just tried that and at first it seemed to make no difference. But at some
> point, one of the two nodes of my testbed started to send encrypted frames
> (both broadcast and unicast) and the other node could receive them okay.
>
> Unfortunately, I just can't make the other node work (the difference being it
> is a x86_64 netbook vs. an i386 embedded atom industrial PC for the first
> node).
>
> My preliminary tests show that setting the nohwcrypt option makes no difference.
not too surprising, the driver does not set IEEE80211_HW_SUPPORTS_PER_STA_GTK.
Therefore the software crypto is always used in this case.
Note: there's a special bit [RX_MAC_CONTROL - bit 6] which instructs the key
cache controller to do the "key security settings" lookup with addr2 for all
bc/mc frames. If we enable this bit and modify carl9170_op_set_key to set the
per station gtk correctly [i.e.: use sta->addr as MAC and put the keys into
the per-sta space [0-63?]] we should be able to enable PER_STA_GTK...
although the driver will be restricted to a single vif [I think].
> Next week, I'll hopefully have more time to investigate and find a repeatable
> procedure to make that work or break.
you should try your setup with mac80211_hwsim first [so we can rule out all
driver bugs].
Regards,
Chr
next prev parent reply other threads:[~2011-05-13 20:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 16:01 WPA in ad-hoc mode with carl9170 Ignacy Gawedzki
2011-05-13 16:39 ` Brian Prodoehl
2011-05-13 17:40 ` Ignacy Gawedzki
2011-05-13 20:31 ` Christian Lamparter [this message]
2011-05-13 21:30 ` Christian Lamparter
2011-05-13 22:29 ` Ignacy Gawedzki
2011-05-13 22:21 ` Ignacy Gawedzki
2011-05-13 23:13 ` Christian Lamparter
2011-05-14 9:41 ` Ignacy Gawedzki
2011-05-14 11:05 ` Christian Lamparter
2011-05-14 15:38 ` WPA in ad-hoc mode (was: ...with carl9170) Ignacy Gawedzki
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=201105132231.48232.chunkeey@googlemail.com \
--to=chunkeey@googlemail.com \
--cc=i@lri.fr \
--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;
as well as URLs for NNTP newsgroup(s).