linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Holger Schurig <hs4233@mail.mn-solutions.de>,
	libertas-dev@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] libertas: monitor mode support for OLPC
Date: Tue, 10 Jul 2007 10:54:02 -0400	[thread overview]
Message-ID: <20070710145402.GA7927@tuxdriver.com> (raw)
In-Reply-To: <1183720126.3818.122.camel@johannes.berg>

On Fri, Jul 06, 2007 at 01:08:46PM +0200, Johannes Berg wrote:
> Javier, Holger,
> 
> > Why not do it this way:
> > 
> > "iwmode eth1 mode monitor" turn's the device into monitor mode. 
> > That's what by far the most drivers use. In this mode, the 
> > device will send all frames to the host, e.g. all beacon frames. 
> > After all, user space can filter:
> > 
> >   tshark -i rtap0 -R '!(wlan.fc.subtype == 8)'
> 
> I suppose you really should be using cfg80211 to create and change the
> mode of new interfaces (and allow only one monitor and/or one STA
> interface). Then you actually get a sysfs file for free, and as a bonus
> it's the same one mac80211 uses :)

ACK

-- 
John W. Linville
linville@tuxdriver.com

      reply	other threads:[~2007-07-10 15:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <468c3f32.081b600a.3817.5051@mx.google.com>
     [not found] ` <200707050842.01533.hs4233@mail.mn-solutions.de>
     [not found]   ` <8e8340660707051037p56e10ec7u3aa4d76893e0b1ed@mail.gmail.com>
2007-07-06  7:22     ` [PATCH] libertas: monitor mode support for OLPC Holger Schurig
2007-07-06  8:18       ` Holger Schurig
2007-07-06 11:08       ` Johannes Berg
2007-07-10 14:54         ` John W. Linville [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=20070710145402.GA7927@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=hs4233@mail.mn-solutions.de \
    --cc=johannes@sipsolutions.net \
    --cc=libertas-dev@lists.infradead.org \
    --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).