diff options
| author | Marc <marc@malloc.me> | 2022-09-10 20:18:18 +0100 |
|---|---|---|
| committer | Marc <marc@malloc.me> | 2022-09-10 20:18:18 +0100 |
| commit | 7c2b373bf37186fd94fdc1d46393780e46f646a8 (patch) | |
| tree | c424e584658ee3fdcf0f0c0d3466f2906681577b /AUTHORS | |
| parent | 18b3f897df1d17e9d140fb24b7bad4bdd2b849f1 (diff) | |
| download | libwifi-7c2b373bf37186fd94fdc1d46393780e46f646a8.tar.gz libwifi-7c2b373bf37186fd94fdc1d46393780e46f646a8.tar.bz2 libwifi-7c2b373bf37186fd94fdc1d46393780e46f646a8.zip | |
core/parse: Better handling of Radiotap information
Radiotap information is now stored in the `libwifi_frame` struct, and will
be kept automatically in `libwifi_frame.radiotap_info` for the lifecycle of
said frame, if it is present.
A new flag has been added for the frame for use with `libwifi_frame.flags`
to detect if the radiotap info is present: `LIBWIFI_FLAGS_RADIOTAP_PRESENT`.
The frame parser will now automatically calculate the band and center channel
from radiotap data, and will store them in `libwifi_radiotap_info.channel.center`
and `libwifi_radiotap_info.channel.band`.
Four new flags have been added for use with the new radiotap band field:
- `LIBWIFI_RADIOTAP_BAND_2GHZ`
- `LIBWIFI_RADIOTAP_BAND_5GHZ`
- `LIBWIFI_RADIOTAP_BAND_6GHZ`
- `LIBWIFI_RADIOTAP_BAND_900MHZ`
These can be used with a binary AND:
`if (rtap.channel.band & LIBWIFI_RADIOTAP_BAND_6GHZ) { }`
Diffstat (limited to 'AUTHORS')
0 files changed, 0 insertions, 0 deletions