From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Wey-Yi Guy <wey-yi.w.guy@intel.com>,
Intel Linux Wireless <ilw@linux.intel.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
651199@bugs.debian.org,
Andreas Gustafsson <olangu@impressions.se>,
Marco d'Itri <md@Linux.IT>,
Gabriel Kerneis <kerneis@pps.jussieu.fr>
Subject: Re: iwlwifi WPA-TKIP crypto failure after group rekeying
Date: Mon, 27 Feb 2012 10:02:34 +0100 [thread overview]
Message-ID: <1330333354.3483.6.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1330320802.8460.105.camel@deadeye> (sfid-20120227_063327_782741_C11A1DED)
Hi Ben,
Thanks for the report.
On Mon, 2012-02-27 at 05:33 +0000, Ben Hutchings wrote:
> Several Debian users (cc'd) have reported a regression in iwlagn in
> Linux 3.1, not fixed in 3.2. The full bug log is at:
>
> http://bugs.debian.org/651199
>
> To summarise, a WPA-TKIP managed connection stops passing traffic and
> the kernel log shows the message "WPA: Group rekeying". This apparently
> doesn't happen if the connection is in heavy use at the time or with
> module parameter swcrypto=1. WPA2 is not affected either.
I think this is due to my patch "iwlagn: rewrite HW crypto" which
accidentally broke key *removal* (of all things), which causes issues
when the first GTK is removed on the second rekeying.
This patch
http://git.kernel.org/?p=linux/kernel/git/iwlwifi/iwlwifi.git;a=commitdiff;h=5dcbf480473f6c3f06ad2426b7517038a2a18911
should fix it. Wey has sent it to John, but he hasn't picked it up yet
for some reason -- it's also marked for stable.
It'd be great to get confirmation that this is the problem, I'm not sure
I'll find time today to reproduce the problem.
johannes
next prev parent reply other threads:[~2012-02-27 9:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 5:33 iwlwifi WPA-TKIP crypto failure after group rekeying Ben Hutchings
2012-02-27 9:02 ` Johannes Berg [this message]
2012-02-27 13:59 ` Guy, Wey-Yi
2012-02-28 2:02 ` Jonathan Nieder
2012-03-05 4:53 ` Jonathan Nieder
2012-03-05 6:52 ` 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=1330333354.3483.6.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=651199@bugs.debian.org \
--cc=ben@decadent.org.uk \
--cc=ilw@linux.intel.com \
--cc=kerneis@pps.jussieu.fr \
--cc=linux-wireless@vger.kernel.org \
--cc=md@Linux.IT \
--cc=olangu@impressions.se \
--cc=wey-yi.w.guy@intel.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).