From: Mark Wells (mark_at_pc-intouch.com)
Date: 2002-04-06 21:35:29 UTC
On Sat, 6 Apr 2002, Jouni Malinen wrote:
> Yes, user space programs would send (and receive) raw 802.11
> frames. This wlan0ap interface with ARPHRD_IEEE80211 type looked like
> best option I implemented it into the driver and a separate user space
> daemon. I'm using raw packet sockets in the daemon to receive and send
> send full 802.11 headers. The kernel driver just passes all management
> frames to wlan0ap interface with full headers. The daemon parses the
> messages and generates replies with full headers. The driver then just
> adds missing Prism2 TX frame fields and sends the frames without other
Just to clarify, is the wlan0ap interface suitable for normal traffic?
> My current work version is able to pass the management frames in both
> directions and the user space daemon knows how to handle
> authentication and association frames. I have not yet implemented
> control ioctls for the daemon to add/remove station data from the
> kernel driver.
I don't know if that's necessary. The management frames themselves could serve this purpose (though this may be contrary to your goal of not having to parse management frames through the driver). Is there any case in which the driver should add a station even though the daemon hasn't sent an association response for that station, or vice versa?