DOT11_WFD_ADDITIONAL_IE - NtDoc

Native API online documentation, based on the System Informer (formerly Process Hacker) phnt headers 
// windot11.h

typedef struct _DOT11_WFD_ADDITIONAL_IE {
  NDIS_OBJECT_HEADER Header;
  ULONG              uBeaconIEsOffset;
  ULONG              uBeaconIEsLength;
  ULONG              uProbeResponseIEsOffset;
  ULONG              uProbeResponseIEsLength;
  ULONG              uDefaultRequestIEsOffset;
  ULONG              uDefaultRequestIEsLength;
}  DOT11_WFD_ADDITIONAL_IE, *PDOT11_WFD_ADDITIONAL_IE;
View the official Windows Driver Kit DDI reference

NtDoc

No description available.

Edit description on GitHub

Windows Driver Kit DDI reference (ns-windot11-_dot11_wfd_additional_ie)

_DOT11_WFD_ADDITIONAL_IE structure

Description

[!Important] WiFiCx is the new Wi-Fi driver model released in Windows 11. We recommend that you use WiFiCx to take advantage of the latest features. The WDI driver model is now in maintenance mode and will only receive high priority fixes.

The DOT11_WFD_ADDITIONAL_IE structure represents an additional Information Element (IE) included in an OID_DOT11_WFD_ADDITIONAL_IE request. An additional IE contains both request and response data for probe and beacon operations.

Members

Specifies the type, revision and size of the DOT11_WFD_ADDITIONAL_IE structure. The required settings for the members of Header are the following:

Member Setting
Type NDIS_OBJECT_TYPE_DEFAULT
Revision DOT11_WFD_ADDITIONAL_IE_REVISION_1
Size DOT11_SIZEOF_WFD_ADDITIONAL_IE_REVISION_1

uBeaconIEsOffset

The offset, in bytes, of an array of beacon IEs. This offset is relative to the start of the buffer that contains this structure. The Wi-Fi Direct (WFD) port must add these addition IEs to the beacon packets when it is acting as a Group Owner.

uBeaconIEsLength

The length, in bytes, of the additional IEs at uBeaconIEsOffset. This member is ignored when the WFD port is operating in device or client mode.

uProbeResponseIEsOffset

The offset, in bytes, of an array of probe response IEs. This offset is relative to the start of the buffer that contains this structure. The Wi-Fi Direct (WFD) port must add these addition IEs to the probe response packets when it is acting as a WFD device or Group Owner.

uProbeResponseIEsLength

The length, in bytes, of the additional IEs at uProbeResponseIEsOffset. This member is ignored when the WFD port is operating in client mode.

uDefaultRequestIEsOffset

The offset, in bytes, of an array of probe request IEs. This offset is relative to the start of the buffer that contains this structure. The Wi-Fi Direct (WFD) port must add these addition IEs to the probe request packets it transmits.

uDefaultRequestIEsLength

The length, in bytes, of the additional IEs at uDefaultRequestIEsOffset.

Syntax

typedef struct _DOT11_WFD_ADDITIONAL_IE {
  NDIS_OBJECT_HEADER Header;
  ULONG              uBeaconIEsOffset;
  ULONG              uBeaconIEsLength;
  ULONG              uProbeResponseIEsOffset;
  ULONG              uProbeResponseIEsLength;
  ULONG              uDefaultRequestIEsOffset;
  ULONG              uDefaultRequestIEsLength;
}  DOT11_WFD_ADDITIONAL_IE, *PDOT11_WFD_ADDITIONAL_IE;

Remarks

The additional IEs at uDefaultRequestIEsOffset are for probe requests originating from the driver only. Explicit device discovery requests from the system are initiated in an OID_DOT11_WFD_DISCOVER_REQUEST. The IEs for an explicit discovery request should come from those IEs in the OID_DOT11_WFD_DISCOVER_REQUEST request and not from the IEs at uDefaultRequestIEsOffset.

View the official Windows Driver Kit DDI reference

Edit description on GitHub