wpa association issue
linux.newbie79 at gmail.com
Mon May 11 01:44:54 EDT 2009
I was building the airo driver not as seperate module and when I statically
set the wpa_enabled variable to non-zero, WPA PSK is working fine :-).
* Aim for me is to set the driver to wpa or wep based on wpa_supplicant
configuration file info.
* I believe wpa and wep cannot exists simultaneously(correct me if I am
* I prefer to use some ioctl calls from wpa_supplicant to driver to enable
wpa or wep.
Can you please share your thought in this?
Thanks in Advance
On Mon, May 11, 2009 at 1:48 PM, linux newbie <linux.newbie79 at gmail.com>wrote:
> Hi Matthieu,
> Many thanks for your reply.
> With the airo driver you mentioned, I coulnt receive the EAPOL messages.
> i.e wpa_supplicant_rx_eapol is not called.
> I have sent a mail regarding this but it is waiting for moderator approval
> as the length of message is long.
> Also below is the aironet card status. Will it work for WPA? or do I need
> to update to some other firmware?
> # cat /proc/driver/aironet/eth1/Status
> Status: WEP
> Mode: 200
> Signal Strength: 27
> Signal Quality: 143
> AP: AllansfordAP04
> Freq: 0
> BitRate: 11mbs
> Driver Version: airo.c 0.6 (Ben Reed & Javier Achirica)
> Device: 350 Series
> Manufacturer: Cisco Systems
> Firmware Version: 5.41
> Radio type: 2
> Country: 0
> Hardware Version: 22
> Software Version: 541
> Software Subversion: 0
> Boot block version: 150
> Thanks in Advance
> On Mon, May 11, 2009 at 7:28 AM, matthieu castet <
> castet.matthieu at free.fr> wrote:
>> linux newbie wrote:
>>> I am using airo net 350 client and linux kernel 2.6.26.
>>> I downloaded latest airo driver that supports wpa from
>>> Hm, it should be the one
>> The version in trunk is old and doesn't build with recent kernel.
>> State: GROUP_HANDSHAKE -> COMPLETED
>>> RTM_NEWLINK: operstate=1 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
>>> Wireless event: cmd=0x8b15 len=20
>>> Wireless event: new AP: 00:00:00:00:00:00
>>> Setting scan request: 0 sec 100000 usec
>>> Added BSSID 00:23:ab:be:90:70 into blacklist
>>> CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
>> This event can be generated when we are not disassociated.
>> Can you post your kernel log ?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the HostAP