Return-path: Received: from mail-qw0-f46.google.com ([209.85.216.46]:64753 "EHLO mail-qw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757606Ab1DAQyv convert rfc822-to-8bit (ORCPT ); Fri, 1 Apr 2011 12:54:51 -0400 Received: by qwk3 with SMTP id 3so2261731qwk.19 for ; Fri, 01 Apr 2011 09:54:50 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <201104010951.42502.chunkeey@googlemail.com> References: <201104010951.42502.chunkeey@googlemail.com> From: =?ISO-8859-1?Q?G=E1bor_Stefanik?= Date: Fri, 1 Apr 2011 18:54:29 +0200 Message-ID: Subject: Re: bad packets in monitor mode with ar9170 devices To: Christian Lamparter Cc: Realman Namingston , linux-wireless@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Fri, Apr 1, 2011 at 9:51 AM, Christian Lamparter wrote: > 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 > -- > 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 > Isn't ar9170 the wireless-N version of zd1211? Because zd1211 also had this problem with ZD_SNIFFER_ON. See http://patches.aircrack-ng.org/zd1211rw_inject_2.6.26.patch -- Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)