Reference Manual

Redpine Signals, Inc. Proprietary and Confidential Page 78
RS9116 n-Link Linux and Android
Technical Reference Manual
Version 2.0
13.1.2 Creating VAP in AP mode
Create VAP in AP mode using command:
Ex:./onebox_util rpine0 create_vap wifi1 ap
After issuing the above command virtual interface with name “wifi1” will be created. User can view the list of interfaces
using the following command.
User needs to enable the appropriate network block settings with the information about the Access point configuration.
To configure the Access Point in different security modes use the configuration file settings. Please refer to the section on
Security for the configuration files for different security modes
Here the virtual interface name is referred as wifi1. User can create the virtual interface with any name of his choice
The steps to be followed in order to recognize the expected concurrent mode operation are outlined below:
1. Boot the RPINE device in STA mode and wait for it to connect to the 3rd party AP.
2. Then start the AP mode, and connect a 3rd party station.
3. In case the 3rd party AP shuts off, or the RPINE STA for some reason is disconnected, the STA will NOT move into
scan phase.
4. We can now scan for the 3rd party AP using the host based scan command,
"./onebox_util rpine0 host_scan <periodicity> <active scan duration> <no of channels>
<list of channels....>"
a. Periodicity : This parameter specifies the interval between the scans. The unit of this
field is seconds. Setting the value of this field as 0 will disable scans.
b. Active scan duration : This parameter determines the duration of the active scan in each channel during the on-
demand scan process. The recommended value for this parameter is 20ms for quicker scan operations and
uninterrupted throughput. The maximum allowed value for this parameter is 255ms.
c. No of channels : Specifies the no of channels to scan
d. List of channels : The list of channels in which the scan is to be performed
Example: ./onebox_util rpine0 host_scan 5 30 3 1 6 11.
This commands enables host based scan, with a periodicity of 5 seconds, active scan
duration of 30ms in the channels 1, 6 & 11.
1. Note, we do not have support for passive scan duration as of now.
2. When the STA is successfully able to connect to the AP, the user can stop the scan by setting the periodicity to "0".
3. Even if the user DOES NOT stop the scan after the RPINE STA is connected to the AP, use of the scan command on
successive disconnections is a MUST.
The host_scan command should be issued only when the AP VAP is also UP.
It is also possible that STA can connect to the 3rd party AP without host_scan command and having AP VAP already
UP. This case is possible due to the process that STA will continuously listen to beacons being received in the present
channel. If any AP beacon matches with sta_settings, STA will start connection procedure. But for this to happen 3rd
party AP should also be in the same channel in which RSI AP & RSI STA are UP.