WPA/WPA2 with Prism54 card

Fri Dec 22 06:22:49 EST 2006

OK,
the first round wasn't that successful ...

I tested the kernel 2.6.19.1 today and when launching wpa_supplicant I
got the following:

root:~> wpa_supplicant -i eth1 -D wext -c
/etc/wpa_supplicant/wpa_supplicant.conf
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - CTRL-EVENT-TERMINATING - signal 2 received
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - root:~>

The program  was hanging after line 2 until I pressed CTRL-C which was
resulting in the rest of the output.

Then I tried that patch. I couldn't apply it though, it seems that it
doesn't match the driver in the latest kernel.

This it the patch output:

root:/usr/src/linux-2.6.19.1> cat
../patches/prism54-wpa-wl2.6-git-BOTH.diff | patch -p1
patching file drivers/net/wireless/prism54/isl_38xx.c
Hunk #1 succeeded at 25 (offset 1 line).
patching file drivers/net/wireless/prism54/isl_ioctl.c
Hunk #1 succeeded at 4 (offset 1 line).
Hunk #2 succeeded at 28 (offset 1 line).
Hunk #3 succeeded at 42 (offset 1 line).
Hunk #4 succeeded at 159 (offset 1 line).
Hunk #5 succeeded at 193 (offset 1 line).
Hunk #6 FAILED at 221.
Hunk #7 succeeded at 408 (offset 1 line).
Hunk #8 succeeded at 431 (offset 1 line).
Hunk #9 succeeded at 561 (offset 1 line).
Hunk #10 succeeded at 597 (offset 1 line).
Hunk #11 succeeded at 611 (offset 1 line).
Hunk #12 succeeded at 871 (offset 1 line).
Hunk #13 succeeded at 1039 (offset 1 line).
Hunk #14 succeeded at 1095 (offset 1 line).
Hunk #15 FAILED at 1132.
Hunk #16 FAILED at 1252.
Hunk #17 succeeded at 1286 (offset 1 line).
Hunk #18 succeeded at 1370 (offset 1 line).
Hunk #19 succeeded at 1385 (offset 1 line).
Hunk #20 succeeded at 1462 (offset 1 line).
Hunk #21 succeeded at 2044 (offset 1 line).
Hunk #22 succeeded at 2115 (offset 1 line).
Hunk #23 succeeded at 2146 (offset 1 line).
Hunk #24 succeeded at 2162 (offset 1 line).
Hunk #25 succeeded at 2225 (offset 1 line).
Hunk #26 succeeded at 2242 (offset 1 line).
Hunk #27 succeeded at 2276 (offset 1 line).
Hunk #28 FAILED at 2383.
Hunk #29 FAILED at 2424.
Hunk #30 succeeded at 2458 (offset 1 line).
Hunk #31 succeeded at 2595 (offset 1 line).
Hunk #32 succeeded at 2686 (offset 1 line).
Hunk #33 succeeded at 2716 (offset 1 line).
Hunk #34 succeeded at 2903 (offset 1 line).
5 out of 34 hunks FAILED -- saving rejects to file
drivers/net/wireless/prism54/isl_ioctl.c.rej
patching file drivers/net/wireless/prism54/isl_ioctl.h
Reversed (or previously applied) patch detected!  Assume -R? [n]
Apply anyway? [n]
Skipping patch.
2 out of 2 hunks ignored -- saving rejects to file
drivers/net/wireless/prism54/isl_ioctl.h.rej
patching file drivers/net/wireless/prism54/isl_oid.h
Hunk #1 succeeded at 4 (offset 2 lines).
Hunk #2 succeeded at 29 (offset 2 lines).
Hunk #3 succeeded at 100 (offset 2 lines).
Hunk #4 FAILED at 131.
Hunk #5 FAILED at 172.
Hunk #6 succeeded at 198 with fuzz 1 (offset 2 lines).
Hunk #7 succeeded at 512 (offset 2 lines).
Hunk #8 succeeded at 545 (offset 2 lines).
2 out of 8 hunks FAILED -- saving rejects to file
drivers/net/wireless/prism54/isl_oid.h.rej
patching file drivers/net/wireless/prism54/islpci_dev.c
Hunk #1 succeeded at 26 (offset 1 line).
Hunk #2 succeeded at 87 (offset 1 line).
patching file drivers/net/wireless/prism54/islpci_dev.h
Hunk #1 FAILED at 71.
1 out of 1 hunk FAILED -- saving rejects to file
drivers/net/wireless/prism54/islpci_dev.h.rej
patching file drivers/net/wireless/prism54/islpci_eth.c
Hunk #1 succeeded at 25 (offset 1 line).
Hunk #2 FAILED at 482.
Hunk #3 FAILED at 499.
2 out of 3 hunks FAILED -- saving rejects to file
drivers/net/wireless/prism54/islpci_eth.c.rej
patching file drivers/net/wireless/prism54/islpci_hotplug.c
Hunk #1 succeeded at 24 (offset 1 line).
Hunk #2 succeeded at 44 (offset 1 line).
Hunk #3 FAILED at 150.
Hunk #4 FAILED at 188.
Hunk #5 FAILED at 235.
Hunk #6 FAILED at 268.
4 out of 6 hunks FAILED -- saving rejects to file
drivers/net/wireless/prism54/islpci_hotplug.c.rej
patching file drivers/net/wireless/prism54/islpci_mgt.c
Hunk #1 succeeded at 26 (offset 1 line).
patching file drivers/net/wireless/prism54/oid_mgt.c
patching file drivers/net/wireless/prism54/oid_mgt.h
patching file drivers/net/wireless/prism54/prismcompat.h
Reversed (or previously applied) patch detected!  Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file
drivers/net/wireless/prism54/prismcompat.h.rej

