All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Beat Meier <mbe_shop@swiss-wireless.com.ar>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Is there an utility analog athstat in madwifi for linux wireless???
Date: Wed, 11 Sep 2013 16:00:33 -0500	[thread overview]
Message-ID: <1378933233.1693.31.camel@dcbw.foobar.com> (raw)
In-Reply-To: <52309B0A.7030504@swiss-wireless.com.ar>

On Wed, 2013-09-11 at 13:32 -0300, Beat Meier wrote:
> Hello
> 
> Is there any tool for wireless debugging like athstat for madwifi which
> tells you CRC errors, long retries etc.??

You're probably looking for 'debugfs', which has the following counters:

	DEBUGFS_ADD_COUNTER(rx_packets, rx_packets);
	DEBUGFS_ADD_COUNTER(tx_packets, tx_packets);
	DEBUGFS_ADD_COUNTER(rx_bytes, rx_bytes);
	DEBUGFS_ADD_COUNTER(tx_bytes, tx_bytes);
	DEBUGFS_ADD_COUNTER(rx_duplicates, num_duplicates);
	DEBUGFS_ADD_COUNTER(rx_fragments, rx_fragments);
	DEBUGFS_ADD_COUNTER(rx_dropped, rx_dropped);
	DEBUGFS_ADD_COUNTER(tx_fragments, tx_fragments);
	DEBUGFS_ADD_COUNTER(tx_filtered, tx_filtered_count);
	DEBUGFS_ADD_COUNTER(tx_retry_failed, tx_retry_failed);
	DEBUGFS_ADD_COUNTER(tx_retry_count, tx_retry_count);
	DEBUGFS_ADD_COUNTER(wep_weak_iv_count, wep_weak_iv_count);

CRC errors might be represented by rx_dropped, but I'm not sure, as the
code doesn't split CRC errors out from other RX decryption errors.

Dan


      reply	other threads:[~2013-09-11 20:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-11 16:32 Is there an utility analog athstat in madwifi for linux wireless??? Beat Meier
2013-09-11 21:00 ` Dan Williams [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1378933233.1693.31.camel@dcbw.foobar.com \
    --to=dcbw@redhat.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mbe_shop@swiss-wireless.com.ar \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.