Can't WPA associate with latest ipw2200 driver (1.1.3)

Hi,

I try to keep up with the latest of your drivers.  However, I'm having a lot
of problem associating with my home AP (a Netgear WGR614v6 router) using
the latest ipw2200-1.1.3/ieee80211-1.1.14 combination.  I have everything
working fine with 1.1.2/1.1.13.  I saw a few posts that might be related to
this issue, but I didn't see any authoritative conclusions.

Here's a little information about my setup.  I'm on a Thinkpad T42 running
Debian's "testing" distribution.  The kernel is a slightly patched
(suspend2, etc.) version of the latest Debian linux-source.2.6.17 package. 
And I'm running Debian's 0.4.9-1 wpasupplicant package.  I don't run
wpa_supplicant in "managed" mode and instead use wpa-conf and wpa-action
lines in my /etc/network/interfaces file to configure my ipw2200 using
the "manual" inet method.  Since ipw2200 isn't even associating, I don't
think the problem is with my wpa-action script.  My wpa-conf file is really
just run-of-the-mill network blocks with the default
ctrl_interface=/var/run/wpa_supplicant and ap_scan=1 settings.  Here's the
block for my home AP:


network={
    ssid="TNKS"
    proto=WPA
    pairwise=TKIP
    key_mgmt=WPA-PSK
    psk="XXXXXXXXXXXXXXXXXXXX"
    priority=2
}


And here's what I get with a iwlist scanning:


          Cell 02 - Address: 00:14:6C:18:1D:80
                    ESSID:"TNKS"
                    Protocol:IEEE 802.11bg
                    Mode:Master
                    Channel:11
                    Encryption key:on
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
                              11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
                              48 Mb/s; 54 Mb/s
                    Quality=76/100  Signal level=-52 dBm  
                    IE: WPA Version 1
                        Group Cipher : TKIP 
                        Pairwise Ciphers (1) : TKIP 
                        Authentication Suites (1) : PSK  
                    Extra: Last beacon: 20ms ago


I would love to give you 0x43fff debugging information relevant to this
problem, but it just floods my kern.log, so I thought I'd give you a
measured description of the problem first, and then see if you guys could
maybe give me a reduced debug hex mask, or some key words to search for in
my kern.log.

Here's something in the meantime (although I know it's not much).  I just
threw up a wpa_cli interactive session for monitoring in parallel to the
wpa_supplicant/wpa_cli pair Debian's ifupdown scripts sets up. When using
driver versions 1.1.3/1.1.14 I get the following output in that session.


Connection to wpa_supplicant re-established
<2>Trying to associate with 00:14:6c:18:1d:80 (SSID='TNKS' freq=0 MHz)
<2>Trying to associate with 00:14:6c:18:1d:80 (SSID='TNKS' freq=0 MHz)
<2>Trying to associate with 00:14:6c:18:1d:80 (SSID='TNKS' freq=0 MHz)
<2>Trying to associate with 00:14:6c:18:1d:80 (SSID='TNKS' freq=0 MHz)
<2>Trying to associate with 00:14:6c:18:1d:80 (SSID='TNKS' freq=0 MHz)
<2>Trying to associate with 00:14:6c:18:1d:80 (SSID='TNKS' freq=0 MHz)
<2>Trying to associate with 00:14:6c:18:1d:80 (SSID='TNKS' freq=0 MHz)
<2>Trying to associate with 00:14:6c:18:1d:80 (SSID='TNKS' freq=0 MHz)
<2>Trying to associate with 00:14:6c:18:1d:80 (SSID='TNKS' freq=0 MHz)
<2>WPA: 4-Way Handshake failed - pre-shared key may be incorrect
<2>CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
<2>CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
<2>Trying to associate with 00:14:6c:18:1d:80 (SSID='TNKS' freq=0 MHz)
<2>Trying to associate with 00:14:6c:18:1d:80 (SSID='TNKS' freq=0 MHz)
<2>Trying to associate with 00:14:6c:18:1d:80 (SSID='TNKS' freq=0 MHz)
<2>Trying to associate with 00:14:6c:18:1d:80 (SSID='TNKS' freq=0 MHz)
<2>Trying to associate with 00:14:6c:18:1d:80 (SSID='TNKS' freq=0 MHz)
<2>Trying to associate with 00:14:6c:18:1d:80 (SSID='TNKS' freq=0 MHz)
<2>Trying to associate with 00:14:6c:18:1d:80 (SSID='TNKS' freq=0 MHz)
<2>Trying to associate with 00:14:6c:18:1d:80 (SSID='TNKS' freq=0 MHz)
<2>Trying to associate with 00:14:6c:18:1d:80 (SSID='TNKS' freq=0 MHz)
<2>WPA: 4-Way Handshake failed - pre-shared key may be incorrect
<2>CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
<2>CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
<2>Trying to associate with 00:14:6c:18:1d:80 (SSID='TNKS' freq=0 MHz)
[ ... this repeats quite a bit ... ]


On versions 1.1.2/1.1.13, however, I get the following nice behavior.  Note
that everything else is the same (kernel, setup, etc.).


Connection to wpa_supplicant re-established
<2>Trying to associate with 00:14:6c:18:1d:80 (SSID='TNKS' freq=0 MHz)
<2>CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
<2>Associated with 00:14:6c:18:1d:80
<2>WPA: Key negotiation completed with 00:14:6c:18:1d:80 [PTK=TKIP GTK=TKIP]
<2>CTRL-EVENT-CONNECTED - Connection to 00:14:6c:18:1d:80 completed (auth)


I don't necessarily need to be on the latest driver, but my fear is that the
problem might persist in subsequent releases and I'll be stuck in
1.1.2/1.1.13 land.  I'm happy to help you out as best as I can, and am
eager to try any suggestions to have to setup my system and gather data.


Thanks a lot,
Sukant Hajra



-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642