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
18
network={
ssid=
"<SSID of Access Point>"
scan_ssid=1
key_mgmt=NONE
}
Next, run the "start_sta.sh" script in the "release" folder to load the driver modules and the supplicant and also
connect to the Access Point specified in the "sta_settings.conf" file.
sh start_sta.sh
After issuing the above command, a virtual interface with the name "wifi0" will be created. You can view the list of
interfaces by entering the following command:
ifconfig –a
You can check whether the connection to the Access Point is successful or not, by running the following command:
iwconfig wifi0
The sample output of this command is
wifi0 IEEE 802.11bgn ESSID:"Range" Nickname:""
Mode:Managed Frequency:2.412 GHz Access Point: 38:A4:ED:DE:BB:06
Bit Rate:39 Mb/s Tx
-Power=16 dBm Sensitivity=1/0
RTS thr:off Fragment thr:off
Encryption key:****-**** Security mode:restricted
Power Management:off
Link Quality=80/80 Signal level=-28 dBm Noise level:0 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
This command gives the status of the device. If the connection is successful, then the connected Access point SSID
along with the MAC address is displayed. If it is not connected to an Access point, a message "Not Associated" is
displayed.
To view the list of Access Points scanned in each channel, you can run the following command in the "release"
folder.
./wpa_cli –i wifi0 scan_results
To obtain an IP address using DHCP, start the DHCP client by entering below commands. (1st command to remove
entry for existing dhcp and 2nd to create a new entry).
User needs to make sure of the module detection w.r.t interface being used. If the module is not detected,
user will end up with errors displayed on the console !