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
88
disconnects from the AP, by default it will move to the INIT state. The user is expected to give the host_scan
command to initiate scanning.
2. SCAN: In This state the device performs scan and sends the scan results to the supplicant. In the STA alone mode,
the scan request from the supplicant is sufficient for the STA to move to this state. In case AP is running and the STA
is started, then the user has to give the host_scan command for the STA to move to this state.
3. AUTH: This is an intermediate state during connection. Once the STA collects the SCAN results and sends to the
supplicant, if any desired BSS is found, then the STA moves to this state to complete authentication.
4. ASSOC: Once the AUTH is successful, the STA moves to the ASSOCIATION State.
5. RUN: Once the ASSOCIATION is successful, the STA moves to RUN state and the user can co-relate this to
Connection Established. Once the STA enters into the RUN state, it automatically disables the host_scan command,
i.e the device no longer performs the SCAN even if the user hasn't explicitly sent the scan stop command. If the user
wishes to continue the SCAN he must initiate it again.
6. DOWN: If the STA VAP is not up, then the output is DOWN
Flow chart
Limitations