OID_DOT11_CURRENT_FREQUENCY

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 set, the OID_DOT11_CURRENT_FREQUENCY object identifier (OID) requests that the miniport driver set the value of the IEEE 802.11a dot11CurrentFrequency management information base (MIB) object for the current PHY type on the 802.11 station.

When queried, OID_DOT11_CURRENT_FREQUENCY requests that the miniport driver return the value of the dot11CurrentFrequency MIB object.

This MIB object defines the current operating frequency channel used by the PHY.

Note  Support for OID_DOT11_CURRENT_FREQUENCY is mandatory if the NIC supports the dot11_phy_type_ofdm PHY type. 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_CURRENT_FREQUENCYis a ULONG value from 0 through 200.

Note  If a service provided by the independent hardware vendor (IHV) is managing the wireless network profiles, the IHV can use whatever value range it supports.

The dot11CurrentFrequency MIB object is only valid for the orthogonal frequency division multiplexing (OFDM) PHY type. If the current PHY type is not set to dot11_phy_type_ofdm, the miniport driver must fail the query request by returning NDIS_STATUS_INVALID_DATA from its MiniportOidRequest function.

When OID_DOT11_CURRENT_FREQUENCY is set, the miniport driver fails the request under the following conditions:

• If the current PHY type is in a powered-off state, the miniport driver must fail the request by returning NDIS_STATUS_POWER_STATE_INVALID from its MiniportOidRequest function. For more information about power states, see OID_DOT11_NIC_POWER_STATE.

• If the 802.11 station is currently performing a scan request, the miniport driver must fail the set request by returning NDIS_STATUS_DOT11_MEDIA_IN_USE from its MiniportOidRequest function. For more information about scan requests, see OID_DOT11_SCAN_REQUEST.

If the miniport driver is operating in the Extensible Station (ExtSTA) mode, it fails the set request of OID_DOT11_CURRENT_FREQUENCY under the following conditions:

• If the desired BSS type is dot11_BSS_type_infrastructure, the miniport driver must fail the set request by returning NDIS_STATUS_INVALID_DATA from its MiniportOidRequest function. For more information about the desired BSS type, see OID_DOT11_DESIRED_BSS_TYPE.

• If the miniport driver has enabled automatic PHY configuration, it can fail the set request if the 802.11 station manages the PHY-layer configuration. In this situation, the driver returns NDIS_STATUS_DOT11_AUTO_CONFIG_ENABLED from its MiniportOidRequest function.

  For more information about automatic PHY configuration, see OID_DOT11_AUTO_CONFIG_ENABLED.

If the miniport driver is operating in 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.

If the miniport driver supports the functionality of multiple MAC entities through virtualization, the driver should not return NDIS_STATUS_DOT11_MEDIA_IN_USE if the medium is blocked by another MAC.

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