Redpine Signals RS9116 User manual

Redpine Signals, Inc.
2107 North First Street, Suite #540, San Jose, California 95131,
United States of America.
Phone: [phone], Fax: [phone]
Email: [email protected]
Website: www.redpinesignals.com
--------------------------------------------------------------------------------------------------------------------------------------------------------
RS9116 n-Link Linux and Android Technical
Reference Manual
Version 2.0
July 2020

RS9116 n-Link Linux and Android Technical Reference Manual
Version 2.0
July 2020
2
Table of Contents
1 Introduction to RS9116.............................................................................................................. 7
2 Getting Started with RS9116 ..................................................................................................... 8
2.1 Hardware Requirements ........................................................................................................... 8
2.2 Software Requirements............................................................................................................. 8
2.3 Software Package Contents ...................................................................................................... 8
3 Compiling the Driver.................................................................................................................. 9
4 Installing the Driver.................................................................................................................. 14
4.1 Installation of Modules ............................................................................................................ 14
4.2 Enabling a Protocol.................................................................................................................. 15
4.3 Disabling a Protocol................................................................................................................. 15
4.4 OneBox-Mobile in Wi-Fi Only Mode......................................................................................... 15
4.5 OneBox-Mobile in Wi-Fi + Bluetooth LE Coexistence Mode ................................................... 28
4.6 Driver Information ................................................................................................................... 30
5 Wi-Fi ioctl Usage Guide ............................................................................................................ 31
5.1 Configuring using Wireless Extensions ................................................................................... 31
5.2 Private (Driver-Specific) Commands for Access Point and Client Modes ............................. 33
5.3 Private (Driver- Specific) Commands for Access Point Mode ................................................ 38
5.4 Private (Driver- Specific) Commands for Client Mode ........................................................... 43
5.5 Configuring Using onebox_util................................................................................................ 44
6 Configuration Using CFG80211 ............................................................................................... 65
6.1 Using iw Wireless Tool ............................................................................................................. 65
7 Enterprise security using CFG80211........................................................................................ 70
7.1 Installation and configuration of FREERADIUS Server........................................................... 70
7.2 Configuration of AP and RADIUS server to use EAP methods................................................ 71
8 HOSTAPD and Wi-Fi Protected Setup (WPS) .......................................................................... 77
8.1 Hostapd Configuration before Compilation........................................................................... 77
8.2 Configuration in hostapd_wps.conf ....................................................................................... 77
8.3 WPS........................................................................................................................................... 78
9 ACS with Hostapd .................................................................................................................... 81

RS9116 n-Link Linux and Android Technical Reference Manual
Version 2.0
July 2020
3
10 Antenna Diversity..................................................................................................................... 82
10.1 Introduction ............................................................................................................................. 82
10.2 Configuration ........................................................................................................................... 82
11 Sniffer Mode ............................................................................................................................. 83
12 Monitor Mode ........................................................................................................................... 84
13 Concurrent Mode ..................................................................................................................... 85
13.1 Installation Procedure ............................................................................................................. 85
14 Background Scan Parameters................................................................................................. 90
15 Power save Modes, Profiles and Parameters ......................................................................... 91
15.1 Power save Modes.................................................................................................................... 91
15.2 Power save Profiles.................................................................................................................. 91
15.3 Wakeup Procedures and Data Retrieval ................................................................................. 91
15.4 Power save Parameters........................................................................................................... 92
15.5 Procedure to enable device power save for USB interface ................................................... 93
16 Compliance and Certification ................................................................................................. 95
16.1 Federal Communication Commission Statement.................................................................. 95
16.2 Industry Canada / ISED Statement ......................................................................................... 95
16.3 Regulatory Module Integration Instructions .......................................................................... 96
17 Wi-Fi Performance Test ioctl usage......................................................................................... 98
17.1 WiFi Transmit Tests.................................................................................................................. 98
17.2 Wi-Fi Receive Tests................................................................................................................. 101
17.3 Continuous Wave (CW) mode................................................................................................ 102
18 Wake-On-Wireless LAN .......................................................................................................... 104
18.1 WoWLAN through onebox_util .............................................................................................. 104
18.2 WoWLAN using Linux power state machine ......................................................................... 104
19 PUF [ Physical Unclonable Functions ] ................................................................................. 107
19.1 Introduction ........................................................................................................................... 107
19.2 Configuration ......................................................................................................................... 107
19.3 PUF Operations and IOCTL Usage......................................................................................... 107
20 GTK Offload ............................................................................................................................ 110

