Ticket #106 (closed defect: fixed)

Opened 6 years ago

Last modified 6 years ago

False report of "stuck beacon" when setting up WDS link

Reported by: mrenzmann Assigned to:
Priority: major Milestone: version 1.0.0 - first stable release
Component: madwifi: 802.11 stack Version: trunk
Keywords: Cc:
Patch is attached: Pending:

Description

This problem has been described in a comment to #91:

... when i bring up the AP device before the first WDS link. I get the message about the beacon queue got stucked, which will reset the device over and over again!

Additional information about the problem would be helpful, though.

Attachments

Change History

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

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

11/02/05 21:07:27 changed by rudger@hopling.com

Been tracing this issue a few ours. It all seem to be related to the rate mechanism of the WDS code (there is no rate mechanism). This resulted in sending frames to the HW with tx rate 0Mbit. In the 5112 devices resulting in beacon queue stuck on 5113 devices no errors are seen, but the frames are not send at all!.

I'm busy creating a final patch file for the WDS rate fixes.

11/03/05 13:18:54 changed by br1

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

11/03/05 22:16:49 changed by rudger@hopling.com

Fixed by adding proper transmit rates to WDS node entries. Committed revision 1282.

11/03/05 22:17:27 changed by rbrenk

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

Add/Change #106 (False report of "stuck beacon" when setting up WDS link)