All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: linux-only "freshness" auth problem??
Date: Sat, 22 Aug 2015 11:52:56 +0300	[thread overview]
Message-ID: <55D83868.1090800@msgid.tls.msk.ru> (raw)
In-Reply-To: <55D83809.7040305@tls.msk.ru>

22.08.2015 11:51, Michael Tokarev wrote:

> Here are the main difference (- for bad, + for good):
>
>   nl80211: Association request send successfully
> -nl80211: Drv Event 20 (NL80211_CMD_DEL_STATION) received for wlan0
> -nl80211: Delete station c0:4a:00:49:1b:f2
>   nl80211: Drv Event 38 (NL80211_CMD_ASSOCIATE) received for wlan0
> -nl80211: MLME event 38; timeout with c0:4a:00:49:1b:f2
> -wlan0: Event ASSOC_TIMED_OUT (15) received
> -wlan0: SME: Association timed out
> -wlan0: Radio work 'sme-connect'@0x7fbf84e5a700 done in 0.137132 seconds
> ...
>
> So in "good" case, there's one event, CMD_DEL_STATION, received
> right before the CMD_ASSOTIATE.  The rest look similar besides a
> few probably irrelevant details (timings, frequency, etc).

In "bad" case ofcourse :)

Thanks!

/mjt

  parent reply	other threads:[~2015-08-22  8:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-21  9:35 linux-only "freshness" auth problem?? Michael Tokarev
2015-08-21  9:53 ` Rafał Miłecki
2015-08-22  8:51   ` Michael Tokarev
     [not found]   ` <55D83809.7040305@tls.msk.ru>
2015-08-22  8:52     ` Michael Tokarev [this message]
2015-08-21 10:16 ` Johannes Berg
2015-08-22  8:39   ` Michael Tokarev
2015-08-24 12:37     ` 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=55D83868.1090800@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=linux-wireless@vger.kernel.org \
    --cc=zajec5@gmail.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.