RS9116 n-Link Linux and Android Technical Reference Manual
Version 2.0
July 2020
4
20.1 Configuration ......................................................................................................................... 110
21 Steps to connect 802.11R client to AP .................................................................................. 111
22 Steps to configure 802.11W ................................................................................................... 112
22.1 Configuring and Compiling Driver for PMF in client mode: ................................................. 112
22.2 Configuring and Compiling Driver for PMF in AP mode: ...................................................... 112
23 Update WLAN region based maximum powers from driver ................................................ 113
24 Bluetooth hcitool and hciconfig Usage ................................................................................ 114
24.1 Bluetooth Power Save Commands ....................................................................................... 116
24.2 Bluetooth Performance Test ioctl Usage.............................................................................. 116
24.3 BLE/BLR Transmit .................................................................................................................. 116
24.4 BLE/BLR Receive .................................................................................................................... 120
24.5 Hopping .................................................................................................................................. 122
25 Android support for RS9116 .................................................................................................. 124
26 Appendix A: Configuration of Kernels from 3.13 and above................................................ 125
26.1 SDIO Stack Options................................................................................................................ 125
26.2 Wireless Extension Tools ....................................................................................................... 126
26.3 Bluetooth Stack Options ....................................................................................................... 127
26.4 Kernel Compilation................................................................................................................ 128
27 Appendix B: Binary Files for Embedded Platforms .............................................................. 129
27.1 Common Hardware Requirements for Embedded Platforms ............................................. 129
27.2 Freescale i.MX6....................................................................................................................... 129
27.3 Freescale i.MX53..................................................................................................................... 130
27.4 Atmel AT91SAM9G45 and AT91SAM9M10 ............................................................................. 131
28 Appendix C: Using the Bluetooth Manager........................................................................... 133
29 Appendix D: Common Configuration Parameters................................................................ 136
29.1 RF Power Mode parameter.................................................................................................... 136
29.2 Country selection................................................................................................................... 136
29.3 Antenna selection .................................................................................................................. 136
30 Appendix E: Installation of Missing Generic Netlink Libraries ............................................. 139
31 Appendix F: Procedure to use latest supplicant with NL80211 interface ........................... 140

RS9116 n-Link Linux and Android Technical Reference Manual
Version 2.0
July 2020
5
31.1 Bgscan and Roaming ............................................................................................................. 140
32 Appendix G: Considerations need to be made during hostapd usage................................ 142
32.1 Parameters updated from hostapd.conf file........................................................................ 142
33 Appendix H: Antennae ........................................................................................................... 143
33.1 Taoglas Antenna .................................................................................................................... 143
33.2 SMARTEQ Antenna................................................................................................................. 143
33.3 InsideWLAN Antenna ............................................................................................................. 143
33.4 PCB Antenna........................................................................................................................... 143
34 RS9116 n-Link Software TRM Revision History..................................................................... 144

RS9116 n-Link Linux and Android Technical Reference Manual
Version : 2.0
July 2020
6
About this Document
This document is a preliminary version of RS9116 n-Link Technical Reference Manual for Linux and Android,
provided to customers

RS9116 n-Link Linux and Android Technical Reference Manual
Version : 2.0
July 2020
7
1 Introduction to RS9116
The OneBox-Mobile(refers to single software providing combo of all the features supported) software supports the
following modes. They are outlined below:
•Wi-Fi (Access Point, Client, Wi-Fi-Direct (P2P), Sniffer and Monitor modes)
•Bluetooth Low Energy
•802.15.4 Compatibility
The OneBox-Mobile Coexistence software supports the following combination of modes. They are as follows:
•WLAN STATION /WIFI-Direct/WLAN PER
•WLAN ACCESS POINT(including muliple APs on different vaps)
•WLAN ACCESS POINT + STATION MODE(on multiple vaps)
•WAKE ON WIRELESS(WOWLAN)
•BT LE MODE /BT LE PER MODE
• WLAN STATION + BT LE MODE      
•WLAN STATION + BT LE MODE
•WLAN ACCESS POINT + BT LE MODE
The subsequent sections explain the use of OneBox-Mobile software . The installation and operation of the driver
on specific representative processor platforms have been explained in the Appendix sections.

