From: ABM Musa <amusa2@uic.edu>
To: Daniel Haid <d.haid@gogi.tv>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Capturing packets with bad FCS in monitor mode
Date: Thu, 05 Aug 2010 11:50:42 -0500 [thread overview]
Message-ID: <4C5AEBE2.5060907@uic.edu> (raw)
In-Reply-To: <201008051840.18914.d.haid@gogi.tv>
On 08/05/2010 11:40 AM, Daniel Haid wrote:
>> I can get packets with crc error using this method and I get lot of
>> corrupted packets. I am using ath9k with openwrt for router station
>> pro+ubiquity sr-71A card and tplink 1043nd.
>>
> I am using an ubiquity sr-71X card, and still not one corrupted packet.
>
> I think I need to artificially create and transmit a corrupted packet. How
> can I do that?
> --
> 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
>
>
I am not sure about how to create corrupted packets. Normally you should
get lot of corrupted packets from surrounding transmission. In my case,
monitor mode hangs sometime and I don't get any packets. Then if I
delete the interface and create a new interface using the iw command I
gave earlier, I get packets with crc error. You can also modify already
created interface using
iw wlan0 set monitor flag fcsfail
Musa
next prev parent reply other threads:[~2010-08-05 16:50 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
2010-08-05 16:30 ` ABM Musa
2010-08-05 16:40 ` Daniel Haid
2010-08-05 16:50 ` ABM Musa [this message]
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=4C5AEBE2.5060907@uic.edu \
--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 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.