Compartilhar via

OID_DOT11_RANDOM_TABLE_FLAG (Compact 2013)

  • Artigo

3/26/2014

When queried, this OID requests that the miniport driver return the value of the IEEE 802.11d dot11RandomTableFlag MIB object for the current PHY type on the 802.11 station.

The dot11RandomTableFlag MIB object specifies whether the current PHY type uses hopping patterns from the Random Table field of the Hopping Pattern Table information element (IE). For more information about this IE, refer to Clause 7.3.2.14 of the IEEE 802.11d-2001 standard.

Note

Support for OID_DOT11_RANDOM_TABLE_FLAG is mandatory if the network adapter supports the dot11_phy_type_fhss PHY type and more than one regulatory domain. For more information about how the miniport driver specifies its list of supported PHY types, see OID_DOT11_SUPPORTED_PHY_TYPES.

The data type for this OID is a BOOLEAN value.

If the dot11RandomTableFlag MIB object is TRUE, the 802.11 station determines its hopping patterns from the Random Table field of the Hopping Pattern Table IE. If dot11RandomTableFlag is FALSE, the 802.11 station determines its hopping patterns through the Hop Index Method as defined in Clause 9.9.2.1 of the IEEE 802.11d-2001 standard.

When queried by OID_DOT11_RANDOM_TABLE_FLAG, the miniport driver fails the request if the following conditions are true:

  • The dot11RandomTableFlag MIB object is valid only for the frequency-hopping spread spectrum (FHSS) PHY type. If the current PHY type is not set to dot11_phy_type_fhss, the miniport driver must fail the request by returning NDIS_STATUS_INVALID_DATA from its MiniportOidRequest function.
  • If the IEEE 802.11d dot11MultiDomainCapabilityImplemented MIB object is FALSE, the miniport driver must fail the request by returning NDIS_STATUS_INVALID_DATA from its MiniportOidRequest function.
    For more information about the dot11MultiDomainCapabilityImplemented MIB object, see OID_DOT11_MULTI_DOMAIN_CAPABILITY_IMPLEMENTED.
  • If the IEEE 802.11d dot11MultiDomainCapabilityEnabled MIB object is FALSE, the miniport driver must fail the request by returning NDIS_STATUS_INVALID_DATA from its MiniportOidRequest function.
    For more information about the dot11MultiDomainCapabilityEnabled MIB object, see OID_DOT11_MULTI_DOMAIN_CAPABILITY_ENABLED.

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_SUPPORTED_PHY_TYPES
MiniportOidRequest
OID_DOT11_MULTI_DOMAIN_CAPABILITY_IMPLEMENTED
OID_DOT11_CURRENT_PHY_ID
Native 802.11 MIB OIDs
NDIS 5.x Legacy Reference