All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhu Yi <yi.zhu@intel.com>
To: Sandesh Goel <sgoel@marvell.com>
Cc: Jouni Malinen <jkm@devicescape.com>,
	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 14:52:45 +0800	[thread overview]
Message-ID: <1179211965.3045.170.camel@debian.sh.intel.com> (raw)
In-Reply-To: <9C9B2DC3D78A6142AC8D10C89669528603F63B68@msiexch01.marvell.com>

On Mon, 2007-05-14 at 22:41 -0700, Sandesh Goel wrote:
> Therefore, the AP should not return the said error code
> (WLAN_STATUS_REASSOC_NO_ASSOC) unless it has checked (using some inter
> AP protocol) that no other AP in the ESS has an existing association
> with the requesting STA. If the AP is returning the error without
> doing this check, I would think that it is an AP bug. 

The AP was the only one in the ESS, so it should be OK.

> It would be interesting to know which AP behaves in this way and
> whether
> is really does the check correctly or not. Note that the AP itself
> having rebooted shouldn't cause this error code to be returned, which
> is what I found strange. 

Do you mean the AP should remember all its associated STAs before it
rebooted?

Thanks,
-yi

  reply	other threads:[~2007-05-15  6:53 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 [this message]
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=1179211965.3045.170.camel@debian.sh.intel.com \
    --to=yi.zhu@intel.com \
    --cc=jkm@devicescape.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=sgoel@marvell.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.