Please note: This project is no longer active. The website is kept online for historic purposes only.
If you´re looking for a Linux driver for your Atheros WLAN device, you should continue here .

Ticket #495 (new task)

Opened 13 years ago

Last modified 13 years ago

wpa_supplicant on DWL-G650: "SIOCGIWRANGE: too old (short) data - assuming WPA is not supported"

Reported by: Assigned to:
Priority: minor Milestone: version 0.9.x - progressive release candidate phase
Component: madwifi: driver Version: trunk
Keywords: wpa Cc:
Patch is attached: 0 Pending:


I'm trying to connect to a WPA access point (which works well - I'm connecting with a HP iPAQ to it using WPA-PSK) from my laptop with a DWL-G650 cardbus card.

I'm using Mandriva 2005 with the today's Subversion madwifi-ng modules.

The modules load fine, I can find the access point using "iwlist ath0":

ath0      Scan completed :
          Cell 01 - Address: 00:0F:3D:EA:28:68
                    Frequency:2.422 GHz (Channel 3)
                    Quality=45/94  Signal level=-50 dBm  Noise level=-95 dBm
                    Encryption key:on
                    Bit Rate:1 Mb/s
                    Bit Rate:2 Mb/s
                    Bit Rate:5.5 Mb/s
                    Bit Rate:11 Mb/s

However, when I launch "wpa_supplicant -Dmadwifi -iath0 -c/etc/wpa_supplicant.conf -ddd" I get:

Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
Line: 373 - start of a new network block
ssid - hexdump_ascii(len=4):
     61 6e 69 61                                       ania
BSSID - hexdump(len=6): 00 0f 3d ea 28 68
proto: 0x2
key_mgmt: 0x2
pairwise: 0x10
PSK (ASCII passphrase) - hexdump_ascii(len=12): [REMOVED]
priority=5 (0x5)
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 5
   id=0 ssid='ania'
Initializing interface (2) 'ath0'
SIOCGIWRANGE: too old (short) data - assuming WPA is not supported
Own MAC address: 00:80:c8:17:64:6a
wpa_driver_madwifi_del_key: keyidx=0
wpa_driver_madwifi_del_key: keyidx=1
wpa_driver_madwifi_del_key: keyidx=2
wpa_driver_madwifi_del_key: keyidx=3
wpa_driver_madwifi_set_countermeasures: enabled=0
wpa_driver_madwifi_set_drop_unencrypted: enabled=1
Setting scan request: 0 sec 100000 usec
Added interface ath0
Wireless event: cmd=0x8b06 len=8

.... here it does nothing for a long time, so I eventually CTRL-C:

CTRL-EVENT-TERMINATING - signal 2 received
Removing interface ath0
No keys have been configured - skip key clearing
wpa_driver_madwifi_set_drop_unencrypted: enabled=0
wpa_driver_madwifi_set_countermeasures: enabled=0
No keys have been configured - skip key clearing

If I turn crypto and wpa debugging on using "80211debug +crypto +wpa", I can see the message in the kernel logs when I launch wpa_supplicant:

Mar 25 00:41:23 laptop kernel: ath0: _ieee80211_crypto_delkey: NONE keyix 65535 flags 0x3 tsc 0 len 0

Change History

03/25/06 16:59:18 changed by anonymous

  • priority changed from major to minor.
  • type changed from defect to task.

After long hours of trying various tweaks, I've finally found out that I need to make wpa_supplicant initiate scanning and AP selection:


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:


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...

04/23/06 02:16:33 changed by kelmo

  • milestone changed from version 0.9.0 - move to new codebase to version 0.9.x - progressive release candidate phase.

Could do, but I am not 100% percent sure about that yet. Possibly related to #275.