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 #1113 (new defect)

Opened 15 years ago

Last modified 15 years ago

wpasupplicant's ap_scan=1 makes madwifi fail on open networks

Reported by: bugreports@nn7.de Assigned to:
Priority: major Milestone:
Component: madwifi: other Version: trunk
Keywords: wpa_supplicant, networkmanager Cc:
Patch is attached: 0 Pending:

Description (Last modified by mrenzmann)

This basically is a followup to: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=385599 . wpa_supplicant's failing also causes NM to fail

(this thread: http://mail.gnome.org/archives/networkmanager-list/2006-November/msg00194.html)

For the bug, when one does:

wpa_supplicant -i ath0 -Dwext -c wpa_supplicant.conf -d

with wpa_supplicant.conf:

eapol_version=1
ap_scan=1
fast_reauth=1

network={
       ssid="Atlantic"
       key_mgmt=NONE
       auth_alg=OPEN
       }

It is impossible to associate to a AP + getting a IP. The output of this seemed pretty similar to the one obtained by NM. wpasupplicant would just keep trying to associate, and then keep scanning. Finally, I decided to try ap_scan=0. Then, wpa_supplicant would say connected and I could (most times) get an IP using dhclient -1 ath0.

Does this give you any clue why the problem exist in newer versions of madwifi (I am using the latest svn).

Note that this was working with r1500.

Change History

01/26/07 10:40:21 changed by mrenzmann

  • description changed.