From: Andy Green <andy@warmcat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: No echo TX pkt to Monitor interfaces for injection
Date: Fri, 03 Aug 2007 11:34:19 +0100 [thread overview]
Message-ID: <46B304AB.8060805@warmcat.com> (raw)
In-Reply-To: <1186136638.4647.32.camel@johannes.berg>
Somebody in the thread at some point said:
> On Fri, 2007-08-03 at 11:15 +0100, Andy Green wrote:
>
>> With the patch, injected packets have the same Monitor mode footprint
>> with hard or soft monitoring (you see the injected radiotap stuff)
>> because the synthesized "tx report" packet doesn't exist in the real
>> world shown by hard monitoring.
>
> I don't see why there's a distinction between hard and soft monitor
> mode. To me, hard monitor mode is basically "show me everything you can"
> while soft is "best effort". Soft monitor mode also makes no sense while
> no other interface is operating.
I also think it makes no sense to have a dependency on what Monitor mode
provides based on the other virtual interfaces, unless the hardware
cannot live up to the various demands at the same time. (What hardware
has this problem that it can't run a Managed interface with hardware
promisc Rx?)
> The synthesized 'tx report packet' isn't that; the only synthesized
> thing is the radiotap header, the rest of the packet is what we actually
> sent and were thus unable to capture ourselves.
Yes, that is true.
>> Acutually I think where it might all be heading is Michael Buesch's
>> method of selecting between hard and soft Monitor mode based on
>> IFF_PROMISC.
>
> Ah. I see. You're thinking of hard/soft monitor as something totally
> different than it is. Soft monitor really is only a hack for
> pseudo-softmac hardware that doesn't allow you to capture control
> packets while another interface is operating.
Well it has leaked out of that raison d'etre and oozed into being what
you get on any secondary virtual interface in Monitor mode.
Still I was suggesting maybe it does have another reason for existing,
the application of the usermode MLME might fit well with the filtered
aspect of it and the existing "TX report echos".
-Andy
next prev parent reply other threads:[~2007-08-03 10:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 22:38 [PATCH] mac80211: No echo TX pkt to Monitor interfaces for injection warmcat
2007-08-03 9:57 ` Johannes Berg
2007-08-03 10:15 ` Andy Green
2007-08-03 10:23 ` Johannes Berg
2007-08-03 10:34 ` Andy Green [this message]
2007-08-03 10:43 ` Johannes Berg
2007-08-06 19:33 ` Johannes Berg
2007-08-07 9:47 ` 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=46B304AB.8060805@warmcat.com \
--to=andy@warmcat.com \
--cc=johannes@sipsolutions.net \
--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).