On Wednesday 14 February 2007 08:23, Ivo van Doorn wrote: > diff --git a/net/d80211/ieee80211_i.h b/net/d80211/ieee80211_i.h > index 5ab9eb5..1891e05 100644 > --- a/net/d80211/ieee80211_i.h > +++ b/net/d80211/ieee80211_i.h > @@ -80,6 +80,7 @@ struct ieee80211_sta_bss { > u8 ssid[IEEE80211_MAX_SSID_LEN]; > size_t ssid_len; > u16 capability; /* host byte order */ > + u16 sequence; > int hw_mode; > int channel; > int freq; I am not so sure that storing this information in struct ieee80211_sta_bss is correct. As far as I can tell, that is strictly for storing information scan results and beacon information. Nothing outside of ieee80211_sta.c uses it. struct sta_info or struct ieee80211_if_ap (sta interfaces have a pointer to the struct ieee80211_if_ap on the master device) may be a better choice. I think struct sta_info is the right one though there is a problem - it isn't allocated until a successful association. -Michael Wu
Attachment:
pgp8FjcRFBUXD.pgp
Description: PGP signature