From: Jouni Malinen <j@w1.fi>
To: Philip Prindeville <philipp_subx@redfish-solutions.com>
Cc: linux-wireless@vger.kernel.org,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: Marshaling issues w/ compat-wireless-2010-08-19
Date: Sat, 28 Aug 2010 20:12:39 +0300 [thread overview]
Message-ID: <20100828171239.GA23885@jm.kir.nu> (raw)
In-Reply-To: <4C746F74.70401@redfish-solutions.com>
On Tue, Aug 24, 2010 at 06:18:44PM -0700, Philip Prindeville wrote:
> I've got a stock Fedora Core 13 install (updated today) with the hostapd-0.6.10 rpm and hostapd-0.7.2 compiled from sources. The NIC is a Ubiquiti SR71e (AR9280).
> (2) Some highly unlikely values from the hostapd debugging messages when parsing out WEP authentication messages (line 507):
> authentication: STA=f8:1e:df:1e:c2:23 auth_alg=35510 auth_transaction=79 status_code=21688 wep=1
> Unsupported authentication algorithm (35510)
I was unable to reproduce this with the current development tree
snapshots. Shared key authentication worked with AR9280 and the current
wireless-testing.git and hostap.git in my tests. If you are still seeing
this, you could also try to disable hw crypto to remove one possible
issue area by using nohwcrypt=1 module parameter when loading ath9k.
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2010-08-28 17:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 1:18 Marshaling issues w/ compat-wireless-2010-08-19 Philip Prindeville
2010-08-25 8:11 ` Johannes Berg
2010-08-25 8:20 ` Johannes Berg
2010-08-25 17:23 ` Philip Prindeville
2010-08-25 18:42 ` Philip Prindeville
2010-08-25 18:44 ` Johannes Berg
2010-08-28 17:12 ` Jouni Malinen [this message]
2010-08-28 17:19 ` Philip Prindeville
2010-08-31 1:07 ` Philip Prindeville
2010-09-03 21:52 ` Philip Prindeville
2010-09-04 8:43 ` Johannes Berg
2010-09-04 22:45 ` Philip Prindeville
2010-09-14 13:04 ` Johannes Berg
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=20100828171239.GA23885@jm.kir.nu \
--to=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=philipp_subx@redfish-solutions.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).