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
25
# ./wpa_cli –i wifi0 p2p_group_add freq=<channel_freq>
The "channel_freq" input mentioned in the above command is the center frequency of the Wi-Fi channel in which
the GO needs to be started The OneBox-Mobile software supports DFS slave mode. However, DFS Channels need to
be avoided till the module is certified for DFS.. If this parameter is not provided, then the GO will start in the
channel specified in the p2p.conf file.
Legacy Wi-Fi clients (non P2P clients) need a passphrase to connect to the p2p group. The command given below
generates the passphrase for legacy Wi-Fi clients.
#. /wpa_cli –i wifi0 p2p_get_passphrase
4.4.6 Installation in Wi-Fi Direct Mode (With NL80211 Support only for Kernel v3.8 or higher)
The steps for installing OneBox-Mobile software in Wi-Fi Direct Mode are as follows:
The "start_p2p_nl80211.sh" script present in the "release" folder needs to be run in order to start the supplicant
and also for installing the Wi-Fi Direct mode. The configurable parameters in the p2p_nl80211.conf file are
outlined below:
• listen channel
• operating channel
• GO Intent
wpa_supplicant version used should be latest one (2.6 or higher). Please check the start_p2p_nl80211.sh script for
better understanding and update it accordingly.
After starting the supplicant, the p2p_commands mentioned below should be executed.
• To find other P2P networks
#. /wpa_cli –i wifi0 p2p_find
• To find other P2P devices in range
#. /wpa_cli –i wifi0 p2p_peers
• To connect to a P2P network
#. /wpa_cli –i wifi0 p2p_connect <BSS ID> pbc go_intent=<intent value>
Here the intent value range is between 0 and 15 (Putting intent value to 0 makes p2p device as client and 15 makes
p2p device as group owner). If you are becoming GO, dhcp server should be running on GO Interface.
4.4.6.1 Autonomous GO Mode
The steps for installing OneBox-Mobile software in Wi-Fi Direct Mode are as follows:
The "start_p2pgo.sh" script present in the "release" folder needs to be run in order to start the supplicant and
also for installing the Wi-Fi Direct mode. The configurable parameters in the p2p_nl80211.conf file are outlined
below:
• listen channel
• operating channel
• GO Intent