Please note: This project is no longer active. The website is kept online for historic purposes only.
If you´re looking for a Linux driver for your Atheros WLAN device, you should continue here .

Ticket #1845 (new defect)

Opened 14 years ago

Last modified 14 years ago

athstats: short and long on-chip retry counters switched?

Reported by: Assigned to:
Priority: major Milestone:
Component: madwifi: tools Version: v0.9.4
Keywords: athstats short long retry counter swap Cc:
Patch is attached: 0 Pending:


I noticed something interesting with the athstats program, packaged with madwifi drivers toolset. I am running a adhdemo network with nine terminals, all with SMC "SMCWPCIT-G" cards, set at 1 mbps.

My interest is with the short and long on-chip retry counters. As far as I know, the RTS threshold decides if packets will be sent using BASIC or RTS access. Packets less than the threshold are considered SHORT and are sent using BASIC access. Packets greater than or equal to the RTS threshold are considered long and sent via RTS access.

If I set the RTS threshold value in iwconfig to "OFF" or "2304" (the maximum length of an 802.11 packets) I have effectively enforced BASIC access on all packets. Therefore, if transmissions fail, the SHORT retry counter should be incremented. However, the athstats program shows an increase in LONG on-chip retries over time. Conversely, if I set the RTS threshold to "1" I see only SHORT on-chip retries.

I'm not sure whether I am missing something obvious here, but I haven't had any luck in the #madwifi channel on freenode. Apologies if I submit this defect in error, but I thought it was an important observation.

Change History

(follow-up: ↓ 2 ) 07/03/08 15:34:57 changed by arctanck

I'm seeing this problem too. Does anyone has an answer to this?

(in reply to: ↑ 1 ) 07/04/08 13:48:07 changed by

I imagine that the only justification for calling RTS retries "SHORT retries" is that the length of a RTS frame is typically shorter than a data frame, which results in a "LONG retry". However, this is confusing, as the standard uses "long" in the context of RTS/CTS access and "short" in the context of basic access. Any suggestions?