From: Ivo van Doorn <ivdoorn@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH 18/24] rt2x00: Add Multicast/Broadcast filtering
Date: Fri, 3 Aug 2007 18:04:04 +0200 [thread overview]
Message-ID: <200708031804.04234.IvDoorn@gmail.com> (raw)
In-Reply-To: <1186155722.4647.55.camel@johannes.berg>
On Friday 03 August 2007, Johannes Berg wrote:
> On Fri, 2007-08-03 at 17:36 +0200, Ivo van Doorn wrote:
>
> > But that would mean that when a non-monitor and monitor interface are
> > enabled at the same time, the montitor interface is quite pointless since
> > all frames can be caught on the regular interface as well.
>
> Not true, monitor mode interfaces gives you a lot more info (radiotap.)
>
> > A monitor interface is supposed to catch as many frames as possible,
> > if a monitor interface does not catch frames not directly send to it, it won't
> > catch anything except beacons.
>
> Not if we want to use monitor interfaces for the userspace mlme.
>
> > Even when there is only 1 interface which is in monitor mode, the user shouldn't
> > have to set the device into promisc mode right?
>
> Actually, imho they should have to. And tcpdump always does anyway.
Well I hope so, otherwise I'll get quite a lot of bugreports. ;)
Next rt2x00 release will not treat monitor mode interfaces special.
Just read the http://www.linuxwireless.org/en/developers/mac80211/semantics article
So the next rt2x00 will comply with that.
Ivo
next prev parent reply other threads:[~2007-08-03 15:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 18:37 [PATCH 18/24] rt2x00: Add Multicast/Broadcast filtering Ivo van Doorn
2007-08-03 14:01 ` Johannes Berg
2007-08-03 15:09 ` Ivo van Doorn
2007-08-03 15:20 ` Johannes Berg
2007-08-03 15:36 ` Ivo van Doorn
2007-08-03 15:42 ` Johannes Berg
2007-08-03 16:04 ` Ivo van Doorn [this message]
2007-08-03 19:34 ` Johannes Berg
2007-08-03 20:11 ` Michael Buesch
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=200708031804.04234.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=johannes@sipsolutions.net \
--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 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.