linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maxim Levitsky <maximlevitsky@gmail.com>
To: linux-wireless@vger.kernel.org, Zhu Yi <yi.zhu@intel.com>
Cc: ipw3945-devel@lists.sourceforge.net,
	"Stefanik Gábor" <netrolller.3d@gmail.com>
Subject: Re: [BUG] Two bugs in monitor mode, iwl3945
Date: Wed, 09 Jul 2008 19:25:51 +0300	[thread overview]
Message-ID: <4874E68F.7090106@gmail.com> (raw)
In-Reply-To: <485F687C.1050407@gmail.com>

Maxim Levitsky wrote:
> I noticed two bugs:
>=20
> 1) Monitor mode hangs the system randomly, and what is interesting th=
at=20
> this
> bug disappears if I patch the driver with packet injection patch from=
=20
> G=E1bor Stefanik.
> I noticed this bug, after I removed his patch to see if it caused som=
e=20
> problems.
> Always reproducible, usually hangs just after airodump launch.
>=20
> 2) If I enable monitor mode regardless of injection patch, the scanni=
ng=20
> results got garbaged,
> iwlist scan reports > 100 quality on most APs, or 0% quality on my=20
> router, shows extremely low and hi power levels, like
> -127dBm or 160 dBm, and those levels change rapidly.
> This why I removed the injection patch, I suspected it, but this bug=20
> appears to be not related to it.
I noticed that exactly same bug happens if I enable promisc mode on the=
=20
wlan0. Does this give any additional clue why this bug happens?

Best regards,
	Maxim levitsky
--
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

  parent reply	other threads:[~2008-07-09 16:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-23  9:10 [BUG] Two bugs in monitor mode, iwl3945 Maxim Levitsky
2008-06-23 12:53 ` Stefanik Gábor
2008-06-23 13:58   ` Maxim Levitsky
2008-07-09 16:25 ` Maxim Levitsky [this message]
2008-07-09 17:04   ` [ipw3945-devel] " Dan Halperin

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=4874E68F.7090106@gmail.com \
    --to=maximlevitsky@gmail.com \
    --cc=ipw3945-devel@lists.sourceforge.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netrolller.3d@gmail.com \
    --cc=yi.zhu@intel.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).