Ticket #107 (closed defect: fixed)

Opened 3 years ago

Last modified 2 years ago

driver not reporting Scan Completed wireless event

Reported by: fikrann@rikanise.net Assigned to:
Priority: major Milestone: version 1.0.0 - first stable release
Component: madwifi: 802.11 stack Version: trunk
Keywords: wpa_supplicant scanning Cc:
Patch is attached: Pending:

Description

While trying to associate, wpa_supplicant (0.3.9 and newer) gets stuck on scanning for a suitable AP; the card is constantly kept in active probe mode and scanning never finishes. My guess is, the scanning logic lacks a path out.

On a side note, replacing the wpa_driver_madwifi_scan () function with one simply calling wireless extensions scan works well and wpa_supplicant does associate properly. Patch for it is included in a separate ticket.

Attachments

Change History

11/02/05 16:33:20 changed by br1

  • milestone changed from Code: version 0.9.0 - move to new codebase to Code: version 1.0.0.

11/02/05 23:57:02 changed by jeff_sadowski@yahoo.com

I too see the same results from wpa_supplicant-0.4.6 after the patches I found in http://madwifi.org/ticket/77 and http://madwifi.org/ticket/108

11/03/05 13:19:30 changed by br1

  • component changed from madwifi: driver to madwifi: 802.11 stack.

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

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

The scan does finish it just takes a damn long time, wpa_supplicant ver 0.4.7 will show a perfect example of this ; )

Add/Change #107 (driver not reporting Scan Completed wireless event)