RS9116 n-Link Linux and Android Technical Reference Manual
Version : 2.0
July 2020
8
2 Getting Started with RS9116
This section lists the hardware and software requirements for the installation of the software and also describes the
steps to be followed to initialize and run the software.
2.1 Hardware Requirements
The Hardware requirements are as follows:
•RS9116N n-Link® Module
•Laptop/PC with SDIO or USB interface or any embedded platform with Linux Board support package.
2.2 Software Requirements
The Software requirements are as follows:
• Linux with kernel version from 2.6.38 to 4.18.5 – should enable the open source SDIO and USB stacks.
•DHCP Server (for Wi-Fi Access Point mode)
•Bluetooth supported commands bluetoothctl and bluetoothd must be present.
•Compatible Bluetooth Host Stack, e.g., the Open Source BlueZ Stack v4.101
•ncurses and ncurses-devel libraries
2.3 Software Package Contents
The OneBox-Mobile Software is delivered as a tarball with a filename in the format:
RS9116.NXX.NL.GEN.LNX.x.y.z.tgz, where the naming convention is as follows:
NXX – defines whether the package supports only Wi-Fi (N00) or BT Low Energy along with Wi-Fi (NB0).
x.y.z – identifies the software package.
Redpine driver comes in proprietary and open source form.The Linux driver package contains the following files/
folders:
•Readme_nLink.txt
•Releasenotes_nLink.txt
•Documents
•Binary_files (optional)
•source (optional)
Based on the Software License Agreement, driver source code will be available for the users from "https://
www.redpinenetworks.us/OpenKM/login.jsp"
If the Laptop/PC does not have an SDIO slot, a SDHC/SD/MMC to CardBus Adapter like the one available at
http://www.hwtools.net/cardreader/SDCBA_C01.html can be used.

For kernel versions 3.13 and above, refer to the section onAppendix A: Configuration of Kernels from 3.13
and above to ensure correct kernel configuration.


RS9116 n-Link Linux and Android Technical Reference Manual
Version : 2.0
July 2020
9
3 Compiling the Driver
This section describes the steps to be followed in order to compile the OneBox-Mobile Linux software for different
platforms.The steps are outlined below:
1. Save the required configuration of Driver using the menuconfig utility.
 Following are the options available in menuconfig:
•Host Interface: SDIO or USB.
•Operating system: Linux or Android
•Nl80211 support
•Hostapd Support
•Wi-Fi
•Bluetooth
 2. To open menuconfig utility, untar the tar ball, go to source->host folder & enter the given below command.
make menuconfig
The following images show the menuconfig utility options.
Figure 1: Main Page of menuconfig

RS9116 n-Link Linux and Android Technical Reference Manual
Version : 2.0
July 2020
10
Figure 2: SelectingOperating System
By default, the driver package includes "BSD" support. In case the user needs "Nl80211" support for Access
point and Station modes, select the menuconfig accordingly. For Nl80211, the "Hostapd" application is used
as a configuration utility.
Figure 3: Selection of NL80211 and Hostapd Support

RS9116 n-Link Linux and Android Technical Reference Manual
Version : 2.0
July 2020
11
By default the configuration is enabled with Wi-Fi and Bluetooth. If the user wants to compile the driver for a
particular protocol, he can disable the unwanted protocols in Menuconfig utility.In case of coex mode, the
Wi-Fi must always be enabled in conjunction with BT protocols, even if Wi-Fi will not be used.
For example, if the user wants to compile the driver only for Bluetooth only, the Wi-Fi and Bluetooth mode
must be enabled. Refer to the following images of Menuconfig utility for more information:
Figure 4: Selection of WIFI Only Mode
 3. After selecting the configuration, exit the menuconfig and save the configuration. Please refer the given below
image of saving the configuration.
If NL80211 support is enabled in the driver, make sure that the following modules are loaded in the kernel
before running the driver in order to avoid module dependencies. This can be verified by using the
commands.
# lsmod | grep cfg80211
# lsmod | grep bluetooth
If they are not installed, can be installed by using the commands below :
# modprobe cfg80211
# modprobe bluetooth


