Re: Prism2 Host AP - new release 2002-04-10
From: David Levitan (david_at_dlevitan.com)
Date: 2002-04-11 15:12:08 UTC
I did. Typed in "iwconfig wlan0 key s:1234567" (well, not that exact
string, but close enough). Also put in "iwconfig wlan0 key restricted".
Then tried to connect from a windows laptop using both 64 bit and 128
bit encryption (with the same string key), and no luck. I haven't had a
chance to really play around with it, and I'll be away for the next few
days, so I'll report my results next week probably. However, what's the
difference between 64 and 128 bit encryption? On the windows client, I
can set it to either. But I haven't found a setting on linux.
Thanks,
David Levitan
Vladimir Ivaschenko wrote:
> Did you try standard iwconfig commands for enabling WEP?
>
> Wed, Apr 10, 2002 at 08:32:20PM -0400 David Levitan wrote about Re: Prism2 Host AP - new release 2002-04-10
>
>
>>quick question: How do I enable a 40 bit key and how do I enable a
>>104bit key? I couldn't find anything in any documentation.
>>Thanks,
>>David Levitan
>>
>>Jouni Malinen wrote:
>> > A new version of Prism2 Host AP driver was just released and it is now
>> > available from http://people.ssh.com/jkm/Prism2/
>> >
>> >
>> > 2002-04-10
>> >
>> > * fixed compilation with older Linux wireless extension versions
>> > (at least version 9 is now required for most wireless extensions)
>> > * kernel driver AP functionality code cleanup
>> > * try to send broadcast deauthentication frames when shutting down
>> > * use smaller default inactivity timeout with stations (5 min)
>> > * send disassociation when 3/4 of inactivity timeout has passed and
>> > deauthentication when full timeout has passed
>> > * added support for WEP in Host AP mode
>> > - card firmware is used to decrypt frames (it seems to work fine)
>> > - encryption is performed in host driver since firmware does not
>> > seem to want to encrypt frames correctly when in Host AP mode
>> > - use 'restricted' as default WEP mode instead of 'open'
>> > - WEP keys are saved in driver data, so SIOCGIWENCODE is now
>> > returning real values and not the bogus values firmware returned
>> > - 40-bit and 104-bit WEP seems to now be working properly in Host AP
>> > mode (both with stations and with WDS links); (note that if
>> > 104-bit WEP is used, station firmware on AP must support 104-bit
>> > WEP in order to decrypt frames)
>> > * fixed a bug in fake-WDS frame generation
>> > - if payload len was odd, the addr4 was broken in RX frames
>> > * drop RX packets that have ToDS flag but wrong BSSID and RX packets
>> > that have FromDS flag (these frames are usually broadcast/multicast
>> > frames in other BSSes)
>> >
>> >
>>
>>
>>
>>
>
This archive was generated by
hypermail 2.1.4.