radiotap.netbsd.org archive mirror
 help / color / mirror / Atom feed
From: Andy Green <andy-/Zus8d0mwwtBDgjK7y7TUQ@public.gmane.org>
To: Sam Leffler <sam-zZXckVAlHaQAvxtiuMwx3w@public.gmane.org>
Cc: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>,
	radiotap-eZodSLrBbDpBDgjK7y7TUQ@public.gmane.org,
	linux-wireless
	<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: radiotap for TX
Date: Thu, 21 Jun 2007 22:12:56 +0100	[thread overview]
Message-ID: <467AE9D8.2030602__48728.9385324859$1216696516$gmane$org@warmcat.com> (raw)
In-Reply-To: <467AE460.1070606-zZXckVAlHaQAvxtiuMwx3w@public.gmane.org>

Sam Leffler wrote:

> Note that using a monitor mode interface for transmit is a bad idea.  It
> is likely you will encounter devices that disallow any packet transmit
> when operating in monitor mode.  In practice this can be worked around
> by using a non-monitor operating mode for the device (e.g. adhoc mode
> w/o setting up beacons) but exporting this notion to user mode is bad
> IMO.  In net80211 there is an adhoc-demo mode which is essentially adhoc
> mode which was originally added for functionality found in old lucent
> cards but more recently has been used for building applications that
> want a "raw 802.11 device".

Hi -

In mac80211 you can run multiple network interfaces off the one physical
device, so you can have an associated WPA connection on one network
interface and another logical "monitor mode" network interface up on the
one physical device.  "Monitor mode" in this case can be the results of
a promiscuous hardware RX that is filtered for the Managed mode logical
interface ... this is AIUI.  So in that way "Monitor Mode" no longer
means a single modal device setting, but really the delivery somehow of
packets to a logical network interface that belongs to the physical device.

Injecting down a "monitor mode interface" then only means to use a
logical network interface that locally is configured to "Monitor Mode",
it doesn't have the same definite implication for physical device
configuration as before mac80211.  (Well.. AIUI).  So hopefully this
objection may not apply.

-Andy

  parent reply	other threads:[~2007-06-21 21:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1182375853.3714.103.camel@johannes.berg>
     [not found] ` <1182375853.3714.103.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
2007-06-21 17:55   ` radiotap for TX David Young
2007-06-21 20:49   ` Sam Leffler
     [not found] ` <20070621175541.GQ19613@che.ojctech.com>
     [not found]   ` <20070621175541.GQ19613-eZ+MEZF6i8Dc+919tysfdA@public.gmane.org>
2007-06-25  6:39     ` Johannes Berg
     [not found] ` <467AE460.1070606@errno.com>
     [not found]   ` <467AE460.1070606-zZXckVAlHaQAvxtiuMwx3w@public.gmane.org>
2007-06-21 21:12     ` Andy Green [this message]
2007-06-25  7:24     ` Johannes Berg
2007-06-20 21:44 Johannes Berg

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='467AE9D8.2030602__48728.9385324859$1216696516$gmane$org@warmcat.com' \
    --to=andy-/zus8d0mwwtbdgjk7y7tuq@public.gmane.org \
    --cc=johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org \
    --cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=radiotap-eZodSLrBbDpBDgjK7y7TUQ@public.gmane.org \
    --cc=sam-zZXckVAlHaQAvxtiuMwx3w@public.gmane.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).