Reference Manual

Redpine Signals, Inc. Proprietary and Confidential Page 98
RS9116 n-Link Linux and Android
Technical Reference Manual
Version 2.0
• Trigger wakeup
18.2.2 Configure WoWLAN
To configure WoWLAN, standard network tool ‘iw’ can be used. Issue below command in the terminal to configure
WoWLAN.
# iw phy <phyX> wowlan enable <trigger_type>
phyX is the phy physical device number of the system for the device. It can be obtained by using the 'info' command. The
command and its example output is shown below.
# iw dev <intf_name> info
Interface wlan0
ifindex 5
wdev 0x100000001
addr 00:23:a7:b9:ab:44
type managed
wiphy 1
channel 6 (2437 MHz), width: 20 MHz (no HT), center1: 2437 MHz
As can be seen, in this case, phy<X> is termed as phy1.
Trigger Type
These are the type of triggers currently available in linux. Possible triggers are:
[any] [disconnect] [magic-packet] [gtk-rekey-failure] [eap-identity-request] [4way-
handshake] [rfkill-release] [net-detect interval <in_msecs> [delay <in_secs>] [freqs
<freq>+] [matches [ssid <ssid>]+]] [active [ssid <ssid>]+|passive]
[randomise[=<addr>/<mask>]]] [tcp <config-file>] [patterns [offset1+]<pattern1> ...]
Triggers which are currently supported are:
<any> - To wake for any received packet
<disconnect> - To wake up for receival of disassociation or deauthentication from connected AP.
<magic-packet> - Receive of any magic packet generated through wowlan applications.
Note:
That host will be waked up if the connection is lost in any case (Like AP is powered off etc). Also host will be wakeup when
GTK rekey packet is received. Hence before going to suspend, it is recommended to configure high GTK rekey timeout