-----Original Message----- From: Zhu Yi [mailto:yi.zhu@xxxxxxxxx] Sent: Tuesday, May 15, 2007 12:23 PM To: Sandesh Goel Cc: Jouni Malinen; linux-wireless@xxxxxxxxxxxxxxx; John W. Linville Subject: RE: [PATCH] mac80211: fail back to use associate from reassociate 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. [Sandesh] [Sandesh] How does the AP know that it is the only one in the ESS? It can't surely assume that. Is it configured with this information? Did it try to find out if there are other APs in the ESS? E.g. would it behave differently if you setup another AP in your ESS? > 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? [Sandesh] [Sandesh] I didn't say that AP needs to remember that. However, it should honor the reassoc request if it is not sure about whether the requesting STA was associated in the ESS or not. Thanks, -yi - To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
