Ticket #108 (closed enhancement: fixed)

Opened 3 years ago

Last modified 3 years ago

Patch for wpa_supplicant to enable wext scan -- temporary solution?

Reported by: fikrann@rikanise.net Assigned to:
Priority: minor Milestone: version 0.9.0 - move to new codebase
Component: madwifi: other Version: trunk
Keywords: wpa_supplicant scanning patch Cc:
Patch is attached: Pending:

Description

This patch switches wpa_supplicant to use wext scanning on madwifi, therefore avoiding the scan problem present in current driver.

Attachments

driver_madwifi.patch (1.0 kB) - added by fikrann@rikanise.net on 11/02/05 10:47:25.

Change History

11/02/05 10:47:25 changed by fikrann@rikanise.net

  • attachment driver_madwifi.patch added.

11/02/05 15:26:14 changed by kelmo

This indeed provided a successful workaround for me also, although i required another patch from ticket #77 to compile wpa_supplicant. (and of course the patch from atheros)

11/03/05 12:14:41 changed by anonymous

This patch did the trick (together with the one from ticket #77 and from madwifi-ng/patches to get wpa_supplicant to compile at all). I am writing this over a wireless connection using WPA PSK, the latest madwifi-ng from subversion and the latest wpa_supplicant from CVS.

Unfortunately doing the scan this way apparently does not work for APs with hidden SSIDs. That is not a problem for me at home (I just switched the broadcasting of the SSID back on) but at the office this will keep me from getting a connection.

I will try to find out, if there is any way to do a SSID specific scan via commands like iwlist etc. to verify, that it really doesn't work and then open a new ticket against madwifi-ng.

11/12/05 05:44:57 changed by Jouni Malinen <jkmaline@cc.hut.fi>

The current wpa_supplicant development snapshot uses the old driver_madwifi scan request, but with a backup timeout (30 sec) to get the scan results even if the driver does not send scan complete event. This will result in longer scan time, but at least the end result seems to be working and is available without having to patch wpa_supplicant.

11/23/05 20:36:55 changed by arosborough@gmail.com

Using wpa_supplicant and 0.4.7 and a cvs snapshot of madwifi-drivers from 20051121 I was able to connect to my AP using WPA-PSK even though it does not broadcast its ssid.

It only works if I enter the command 'iwconfig ath0 essid <myessid> channel 6 ap <mybssid>' while wpa_supplicant is in the process of scanning aps. ap_scan=1 and scan_ssid=0

11/25/05 12:41:29 changed by kelmo

  • status changed from new to closed.
  • resolution set to fixed.

Confirmed working with wpa_supplicant 0.4.7

Add/Change #108 (Patch for wpa_supplicant to enable wext scan -- temporary solution?)