Network Disassociation

After it is associated, the 802.11 device can disassociate through one of the following:

  • Implicit disassociation
    The device has lost contact with the access point (AP) and cannot roam to another BSSID in the SSID.

  • Explicit disassociation
    An explicit disassociation can be triggered through one of the following:

When the device disassociates, the driver must make a media disconnect indication. When making this indication, the miniport driver must follow the rules discussed in Media Status Indications for 802.11 Networks.

Note   Under certain conditions, the driver must not make a media disconnect indication when either the desired SSID or BSSID are changed. For more information about these conditions, see Media Status Indications for 802.11 Networks.

 

After it makes the media disconnect indication, the driver must do the following:

  • The driver must clear any keys for all cipher suites enabled on the device. These keys are set through OID_802_11_ADD_WEP or OID_802_11_ADD_KEY.

  • The driver must clear its PMK cache. The PMK cache is set through OID_802_11_PMKID.

  • If media streaming was enabled, then the driver must disable media streaming and set its streaming mode to Ndis802_11MediaStreamOff.

  • The driver must clear the DecryptSuccessCount and DecryptFailureCount counters from the NDIS_802_11_STATISTICS structure. For more information about these statistical counters, see OID_802_11_STATISTICS.

 

 

Send comments about this topic to Microsoft