linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: Ulrich Kunitz <kune@deine-taler.de>
Cc: Andy Green <andy@warmcat.com>, Daniel Drake <dsd@gentoo.org>,
	linux-wireless@vger.kernel.org,
	John Linville <linville@tuxdriver.com>
Subject: Re: Arrested Development
Date: Sun, 8 Jul 2007 20:18:22 +0200	[thread overview]
Message-ID: <200707082018.23045.mb@bu3sch.de> (raw)
In-Reply-To: <20070708181524.GA12389@deine-taler.de>

On Sunday 08 July 2007 20:15:24 Ulrich Kunitz wrote:
> On 07-07-08 17:22 Andy Green wrote:
> 
> > I rebooted into the new kernel and did this only
> > 
> > # iwconfig wlan0 mode monitor
> > # ifconfig wlan0 up
> > # iwconfig wlan0 channel 6
> > # tcpdump -i wlan0
> > 
> > But all I could see were beacons, this is despite I am ssh-d into that
> > box over the same channel 6 network with WPA and should surely be seeing
> > the encrypted packets?
> 
> I assume you were connected over a different interface. It appears
> that the code, which enables the reception of all packets hasn't
> been called or is wrong. Currently you will see only packets that
> are sent to the interface. Promiscous mode is also interesting,
> but shouldn't have any importance in monitor mode, which the
> iwconfig manual describes as passing all packets on the frequency.
> 
> > Then I decided to start wpa_supplicant (this
> > is an FC6 box so it was service wpa_supplicant start) and I got this oops:
> > 
> > ...
> > EIP is at zd_mac_config_interface+0xc/0x35 [zd1211rw_mac80211]
> > ...
> 
> I believe Jon Smirl reported the same bug. But I didn't quite
> understand how to provoke it.

I think it's the NULL pointer dereference of the mac address pointer,
if there's only a monitor interface. The address pointer can be NULL.

-- 
Greetings Michael.

  reply	other threads:[~2007-07-08 18:19 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-06  6:52 Arrested Development Andy Green
2007-07-06 11:07 ` Johannes Berg
2007-07-06 13:46 ` Daniel Drake
2007-07-06 13:50 ` Daniel Drake
2007-07-06 15:13   ` Andy Green
2007-07-08 14:00     ` Ulrich Kunitz
2007-07-08 16:22       ` Andy Green
2007-07-08 18:15         ` Ulrich Kunitz
2007-07-08 18:18           ` Michael Buesch [this message]
2007-07-08 18:29             ` Andy Green
2007-07-08 19:08             ` Johannes Berg
2007-07-09  0:40               ` Daniel Drake
2007-07-09  5:15                 ` Johannes Berg
2007-07-08 18:42         ` Jon Smirl
2007-07-08 18:46           ` Andy Green
2007-07-08 19:04             ` Jon Smirl
2007-07-08 19:17               ` Andy Green
2007-07-08 20:37                 ` Ulrich Kunitz
2007-07-08 21:23                   ` Johannes Berg
2007-07-08 21:46                     ` Andy Green
2007-07-08 22:38                       ` Ulrich Kunitz
2007-07-08 22:55                         ` Michael Buesch
2007-07-09  5:57                           ` Uli Kunitz
2007-07-09  5:29                         ` Andy Green
2007-07-08 22:44                     ` Michael Wu
2007-07-09  5:15                       ` Johannes Berg
2007-07-09  5:32       ` Andy Green

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=200707082018.23045.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=andy@warmcat.com \
    --cc=dsd@gentoo.org \
    --cc=kune@deine-taler.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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).