Hi, I'm looking at deauthentication & disassociation with cfg80211 API. AFAIK both frames can be send by STA as well as AP (according to the standard). I was looking info few cfg80211 callbacks and have few questions. 1) @disassoc I think it's just for disassociating from AP. Is that correct? 2) @del_station Now, this gets tricky for me. I think this callback is for AP mode to deauthenticae/disassociate a STA. It seems hostapd follows the same idea as in driver_nl80211.c it uses NL80211_CMD_DEL_STATION for both: deauth and disassoc (without building own frame). So I started analyzing this with the base case: mac80211 (ieee80211_del_station). I expected to find a place where mac80211 constructs deauth/disassoc management frame and transmits it. But I really couldn't. It seems that all ieee80211_del_station does is calling __sta_info_destroy / __sta_info_destroy_part1 / __sta_info_destroy_part2. Did I miss something? Or does mac80211 really ignore sending proper management frames in this case? On the other hand cfg80211 drivers seem to be doing something more in the @del_station callback. E.g.: a) wil6210 seems to be sending some frame: wmi_send(wil, WMI_DISCONNECT_STA_CMDID, &cmd, sizeof(cmd)); b) brcmfmac does as well: brcmf_fil_cmd_data_set(ifp, BRCMF_C_SCB_DEAUTHENTICATE_FOR_REASON, &scbval, sizeof(scbval)); c) mwifiex as well: mwifiex_send_cmd(priv, HostCmd_CMD_UAP_STA_DEAUTH, ...); Can you help to understand this, please? Is @del_station handler supposed to actually send a proper management frame? -- Rafał -- 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
