(new info) Problems with wpa_supplicant and Linksys WPC54G + WPA EAP-TTLS

Stephen Mathezer mathezer at yahoo.com
Mon Dec 20 16:50:12 EST 2004


Sure. My wpa_supplicant.conf is pretty vanilla:

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
network={
ssid="gear"
key_mgmt=WPA-EAP
pairwise=TKIP
group=TKIP
eap=TLS
identity="Cgy04662-Linux"
ca_cert="/etc/ssl/cacert.pem"
client_cert="/etc/ssl/cgy04662_cert.pem"
private_key="/etc/ssl/cgy04662_req.pem"
private_key_passwd="xxxxxxx"
priority=100
}

This is the driver that I used both with Ndiswrapper and DriverLoader.

ftp://ftp.linksys.com/pub/network/WPC54Gv4_driver_rev_1.22.1.2004.zip

# ls -al /etc/ndiswrapper/wlipnds/
total 148
drwxr-xr-x 2 root root 4096 Nov 5 15:53 ./
drwxr-xr-x 3 root root 4096 Nov 5 15:53 ../
lrwxrwxrwx 1 root root 49 Nov 5 15:53 17FE:2220.conf -> 
/etc/ndiswrapper/wlipnds/17FE:2220:1737:0029.conf
-rw-r--r-- 1 root root 220 Nov 5 15:53 17FE:2220:1737:0029.conf
-rw-r--r-- 1 root root 117248 Nov 5 15:53 i2220ntx.sys
-r--r--r-- 1 root root 13067 Nov 5 15:53 wlipnds.inf

My eap.conf from FreeRadius is:

eap{
default_eap_type=tls
timer_expire=60
ignore_unknown_eap_types=no
cisco_accounting_username_bug=no
tls{
private_key_password=xxxx
private_key_file=${raddbdir}/certs/freeradius_req.pem
certificate_file=${raddbdir}/certs/freeradius_cert.pem
CA_file=/etc/ssl/cacert.crt
dh_file=${raddbdir}/certs/dh
random_file=${raddbdir}/certs/random
fragment_size=1024
}
}

Hope that helps

Oh yeah, I forgot to mention previously, EAP-PSK also works fine with 
Ndiswrapper. It was only TLS that gave me grief.

-Steve

Dan Parsons wrote:

> Very interesting indeed... would you mind showing me what your 
> wpa_supplicant.conf file looks like? Also, maybe a link to the .zip or 
> .exe of the Windows drivers you're using?
>
> Dan Parsons
> Systems Administrator
> Pioneer Research Center USA, Inc.
>
> On Dec 20, 2004, at 1:30 PM, Stephen Mathezer wrote:
>
>> Dan Parsons wrote:
>>
>>> While I'm waiting for the ndiswrapper folk to get back to me, I 
>>> decided to get LinuxAnt's DriverLoader a try instead of ndiswrapper. 
>>> So far I haven't had any system crashes, which is great. However 
>>> WPA+EAP-TTLS still isn't working. Below is some debugging 
>>> information for you... does it look like the same issue as what I'm 
>>> having with ndiswrapper? I'm using the same Windows drivers with it 
>>> as I was with ndiswrapper and also the same card.
>>>
>>> I thank you in advance for any information you can give me.
>>
>>
>> I realize that I am talking TLS whereas you are talking TTLS, but for 
>> what it is worth, I have a WPC54GV4 and have had the following 
>> experience:
>>
>> -EAP-TLS works fine under Windows XP
>> -EAP-TLS works fine with DriverLoader
>> -EAP-TLS fails with ndiswrapper and wpa_supplicant 0.2.5. As of 
>> Ndiswrapper 0.12 I could actually see a conversation with the radius 
>> server, which was new, but I still couldn't complete authentication.
>> -An identical wpa_supplicant config works fine with the native 
>> Madwifi drivers with my Dlink-650G
>>
>> I haven't had time (or inclination) to dig too much since I do have 
>> one working card. It is interesting however that DriverLoader worked 
>> for me but not for you.
>>
>> -Steve
>




More information about the HostAP mailing list