Re: Linksys/Dell SRX400 problem with WPA-PSK/TKIP

["Darren Albers" <dalbers gmail com>]

On 8/18/06, Robert G. Brown <rgb phy duke edu> wrote:
> Aug 18 15:48:50 lilith NetworkManager: <information> wpa_supplicant(4002): WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
> Aug 18 15:48:50 lilith NetworkManager: <information> wpa_supplicant(4002): Authentication with 00:16:b6:f7:28:53 timed out.
> Aug 18 15:48:50 lilith NetworkManager: <information> wpa_supplicant(4002):  2d 32 30 00 00 00
> Aug 18 15:48:50 lilith NetworkManager: <information> wpa_supplicant(4002): Added BSSID 00:16:b6:f7:28:53 into blacklist
> Aug 18 15:48:50 lilith NetworkManager: <information> wpa_supplicant(4002): State: GROUP_HANDSHAKE -> DISCONNECTED
> Aug 18 15:48:50 lilith NetworkManager: <information> wpa_supplicant(4002): wpa_driver_wext_disassociate
> Aug 18 15:48:51 lilith NetworkManager: <information> wpa_supplicant(4002): wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
> ...
>
> where at no time does it get a connection (and it periodically complains
> about being disconnected).  Doesn't look quite like it does when it
> successfully connects.
>
> Has anyone seen this before?  Is there a workaround or am I doing
> something stupid?  It's really inconvenient to have to hook into the
> network directly, especially since the core network is a total mess (no
> DHCP server at all, for example, so all eth0 connections have to be done
> the hard way).  Before, with WPA-PSK/EAS I was able to go all over the
> building from a single WAP.  Sigh.

It is certainly odd that it worked with WPA/AES and not with WPA/TKIP.

Can you try creating a wpa_supplicant.conf like this:
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=2
fast_reauth=1
network={
     ssid="Enteryour SSID Here"
     proto=WPA
     key_mgmt=WPA-PSK
     pairwise=TKIP
     group=TKIP
     psk=enteryourkeyhere
}

And then try one of the two commands to bring up WPA_Supplicant:
wpa_supplicant -d -c/path/to/wpa_supplicant.conf -ieth1 -Dwext
or
wpa_supplicant -d -c/path/to/wpa_supplicant.conf -ieth1 -Dndis

Replace eth1 with your interface name.

Then bring up the interface normally ie ifup eth1

If it connects fine with -Dwext then something wierd is happening
between NetworkManager and WPA_Supplicant.

If it only connects via -Dndis then you are running a version of
NDISWrapper that doesn't support WEXT (Though this is unlikely since
WPA/AES worked...) and you will need to update NDISWrapper.