RS9116 n-Link Linux and Android Technical Reference Manual
Version : 2.0
July 2020
12
Figure 5: Save the changes before exiting
 4. Now to compile the driver, enter the following command:
make
The code is compiled and the binaries are generated in thesource/host/release folder.For embedded
platforms, modify the path assigned to the "DEF_KERNEL_DIR" variable in the Makefile:
cd RS9116.NXX.NL.GEN.LNX.x.y.z/source/host
vim Makefile
The DEF_KERNEL_DIR variable has to be assigned along with the compiled kernel path. For an x86 based
Linux platform, the path is usually "/lib/modules/<kernel_version>/build" and this is the path assigned in
the Makefile provided in the package.
Example:
DEF_KERNEL_DIR:= /lib/modules/3.4.66/build
Next, use the "make" command to start compiling the driver. For embedded platforms, add the target
platform and toolchain path as cross compilation option to the "make" command.
For example, if the target platform is ARM and tool chain path is "/opt/freescale/usr/local/gcc-4.4.4-
glibc-2.11.1-multilib-1.0/arm-fsl-linux-gnueabi/bin/arm-none-linux-gnueabi-" , then the command is
issued as:
make ARCH=arm CROSS_COMPILE=/opt/freescale/usr/local/gcc-4.4.4-glibc-2.11.1-multilib-1.0/arm-fsl-linux-
gnueabi/bin/arm-none-linux-gnueabi-

RS9116 n-Link Linux and Android Technical Reference Manual
Version : 2.0
July 2020
13
In order to un-install the RSI opensource driver, use the following commands:
# rmmod rsi_usb
# rmmod rsi_sdo
# rmmod rsi_91x
Before installing the Onebox RS9116 Driver modules, make sure that the RSI opensource modules are
uninstalled. This has been taken care in the onebox_insert.sh script.


RS9116 n-Link Linux and Android Technical Reference Manual
Version : 2.0
July 2020
14
4 Installing the Driver
4.1 Installation of Modules
After completion of compilation, the driver generates the following modules in the release folder. They are outlined
below:
•onebox_common_gpl.ko
•onebox_gpl.ko
•onebox_nongpl.ko
•onebox_wlan_gpl.ko
•onebox_wlan_nongpl.ko
•onebox_bt_gpl.ko
•onebox_bt_nongpl.ko
•wlan.ko
•wlan_wep.ko
•wlan_ccmp.ko
•wlan_tkip.ko
•wlan_acl.ko
•wlan_scan_sta.ko
•wlan_xauth.ko
Now,Load various modules in the following order:
Load onebox common gpl module
# insmod onebox_common_gpl.ko
 Load protocol related Modules (Wi-Fi, BT)
 Load common Hal Modules (onebox_nongpl.ko and onebox_gpl.ko).
Note: Please change operating voltage configuration (1.8V or 3.3V) in common_insert.sh file in
FEATURE_BITMAP_9116.
Example: For 3.3V keep FEATURE_BITMAP_9116=0
 For 1.8V keep FEATURE_BITMAP_9116=2
 For 3.3V, 5Mhz BW keep FEATURE_BITMAP_9116=32

Note: Please select appropriate SLEEP CLOCK SOURCE in common_insert.sh file as required
SLEEP CLOCK SOURCE SELCECTION =
0 - Use 32khz internal RC clock as sleep clock
1 - Use 32KHz clock from external XTAL OSCILLATOR (Applicable only for Silicon Version <= 1.3 )
2 - Use 32KHz bypass clock on UULP_GPIO_3
3 - Use 32KHz bypass clock on UULP_GPIO_4

Note: Please configure SLEEP_GPIO in common_insert.sh file as connected
SLEEP_IND_GPIO_SEL =
0 - UULP_GPIO_3
1 - UULP_GPIO_0


RS9116 n-Link Linux and Android Technical Reference Manual
Version : 2.0
July 2020
15
4.2 Enabling a Protocol
Execute following command to enable required protocol(s):
# ./onebox_util rpine0 enable_protocol $protocol_value
Below are the possible values of protocol.
• 1 – Enables Wi-Fi only
• 2 – Enables Bluetooth only
• 3– Enables both Wi-Fi+Bluetooth
Note:
•If user selects only Wi-Fi in Menuconfig during the compilation of Driver, use the command below :
 sh wlan_enable.sh
