All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Wolfgang Breyha <wbreyha@gmx.net>
Cc: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: iwlwifi havoc on some APs (rekeying?)
Date: Mon, 12 Dec 2011 10:04:17 +0100	[thread overview]
Message-ID: <1323680657.3442.7.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4EE35877.1060507@gmx.net> (sfid-20111210_140255_490293_C3C0F113)

On Sat, 2011-12-10 at 14:02 +0100, Wolfgang Breyha wrote:
> On 09/12/11 19:26, Johannes Berg wrote:
> > What's "this area"? This isn't exactly the first report of random memory
> > corruption ... I think the last one was something with 32/64 bit but I
> > don't remember.
> 
> To narrow down "this area" I tried the following:
> 
> *) I reconfigured my soekris AP hostapd to use wpa_group_rekey=0
>    .... and it works like a charm since then
> 
> *) I reconfigured the ubiquiti UniFi AP to use wpa_group_rekey=120
>    ... and I'am pretty sure now that it is exactly the second rekeying
>    that starts messing up the system. Exactly after wpa_supplicant logs
> WPA: Group rekeying completed with 06:27:22:xx:xx:xx [GTK=TKIP]
>    the second time, video streaming with VLC immediatly leeds to all the
>    mentioned sideeffects.
> 
> Maybe it's possible to reproduce it with any hostapd based AP with
> active wpa_group_rekey.

Ok, thanks.

Are you running a 32-bit kernel on a 64-bit machine by any chance?
Somebody else reported that using a 64-bit kernel helped similar issues.

johannes


  reply	other threads:[~2011-12-12  9:04 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-09 14:50 iwlwifi havoc on some APs (rekeying?) Wolfgang Breyha
2011-12-09 16:02 ` Guy, Wey-Yi
2011-12-09 18:05   ` Wolfgang Breyha
2011-12-09 17:23     ` Guy, Wey-Yi
2011-12-09 18:26       ` Johannes Berg
2011-12-09 17:44         ` Guy, Wey-Yi
2011-12-10 13:02         ` Wolfgang Breyha
2011-12-12  9:04           ` Johannes Berg [this message]
2011-12-12 10:09             ` Wolfgang Breyha
2011-12-12 10:12               ` Johannes Berg
2011-12-12 11:21                 ` Wolfgang Breyha
2011-12-12 17:48                   ` Johannes Berg
2011-12-12 18:17                     ` Wolfgang Breyha
2011-12-13 15:38                       ` Johannes Berg
2011-12-14 14:22                         ` Wolfgang Breyha
2011-12-14 22:10                           ` Johannes Berg
2011-12-14 22:51                             ` Daniel Halperin
2011-12-14 22:55                               ` Johannes Berg
2011-12-14 23:07                                 ` Wolfgang Breyha
2011-12-15  0:46                                 ` Wolfgang Breyha
2011-12-15 13:01                                   ` Johannes Berg
2011-12-15 19:47                                     ` Wolfgang Breyha
2011-12-12 19:39                     ` Wolfgang Breyha
2012-02-18 13:09 ` Johannes Berg
2012-02-24  7:25   ` 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=1323680657.3442.7.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=wbreyha@gmx.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.