Hi,
I am using ralink driver 1.0.4.0 and wpa_supplicant 0.4.7 in the linux platform 2.4.22 [RedHat 9].
I am facing piculiar problem. I can associate to the wireless router if I use cofig file rt73sta.dat in the driver using WPA-PSK mode.
But, if I use wpa_supplicant, I am not getting any IP address. Infact, the entry for wireless interface is removed from ifconfig output. I saw the same problem with higher version of wpa_supplicant, 0.5.8 and 0.6.0.
The problem is not there for the ralink driver 1.0.3.3.

I executed the following commands,

# insmod rt73.o
# ifconfig rausb0 up
# wpa_supplicant -c <wpa_supplicant.config file name> -i rausb0 -D ralink -dd
# dhclient

Please help me.

Regards,

Amit

I saw the following error message in the terminal,
ioctl[SIOCGIWAP]: Transport endpoint is not connected

And, in the /var/log/message i found the following error message,

<7>ERROR: CRC ok but CipherErr 3 (len = 163, Mcast=0, Cipher=TKIP, KeyId=)

I configured wpa_supplicant.cfg for

key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP

I also observed the following Error message,

ERROR: CRC ok but CipherErr 3 (len = 163, Mcast=0, Cipher=TKIP, KeyId=0)

I don't know if this will help, but you might want to try -D wext instead of -D ralink. You also might want to post your wpa_supplicant.conf in case you've got an error in there.

i am using ralink device not wext

You need to do some reading about wpa_supplicant. The driver you specify with the -D flag is to allow wpa_supplicant to communicate with the actual card, and the wext driver is a generic interface that works through iwconfig, and therefore doesn't care what device you have. In many cases it works better than the specific driver for the chipset.

that means, u want to say, I dont need to load device driver for ralink wireless usb ? Or, I need to load the driver but no need to pass the driver name as argument when start wpa_supplicant daemon?
Actually, the packed was dropped by wpa_supplicant at the time of association. anyways, i shall try ur suggestion.

No, that isn't what I mean. When you're dealing with wpa_supplicant, you're actually dealing with two drivers, the device driver for the hardware itself (in your case the Ralink driver) and the driver that allows wpa_supplicant to communicate with the device (in this case the wext driver I've been suggesting). The second drivers I'm talking about are included as part of wpa_supplicant, but you must specify which one to use when you start wpa_supplicant.

no result, i passed wext at the start up time, but no result.

wpa_supplicant -c wpa.cfg -irausb0 -Dwext -B

It is throwing some other error.

Posting the error will help immensely since nobody besides you can see your screen.

wpa_supplicant -c wpa.cfg -irausb0 -Dwext -B
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 -

1. Does the device work without any security. It's not clear from your post but if you haven't, try getting an IP address without WEP or WPA. If that doesn't work, you're fighting an uphill battle.

2. modprobe rt73 instead of insmod rt73.o
That will pull in any dependent modules.

3. Use the absolute path for the config file. You can't count on being in the same directory as wpa.cfg, especially if you automate the call to wpa_supplicant at boot.

ex: -c /etc/wpa_supplicant/wpa.cfg (Use your path, I made that one up.)

Yes, without wpa_supplicant I am getting IP. even with security, WPA implemented in driver, getting IP.

There is no dependency with other module.

Supplicant is reading the file wpa.cfg properly, i saw in the log.

I did some Googling on the error, but I'm not seeing any definitive answer. The most likely answer, in my opinion, is that the kernel wasn't compiled with a full set of WPA options enabled. Starting around 2.6.13, a lot of the WPA support was moved into the kernel, and the wext driver kind of depends on it. And from what I've been reading, the other drivers that wpa_supplicant has might conflict, so trying to fix wext is the way to go.

Have you compiled your own kernel or is this a stock kernel from your distro?