OID_DOT11_HOP_ALGORITHM_ADOPTED (Compact 2013)

Article
07/31/2017

3/26/2014

When queried, this OID requests that the miniport driver return the value of the IEEE 802.11d dot11HopAlgorithmAdopted management information base (MIB) object for the current PHY type on the 802.11 station.

The dot11HopAlgorithmAdopted MIB object specifies the type of algorithm that generates the hopping patterns used by the frequency-hopping spread spectrum (FHSS) PHY.

Note

Support for OID_DOT11_HOP_ALGORITHM 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 the DOT11_HOP_ALGO_ADOPTED enumeration.

The miniport driver fails a query of OID_DOT11_HOP_ALGORITHM if the following conditions are true:

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

Requirements

Header

windot11.h

OID_DOT11_HOP_ALGORITHM_ADOPTED (Compact 2013)

Requirements

See Also

Reference

Additional resources