A miniport driver must make an NDIS_STATUS_DOT11_INCOMING_ASSOC_STARTED status indication when the NIC receives the first valid 802.11 authentication request from a peer station on an infrastructure BSS.
A miniport driver can also make this indication when it receives a valid re-association request packet from a peer station that is in an authenticated (class 2) state.
The data type for this indication is the DOT11_INCOMING_ASSOC_STARTED_PARAMETERS structure.
The miniport driver must not make this indication when the received association request is not valid, or if the peer station's association state is not valid.
This indication marks the beginning of an association indication block, which denotes the time between NDIS_STATUS_DOT11_INCOMING_ASSOC_STARTED and NDIS_STATUS_DOT11_INCOMING_ASSOC_COMPLETION indications when a NIC is operating in ExtAP OP mode. Every NDIS_STATUS_DOT11_INCOMING_ASSOC_STARTED indication made by the driver must have a corresponding NDIS_STATUS_DOT11_INCOMING_ASSOC_COMPLETION indication.
A peer station cannot have multiple overlapping incoming association indication blocks. Incoming association indication blocks for different peer stations can overlap.
The miniport driver calls NdisMIndicateStatusEx to make an NDIS_STATUS_DOT11_INCOMING_ASSOC_STARTED indication, and must pass a pointer to an NDIS_STATUS_INDICATION structure through the StatusIndication parameter. When the driver makes this indication, it must set the following members of the NDIS_STATUS_INDICATION structure:
StatusCode must be set to NDIS_STATUS_DOT11_INCOMING_ASSOC_STARTED.
StatusBuffer must be set to the address of a DOT11_INCOMING_ASSOC_STARTED_PARAMETERS structure.
StatusBufferSize must be set to sizeof(DOT11_INCOMING_ASSOC_STARTED_PARAMETERS).
|Available in Windows 7 and later versions of the Windows operating systems.|
Build date: 5/21/2013