Help - Search - Members - Calendar
Full Version: Wpa Vs. 1.1.0beta1
OESF Forums > Distros, Development, and Model Specific Forums > Distro Support and Discussion > pdaXrom
ant
Hello,

I got a D-Link DCF-660W manfid 0xd601, 0x0005 and flashed it to the latest 1.84 fw.
Works ok with WEP, but I want WPA-PSK.

Looking here
http://hostap.epitest.fi/cgi-bin/viewcvs.c...README?rev=HEAD

and in the sources I found some modifications are needed after standard installation:

1)
edit /etc/pcmcia/config, /etc/pcmcia/hermes.conf, /etc/pcmcia/hostap_cs.conf, /etc/pcmcia/spectrum.conf
Your card should be listed only once. The DCF-660W name was misspelled.
Comment out all other cards with the same manfid.

2)
edit /etc/hostap_cs.conf and at the beginning add the missing modules

device "hostap_cs"
class "hostap" module "hostap", "hostap_cs", “hostap_crypt_wep”
#class "network" module "hostap", "hostap_cs"

3)
Add MODE="Managed" and WPA="y" to the network scheme in
/etc/pcmcia/wireless.opts.


4)
Following the webapp_supplicants docs (and loading more modules):

Add the following block to the end of 'start' action handler in

if [ "$WPA" = "y" -a -x /usr/sbin/wpa_supplicant ]; then

#load crypto modules
modprobe hostap_crypt_tkip
modprobe hostap_crypt_ccmp

/usr/sbin/wpa_supplicant -Bw -c/etc/wpa_supplicant.conf \
-i$DEVICE

fi


Add a separate block for the 'stop' action handler

'stop')

if [ "$WPA" = "y" -a -x /usr/sbin/wpa_supplicant ]; then

#unload crypto modules
rmmod hostap_crypt_tkip
rmmod hostap_crypt_ccmp

killall wpa_supplicant
fi

5) edit /etc/wpa_supplicant.conf



Wit these changes the hostap crypto modules are loaded. GOOD!

What I don't understand is why the webapp_supplicant dies immediatly...
No trace of it in the process list.


Interestingly enough, If I test with another card (a spectrum card) the wpa_supplicant is loaded and running (too bad actually spectrum cards are not working with hostap).


Can somebody help me?


TIA

Ant



P.S. there is a new version of hostap...who dare to compile it?
ant
There is a new release 0.47 at http://hostap.epitest.fi.

BUT...the kernel patches start from 2.4.20.
I run an SLC-860 so have 2.4.18....

Think it is worth a rebuild.

Ant
ant
Some new findings:

there are DIFFERENT hostap.* modules in

/lib/modules/2.4.18-rmk7-pxa3-embedix/net

and in

/lib/modules/2.4.18-rmk7-pxa3-embedix/kernel/drivers/net/wireless

Which are newer?


Ant


EDIT:

depmod gives *** Unresolved symbols in /lib/modules/2.4.18-rmk7-pxa3-embedix/net/hostap.o
ant
Sooo, here the output of:

wpa_supplicant -w -c/etc/wpa_supplicant.conf -Dhostap -iwlan0 -dd >./dump.txt 2>&1

ioctl[PRISM2_IOCTL_PRISM2_PARAM]: Operation not supported
Failed to enable WPA in the driver.
ioctl[PRISM2_IOCTL_HOSTAPD]: Operation not supported
ioctl[PRISM2_IOCTL_PRISM2_PARAM]: Operation not supported
Failed to disable WPA in the driver.
ioctl[PRISM2_IOCTL_PRISM2_PARAM]: Operation not supported
ioctl[PRISM2_IOCTL_PRISM2_PARAM]: Operation not supported
ioctl[PRISM2_IOCTL_HOSTAPD]: Invalid argument
ioctl[PRISM2_IOCTL_HOSTAPD]: Invalid argument
ioctl[PRISM2_IOCTL_HOSTAPD]: Invalid argument
ioctl[PRISM2_IOCTL_HOSTAPD]: Invalid argument
Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'hostap'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
Line: 2 - start of a new network block
ssid - hexdump_ascii(len=17): XXXXXXXXXXXXXXXXXXXXXXXXX

proto: 0x1
key_mgmt: 0x2
pairwise: 0x18
group: 0x1e
PSK - hexdump(len=32): [REMOVED]
priority=5 (0x5)
Priority group 5
id=0 ssid='XXXXXXXXXXXXXX'
Initializing interface (2) 'wlan0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Own MAC address: 00:13:46:XX:XX:XX
wpa_driver_hostap_set_wpa: enabled=1
wpa_driver_hostap_set_wpa: enabled=0
wpa_driver_hostap_set_drop_unencrypted: enabled=0
wpa_driver_hostap_set_countermeasures: enabled=0
wpa_driver_hostap_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
Failed to set encryption.
wpa_driver_hostap_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
Failed to set encryption.
wpa_driver_hostap_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
Failed to set encryption.
wpa_driver_hostap_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
Failed to set encryption.



Failed to enable WPA in the driver means ...no wpa with this build!
Hope to be wrong...
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2014 Invision Power Services, Inc.