#495: wpa_supplicant on DWL-G650: "SIOCGIWRANGE: too old (short) data - assuming
WPA is not supported"
-------------------------------------------------+--------------------------
Reporter: [EMAIL PROTECTED] | Owner:
Type: task | Status: new
Priority: minor | Milestone: version 0.9.0
- move to new codebase
Component: madwifi: driver | Version: trunk
Resolution: | Keywords: wpa
Patch_attached: 0 |
-------------------------------------------------+--------------------------
Changes (by anonymous):
* priority: major => minor
* type: defect => task
Comment:
After long hours of trying various tweaks, I've finally found out that I
need to make wpa_supplicant initiate scanning and AP selection:
{{{
ap_scan=1
}}}
Actually this is the default that I have mistekenly changed it to 0 when
initially configuring WPA supplicant, so it's rather a mistake on my side.
Earlier I had:
{{{
ap_scan=0
}}}
Here are the comments about this option in my wpa_supplicant.conf:
{{{
# AP scanning/selection
# By default, wpa_supplicant requests driver to perform AP scanning and
then
# uses the scan results to select a suitable AP. Another alternative is to
# allow the driver to take care of AP scanning and selection and use
# wpa_supplicant just to process EAPOL frames based on IEEE 802.11
association
# information from the driver.
# 1: wpa_supplicant initiates scanning and AP selection
# 0: driver takes care of scanning, AP selection, and IEEE 802.11
association
# parameters (e.g., WPA IE generation); this mode can also be used with
# non-WPA drivers when using IEEE 802.1X mode; do not try to associate
with
# APs (i.e., external program needs to control association)
# 2: like 0, but associate with APs using security policy and SSID (but
not
# BSSID); this can be used, e.g., with ndiswrapper and NDIS driver to
# enable operation with hidden SSIDs and optimized roaming; in this
mode,
# only the first network block in the configuration file is used and
this
# configuration should have explicit security policy (i.e., only one
option
# in the lists) for key_mgmt, pairwise, group, proto variables
}}}
Could the madwifi driver work with ap_scan=0? It seems reasonable that the
driver could take care of scanning and AP association as well...
--
Ticket URL: <http://madwifi.org/ticket/495>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
