From: Zhu Yi <yi.zhu@intel.com>
To: Jouni Malinen <jkm@devicescape.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: Thu, 10 May 2007 11:20:50 +0800 [thread overview]
Message-ID: <1178767250.3045.36.camel@debian.sh.intel.com> (raw)
In-Reply-To: <20070509152855.GB941@devicescape.com>
On Wed, 2007-05-09 at 08:28 -0700, Jouni Malinen wrote:
> Can you please identify such an AP? This sounds like a workaround that
> makes the non-AP STA (client) behave in a way that does not match with
> IEEE 802.11 standard and in general, I'm against this change without a
> very good reason for it.
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.
I don't see how it breaks the 802.11 standard. If you do, please point
it out and how are you going to fix this problem?
> This type of change would, e.g., break IEEE
> 802.11r fast transition which can only be done using reassociation.
In .11r, can AP reject reassociation request if there is no previous
association from the same STA?
Thanks,
-yi
next prev parent reply other threads:[~2007-05-10 3:20 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 [this message]
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
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=1178767250.3045.36.camel@debian.sh.intel.com \
--to=yi.zhu@intel.com \
--cc=jkm@devicescape.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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 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).