Re: [Madwifi-devel] How to Read MIB Counters Stats?
Status: Beta
Brought to you by:
otaku
From: Tsung C. W. <tw...@br...> - 2003-11-28 01:51:08
|
Hi Sam, thanks for the reply.. just one question on this ----- Original Message ----- From: "Sam Leffler" <sa...@er...> To: "Tsung Chwen Woo" <tw...@br...>; "madwifi-devel" <mad...@li...> Sent: Tuesday, November 25, 2003 4:20 PM Subject: Re: [Madwifi-devel] How to Read MIB Counters Stats? > On Monday 24 November 2003 10:21 pm, Tsung Chwen Woo wrote: > > Dear All, > > > > I am currently starting on a project to try extract all the counters > > defined in the MIB (e.g. RTS_Success_Count, ACK_Failure_Count, > > FCS_Error_Count, and so on). > > I am very new to developing drivers so please bear with me! > > > > I can see that in ah.h, HAL_MIB_STATS struct can be found and I reckon that > > I will have to use ath_hal_attach function to obtain those statistics. Then > > use iwpriv function to present the statistics, this done by modifying the > > code in if_ieee80211wireless.c. > > Can it be done this way? Can I also extract more counter values than the > > ones stated in HAL_MIB_STATS, like those stated in the standard802dot11 > > MIB? > > > > The HAL call to fetch the MIB statistics can only be done after the h/w is up > and running. You should probably do it periodically from a timer routine in > the driver and then offer the most recent statistics to applications via some > wireless extensions call. If this doesn't make sense then you need to get up > to speed on Linux device drivers first... I understand what you mean, if I want to collect more statistics than those mentioned in the struct of HAL_MIB_STATS (ackrcv_bad, rts_bad, rts_good, fcs_bad, beacons) like received_frag_count, msdu_retry_count, WEP_undecryptable, etc, will I have to obtain the location (or specific bus tag and handle) where those statistics are stored in the hardware from Atheros? > > I have noticed that in if_wavelan_ieee.h, that wi_counters struct is being > > defined having all the desired counters. Does this mean that both Atheros > > and WaveLAN chipset supports the extraction of these counters? If so, how > > can they be extracted? > > Most of the relevant statistics are collected by the driver and you can return > them as needed. The Atheros-specific MIB statistics are not collected at the > moment and probably are only useful when operating as an AP. The WaveLan > stuff is only relevant in that you may want to export the statistics to user > applications using that format so that you can reuse user apps that > understand it. Otherwise you'll have to modify whatever tools you plan to > use to understand the Atheros-specific data structures--or whatever data > structure you return from the driver. > > Sam > > |