Partager via

OID_DOT11_MULTI_DOMAIN_CAPABILITY (Compact 2013)

  • Article

3/26/2014

When queried, this OID requests that the miniport driver return the list of supported regulatory domains associated with:

  • The value of the IEEE 802.11d dot11CountryString management information base (MIB) object. For more information about the dot11CountryString management information base (MIB) object, see OID_DOT11_COUNTRY_STRING.
  • The current PHY type on the 802.11 station

The data type for this OID is the DOT11_MD_CAPABILITY_ENTRY_LIST structure.

When OID_DOT11_MULTI_DOMAIN_CAPABILITY is queried, the miniport driver fails the query request if the following conditions are true:

  • If the dot11MultiDomainCapabilityImplemented MIB object is FALSE, the 802.11 station does not support multiple regulatory domains. In this situation, the miniport driver must return NDIS_STATUS_BAD_VERSION from its MiniportOidRequest function.
    For more information about the dot11MultiDomainCapabilityImplemented MIB object, see OID_DOT11_MULTI_DOMAIN_CAPABILITY_IMPLEMENTED.
  • If the dot11MultiDomainCapabilityEnabled MIB object is FALSE, the 802.11 station has not enabled the support for multiple regulatory domains. In this situation, the miniport driver must return NDIS_STATUS_INVALID_DATA from its MiniportOidRequest function.
  • If the 802.11 station has not completed an explicit scan initiated through a set of OID_DOT11_SCAN_REQUEST, the miniport driver must return NDIS_STATUS_MEDIA_IN_USE from its MiniportOidRequest function.

When OID_DOT11_MULTI_DOMAIN_CAPABILITY is queried, the miniport driver must verify that the InformationBuffer member of the MiniportOidRequest function’s OidRequest parameter is large enough to return the complete DOT11_MD_CAPABILITY_ENTRY_LIST structure, including all entries in the dot11MDCapabilityEntry array. The value of the InformationBufferLength member of the OidRequest parameter determines what the miniport driver must do, for example:

  • If the value of the InformationBufferLength member is less than the length, in bytes, of the complete DOT11_MD_CAPABILITY_ENTRY_LIST structure, the miniport driver must do the following:
    • For the OidRequest parameter, set the BytesWritten member to zero and the BytesNeeded member to the length, in bytes, of the DOT11_MD_CAPABILITY_ENTRY_LIST structure.
    • Fail the query request by returning NDIS_STATUS_BUFFER_OVERFLOW from its MiniportOidRequest function.
  • If the value of the InformationBufferLength member is greater than or equal to the length, in bytes, of the complete DOT11_MD_CAPABILITY_ENTRY_LIST structure, the miniport driver must do the following to complete a successful query request:
    • For the DOT11_MD_CAPABILITY_ENTRY_LIST structure, set the uNumOfEntries and uTotalNumOfEntries members to the total number of entries in the dot11MDCapabilityEntry array.
    • For the OidRequest parameter, set the BytesNeeded member to zero and the BytesWritten member to the length, in bytes, of the complete DOT11_MD_CAPABILITY_ENTRY_LIST structure. The miniport driver must also copy the complete DOT11_MD_CAPABILITY_ENTRY_LIST structure to the InformationBuffer member.
    • Return NDIS_STATUS_SUCCESS from its MiniportOidRequest function.

If the miniport driver is operating in Extensible Station (ExtSTA) mode, the current PHY type is determined through the ExtSTA msDot11CurrentPhyID MIB object. This MIB object specifies the index of the current PHY type within the 802.11 station’s list of supported PHY types. For more information about msDot11CurrentPhyID, see OID_DOT11_CURRENT_PHY_ID.

Requirements

Header

windot11.h

See Also

Reference

NDIS 5.x Legacy Wireless LAN OIDs
OID_DOT11_COUNTRY_STRING
DOT11_MD_CAPABILITY_ENTRY_LIST
MiniportOidRequest
OID_DOT11_MULTI_DOMAIN_CAPABILITY_IMPLEMENTED
OID_DOT11_SCAN_REQUEST
OID_DOT11_CURRENT_PHY_ID
OID_DOT11_MULTI_DOMAIN_CAPABILITY_ENABLED
Native 802.11 MIB OIDs
NDIS 5.x Legacy Reference