fuchsia.wlan.fullmac

SUCCESS

TRANSMISSION_FAILURE

SUCCESS

BSS_ALREADY_STARTED_OR_JOINED

RESET_REQUIRED_BEFORE_START

NOT_SUPPORTED

SUCCESS

BSS_ALREADY_STOPPED

INTERNAL_ERROR

SUCCESS

REFUSED_REASON_UNSPECIFIED

REFUSED_NOT_AUTHENTICATED

REFUSED_CAPABILITIES_MISMATCH

REFUSED_EXTERNAL_REASON

REFUSED_AP_OUT_OF_MEMORY

REFUSED_BASIC_RATES_MISMATCH

REJECTED_EMERGENCY_SERVICES_NOT_SUPPORTED

REFUSED_TEMPORARILY

SUCCESS

REFUSED

ANTI_CLOGGING_TOKEN_REQUIRED

FINITE_CYCLIC_GROUP_NOT_SUPPORTED

REJECTED

FAILURE_TIMEOUT

OPEN_SYSTEM

SHARED_KEY

FAST_BSS_TRANSITION

SAE

SUCCESS

NOT_SUPPORTED

INVALID_ARGS

INTERNAL_ERROR

SHOULD_WAIT

CANCELED_BY_DRIVER_OR_FIRMWARE

ACTIVE

PASSIVE

1

The values of this table apply to the band indicated in this field.

Required.

2

Basic rates supported in units of 500 kbit/s (as defined in IEEE Std 802.11-2016, 9.4.2.3), e.g., 0x02 represents 1 Mbps. The value returned by this type indicates all the non-HT rates the device supports transmitting and receiving.

Required.

3

HT PHY mode capabilities.

Optional. If this field is not present, then the device does not support HT PHY mode in this band.

4

VHT PHY mode capabilities.

Optional. If this field is not present, then the device does not support VHT PHY mode in this band.

5

A list of operating channels considered valid by hardware, in the context of regulatory information known to the device driver, at the time of its construction during iface creation. In this context, an operating channel means a channel which APs may transmit Beacon frames on in the current regulatory domain.

This list should be used to determine efficacy of subsequent requests to scan a subset of channels using the iface, or to determine which operating channel to use when starting an AP.

Required.

1

The peer's MAC address. Required.

2

The status code for this SAE frame. Required.

3

The sequence number. Required.

4

Contains fields in the frame body relevant to SAE. See IEEE Std 802.11-2016 table 9-35 and table 9-36 for more details. Required.

1

2

3

1

2

1

2

Timeout specified in beacon interval.

3

Additional parameters specific to the authentication exchange.

4

sae_password is ignored except when SAE_DRIVER_AUTH is enabled and the auth_type is SAE.

5

WEP key used in the authentication exchange. This is only populated for the WEP security type, otherwise this field is empty.

6

Additional parameters specific to the association exchange.

7

WEP key used in the authentication exchange. This is only populated for the WEP security type, otherwise this field is empty.

1

2

1

2

1

2

3

1

2

3

4

5

1

2

1

2

3

4

1

1

MAC address of the peer. Required.

2

Reason code for deauthentication. Required.

3

locally_initiated is true if deauth is initiated from the device, and is false if it's initiated remotely (e.g. due to deauth frame)

1

ZX_OK indicates that the disassociate request was serviced and the peer was disassociated. Other errors indicate that the request could not be serviced, for these or other reasons:

• ZX_ERR_BAD_STATE: association not possible in current state (e.g. disconnected)
• ZX_ERR_INVALID_ARGS: no association exists with specified peer
• ZX_ERR_SHOULD_WAIT: disassociate request could not be serviced because firmware or driver was busy

1

Address of the peer that was disassociated. Required.

2

Reason for the disassociation. Required.

3

Whether the disassociation was initiated from the device. Required. locally_initiated is true if disassociation was initiated from the device (e.g. firmware or vendor driver started the disassociation); false if the disassociation was initiated externally (e.g. due to receipt of a disassociate frame from an AP).

1

The result of the transmission. Required.

2

