userspace station-mode action frame handling
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 2 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | mac80211: reject unhandled action framesnet/ | +57 | 0 replies | |
| 2/2 | cfg80211/mac80211: allow registering for and sending action framesinclude/ include/ include/ +10 more | +623 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC/RFT 0/2] userspace station-mode action frame handling
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