stardotstar
l33t
Joined: 10 Feb 2006
Posts: 887
Location: 2074/SYD/NSW/AU
|
 Posted: Tue Jul 08, 2008 10:23 pm Post subject: wpa_sup and wpa strange behaviour... |
 |
|
Hi all,
I am having *some* success with wpa_supplicant at the moment using the madwifi drivers.
I find that I can't always associate with my networks using any method I can understand from the man pages.
I have only one network at any location - two in particular both use wpa-psk tkip and I have been able to associate with them using the existing settings but only when the other network is hashed out of the wpa_supp.conf file...
As I understood it the process is to evaluate available networks in the order they are listed in the .conf and then by signal strength and security method with wpa prefered.
None of this should matter in the case of: only one network in range OR other networks set to disabled=1 in the config.
when I use wpa_cli I get confusing reports - despite listing the ssid and bssid the process reports timeouts to a null bssid:
| Code: | aegis ~ # wpa_cli
wpa_cli v0.5.7
Copyright (c) 2004-2006, Jouni Malinen <jkmaline@cc.hut.fi> and contributors
This program is free software. You can distribute it and/or modify it
under the terms of the GNU General Public License version 2.
Alternatively, this software may be distributed under the terms of the
BSD license. See README and COPYING for more details.
Selected interface 'ath0'
Interactive mode
> status
wpa_state=ASSOCIATING
> list
network id / ssid / bssid / flags
0 skink 00:13:46:bd:49:16 [DISABLED]
1 wraith 00:17:9a:46:7c:a5 [CURRENT]
> status
wpa_state=ASSOCIATING
> <2>Authentication with 00:00:00:00:00:00 timed out.
<2>Trying to associate with SSID 'wraith'
<2>Authentication with 00:00:00:00:00:00 timed out.
<2>Trying to associate with SSID 'wraith'
|
Here is the config: Note I have used several hashes to see if eapol/scan_ssid etc make any diff.
| Code: |
aegis ~ # cat /etc/wpa_supplicant/wpa_supplicant.conf
# This is a network block that connects to any unsecured access point.
# We give it a low priority so any defined blocks are preferred.
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=users
update_config=1
ap_scan=2
#fast_reauth=1
#eapol_version=1
#network={
# key_mgmt=NONE
# priority=-9999999
#}
network={
ssid="skink"
bssid=00:13:46:bd:49:16
proto=WPA
pairwise=TKIP
key_mgmt=WPA-PSK
psk="secretpasswrd"
disabled=1
}
network={
bssid=00:17:9A:46:7C:A5
ssid="wraith"
# scan_ssid=1
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
psk=3776c39877e64cf4f68f98f89256cd462698261b03e83c65905b027b98b114e8
disabled=0
priority=1
}
|
| Code: | > get_capability pairwise
CCMP TKIP NONE> get_capability proto
RSN WPA> list
network id / ssid / bssid / flags
0 wraith 00:17:9a:46:7c:a5
> select_network 0
<1>Setting scan request: 0 sec 0 usec
OK
> list
network id / ssid / bssid / flags
0 wraith 00:17:9a:46:7c:a5
> scan_results
> ap_scan 1
OK
> status
wpa_state=SCANNING
> scan_results
> list
network id / ssid / bssid / flags
0 wraith 00:17:9a:46:7c:a5
> reassociate
<1>Setting scan request: 0 sec 0 usec
OK
> <1>Setting scan request: 5 sec 0 usec
<1>Setting scan request: 5 sec 0 usec
<1>Setting scan request: 5 sec 0 usec
<1>Setting scan request: 5 sec 0 usec
<1>Setting scan request: 5 sec 0 usec
set
set variables:
EAPOL::heldPeriod (EAPOL state machine held period, in seconds)
EAPOL::authPeriod (EAPOL state machine authentication period, in seconds)
EAPOL::startPeriod (EAPOL state machine start period, in seconds)
EAPOL::maxStart (EAPOL state machine maximum start attempts)
dot11RSNAConfigPMKLifetime (WPA/WPA2 PMK lifetime in seconds)
dot11RSNAConfigPMKReauthThreshold (WPA/WPA2 reauthentication threshold
percentage)
dot11RSNAConfigSATimeout (WPA/WPA2 timeout for completing security
association in seconds)
> <1>Setting scan request: 5 sec 0 |
can't associate with this network at all this morning!
anybody with any insight into this state would be appreciated!
\\'
_________________
]8P |
|
Networking & Security
