linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Jouni Malinen <j@w1.fi>
Cc: linux-wireless@vger.kernel.org
Subject: [RFC/RFT 0/2] userspace station-mode action frame handling
Date: Sun, 17 Jan 2010 15:49:18 +0100	[thread overview]
Message-ID: <20100117144918.773071520@sipsolutions.net> (raw)

Jouni, all,

These two patches now implement returning unknown
action frames and registering for certain action
frames from userspace, as well as sending as before.

A few design decisions:
 * AP mode is unchanged, hostapd is responsible for
   returning unknown action frames (cooked monitor).
 * Registration/transmission works only in station
   mode (would be easy to change in the future).
 * Registration needs to specify which frames to receive
   by providing a frame match buffer, which matches
   the first few bytes of the frame, so for instance
   the buffer [0x04] would register for all public
   action frames, and [0x7f, 0x00, 0x02, 0xb3] would
   register for certain Intel vendor action frames.
 * Action frames that are registered for are unicast
   to the socket that registered for it.
 * If userspace wants to know about returned action
   frames for ones it sent, it needs to register
   for them specifically, for my example above it
   would be [0xff, 0x00, 0x02, 0xb3].

johannes


             reply	other threads:[~2010-01-17 15:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-17 14:49 Johannes Berg [this message]
2010-01-17 14:49 ` [RFC/RFT 1/2] mac80211: reject unhandled action frames Johannes Berg
2010-01-17 14:49 ` [RFC/RFT 2/2] cfg80211/mac80211: allow registering for and sending " Johannes Berg
2010-02-15  8:16 ` [RFC/RFT 0/2] userspace station-mode action frame handling Jouni Malinen
2010-02-15  9:40   ` 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=20100117144918.773071520@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=j@w1.fi \
    --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).