OID_DOT11_RANDOM_TABLE_FLAG

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.

When queried, the OID_DOT11_RANDOM_TABLE_FLAG object identifier (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 NIC 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 OID_DOT11_RANDOM_TABLE_FLAG 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 under the following conditions:

• The dot11RandomTableFlag MIB object is valid for only 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.

Note  A Native 802.11 miniport driver that is designed to run on the Windows Vista or Windows Server 2008 operating systems must always reset this 802.11 MIB OID to its default value. This is the case regardless of the value of the bSetDefaultMIB member of the DOT11_RESET_REQUEST structure. This requirement applies to a miniport driver that, in a call to the NdisMSetMiniportAttributes function, sets MiniportAttributes -> Native_802_11_Attributes -> Header -> Revision to NDIS_MINIPORT_ADAPTER_802_11_ATTRIBUTES_REVISION_1.

Requirements

See also

Native 802.11 MIB OIDs

Native 802.11 Wireless LAN OIDs