When set, the OID_DOT11_OPERATIONAL_RATE_SET object identifier (OID) requests that the miniport driver set the operational data rates to the specified value.

When queried, this OID requests that the miniport driver return the set of operational data rates.

The data type for OID_DOT11_OPERATIONAL_RATE_SET is the DOT11_RATE_SET structure, based on the IEEE 802.11 dot11OperationalRateSet management information base (MIB) object.

The operational rate set of the 802.11 station defines the rates at which the station can transmit data. The 802.11 station specifies the rates it supports in the Supported Rates information element (IE) of various 802.11 management frames, such as Beacon and Probe Response frames. For more information about the Supported Rates IE, refer to Clause of the IEEE 802.11-2012 standard.

The 802.11 station also uses the operational rate set to determine whether it can connect to a BSS based on the Supported Rates IE from Beacons or Probe Response frames received within the BSS network. For more information about this process, refer to Clause 6.3 of the IEEE 802.11-2012 standard.

If the 802.11 station has not completed a scan request when OID_DOT11_OPERATIONAL_RATE_SET is set, it must use the specified operational rate set for the next 802.11 Probe Request frame that it transmits.

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.



Available in Windows Vista and later versions of the Windows operating systems.


Windot11.h (include Ndis.h)

See also

Native 802.11 MIB OIDs
Native 802.11 Wireless LAN OIDs



Send comments about this topic to Microsoft

© 2016 Microsoft