linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: andy@warmcat.com
To: linux-wireless@vger.kernel.org
Subject: [PATCH 0/7] Try #8: Radiotap on Monitor Mode interfaces for rx and tx
Date: Mon, 09 Apr 2007 16:48:02 +0100	[thread overview]
Message-ID: <20070409154802.470925215@warmcat.com> (raw)

Hi folks -

This set of patches change the Monitor Mode wireless interfaces to use radiotap
both for monitoring and for packet injection.  The monitoring side is done by a patch
from Michael Wu.  For example, tcpdump can handle the resulting radiotap packets.

For injecting packets, you issue a packet using libpcap or a SOCK_PACKET
socket down an interface to the wireless device that is in Monitor Mode.  
The packet has a normal radiotap header prepended to the IEEE80211 header.
The radiotap header is variable length depending on what the user wants to 
specify: currently the transmit rate, power and antenna are interpreted,
and any other entries are skipped.

The radiotap parser is broken out into its own file under cfg80211.

A usermode app packetspammer is available from here

http://penumbra.warmcat.com/_twk/tiki-index.php?page=packetspammer

which allows easy injection of these packets from the commandline.  At the moment it
loops issuing packets at a variety of rates which can be seen from another
machine's monitor mode interface on the same channel.  There are instructions for
build and using it on the page above.

Currently it has been tested for both rx and tx using zd1211rw-mac80211.

The patches are based against this morning's wireless-dev.

I also added some documentation files which explains how to use the injection
functionality and radiotap header notes.

I have used the radiotap include patch from Michael Wu which basically syncs 
wireless-dev with the one in wireless-2.6, and his latest radiotap rx patch.

Michael Wu's rx patch exposed an issue with zd1211rw-mac80211 using its
hardware-dependent rx rate coding which differs from the coding used to
specify tx rates.  I therefore added a small broken-out patch in this set
which converts the reported rx rate from zd1211rw-mac80211 to use the
corresponding tx rate coding, so mac80211 can use the reported rate with
its rate tables (which use the hardware-specific tx rate coding) to find
the absolute bitrate and report that via radiotap.

-- 

             reply	other threads:[~2007-04-09 15:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-09 15:48 andy [this message]
2007-04-09 15:48 ` [PATCH 1/7] sync wireless-dev with radiotap header in wireless-2.6 andy
2007-04-09 15:48 ` [PATCH 2/7] mac80211: Add radiotap support andy
2007-04-09 15:48 ` [PATCH 3/7] mac80211: Monitor mode radiotap injection docs andy
2007-04-09 15:48 ` [PATCH 4/7] mac80211: Define present bitmap extend bit mask andy
2007-04-09 15:48 ` [PATCH 5/7] cfg80211: Radiotap parser andy
2007-04-09 15:48 ` [PATCH 6/7] mac80211: Monitor mode radiotap-based packet injection andy
2007-04-09 15:48 ` [PATCH 7/7] zd1211rw-mac80211: return hardware specific tx rate code for rx status andy

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=20070409154802.470925215@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).