This value corresponds to the dst_addr in the EapolTxRequest we're confirming. IEEE 802.11-2020 does not include this field, but we need it to disambiguate if multiple EAPoL handshakes are ongoing. Required.

1

The address of the sender. Required.

2

The address of the intended destination. Required.

3

The bytes of the EAPoL frame data. Required.

1

The pairwise master key bytes. Required.

2

The PMK IDs. Required.

1

2

1

2

3

1

BSSID of the target BSS. Required.

2

Result of the roam attempt. Required.

3

Whether the original BSS association has been maintained through the roam attempt. Required. A successful roam always incurs disassociation from the original BSS, so if status_code is success then this field must be set to false; a roam failure typically incurs disassociation from the original BSS, but may not in some cases (e.g. in some Fast BSS Transition scenarios).

4

Whether the client is authenticated with the target BSS. If status_code is success, then this field must be set to true; if the roam attempt failed, this field may be true or false. This allows higher layers to decide how to clean up connection state after a failed roam attempt.

5

Association ID for this association with the AP. Required if status_code is success.

6

IEs for this association with the AP. Required if status_code is success.

1

BSSID of the target BSS. Required.

2

Result of the roam attempt. Required.

3

Whether the original BSS association has been maintained through the roam attempt. Required. A successful roam always incurs disassociation from the original BSS, so if status_code is success then this field must be set to false; a roam failure typically incurs disassociation from the original BSS, but may not in some cases (e.g. in some Fast BSS Transition scenarios).

4

Whether the client is authenticated with the target BSS. If status_code is success, then this field must be set to true; if the roam attempt failed, this field may be true or false. This allows higher layers to decide how to clean up connection state after a failed roam attempt.

5

Association ID for this association with the AP. Required if status_code is success.

6

IEs for this association with the AP. Required if status_code is success.

1

BSSID of the target BSS. Required.

2

Full BSS description of the target BSS. Required. If the data in BssDescription is incorrect or incomplete, the roam cannot succeed, because higher layers will not be able to complete required actions (e.g. SAE).

3

Whether the original BSS association has been maintained at the start of a roam attempt. Required. 802.11 dictates that a STA can only be associated with a single BSS, so a roam attempt typically incurs disassociation at the start of the roam attempt. However, 802.11 also provides a mechanism (i.e. Fast BSS Transition) that allows a device to maintain association with the original BSS while establishing authentication with the target BSS, in order to avoid losing the original association if authentication with the target BSS fails.

1

1

The result of the StartBss request. Required.

1

The result of the StopBss request. Required.

1

The WlanFullmacImplifc client end. Required.

1

1

1

Full BSS description of the target BSS. Required. If the data in BssDescription is incorrect or incomplete, the roam cannot succeed, because higher layers will not be able to complete required actions (e.g. SAE).

1

The peer's MAC address. Required.

2

The status of the SAE handshake. Required.

1

2

1

2

3

4

5

6

7

1

Unique transaction id (will be indicated in corresponding scan results).

2

3

List of channels to scan on. An empty list of channels will cause a scan request to immediately return a OnScanEnd with code INVALID_ARGS.

Invalid channel numbers will be silently ignored. The validity of a channel number depends on the current regulatory region, and a FullMAC driver cannot always determine the region setting. This is especially the case when firmware changes the region setting dynamically.

4

List of SSIDs to scan for. An empty list of ssids is the same as specifying a list containing only the wildcard SSID.

There is no limit on the number of SSIDs specified. A large number of SSIDs may result in extended scan times because of hardware limitations on the number of SSIDs permitted per scan request and the technical limitation in IEEE 802.11-2016 that limits the number of SSIDs in a single Probe Request frame to ieee80211.SSID_LIST_MAX SSIDs.

5

Minimum amount of time in msecs spent on a channel during scan.

6

Maximum amount of time in msecs spent on a channel during scan.

1

1

The SME server end channel. Required.

1

Station address. Required.

2

MAC role. Required.

3

Supported bands. Required.

1

2

1

2

1

2

1

2

1

2

1

2

1

2

1

2

Max length for vendor IEs to be added to the association request. This is currently used for WPA.