From: Mike Kershaw <dragorn@kismetwireless.net>
To: G?bor Stefanik <gst@remote-exploit.org>
Cc: "Info[at]Giuppi" <info@giuppi.com>,
Hin-Tak Leung <hintak.leung@gmail.com>,
linux-wireless@vger.kernel.org
Subject: Re: rtl8187 bug report
Date: Tue, 24 Mar 2009 16:13:19 -0400 [thread overview]
Message-ID: <20090324201319.GB14489@drd1813.lan> (raw)
In-Reply-To: <20090322235416.GA32143@drd1813.cave.swamp>
[-- Attachment #1: Type: text/plain, Size: 1659 bytes --]
On Sun, Mar 22, 2009 at 07:54:16PM -0400, Mike Kershaw wrote:
> On Fri, Mar 20, 2009 at 10:06:49PM +0100, G?bor Stefanik wrote:
> > Could you please test if you can see packets originating from your
> > network in Kismet or Wireshark?
> > Also, did you use the included airmon-ng script to enable monitor
> > mode, or did you just do "ifconfig wlan0 down; iwconfig wlan0 mode
> > monitor, ifconfig wlan0 up"? (The two are significantly different, as
> > airmon-ng uses iw/nl80211 to enable monitor mode on a separate
> > interface - it would be good if you tried it both ways.)
>
> I have actually seen similar problems with the 8187 (unknown if it is B
> or L - the drivers think it's B, but the production run of the hardware
> is NORMALLY L and may have recently changed; I have known-B generic cards
> and maybe-B Alfa cards)
I am NOT seeing this behavior under 2.6.29 so far (~1hr test) with
channel hopping enabled (siocsiwchan, nothing fancy) at 3x a second,
single rfmon vap set via siociwmode.
-m
--
Mike Kershaw/Dragorn <dragorn@kismetwireless.net>
GPG Fingerprint: 3546 89DF 3C9D ED80 3381 A661 D7B2 8822 738B BDB1
"Hostility towards Microsoft is not difficult to find on the Net, and it
blends two strains: resentful people who feel Microsoft is too powerful,
and disdainful people who think it's tacky. This is all strongly reminiscent
of the heyday of Communism and Socialism, when the bourgeoisie were hated
from both ends: by the proles, because they had all the money, and by the
intelligentsia, because of their tendency to spend it on lawn ornaments."
-- Neal Stephenson
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2009-03-24 20:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 17:23 rtl8187 bug report Info[at]Giuppi
2009-03-19 21:39 ` Hin-Tak Leung
2009-03-19 23:28 ` Info[at]Giuppi
2009-03-20 1:56 ` Hin-Tak Leung
2009-03-20 13:30 ` Info[at]Giuppi
2009-03-20 19:30 ` Hin-Tak Leung
2009-03-20 21:06 ` Gábor Stefanik
2009-03-22 0:33 ` Info[at]Giuppi
2009-03-22 23:54 ` Mike Kershaw
2009-03-24 20:13 ` Mike Kershaw [this message]
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=20090324201319.GB14489@drd1813.lan \
--to=dragorn@kismetwireless.net \
--cc=gst@remote-exploit.org \
--cc=hintak.leung@gmail.com \
--cc=info@giuppi.com \
--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).