On Fri, 2009-02-20 at 21:25 +0200, Jouni Malinen wrote:
> nl80211: Event notifications for MLME events
That looks good to me.
> +/**
> + * enum nl80211_auth_type - AuthenticationType
> + *
> + * @NL80211_AUTHTYPE_OPEN_SYSTEM
> + */
> +enum nl80211_auth_type {
> + NL80211_AUTHTYPE_UNSPECIFIED,
This seems a little odd, is that really useful? And if it is, what do we
do? Try all?
> +struct cfg80211_auth_request {
> + struct ieee80211_channel *chan;
> + u8 *peer_addr;
> + const u8 *ssid;
> + size_t ssid_len;
> + enum nl80211_auth_type auth_type;
> + const u8 *ie;
> + size_t ie_len;
> +};
> +
> +struct cfg80211_assoc_request {
> + struct ieee80211_channel *chan;
> + u8 *peer_addr;
> + const u8 *ssid;
> + size_t ssid_len;
> + const u8 *ie;
> + size_t ie_len;
> +};
> +
> +struct cfg80211_deauth_request {
> + u8 *peer_addr;
> + u16 reason_code;
> + const u8 *ie;
> + size_t ie_len;
> +};
> +
> +struct cfg80211_disassoc_request {
> + u8 *peer_addr;
> + u16 reason_code;
> + const u8 *ie;
> + size_t ie_len;
> +};
Seems sensible to me.
Should we have some more code in cfg80211 to keep track of the BSSes
we're authenticated/the one we're associated to, and have some commands
to query those from userspace?
johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
