All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hin-Tak Leung <hintak.leung@gmail.com>
To: "Info[at]Giuppi" <info@giuppi.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: rtl8187 bug report
Date: Thu, 19 Mar 2009 21:39:20 +0000	[thread overview]
Message-ID: <3ace41890903191439q1c375925md2e4227f79147399@mail.gmail.com> (raw)
In-Reply-To: <49C12DFA.80308@giuppi.com>

On Wed, Mar 18, 2009 at 5:23 PM, Info[at]Giuppi <info@giuppi.com> wrote=
:
> I have a rtl8187B usb dongle, works pretty well with new driver rtl81=
87.
> Thanks for the great job you're doing.
>
> The problem comes when I try to handle my WEP protected network in
> monitor mode.
> It becomes really slow in finding/showing the network and when it
> appears in the list, no activity
> is detected. I mean beacons or data remains at 0 in the airodump-ng
> screen (from latest svn aircrack-ng suite)
>
> Everything works fine in managed mode and the network is easily detec=
ted
> and i can connect too.
>
> I also have a rt73usb device and this one works as expected.
>
> I'm currently using ubuntu-backport modules but I've also tryed the
> compat-wireless package dated 17 march
> kernel version 2.6.27-13-generic
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wirel=
ess" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at =A0http://vger.kernel.org/majordomo-info.html
>

I am not familiar with aircrack-ng, but I believe it can be used with
a modified version of the vendor rtl8187 driver, (and the aircrack-ng
people hosts a modified version of the vendor driver on their web
site). I have not actually looked at their modification so I have no
idea what modification is required for aircrack-ng to work well, but I
believe *some* adaptation is required?

On a different issue - I think such adaptation are frown upon and will
not make it into the standard kernel, due to its nature of typical
usage in a controversal scenario. Maybe other wireless dev people,
especially Herton and Larry, can advise.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-03-19 21:39 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 [this message]
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

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=3ace41890903191439q1c375925md2e4227f79147399@mail.gmail.com \
    --to=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 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.