From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Felix Fietkau <nbd@openwrt.org>
Cc: linux-wireless@vger.kernel.org
Subject: WEP-LEAP regression
Date: Wed, 20 Jun 2012 16:33:31 +0200 [thread overview]
Message-ID: <20120620143330.GA8505@redhat.com> (raw)
Our QA reported regression on ath9k connecting to legacy WEP-LEAP AP,
with the following supplicant parameters:
fast_reauth=1
ap_scan=1
eapol_version=1
network={
ssid="qe-wep-enterprise-cisco"
key_mgmt=IEEE8021X
auth_alg=LEAP
eap=LEAP
identity="AAA"
password="BBB"
}
Device associate but DHCP fails (we do no recive any frame).
Reverting both related commits:
commit f88373fa47f3ce6590fdfaa742d0ddacc2ae017f
Author: Felix Fietkau <nbd@openwrt.org>
Date: Sun Feb 5 21:15:17 2012 +0100
ath9k: fix a WEP crypto related regression
and
commit 7a532fe7131216a02c81a6c1b1f8632da1195a58
Author: Felix Fietkau <nbd@openwrt.org>
Date: Sat Jan 14 15:08:34 2012 +0100
ath9k_hw: fix interpretation of the rx KeyMiss flag
fixes the problem.
Felix could you look at this?
Stanislaw
next reply other threads:[~2012-06-20 14:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 14:33 Stanislaw Gruszka [this message]
2012-06-20 19:59 ` WEP-LEAP regression Felix Fietkau
2012-06-21 10:21 ` Stanislaw Gruszka
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=20120620143330.GA8505@redhat.com \
--to=sgruszka@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@openwrt.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).