NDIS_STATUS_DOT11_ASSOCIATION_COMPLETION

Important  The Native 802.11 Wireless LAN interface is deprecated in Windows 10 and later. Please use the WLAN Device Driver Interface (WDI) instead. For more information about WDI, see WLAN Universal Windows driver model.
 

A miniport driver must make an NDIS_STATUS_DOT11_ASSOCIATION_COMPLETION indication after an association operation completes.

The miniport driver indicates the start of the association operation through the NDIS_STATUS_DOT11_ASSOCIATION_START indication. Every NDIS_STATUS_DOT11_ASSOCIATION_START indication made by the driver must have a corresponding NDIS_STATUS_DOT11_ASSOCIATION_COMPLETION indication.

For more information about this association operation, see Association Operations.

The data type for this indication is the DOT11_ASSOCIATION_COMPLETION_PARAMETERS structure.

The miniport driver calls NdisMIndicateStatusEx to make an NDIS_STATUS_DOT11_ASSOCIATION_COMPLETION indication, and must pass a pointer to an NDIS_STATUS_INDICATION structure through the StatusIndication parameter. When making this indication, the driver must set the following members of the NDIS_STATUS_INDICATION structure:

  • StatusCode must be set to NDIS_STATUS_DOT11_ASSOCIATION_COMPLETION.

  • StatusBuffer must be set to the address of a DOT11_ASSOCIATION_COMPLETION_PARAMETERS structure.

  • StatusBufferSize must be set to sizeof(DOT11_ASSOCIATION_COMPLETION_PARAMETERS).

After the miniport driver makes the NDIS_STATUS_DOT11_ASSOCIATION_COMPLETION indication with the uStatus member set to DOT11_ASSOCIATION_STATUS_SUCCESS, the miniport driver must do the following:

  • Be prepared to send and receive packets. If the 802.11 station performed the association operation within the context of either a connection or roaming operation, the miniport driver must be able to send or receive packets before it makes the NDIS_STATUS_DOT11_CONNECTION_COMPLETION or NDIS_STATUS_DOT11_ROAMING_COMPLETION indications.

  • Add an entry for the current association into its association information list. If the IEEE 802.11 dot11DesiredBSSType MIB object is set to dot11_BSS_type_infrastructure, the miniport driver must remove the entry for the previous association from its association information list.

    For more information about the association information list, see OID_DOT11_ENUM_ASSOCIATION_INFO.

  • Initialize the authentication algorithm (which is specified by the AuthAlgo member) and cipher algorithms (which are specified by the UnicastCipher and MulticastCipher members) for the association.

  • Delete all non-static default cipher keys. Non-static default cipher keys are created with the bStatic member of the DOT11_CIPHER_DEFAULT_KEY_VALUE structure set to FALSE. For more information about this structure, see OID_DOT11_CIPHER_DEFAULT_KEY.

  • Delete any non-static key-mapping keys for the AP or peer station identified by the MacAddr member. Non-static key-mapping keys are created with the bStatic member of the DOT11_CIPHER_KEY_MAPPING_KEY_VALUE structure set to FALSE. For more information about this structure, see OID_DOT11_CIPHER_KEY_MAPPING_KEY.

For more information about the IEEE 802.11 dot11DesiredBSSType MIB object, see OID_DOT11_DESIRED_BSS_TYPE

Requirements

Version

Available in Windows Vista and later versions of the Windows operating systemss.

Header

Windot11.h (include Ndis.h)

 

 

Send comments about this topic to Microsoft

Show: