Madwifi + wpa_supplicant (cannot get IP)

[Pavel Roskin]

Hello!

On Wed, 2006-11-29 at 20:40 -0500, Carlos Moffat wrote:
> You're right, is not. I'm trying to get wpa_supplicant to work 'cause
> Network-Manager uses it for all connection, independent of whether you
> need WPA or not. This seems like a good idea, except that now I have
> moving part to worry about. I don't know where to file a bug, 'cause I
> don't know if the problem is with Madwifi or wpa_supplicant (NM seems to
> be innocent)

wpa_supplicant is supposed to work even without WPA and WEP.  I can make
it work with HostAP driver on the client side, even using the wext
driver in wpa_supplicant.

With the current madwifi, things are different.  Sometimes it works,
sometimes it doesn't.

That's what I'm seeing if the connection would work:

# wpa_supplicant -D wext -i ath0 -c hostap.conf 
Trying to associate with 00:0b:6b:56:01:bb (SSID='WDS1' freq=2437 MHz)
ioctl[SIOCSIWAUTH]: Invalid argument
WEXT auth param 1 value 0x1 - Association request to the driver failed
Associated with 00:0b:6b:56:01:bb
CTRL-EVENT-CONNECTED - Connection to 00:0b:6b:56:01:bb completed (auth)
[id=0 id_str=]

And that's what I'm seeing when no traffic can pass:

# wpa_supplicant -D wext -i ath0 -c hostap.conf 
Associated with 00:00:00:00:00:00
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Associated with 00:0b:6b:56:01:bb
CTRL-EVENT-CONNECTED - Connection to 00:0b:6b:56:01:bb completed (auth)
[id=0 id_str=]

Somehow, the error in ioctl indicates that the connection would work.
There is one trick to cause this.  Just sett ESSID to a bogus value.
Then you'll get the ioctl error, and the traffic would go through.

I'm using wpa_supplicant 0.5.6.  Linux kernel is current wireless-2.6
branch.

I don't have time to research it further at the moment.

-- 
Regards,
Pavel Roskin