Linksys/Dell SRX400 problem with WPA-PSK/TKIP
- From: "Robert G. Brown" <rgb phy duke edu>
- To: networkmanager-list <networkmanager-list gnome org>
- Subject: Linksys/Dell SRX400 problem with WPA-PSK/TKIP
- Date: Fri, 18 Aug 2006 19:44:09 -0400 (EDT)
Hi, I'm trying to establish WPA-PSK connections to a linksys router. At
home I currently have a fancy new netgear WPN824v2 rangemax WAP/router
and WPA-PSK/TKIP to it seems to work just fine with a preshared key. At
a medical practice I'm trying to help set up, the Linksys routers "have"
to be set up WPA-PSK/TKIP in order for doc PDAs to be able to wirelessly
connect and use certain applications. I discovered empirically when
setting them up originally that they'd work within NM 0.6.4 with the WAP
set up to use WPA-PSK/AES and a preshared key, but when the WAP is
switched to TKIP with the same preshared key, it refuses to connect. In
terms of stages, the little lower ball doesn't turn green and the log
shows no connection or advances to where DHCP can happen. For example:
Aug 18 15:48:50 lilith NetworkManager: <information> wpa_supplicant(4002): 01 00 00 50 f2 02 01 00 00 50 f2 02
Aug 18 15:48:50 lilith NetworkManager: <information> wpa_supplicant(4002): RX EAPOL from 00:16:b6:f7:28:53
Aug 18 15:48:50 lilith NetworkManager: <information> wpa_supplicant(4002): RX EAPOL - hexdump(len=123): 01 03 00 77 fe 01 c9 00 20 3c 51 69 8d 00 00 00 02 e2 64 fb be 4d d9 a7 3b 43 ef 1f e2 55 c6 2d 64 e7 53 21 50 c3 92 b6 37 02 20 aa 13 c5 60 64 09 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90 ee 1d de 01 4b e0 03 bd b0 ca a1 26 bb fb d5 00 18 dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
Aug 18 15:48:50 lilith NetworkManager: <information> wpa_supplicant(4002): IEEE 802.1X RX: version=1 type=3 length=119
Aug 18 15:48:50 lilith NetworkManager: <information> wpa_supplicant(4002): EAPOL-Key type=254
Aug 18 15:48:50 lilith NetworkManager: <information> wpa_supplicant(4002): WPA: RX EAPOL-Key - hexdump(len=123): 01 03 00 77 fe 01 c9 00 20 3c 51 69 8d 00 00 00 02 e2 64 fb be 4d d9 a7 3b 43 ef 1f e2 55 c6 2d 64 e7 53 21 50 c3 92 b6 37 0 2 20 aa 13 c5 60 64 09 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90 ee 1d de 01 4b e0 03 bd b0 ca a1 26 bb fb d5 00 18 dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
Aug 18 15:48:50 lilith NetworkManager: <information> wpa_supplicant(4002): State: 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE
Aug 18 15:48:50 lilith NetworkManager: <information> wpa_supplicant(4002): 16:b6:f7:28:53 (ver=1)
Aug 18 15:48:50 lilith NetworkManager: <information> wpa_supplicant(4002): WPA: IE KeyData - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
Aug 18 15:48:50 lilith NetworkManager: <information> wpa_supplicant(4002): WPA: Sending EAPOL-Key 4/4
Aug 18 15:48:50 lilith NetworkManager: <information> wpa_supplicant(4002): WPA: TX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 01 09 00 20 3c 51 69 8d 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 76 7c 01 7f 40 11 86 5d 20 0a db 80 f8 ec 26 ba 00 00
Aug 18 15:48:50 lilith NetworkManager: <information> wpa_supplicant(4002): WPA: Installing PTK to the driver.
Aug 18 15:48:50 lilith NetworkManager: <information> wpa_supplicant(4002): WPA: RSC - hexdump(len=6): 00 00 00 00 00 00
Aug 18 15:48:50 lilith NetworkManager: <information> wpa_supplicant(4002): wpa_driver_wext_set_key: alg=2 key_idx=0 set_tx=1 seq_len=6 key_len=32
Aug 18 15:48:50 lilith NetworkManager: <information> wpa_supplicant(4002): State: 4WAY_HANDSHAKE -> GROUP_HANDSHAKE
Aug 18 15:48:50 lilith NetworkManager: <information> wpa_supplicant(4002): EAPOL: startWhen --> 0
Aug 18 15:48:50 lilith NetworkManager: <information> wpa_supplicant(4002): EAPOL: SUPP_PAE entering state CONNECTING
Aug 18 15:48:50 lilith NetworkManager: <information> wpa_supplicant(4002): EAPOL: txStart
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.
rgb
--
Robert G. Brown http://www.phy.duke.edu/~rgb/
Duke University Dept. of Physics, Box 90305
Durham, N.C. 27708-0305
Phone: 1-919-660-2567 Fax: 919-660-2525 email:rgb phy duke edu
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]