ScanFlags | netlink

scan request control flags

Scan request control flags are used to control the handling of NL80211_CMD_TRIGGER_SCAN and NL80211_CMD_START_SCHED_SCAN requests.

NL80211_SCAN_FLAG_LOW_SPAN, NL80211_SCAN_FLAG_LOW_POWER, and NL80211_SCAN_FLAG_HIGH_ACCURACY flags are exclusive of each other, i.e., only one of them can be used in the request.

Hierarchy

ScanFlags

Index

Properties

Optional __unknown

__unknown?: number

Optional acceptBcastProbeResp

acceptBcastProbeResp?: true

accept broadcast probe responses

Optional ap

ap?: true

force a scan even if the interface is configured as AP and the beaconing has already been configured. This attribute is dangerous because will destroy stations performance as a lot of frames will be lost while scanning off-channel, therefore it must be used only when really needed

Optional filsMaxChannelTime

filsMaxChannelTime?: true

fill the dwell time in the FILS request parameters IE in the probe request

Optional flush

flush?: true

flush cache before scanning

Optional highAccuracy

highAccuracy?: true

Accuracy here intends to the extent of scan results obtained. Thus HIGH_ACCURACY scan flag aims to get maximum possible scan results. This flag hints the driver to use the best possible scan configuration to improve the accuracy in scanning. Latency and power use may get impacted with this flag.

Optional lowPower

lowPower?: true

This flag intends the scan attempts to consume optimal possible power. Drivers can resort to their specific means to optimize the power. Scan accuracy may get impacted with this flag.

Optional lowPriority

lowPriority?: true

scan request has low priority

Optional lowSpan

lowSpan?: true

Span corresponds to the total time taken to accomplish the scan. Thus, this flag intends the driver to perform the scan request with lesser span/duration. It is specific to the driver implementations on how this is accomplished. Scan accuracy may get impacted with this flag.

Optional minPreqContent

minPreqContent?: true

minimize probe request content to only have supported rates and no additional capabilities (unless added by userspace explicitly.)

Optional oceProbeReqDeferralSuppression

oceProbeReqDeferralSuppression?: true

allow probe request tx deferral (dot11FILSProbeDelay shall be set to 15ms) and suppression (if it has received a broadcast Probe Response frame, Beacon frame or FILS Discovery frame from an AP that the STA considers a suitable candidate for (re-)association - suitable in terms of SSID and/or RSSI.

Optional oceProbeReqHighTxRate

oceProbeReqHighTxRate?: true

send probe request frames at rate of at least 5.5M. In case non OCE AP is discovered in the channel, only the first probe req in the channel will be sent in high rate.

Optional randomAddr

randomAddr?: true

use a random MAC address for this scan (or for scheduled scan: a different one for every scan iteration). When the flag is set, depending on device capabilities the @NL80211_ATTR_MAC and

nl80211_attr_mac_mask: attributes may also be given in which case only the masked bits will be preserved from the MAC address and the remainder randomised. If the attributes are not given full randomisation (46 bits, locally administered 1, multicast 0) is assumed. This flag must not be requested when the feature isn't supported, check the nl80211 feature flags for the device.

Optional randomSn

randomSn?: true

randomize the sequence number in probe request frames from this scan to avoid correlation/tracking being possible.