Reference Manual
Table Of Contents
- Introduction to RS9116
- Getting Started with RS9116
- Compiling the Driver
- Installing the Driver
- Installation of Modules
- Enabling a Protocol
- Disabling a Protocol
- OneBox-Mobile in Wi-Fi Only Mode
- Installation in Wi-Fi Client Mode (with BSD interface support)
- Installation in Access Point Mode (with BSD interface support)
- Installation in Wi-Fi Client Mode (with NL80211 support)
- Installation in Wi-Fi AP mode (with NL80211 support)
- Installation in Wi-Fi Direct Mode (With BSD Interface Support)
- Installation in Wi-Fi Direct Mode (With NL80211 Support only for Kernel v3.8 or higher)
- OneBox-Mobile in Wi-Fi + Bluetooth LE Coexistence Mode
- Driver Information
- Wi-Fi ioctl Usage Guide
- Configuration Using CFG80211
- Enterprise security using CFG80211
- HOSTAPD and Wi-Fi Protected Setup (WPS)
- ACS with Hostapd
- Antenna Diversity
- Sniffer Mode
- Monitor Mode
- Concurrent Mode
- Background Scan Parameters
- Power save Modes, Profiles and Parameters
- Compliance and Certification
- Wi-Fi Performance Test ioctl usage
- Wake-On-Wireless LAN
- PUF [ Physical Unclonable Functions ]
- GTK Offload
- Steps to connect 802.11R client to AP
- Steps to configure 802.11W
- Update WLAN region based maximum powers from driver
- Bluetooth hcitool and hciconfig Usage
- Android support for RS9116
- Appendix A: Configuration of Kernels from 3.13 and above
- Appendix B: Binary Files for Embedded Platforms
- Appendix C: Using the Bluetooth Manager
- Appendix D: Common Configuration Parameters
- Appendix E: Installation of Missing Generic Netlink Libraries
- Appendix F: Procedure to use latest supplicant with NL80211 interface
- Appendix G: Considerations need to be made during hostapd usage
- RS9116 n-Link Software TRM Revision History
RS9116 n-Link Linux and Android Technical Reference Manual
Version 2.0
August 2019
105
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.
18.2.3 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]
[rfkillrelease]
[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.
18.2.4 Suspend system
Use below command to suspend the system.
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