Compartir a través de

Guidelines for Native 802.11 Extensible Station Receive Operations

  • Artículo

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.

 

This section describes the guidelines for receive operations performed by a Native 802.11 miniport driver operating in Extensible Station (ExtSTA) mode. For more information about this operation mode, see Extensible Station Operation Mode.

When performing a receive operation, the 802.11 station and miniport driver must follow these guidelines.

  • If the 802.11 station supports and enables multiple PHYs for the current basic service set (BSS) network connection, the station must detect and discard duplicate media access control (MAC) protocol data unit (MPDU) fragments received by more than one PHY.

  • If the 802.11 station supports IEEE 802.1p packet prioritization or 802.1Q virtual LAN (VLAN), the station must remove the 802.1Q/p tag header after the 802.11 MAC and IEEE LLC/SNAP headers. The miniport driver returns its support for 802.1Q/p when queried by OID_GEN_MAC_OPTIONS.

    The miniport driver must return the 802.1Q/p tag header through the NDIS_NET_BUFFER_LIST_8021Q_INFO structure associated with the NET_BUFFER_LIST structure used for the received packet. The miniport driver accesses the NDIS_NET_BUFFER_LIST_8021Q_INFO structure by calling the NET_BUFFER_LIST_INFO macro with the Ieee8021QNetBufferListInfo identifier.

    For more information about the 802.1Q/p tag header, refer to Clause 9 of the IEEE 802.1Q-1998 standard.

  • If the 802.11 station supports wireless Quality of Service (QoS) extensions not supported by the operating system, the station must remove any QoS extensions from the MAC header and payload data. The miniport driver must return the appropriate IEEE 802.1D priority value through the NDIS_NET_BUFFER_LIST_8021Q_INFO structure that is associated with the NET_BUFFER_LIST structure used for the received packet.

    Note  The Windows Vista operating system does not support the wireless QoS extensions defined in either the IEEE 802.11e-2005 standard or Wireless Multimedia (WMM) specification (IEEE Document 802.11-03-504r7). However, the operating system will process the QoS Control field in the IEEE MAC header. In this situation, the miniport driver can either retain or remove the QoS Control field before indicating the received packet. The driver must still return the appropriate 802.1D priority value through the NDIS_NET_BUFFER_LIST_8021Q_INFO structure. For more information about QoS support, see IEEE 802.11e/WMM Support.

     

  • The 802.11 station must receive 802.11 packets that match the following conditions:

    • The destination address (DA) in the 802.11 MAC header matches either the 802.11 station's MAC address or an entry within the station's multicast address table. For more information about the multicast address table, see OID_DOT11_MULTICAST_LIST.
    • If connected to a BSS network, the BSS Identifier (BSSID) address in the 802.11 MAC header matches the BSSID of the network. If not connected to a BSS network, the 802.11 station must receive 802.11 packets with any BSSID address.

  • The 802.11 station must not filter received packets based on the From DS or To DS subfields of the Frame Control field within the 802.11 MAC header. For more information about these subfields, refer to Clause 8.2.4.1 of the IEEE 802.11-2012 standard.

  • If the packet is received with a DA that matches either the 802.11 station's MAC address or an entry within the station's multicast address table, the 802.11 station must do the following:

    • If the packet is received with an encrypted payload, the 802.11 station must discard the packet if any of the following are true:
      • A cipher key is not available to decrypt the packet.
      • The packet payload data fails to decrypt successfully.
      • The packet payload data fails the message integrity code (MIC) verification. If the TKIP cipher algorithm is enabled, the miniport driver must perform the actions defined in TKIP Countermeasures.
      • The packet fails the replay mechanism defined for the cipher algorithm.
      • A privacy exemption is defined for the packet's EtherType that specifies an action of DOT11_EXEMPT_ALWAYS. For more information about privacy exemptions, see Privacy Exemption Lists.
    • If the packet is received with an unencrypted payload, the 802.11 station must discard the packet if any of the following are true:
      • A cipher key is available to decrypt the packet and a privacy exemption is defined for the packet's EtherType that specifies an action of DOT11_EXEMPT_ON_KEY_UNAVAILABLE. For more information about privacy exemptions, see Privacy Exemption Lists.
      • The IEEE 802.11 dot11ExcludeUnencrypted management information base (MIB) object is set to TRUE. For more information about this MIB object, see OID_DOT11_EXCLUDE_UNENCRYPTED.

  • The miniport driver must increment the appropriate MAC and PHY statistical counters for all MPDU fragments and MSDU/MPPDU packets either received successfully or discarded by the 802.11 station. For more information about these statistical counters, see OID_DOT11_STATISTICS.