This is my wpa_supplicant.conf:

update_config=0
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
fast_reauth=1

network={
    ssid="rutschnet"
    psk="<secret_hey_here>"
    proto=WPA
    key_mgmt=WPA-PSK
    pairwise=TKIP
    group=TKIP
}

Did you modify the in-kernel driver in a complete way so that it
supports wext without that additional patch ? Or do I need it anyway ?

Thanks,
Jens

Dan Williams schrieb:
> On Wed, 2006-12-20 at 23:08 +0100, Jens Rutschmann wrote:
>   
>> Hello,
>> in my Notebook I have a miniPCI card with Intersil Prism54 chipset.
>> Currently I am forced to use WEP encryption on my wireless network
>> because wpa_supplicant doesn't support the card right now.
>>
>> Is there any chance that wpa_supplicants' prism54 driver will be
>> completed in the near future ?
>>     
>
> 'wext' is the future (and cfg80211 after that), so card-specific
> interfaces shouldn't be used if at all possible.
>
> I ported the WPA support of the prism54 driver to the 'wext'
> wpa_supplicant driver a while ago.  It should be able to exist alongside
> the prism54-specific ioctls for WPA.  I was not able to extensively test
> it, however, because my card died halfway through.
>
> I believe that patch is already upstream.  Could you test it out?  I
> think it's in 2.6.19 and later kernels.
>
> There is also another patch floating around (in desperate need of
> testers) that completes the 'wext' support of the prism54 driver.  If
> the 'wext' bits of prism54 don't work with wpa_supplicant, we need to
> fix that.
>
> http://marc.theaimsgroup.com/?l=linux-netdev&m=116453812608332&w=2
>
> Dan
>
>   
>> I read in the mailing list that several components need to support WPA
>> to get it running:
>> The hardware: specifications of my chipset say that it supports  "AES
>> hardware acceleration"
>> The driver: I use the in-kernel driver (kernel 2.6.18)
>> And finally wpa_supplicant itself: I guess that concerns
>> wpa_supplicants' prism54 driver.
>>
>> Can I even get this running if wpa_supplicants' driver would support it ?
>> Or would it be better to buy a new card with Atheros or Intel chipset?
>>
>> Regards,
>> Jens Rutschmann
>>
>> _______________________________________________
>> HostAP mailing list
>> HostAP at shmoo.com
>> http://lists.shmoo.com/mailman/listinfo/hostap
>>     
>
>   