From: Christian Lamparter <chunkeey@googlemail.com>
To: Realman Namingston <realname1776@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: bad packets in monitor mode with ar9170 devices
Date: Fri, 1 Apr 2011 09:51:42 +0200 [thread overview]
Message-ID: <201104010951.42502.chunkeey@googlemail.com> (raw)
In-Reply-To: <AANLkTi=pWrS9jK1obHLiXu+oLK6YS00fG-YQqzUieYH7@mail.gmail.com>
On Friday 01 April 2011 05:12:45 Realman Namingston wrote:
> ar9170-based devices record a fair amount of bad packets in monitor
> mode both with the old ar9170usb and new carl9170 drivers. The packets
> contain random BSSIDs, some measure of additional random data, and
> seem to scale proportional to the amount of traffic occurring on the
> observed channel. This behavior makes the devices rather unattractive
> for use in Kismet and site survey applications.
>
> I assume this is due to a shortcoming of the hardware.. but is there
> any potential fix possible?
no, you misunderstood that completely: it's a shortcoming of kismet!
quote:
"Usually the wireless adapter is unable to transmit in monitor mode and
is restricted to a single wireless channel, though this is dependent on
the wireless adapter's driver, its firmware, and its chip set's features.
Also, in monitor mode the adapter does not check to see if the cyclic
redundancy check (CRC) values are correct for packets captured, so some
captured packets may be corrupted."
http://en.wikipedia.org/wiki/Monitor_mode
next prev parent reply other threads:[~2011-04-01 7:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-01 3:12 bad packets in monitor mode with ar9170 devices Realman Namingston
2011-04-01 7:51 ` Christian Lamparter [this message]
2011-04-01 16:54 ` Gábor Stefanik
2011-04-01 17:33 ` Christian Lamparter
2011-04-05 0:16 ` Gábor Stefanik
2011-04-05 0:28 ` Richard Farina
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=201104010951.42502.chunkeey@googlemail.com \
--to=chunkeey@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=realname1776@gmail.com \
/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).