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
139
30 Appendix E: Installation of Missing Generic Netlink Libraries
Create a directory in the location where Tool chain and BSP are present
mkdir build
Download the libnl 3.2.xx.tar.gz\[Referring 3.2.27.tar.gz as an example here \] library and extract it in the build
directory.
cd build
tar xvf
3.2.27.tar.gz
Configure the libnl library for target platfrom
CC=/path to the toochain/bin/arm-linux-gnueabihf-gcc
./configure --host=arm-linux-gnueabihf -prefix=/<complete path to build directory>/
Here headers will be installed in ${prefix}/include/libnl3.
Make and install the libraries in the destination directory or else they will be installed in /usr/local/lib and /usr/
local/include/libnl folders of host machine by default.
Follow the example given below:
make DESTDIR=$(arm-cortex_a8-linux-gnueabihf-gcc -print -/<path to build directory>/build/)
Exporting the path for build directory in the command line or add these flags in the supplicant and hostapd config
files under CONFIG_DRIVER_NL80211= y variable.
#export LDFLAGS='-L/<path to build directory>/lib/libnl'
OR
CFLAGS += -I/<path to build directory>/include/libnl3
Ex: LIBS += -L/<path to build directory>/lib/libnl
LIBS : Contains a list of additional libraries to pass to the linker command.
libnl CFlags should be enabled with CONFIG_LIBNL32=y in supplicant and hostpad .config file \[The above
configuration settings should be set to "y" in case NL80211 is used\]. Make sure that the NL80211 support
and Hostapd support are enabled in the menuconfig during compilation.