Just tried the patch from message #133 and it worked against 3.2.9 as well
as 3.3.0-rc6 (master as of the time I cloned earlier today) with no other
modifications to the instructions contained in that message. The patch
appears to be holding up, after at least two successful rekeyings the
Hi,
Johannes Berg wrote:
On Mon, 2012-02-27 at 05:33 +, Ben Hutchings wrote:
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
Hi,
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
Hi Ben,
Thanks for the report.
On Mon, 2012-02-27 at 05:33 +, 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
Hi Ben/Johannes,
On Mon, 2012-02-27 at 10:02 +0100, Johannes Berg wrote:
Hi Ben,
Thanks for the report.
On Mon, 2012-02-27 at 05:33 +, 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:
tags 651199 = upstream patch
quit
Johannes Berg wrote:
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
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
7 matches
Mail list logo