First of all, this library is designed to be easily extendable. \
There's an architectural/contribution guide in docs/Frame.md and pull requests are highly welcome.
Covering the whole spectrum of possible 802.11 frames or all different implementations of wifi tools out there is an impossible task for a single person, let's try to tackle this together!
The first goal of libwifi is to provide a convenient way of parsing raw IEEE 802.11 frames!
The emphasis is on convenient, since this library doesn't focus on providing a super high-performance implementation. The focus is rather on providing an easy-to-use API. \ This includes consistent and intuitive structs representing the structure of a given frame. \ However, this doesn't mean that this library isn't quite fast anyway ;).
The second goal is to provide an unified API to: 1. query information about your wifi interfaces (iwlist equivalent). 2. set attributes and configure your wifi interfaces (iwconfig equivalent).
As a prototype it's planned to call and parse existing binaries. However, a native re-implementation of those tools is desired in a long-term manner. \ For instance, the wireless-tools are a great C-library with a lot of documentation and very will structured code. This could be used as a guide-line for re-implementation.
Parsing a frame is fairly straight forward:
``` use libwifi::parse;
let bytes = [ 180, 0, // FrameControl 158, 0, // Duration 116, 66, 127, 77, 29, 45, // First Address 20, 125, 218, 170, 84, 81, // Second Address ];
match libwifi::parse(&bytes) { Ok(frame) => { println!("Got frame: {:?}", frame); } Err(err) => { println!("Error during parsing :\n{}", err); } }; ```
A full example on how to capture, process and parse wifi traffic can be found in the examples directory.
Parser and Frames
StationInfo struct.Interface handling
I would love to add proper interface handling to the library. This includes features to:
This library requires nightly for now!
It uses the destructuring_assignment feature, which adds a lot of convenience when working with the nom library. \
If you want to start using it in a professional environment, I'm open to PRs that refactor the usages of this feature. Shouldn't take longer than a few minutes to do. \ Until then, I'm hoping that this feature will be included to stable soon :).