Ticket #1057 (closed defect: fixed)

Opened 2 years ago

Last modified 10 months ago

Beacon miss handling starts only after many seconds

Reported by: roee Assigned to:
Priority: major Milestone: version 0.9.5
Component: madwifi: other Version: v0.9.2
Keywords: Cc:
Patch is attached: 0 Pending:

Description

I'm seeing inconsistent behavior regarding beacon miss handling.

I have a setup of both STA & AP running madwifi 0.9.2 on XScale IXP425 BE.

I let the STA associate with the AP and then I hard-reset the AP.

Sometimes the beacon miss fires almost immediately, which is good because I see in the source code that the beacon miss interval is adjusted to 7 beacon intervals i.e. it should alert after around 700 ms in the default beacon interval.

However sometimes many seconds can pass (i.e. 20 seconds and even 30 seconds) before the beacon miss function is called (ieee80211_beacon_miss() ).

I'm wondering what causes such a big variation in the generation of the beacon miss interrupt and it looks like a bug to me because this may lead to really weird scenarios where the AP completes a full reboot without the station detecting it i.e. station thinks it's associated and AP doesn't know about it.

Attachments

Change History

12/26/06 08:38:29 changed by mrenzmann

  • version set to v0.9.2.

02/07/08 04:41:13 changed by mtaylor

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

Code in trunk now supports specification of how long to miss beacons. Typically drivers will use a value from 1 second to 2.5 seconds, because during congestion you will find normal contention for the medium causes beacons to be skipped. Feel free to tune the beacon miss interval using bmiss (beacons, integral) or bmiss_ms (rounded up to nearest multiple of beacon interval).

Fixed in trunk.

02/07/08 06:12:49 changed by mrenzmann

  • milestone set to version 0.9.5.

Add/Change #1057 (Beacon miss handling starts only after many seconds)