From: Daniel Haid <d.haid@gogi.tv>
To: "ABM Musa" <amusa2@uic.edu>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Capturing packets with bad FCS in monitor mode
Date: Thu, 5 Aug 2010 18:19:55 +0200 [thread overview]
Message-ID: <201008051819.55252.d.haid@gogi.tv> (raw)
In-Reply-To: <475A8455ABBB4AD79E2B0AD03B1F69B9@personal>
> Packets with crc error can be captured using corresponding flag of iw.
>
> iw phy phy0 interface add wlan0 type monitor flags fcsfail
Is this supported on ath9k? I do not see any difference so far
with the packet capturing.
I also do not find the FIF_FCSFAIL flag be used anywhere in
the ath9k code.
Will I get lots of corrupted packets if this is enabled properly or only
casually?
next prev parent reply other threads:[~2010-08-05 16:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-05 14:14 Capturing packets with bad FCS in monitor mode Daniel Haid
2010-08-05 14:43 ` ABM Musa
2010-08-05 14:56 ` Johannes Berg
2010-08-05 16:19 ` Daniel Haid [this message]
2010-08-05 16:30 ` ABM Musa
2010-08-05 16:40 ` Daniel Haid
2010-08-05 16:50 ` ABM Musa
2010-08-05 22:58 ` Qasim Javed
2010-08-06 0:58 ` Daniel Haid
2010-08-06 1:06 ` Daniel Haid
2010-08-06 10:09 ` radiotap rate no longer supported in mac80211? Daniel Haid
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=201008051819.55252.d.haid@gogi.tv \
--to=d.haid@gogi.tv \
--cc=amusa2@uic.edu \
--cc=linux-wireless@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).