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_ADDITIONAL_IE object identifier (OID) requests that the miniport driver set the value of the msDot11AdditionalIEs management information base (MIB) object to the specified data.

When queried, this OID requests that the miniport driver return the value of the msDot11AdditionalIEs MIB object.

The msDot11AdditionalIEs MIB object specifies the values of the additional information elements (IEs) in the BSS 802.11 beacon or probe response frame.

Note Support for this OID is mandatory.

The data type for this OID is the DOT11_ADDITIONAL_IE structure.

When this OID is set, the NIC must behave as follows:

  • If the Extensible AP is in the INIT state, the NIC must complete the request.

  • If the Extensible AP is in the OP state, the NIC must complete the request and, upon completion of the set request, the NIC must begin using the new additional IEs in the beacon or probe response frames that it sends.

The NIC should place additional IEs at the end of beacon or probe response frames.

The NIC must ensure that the corresponding additional IEs appear in every beacon or probe response frame that it sends, unless the additional IEs would cause the size of the frame to exceed the MAC management protocol data unit (MMPDU) limit. In this case, the NIC should discard the new additional IEs, keep the original list of additional IEs, and return NDIS_STATUS_BUFFER_OVERFLOW. However, this overflow situation should not change the NIC operational mode or state.

The miniport driver should reset the members of the DOT11_ADDITIONAL_IE structure to the default values when it receives an OID_DOT11_RESET_REQUEST request.



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


Windot11.h (include Ndis.h)

See also



Native 802.11 Wireless LAN OIDs

Send comments about this topic to Microsoft