wpa_supplicant: mysterious disconnection

Brendan Jurd bj
Fri May 18 14:48:35 PDT 2007


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello the list,

I've just recently started using wpa_supplicant (with a Linksys WPC54Gv3
PC card), and got it working just fine with the wireless AP at work.
But I haven't had any success connecting to my AP at home.  To make
things even more peculiar, the AP hardware at both sites is identical
(WAP54G) and as far as I know the wireless security settings are
identical as well (WPA-PSK/TKIP).

I'm using ap_scan=2, so first wpa_supplicant tries to connect to my work
AP, doesn't find it, so then tries to connect to my home AP.  Here's the
weird part; it authenticates and connects successfully, and then
immediately disconnects.  I can't figure out why.

I've included an excerpt of the output from wpa_supplicant, and I'm
hoping to get some guidance on how to interpret these results.  Why is
the connection dying as soon as it's established?

I did search the list archives and found a couple of threads with
similar problems posted, but no resolution.

# wpa_supplicant -Dwext -iwlan0 -d -c/etc/wpa_supplicant/wpa_supplicant.conf

... attempt to connect to work AP ...

... authentication with home AP ...

State: GROUP_HANDSHAKE -> COMPLETED
CTRL-EVENT-CONNECTED - Connection to 00:12:17:68:ea:a9 completed (auth)
[id=1 id_str=swords]
wpa_driver_wext_set_operstate: operstate 0->1 (UP)
WEXT: Operstate: linkmode=-1, operstate=6
EAPOL: External notification - portValid=1
EAPOL: External notification - EAP success=1
EAPOL: SUPP_PAE entering state AUTHENTICATING
EAPOL: SUPP_BE entering state SUCCESS
EAP: EAP entering state DISABLED
EAPOL: SUPP_PAE entering state AUTHENTICATED
EAPOL: SUPP_BE entering state IDLE
EAPOL: startWhen --> 0
RTM_NEWLINK: operstate=1 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Setting scan request: 0 sec 100000 usec
Added BSSID 00:12:17:68:ea:a9 into blacklist
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
State: COMPLETED -> DISCONNECTED

The key line here seems to be "Wireless event: new AP:
00:00:00:00:00:00".  Not sure what that's about, but it's definitely not
sane.

My wpa_supplicant.conf has:

network={
        id_str="swords"
        ssid="florin"
        scan_ssid=1
        proto=WPA
        key_mgmt=WPA-PSK
        pairwise=TKIP
        group=TKIP
	psk="_blanked_"
        priority=9
}

Finally, I'm running the latest stable gentoo packages wpa_supplicant
0.5.7 and ndiswrapper 0.33.

TIA

- --
BJ
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGTh8a5YBsbHkuyV0RAi9aAKDyZ5SCSqDPo+2GvjG0JYRorLl1FACeOScn
5qXkpPkFga2ZVdJQhXQzmA0=
=zti0
-----END PGP SIGNATURE-----




More information about the Hostap mailing list