All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jouni Malinen" <jkm@devicescape.com>
To: Zhu Yi <yi.zhu@intel.com>
Cc: linux-wireless@vger.kernel.org,
	"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH] mac80211: fail back to use associate from reassociate
Date: Tue, 15 May 2007 06:03:40 -0700	[thread overview]
Message-ID: <20070515130340.GA25641@devicescape.com> (raw)
In-Reply-To: <1178767250.3045.36.camel@debian.sh.intel.com>

On Thu, May 10, 2007 at 11:20:50AM +0800, Zhu Yi wrote:

> I take it an error handling code. When an AP denies a STA reassociation
> request with the reason "there is no previous association, why do you
> send reassociation request to me?", this is an indication for the STA to
> switch to association request and retry. Currently, mac80211 just try
> reassociation over and over. The result is it can never associate with
> the AP.

OK. This sounds reasonable. I went through the IEEE 802.11 standard and
it does not seem to describe this part of re-association process in any
level of detail apart from allocation a status code for reporting
failures to validate association status.

> In .11r, can AP reject reassociation request if there is no previous
> association from the same STA?

.11r does not use this status code. I was concerned about this in
general, i.e., anything that converts re-association to association
sounds somewhat undesired, but it looks like this particular status code
could be the only exception for this. I still don't see how the AP in
this case would have known about the association status for the full ESS
(since I don't see how it would know that it is the only AP in the ESS).
Anyway, non-AP STA does not have enough context to determine what
exactly happen, so it cannot really do much more than either stop trying
to re-associate or try to associate what is what your change is
proposing ot do.

-- 
Jouni Malinen                                            PGP id EFC895FA

      parent reply	other threads:[~2007-05-15 13:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-09  5:41 [PATCH] mac80211: fail back to use associate from reassociate Zhu Yi
2007-05-09 15:28 ` Jouni Malinen
2007-05-10  3:20   ` Zhu Yi
2007-05-15  5:41     ` Sandesh Goel
2007-05-15  6:52       ` Zhu Yi
2007-05-15  9:36         ` Sandesh Goel
2007-05-15 13:03     ` Jouni Malinen [this message]

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=20070515130340.GA25641@devicescape.com \
    --to=jkm@devicescape.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=yi.zhu@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.