•If user selects only Bluetooth in Menuconfig during thecompilation of Driver, use the command below :
 sh bt_enable.sh
•If user selects both Wi-Fi and Bluetooth in Menuconfig during thecompilation of Driver,use the command
below :
 sh wlan_bt_insert.sh
• If user selects all the protocols in Menuconfig during thecompilation of Driver, use the command below :
 sh onebox_insert.sh
 and need to run individual protocol enable scripts.
4.3 Disabling a Protocol
Execute he following command to disable required protocol(s):
# ./onebox_util rpine0 disable_protocol $protocol_value
• the possible values of protocol is same as mentioned in Enabling a Protocol.
Note:
•If user wants to disable only WLAN,use the command below :
 sh wlan_disable.sh
•If user wants to disable only Bluetooth,use the command below :
 sh bt_disable.sh
• If user wants to disable both WLAN and Bluetooth, use the command below :
 sh remove_all.sh
4.4 OneBox-Mobile in Wi-Fi Only Mode
The steps for starting the Wi-Fi Only mode in Client, AccessPoint and Wi-Fi Direct modes are as follows:
1. Open the common_insert.sh file present in the "release" folder.
Disabling of protocol is not recommended when Wi-Fi is operating in AccessPoint mode.


RS9116 n-Link Linux and Android Technical Reference Manual
Version : 2.0
July 2020
16
2. Ensure DRIVER_MODE and COEX_MODE are set as below:
•DRIVER_MODE = 1
•COEX_MODE = 1 (For Station Mode only/WIFI-Direct)
•COEX_MODE = 2 (For Access Point Mode)
• COEX_MODE = 3 (For BothAccess Point and Station Modes)
4.4.1 Installation in Wi-Fi Client Mode (with BSD interface support)
The steps for installing OneBox-Mobile software in Wi-Fi Client Mode are as follows:
1. Edit the "sta_settings.conf" file in the "release" folder and enter the parameters of the Wi-Fi network as
given below:
For Open (non-Secure) mode
network={
ssid="<SSID of Access Point>"
key_mgmt=NONE
}
For WPA-PSK (TKIP) mode
network={
ssid="<SSID of Access Point>"
key_mgmt=WPA-PSK
psk=<passphrase specified in the Access Point>
proto=WPA
pairwise=TKIP
group=TKIP
}
For WPA2-PSK (CCMP) mode
network={
ssid="<SSID of Access Point>"
key_mgmt=WPA-PSK
psk=<passphrase specified in the Access Point>
proto=WPA2
pairwise=CCMP
group=CCMP
}
For WEP-64 mode
For SDIO mode, ensure that the SDIO stack related modules are already inserted in the kernel
referAppendix A: Configuration of Kernels from 3.13 and above section to install sdio stack modules .


RS9116 n-Link Linux and Android Technical Reference Manual
Version : 2.0
July 2020
17
network={
ssid="<SSID of Access Point>"
key_mgmt=NONE
wep_key0=XXXXXXXXXX
wep_tx_keyidx=X
}
The key can be input either in ASCII or Hexadecimal formats:
ASCII Format: wep_key0="12345"
Hexadecimal Format: wep_key0=1234567890
The key index can vary between 0 and 3.
For WEP-128 mode
network={
ssid="<SSID of Access Point>"
key_mgmt=NONE
wep_key0=XXXXXXXXXXXXXXXXXXXXXXXXXX
wep_tx_keyidx=X
}
The key can be input either in ASCII or Hexadecimal formats:
ASCII Format: wep_key0="1234567890123"
Hexadecimal Format: wep_key0=12345678901234567890123456
The key index can vary between 0 and 3.
For WEP-Shared (64-bit) mode
network={
ssid="<SSID of Access Point>"
key_mgmt=NONE
wep_key0=XXXXXXXXXX
wep_tx_keyidx=X
auth_alg=SHARED
}
The key can be input either in ASCII or Hexadecimal formats:
ASCII Format: wep_key0="12345"
Hexadecimal Format: wep_key0=1234567890
The key index can vary between 0 and 3.
To connect to an Access Point whose SSID is not broadcast (Hidden), add the following line to the network block.
scan_ssid=1
For example

