From: Johannes Berg <johannes@sipsolutions.net>
To: Paul Stewart <pstew@chromium.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] cfg80211: Ignore downstream DEAUTH for authtry_bsses
Date: Thu, 09 Jun 2011 21:17:18 +0200 [thread overview]
Message-ID: <1307647038.3904.0.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <20110609191327.20D2C2038D@glenhelen.mtv.corp.google.com> (sfid-20110609_211330_842374_E21EE85A)
On Wed, 2011-06-08 at 05:52 -0700, Paul Stewart wrote:
> If we receive a DEAUTH message from an AP while performing
> an AUTH request, this does not constitute a reply to our AUTH
> request. In some cases an incoming DEAUTH may be due to the AP
> clearing out old state from a previous authentication.
> Instead we should ignore it and continue waiting for an AUTH
> response.
Ack, but you should do something about how you submit patches -- they
always end up at the bottom of my list because you're sending them with
the commit date as the email date.
johannes
next prev parent reply other threads:[~2011-06-09 19:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 12:52 [PATCH] cfg80211: Ignore downstream DEAUTH for authtry_bsses Paul Stewart
2011-06-09 19:17 ` Johannes Berg [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-06-06 23:00 [RFC] cfg80211: Fix handling of previous_auth deauth Paul Stewart
2011-06-08 11:02 ` Johannes Berg
[not found] ` <BANLkTimdAHt9VUUmNB2uzgm8ymeo6J+EeA@mail.gmail.com>
2011-06-08 11:44 ` Johannes Berg
2011-06-08 11:48 ` Paul Stewart
2011-06-08 11:50 ` Johannes Berg
2011-06-08 12:52 ` [PATCH] cfg80211: Ignore downstream DEAUTH for authtry_bsses Paul Stewart
2011-06-08 13:19 ` 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=1307647038.3904.0.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=pstew@chromium.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).