From: Andy Green <andy@warmcat.com>
To: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] zd1211rw-mac80211: debug output for mac80211 ops
Date: Tue, 31 Jul 2007 00:25:21 +0100 [thread overview]
Message-ID: <46AE7361.90406@warmcat.com> (raw)
In-Reply-To: <200707310105.55863.mb@bu3sch.de>
Somebody in the thread at some point said:
> On Tuesday 31 July 2007, Ulrich Kunitz wrote:
>> What about add_interface/remove_interfaces and monitor interfaces?
>>
>> There seems to be difference between "hard" and "soft" monitor
>> mode. Currently I'm not sure what the semantics is. There seems to
>> be also calls to add_interface/remote_interface with if_id -1. I
>> guess that means something like all interfaces. The expected
>> behaviour is not documented for that case.
> I don't know what you mean by hard/soft monitor.
Currently there are two distinct kinds of "monitor mode" result returned
by zd1211rw-mac80211 and iwl3945 at least.
The "hard" one to use Ulrich's name is what you want to see with Monitor
mode, the physical device is in hardware promisc and you see all kinds
of beacons and foreign network encrypted packets.
The "soft" one is a faked up repeating of incoming (and outgoing!
twice!) packets that happen to be around during the filtered operation
of the device, in the case where the device operates as Managed and is
not in hardware promisc. In this mode, you see only your associated
station beacons and your own packets, not even packets from other
stations on your AP.
You get "hard" monitoring when you have only one virtual interface and
it is in monitor mode. You get "soft" bogus monitoring when your
monitor mode interface is a second virtual one.
I posted a few times about this last week giving details of what you get
under what circumstances. It really would be much better if the device
is kicked to hardware promisc if ANY virtual interface is in Monitor
mode, therefore the results are consistent regardless of the number of
virtual interfaces that happen to be around.
-Andy
next prev parent reply other threads:[~2007-07-30 23:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070730023128.99E927B409F@zog.reactivated.net>
2007-07-30 3:21 ` [PATCH] zd1211rw-mac80211: debug output for mac80211 ops Michael Wu
2007-07-30 14:51 ` John W. Linville
2007-07-30 22:52 ` Ulrich Kunitz
2007-07-30 23:05 ` Michael Buesch
2007-07-30 23:25 ` Andy Green [this message]
2007-07-31 21:12 ` Jiri Benc
2007-07-31 21:30 ` Michael Buesch
2007-07-31 21:42 ` Andy Green
2007-07-31 21:50 ` Andy Green
2007-07-31 5:22 ` Michael Wu
2007-07-31 9:39 ` Michael Buesch
2007-07-31 21:06 ` Jiri Benc
2007-07-31 21:39 ` Michael Buesch
2007-07-31 5:06 ` Michael Wu
2007-07-31 21:00 ` Jiri Benc
2007-07-31 21:37 ` Michael Buesch
2007-07-31 22:10 ` Jiri Benc
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=46AE7361.90406@warmcat.com \
--to=andy@warmcat.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 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).