Wake-Up Events

This section applies only to NDIS 6.20 and later.

The NIC should wake up the host computer whenever any of the following events occur:

WOL Packet Received

In this case, the NIC (or the Native 802.11 Wireless LAN infrastructure) receives a pattern that matches a previously set wake-on-LAN (WOL) pattern. WOL pattern matching should be performed on IEEE 802.11 data packets (except 802.11 null data packets) with configured IPv4, IPv6, IPSec, TCP and Teredo wake-up patterns. If the NIC provides the pattern matching, it must be done after the packets have been decrypted and the message integrity code (MIC) is verified. If the matching is performed in the infrastructure, it must be done before the packets are encrypted and MIC-protected.

WOL Magic Pattern Received

In this case, the NIC receives a packet that matches the WOL magic packet wake-up pattern. The hardware vendor should define the method for transmitting the magic packets used for WOL. Although most implementations will use IEEE 802.11 data packets, transmitting magic packets in IEEE 802.11 management or control frames is not prohibited.

AP Association Lost

In this case, the NIC loses the association with its current AP. The unreachable timeout threshold is NIC dependent but must not exceed 5 minutes. After the host computer wakes up, the miniport driver must report the AP disassociation to the operating system.

GTK Handshake Error

In this case, the NIC encounters an error in a two-way handshake.

802.1x EAP-Request/Identity Packet Received

In this case, the operating system attempts WPA2-Enterprise authentication by sending an 802.1x EAP-Request/Identity WOL pattern.

Four-way Handshake Request Received

In this case, the NIC receives a request from the associated AP to perform a four-way handshake authentication. When the host computer is awake, the operating system performs the four-way pairwise transient key (PTK) handshake procedure.

 

 

Send comments about this topic to Microsoft

Show:
© 2015 Microsoft