> > sme->crypto.wpa_versions > > > sme->crypto.n_ciphers_pairwise, sme->crypto.ciphers_pairwise > > > sme->crypto.n_akm_suites, sme->crypto.akm_suites > > All these pretty much exist for hw that doesn't want to use the > IE(s) contained in the connect parameters. If you send an assoc > request with those IEs, you can safely ignore the parameters > here. It's just there so one doesn't have to parse the IEs. Okay, then I conclude that it's save to ignore sme->privacy sme->crypto.wpa_versions sme->crypto.n_ciphers_pairwise sme->crypto.ciphers_pairwise sme->crypto.n_akm_suites sme->crypto.akm_suites inside .connect() if I check sme->crypto.cipher_suite for WLAN_CIPHER_SUITE_WEP40 WLAN_CIPHER_SUITE_WEP104 WLAN_CIPHER_SUITE_TKIP WLAN_CIPHER_SUITE_CCMP 0 (meaning no encryption/WEP obfuscation) lbs_cfg_connect() calls lbs_associate() which hands the complete sme->ie to as a TLV to the firmware. However, I don't do any parsing of sme->ie by myself. -- http://www.holgerschurig.de -- 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