RS9116 n-Link Linux and Android Technical Reference Manual
Version : 2.0
July 2020
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 !


RS9116 n-Link Linux and Android Technical Reference Manual
Version : 2.0
July 2020
19
$ dhclient -r wifi0
$ dhclient -v wifi0
The sample output of dhclient command is given below
Listening on LPF/wifi0/88:da:1a:1e:b2:58
Sending on LPF/wifi0/88:da:1a:1e:b2:58
Sending on Socket/fallback
DHCPDISCOVER on wifi0 to 255.255.255.255 port 67 interval 4 (xid=0x133cec16)
DHCPREQUEST on wifi0 to 255.255.255.255 port 67 (xid=0x133cec16)
DHCPOFFER from 192.168.43.1
DHCPACK from 192.168.43.1 (xid=0x133cec16)
bound to 192.168.43.167 -- renewal in 1783 seconds
4.4.2 Installation in Access Point Mode (with BSD interface support)
The steps for installing OneBox-Mobile software in Access Point Mode are as follows:
1. The "start_ap.sh" script present in the "release" folder needs to be run with the different configuration
files present in the same folder in order to install an Access Point in different security modes.
# sh start_ap.sh <conf_file>
For example : sh start_ap.sh wpa_supplicant_open.conf
The different configuration files (.conf files) present in the "release" folder are as follows:
For Access Point in Open Mode, wpa_supplicant_open.conf configuration file is used, and this starts an Access
Point with the following parameters:
•SSID: REDPINE_AP
•Channel 1 of 2.4GHz Band (2412 MHz)
•Open (non-Secure) mode
For Access Point in WEP-64 Mode, wpa_supplicant_wep64.conf configuration file is used, and this starts an Access
Point with the following parameters:
•SSID: onebox_wep
•Channel 1 of 2.4GHz Band (2412 MHz)
•Security Mode: WEP-64
•WEP Key: 1234567890
•Key Index: 0
For Access Point in WEP-128 Mode, wpa_supplicant_wep128.conf configuration file is used, and this starts an
Access Point with the following parameters:
•SSID: onebox_wep
•Channel 1 of 2.4GHz Band (2412 MHz)
•Security Mode: WEP-128
•WEP Key: 12345678901234567890123456
•Key Index: 0
For Access Point in WPA-PSK (TKIP) Mode, wpa_supplicant_tkip.conf configuration file is used, and this starts an
Access Point with the following parameters:
•SSID: onebox_tkip

RS9116 n-Link Linux and Android Technical Reference Manual
Version : 2.0
July 2020
20
•Channel 1 of 2.4GHz Band (2412 MHz)
•Security Mode: WPA-PSK (TKIP)
•Passphrase: "12345678"
For Access Point in WPA2-PSK (CCMP) Mode, wpa_supplicant_ccmp.conf configuration file is used, and this starts
an Access Point with the following parameters:
•SSID: onebox_ccmp
•Channel 1 of 2.4GHz Band (2412 MHz)
•Security Mode: WPA2-PSK (CCMP)
•Passphrase: "12345678"
The Access Point does not support WEP-Shared algorithm in the current release.
 2. After running the "start_ap.sh" script a virtual interface with the name "wifi1" will be created. You can view
the list of interfaces using the following command:
ifconfig –a
You can check whether the Access Point has been started successfully or not, by running the following command:
iwconfig wifi1
The sample output of this command is
wifi1 IEEE 802.11bgn ESSID:"test" Nickname:""
Mode:Master Frequency:2.432 GHz Access Point: 88:DA:1A:16:E5:5D
Bit Rate:6 Mb/s Tx-Power=30 dBm Sensitivity=1/0
RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=80/80 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. It displays the Access Point's SSID along with the MAC address and
channel frequency. If the Access Point does not start, a message saying "Exiting: Driver Initialization not
completed even after waiting for xxms" is displayed.
To start a DHCP server, use the commands below.
sh dhcp_server.sh wifi1
Note:  If DHCP server is not present , we can also assign IP statically by using following command. Also it should be
noted that dhclient at connected clients will not work as dhcp server is not started at AP. We should assign IP
statically at client side also.
All the above mentioned parameters can be modified in the respective configuration files by the user. The
values provided in the above mentioned parameters are only for reference.
