Ticket #139 (closed defect: invalid)

Opened 5 years ago

Last modified 4 years ago

[wpa_supplicant/madwifi] "Authentication with 00:00:00:00:00:00 timed out."

Reported by: xmxwx Assigned to: xmxwx
Priority: high Milestone: 3.0
Component: Madwifi Version: 2.0
Severity: blocker Keywords:
Cc:

Description

wpa_supplicant running on madwifi sta (client mode) "hangs" after trying to reassociate to AP when there is little traffic (packet rate?) on the device.

The "hang" means that despite the fact that wpa_supplicant is claiming to be trying to associate no packets are being sent out through the device.

Easy to reconstruct: 

wpa_cli
reassociate

The probability of failure seems to depend somehow on the activity of the interface. The less ping -i is run on the interface, the more stable the connection is.

Change History

12/31/06 16:37:19 changed by xmxwx

  • status changed from new to assigned.

Using -Dmadwifi instead of -Dwext seems to help here. The error occurs as well, but the authentication is eventually established.

madwifi.org does not clearly state which of these drivers is preferred.

The same (or at least similar) problem is reported in: http://madwifi.org/ticket/742

01/01/07 23:02:20 changed by xmxwx

And possibly another instance of the problem: http://madwifi.org/ticket/961

01/01/07 23:04:53 changed by xmxwx

Or rather of a similar one, because #961 refers to unsuccessful usage of -Dmadwifi.

02/08/07 13:13:56 changed by xmxwx

  • owner deleted.
  • status changed from assigned to new.

02/08/07 13:14:50 changed by xmxwx

  • owner set to xmxwx.

02/21/07 01:32:48 changed by xmxwx

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

In the new testing environment I am unable to reproduce the problem. Maybe it had been caused by low link quality in the previous test, maybe it was a "random hardware problem".

03/15/08 15:49:29 changed by pjf

  • milestone changed from 2.1rc1 to 3.0.

Milestone 2.1rc1 deleted