linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jouni Malinen <j@w1.fi>
To: pat-lkml <pat-lkml@erley.org>
Cc: Jouni Malinen <jouni.malinen@atheros.com>,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH] ath9k: Add module parameter to disable hardware crypto
Date: Tue, 24 Feb 2009 17:07:10 +0200	[thread overview]
Message-ID: <20090224150710.GA1419@jm.kir.nu> (raw)
In-Reply-To: <49A40320.1040902@erley.org>

On Tue, Feb 24, 2009 at 09:24:32AM -0500, pat-lkml wrote:

> With this patch, and nohwcrypt=1, I get the following in hostapd (this
> system runs as an access point) when I try to associate with a client.
> 
> I can't say whether this is a hostapd problem or an ath9k problem yet,
> but it's a different behavior than with nohwcrypt=0 or without this 
> patch.  With this patch, wpa2 works perfectly, as without it, as well
> as wep working perfectly.  

Are you saying that you get different behavior from hostapd when
comparing nohwcrypt=0 and nohwcrypt=1 (i.e., no changes in the driver
code, just the module parameter change)?

> I wouldn't call this report a 'ACK/NACK' report as it has caused no
> new problems, nor fixed any old problems.  Unfortunately I don't have 
> a log around of the old behavior right now, for comparison.  I just 
> wanted to report what I've found based on this patch.

> wlan0: STA 00:1f:a7:70:2d:8d WPA: sending 1/4 msg of 4-Way Handshake
> wlan0: STA 00:1f:a7:70:2d:8d WPA: EAPOL-Key timeout
> wlan0: STA 00:1f:a7:70:2d:8d WPA: sending 1/4 msg of 4-Way Handshake
> wlan0: STA 00:1f:a7:70:2d:8d WPA: EAPOL-Key timeout
> wlan0: STA 00:1f:a7:70:2d:8d WPA: sending 1/4 msg of 4-Way Handshake
> wlan0: STA 00:1f:a7:70:2d:8d WPA: received EAPOL-Key frame (2/4 Pairwise)
> wlan0: STA 00:1f:a7:70:2d:8d WPA: invalid MIC in msg 2/4 of 4-Way Handshake
> wlan0: STA 00:1f:a7:70:2d:8d WPA: received EAPOL-Key 2/4 Pairwise with unexpected replay counter
> wlan0: STA 00:1f:a7:70:2d:8d WPA: received EAPOL-Key 2/4 Pairwise with unexpected replay counter
> wlan0: STA 00:1f:a7:70:2d:8d WPA: EAPOL-Key timeout

Which client are you using? Are you sure that the passphrase/PSK is set
correctly? The nohwcrypt patch should make absolutely no difference for
this part (this is key handshake which in the initial phase is sent
without encrypted EAPOL-Key frames, so neither sw nor hw crypto used).

-- 
Jouni Malinen                                            PGP id EFC895FA

  reply	other threads:[~2009-02-24 15:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-24 11:42 [PATCH] ath9k: Add module parameter to disable hardware crypto Jouni Malinen
2009-02-24 13:49 ` Johannes Berg
2009-02-24 14:06   ` Jouni Malinen
2009-02-24 14:23     ` Johannes Berg
2009-02-24 14:24 ` pat-lkml
2009-02-24 15:07   ` Jouni Malinen [this message]
2009-02-24 15:32     ` pat-lkml
2009-02-24 20:07       ` pat-lkml
2009-02-24 22:45         ` pat-lkml
2009-02-25 18:19         ` ath9k and TKIP hw crypto in AP mode Jouni Malinen
2009-02-25 23:46           ` pat-lkml
2009-02-26  0:10             ` pat-lkml
2009-02-26  9:10               ` Jouni Malinen
2009-02-24 16:15 ` [PATCH] ath9k: Add module parameter to disable hardware crypto Michael Buesch
2009-02-24 17:07   ` Jouni Malinen

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=20090224150710.GA1419@jm.kir.nu \
    --to=j@w1.fi \
    --cc=jouni.malinen@atheros.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pat-lkml@erley.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).