|
wpa_supplicant / hostapd
2.5
|
|
wpa_supplicant / hostapd
2.5
|
Scan result for an BSS/IBSS. More...
#include <driver.h>
Scan result for an BSS/IBSS.
| flags | information flags about the BSS/IBSS (WPA_SCAN_*) |
| bssid | BSSID |
| freq | frequency of the channel in MHz (e.g., 2412 = channel 1) |
| beacon_int | beacon interval in TUs (host byte order) |
| caps | capability information field in host byte order |
| qual | signal quality |
| noise | noise level |
| level | signal level |
| tsf | Timestamp |
| age | Age of the information in milliseconds (i.e., how many milliseconds ago the last Beacon or Probe Response frame was received) |
| est_throughput | Estimated throughput in kbps (this is calculated during scan result processing if left zero by the driver wrapper) |
| snr | Signal-to-noise ratio in dB (calculated during scan result processing) |
| ie_len | length of the following IE field in octets |
| beacon_ie_len | length of the following Beacon IE field in octets |
This structure is used as a generic format for scan results from the driver. Each driver interface implementation is responsible for converting the driver or OS specific scan results into this format.
If the driver does not support reporting all IEs, the IE data structure is constructed of the IEs that are available. This field will also need to include SSID in IE format. All drivers are encouraged to be extended to report all IEs to make it easier to support future additions.
This structure data is followed by ie_len octets of IEs from Probe Response frame (or if the driver does not indicate source of IEs, these may also be from Beacon frame). After the first set of IEs, another set of IEs may follow (with beacon_ie_len octets of data) if the driver provides both IE sets.
1.8.6
