Static wep keys not set

Nicolas Dichtel nicolas.dichtel at 6wind.com
Thu Apr 5 04:01:52 EDT 2007


Pavel Roskin a écrit :
> On Tue, 2007-04-03 at 18:10 +0200, Nicolas Dichtel wrote:
>> I've already sent a mail (and a proposal patch) about this issue
>> (http://lists.shmoo.com/pipermail/hostap/2006-November/014640.html).
>>
>> As I said in my previous mail:
>>
>> 802.11 specifications say:
>> "APs set the Privacy subfield to 1 within transmitted Beacon, Probe 
>> Response, Association Response, and
>> Reassociation Response management frames if WEP encryption is required 
>> for all data type frames
>> exchanged within the BSS. If WEP encryption is not required, the Privacy 
>> subfield is set to 0."
>
> It sounds like if the privacy bit is set before the key, all
> communication will stop to satisfy that requirement.  Setting the key
> first seems more reasonable to me.  Is my understanding correct?
If we set the key before the privacy bit, this requirement will not be 
satisfy too ;-)
>
> If yes, then the fix belongs to MadWifi, not to hostapd.  Well, hostapd
> could have a MadWifi specific workaround for now.
cc madwifi-devel at lists.sourceforge.net to have any feedback.

Nicolas



More information about the HostAP mailing list