Date: Sat, 10 Sep 2005 10:55:12 -0700 From: Brooks Davis <brooks@one-eyed-alien.net> To: Sam Lawrance <boris@brooknet.com.au> Cc: current@freebsd.org Subject: Re: wpa_supplicant AP scanning doesn't work after first association Message-ID: <20050910175512.GA9155@odin.ac.hmc.edu> In-Reply-To: <1126360250.828.38.camel@dirk.no.domain> References: <1126360250.828.38.camel@dirk.no.domain>
next in thread | previous in thread | raw e-mail | index | archive | help
--5mCyUwZo2JvN/JJP
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Sat, Sep 10, 2005 at 11:50:50PM +1000, Sam Lawrance wrote:
> Hi,
>=20
> The station boots up and associates with the AP OK. This works great
> for days. If I power down the AP and power it up again, after
> disassociating, wpa_supplicant fails to locate the access point in its
> scans.
>=20
> I am using RELENG_6 from 3 September.
>=20
> The station is a D-Link DWL-G510 (atheros based)
> ath0@pci0:8:0: class=3D0x020000 card=3D0x3a161186 chip=3D0x001a168c rev=
=3D0x01 hdr=3D0x00.
>=20
> rc.conf entry:
> ifconfig_ath0=3D"WPA inet 192.168.0.1 netmask 255.255.255.0"
>=20
> wpa_supplicant.conf contains:
> ctrl_interface=3D/var/run/wpa_supplicant
> ctrl_interface_group=3Dwheel
> network=3D{
> ssid=3D"sunset"
> scan_ssid=3D1
> key_mgmt=3DWPA-PSK
> psk=3D ... etc etc ...
> }
>=20
> The access point is a D-Link DI-524 firmware v2.02, configured for
> WPA-PSK
>=20
> Output from wpa_supplicant:
>=20
> Starting AP scan (specific SSID)
> Scan SSID - hexdump_ascii(len=3D6):
> 73 75 6e 73 65 74 sunset =20
> Received 0 bytes of scan results (1 BSSes)
> Scan results: 1
> Selecting BSS from priority group 0
> 0: 00:0f:3d:29:79:f5 ssid=3D'sunset' wpa_ie_len=3D24 rsn_ie_len=3D0
> selected
> Trying to associate with 00:0f:3d:29:79:f5 (SSID=3D'sunset' freq=3D2437 M=
Hz)
> Cancelling scan request
> Automatic auth_alg selection: 0x1
> WPA: using IEEE 802.11i/D3.0
> WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2
> WPA: using GTK TKIP
> WPA: using PTK TKIP
> WPA: using KEY_MGMT WPA-PSK WPA: Own WPA IE - hexdump(len=3D24): dd 16 00=
50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
> No keys have been configured - skip key clearing
> wpa_driver_bsd_set_drop_unencrypted: enabled=3D1=20
> wpa_driver_bsd_associate: ssid 'sunset' wpa ie len 24 pairwise 2 group 2 =
key mgmt 1
> wpa_driver_bsd_associate: set PRIVACY 1
> Setting authentication timeout: 5 sec 0 usec
> Association event - clear replay counter
> Associated to a new BSS: BSSID=3D00:0f:3d:29:79:f5
> No keys have been configured - skip key clearing
> Associated with 00:0f:3d:29:79:f5
> Setting authentication timeout: 10 sec 0 usec
> RX EAPOL from 00:0f:3d:29:79:f5=20
>=20
> ... power down AP, wait a minute, power up AP ...
>=20
> Starting AP scan (broadcast SSID)
> Received 0 bytes of scan results (0 BSSes)
> Scan results: 0
> Selecting BSS from priority group 0
> No suitable AP found.
> Setting scan request: 5 sec 0 usec
> Starting AP scan (specific SSID)
> Scan SSID - hexdump_ascii(len=3D6):
> 73 75 6e 73 65 74 sunset =20
> Received 0 bytes of scan results (0 BSSes)
> Scan results: 0
> Selecting BSS from priority group 0
> No suitable AP found.
>=20
>=20
> Please let me know what other information I can collect to help figure
> this out. I hope it's not pilot error :)
Running current as of August 23rd an connecting using WPA-PSK to connect
to a DI-524 running firmware 1.11, I reconnect promptly when I power the
AP back on.
-- Brooks
--=20
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4
--5mCyUwZo2JvN/JJP
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQFDIx4AXY6L6fI4GtQRAuaNAJ9M2N9tV63ia7jzBnQhQOFnS+x9dgCeOR0t
98jXtPRPvNjUf22+7nbfZy0=
=aGc0
-----END PGP SIGNATURE-----
--5mCyUwZo2JvN/JJP--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050910175512.GA9155>