From: "ABM Musa" <amusa2@uic.edu>
To: "'Daniel Haid'" <d.haid@gogi.tv>, <linux-wireless@vger.kernel.org>
Subject: RE: Capturing packets with bad FCS in monitor mode
Date: Thu, 5 Aug 2010 09:43:57 -0500 [thread overview]
Message-ID: <475A8455ABBB4AD79E2B0AD03B1F69B9@personal> (raw)
In-Reply-To: <201008051614.11546.d.haid@gogi.tv>
Packets with crc error can be captured using corresponding flag of iw.
iw phy phy0 interface add wlan0 type monitor flags fcsfail
However, there is also option for plcpfail flag but I never obtained any
packet with plcpfail using this flag. Any info about that will be helpful.
Musa
-----Original Message-----
From: linux-wireless-owner@vger.kernel.org
[mailto:linux-wireless-owner@vger.kernel.org] On Behalf Of Daniel Haid
Sent: Thursday, August 05, 2010 9:14 AM
To: linux-wireless@vger.kernel.org
Subject: Capturing packets with bad FCS in monitor mode
Hello,
is it possible to receive packets with bad FCS in monitor mode (ath9k
driver)?
There is a comment in ath9k/common.c which says that a bad checksum is
ignored in monitor mode, but I have so far never been able to receive a
packet with bad FCS (I do not know how to generate such packets, so I might
just be too lucky that all packets are received unimpaired).
Does ath9k hardware drop packets with bad FCS directly? If so, can it be
disabled?
Best regards.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@vger.kernel.org More majordomo info at
http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-08-05 14:52 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 [this message]
2010-08-05 14:56 ` Johannes Berg
2010-08-05 16:19 ` Daniel Haid
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=475A8455ABBB4AD79E2B0AD03B1F69B9@personal \
--to=amusa2@uic.edu \
--cc=d.haid@gogi.tv \
--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).