Changes

Jump to: navigation, search

FTMr configuration

10,949 bytes added, 13:27, 28 November 2018
Created page with "= Configuration overview = The FTM Responder device is pre-assemble with software image on SD Card installed on the FTMR device (e.g. Compulab Fitlet2). The so..."
= Configuration overview =
The FTM Responder device is pre-assemble with software image on SD Card
installed on the FTMR device (e.g. Compulab Fitlet2).

The software image based on Yocto BSP for Intel E3900 is pre compiled
with Intel AC8260 WIFI driver supporting 11mcFTM Responder mode,
Bluetooth driver for AC8260 and set of network services to enable out of
the box operation. A user can deploy the device with default setting, apply
power and the FTMR device will boot automatically and start operate. You
will be able to scan with your mobile and detect the FTM Responder device
as well measure FTM Ranges from our mobile few minutes after FTMR is
power on. For transferring data via FTMR device, please refer to the above
chapters describing network topology deployment and backhauling mode
and configuration. If there is no backhaul connected to the FTMR device, the
FTMR device will automatically serve responding to Wi-Fi location range
measurements request sent by mobile devices supporting 11mcFTM and
certified by the WIFI Alliance for Wi-Fi Location .

The following sub chapters describe the out of the box configuration as well
parameters that the user can change within the FTM Responder device.

In order to connect to the FTM Responder device you shall use remote PC
connect to the FTMR via SSH.

Note: Changing parameters within FTM Responder is only for qualified
technician who is familiar with FTMR device technical details.

= Out of the Box Configuration =
1) Wi-Fi Backhaul (BH) – Association with a Wi-Fi network:

The FTM Responder device will search automatically for an access point (AP)
named “INTC_FTMR1”, with password “WCSLCDFTMR”, operating at 5GHz
band.
If such an external access point detected, the FTM Responder will connect
and associate to the Access Point and use the AP’s Wi-Fi channel for FTM
and SoftAP. In case the FTMR device does not detect the external access
point configured for FTMR Wi-Fi Backhauling, the FTM Responder device will
restart its Backhauling interface and try to reactivate it every 15 minutes,
searching for an External Access point with SSID defined in the FTMR file
/etc/wpa_supplicant.conf.

2) FTM Responder device Wi-Fi SoftAP : a Wi-Fi interface enabling for
mobile devices to associate and transfer data over Wi-Fi network created
by the FTM Responder device:

Channel is set according to Backhauling of the external Access point that the
FTMR will be associated (in case of Wi-Fi backhaul mode). Note: If the
external Access point with specific SSID defined for FTMR Wi-Fi Backhauling
is not in the RF range of standard radio signal between the External Access
point / Router and FTMR the FTMR will not associate automatically to the
external Wi-Fi Access point.
In case the FTMR is not associated after boot to external Access point (Wi-Fi
Backhauling),the SoftAP and FTM Wi-Fi channel set in /etc/hostapd.conf will
be used. Default channel defined in the hostapd.conf for “out of the box” is
CH48 (Freq. 5240 MHz).

i. Channel Bandwidth (BW) : 80MHz.
ii. SSID#1 (SoftAP) : DO_NOT_CONNECT
note: this is the SSID that a mobile device can be associate in
order to transfer data over Wi-Fi via the FTM Responder device in
case a backhauling is connected to the FTMR device.
You can change SSID#1 name to another name in all the
hostapd.conf files within all the FTMR responder devices in case
you prefer to use other SSID#1 name.
iii. Password (for SSID#1): responders

Out of the box values (in the hostapd.conf file):

Parameter name |Out of the box value
--------------------|--------------------
Interface wlp1s0
Channel 48
vht_oper_chwidth 1 (80 MHz)
(channel BW)
SSID (#1, SoftAP) DO_NOT_CONNECT
ht_capab [SMPS-DISABLED][HT40-]
Hw_mode A

= FTM Responder: Configuring parameters =
In case there is a need to configure the FTMR parameters, this can be by
configuring the following files.

There are 3 files that the a qualified technician and System integrator who
deploy FTM Responder devices in a venue can edit, in order to set the
deployment parameters different than the out of the box deployment:

1) WPA_supplicant.conf

This file holds the data on the SSID (SSID#2 of the External Access point
allocated for Wi-Fi Backhauling) and Password of the external Access
point that the FTMR to be associated in order to establish a Wi-Fi
backhaul network connection between the FTMR and the external
nearby access point.
Note: in case you want to ensure No automatic connection of Wi-Fi
Backhauling established, you can define a SSID#2 with a name that the
FTMR will never be able to associate to external Access Point

File is located at /etc/wpa_supplicant.conf

Parameter Out of the Box
WiFi BH SSID (#2) INTC_FTMR1
WiFi BH Password WCSLCDFTMR

2) Hostapd.conf

This file holds all parameters of the SoftAP that is visible to the user from
the responders network.

File is located at /etc/hostapd.conf.

Parameter Out of the Box settings
interface wlp1s0
channel 48
vht_oper_chwidth 1 (80 MHz)
(channel BW)
SSID (#1, SoftAP) DO_NOT_CONNECT
ht_capab [SMPS-DISABLED][HT40-]
Hw_mode a


3) Iwlwifi.conf

In this file, it is possible to enable / disable the Wi-Fi Firmware behavior,
using some parameters

File is located at /etc/modprobe.d/iwlwifi.conf.

Parameter Out of the Box settings
CAM mode options iwlmvm power_scheme=1
enabled
ASAP mode options iwlwifi ftm_resp_asap=1
enabled
Read options iwlwifi nvm_file="nvm-sfp-b2-open.bin” - COMMENTED
configurations
from bin file is
disabled

The end 2 end topology to serve multi-client by single FTM Responder
optimize when FTM Responder are set to operate in ASAP mode (this
mode is define in the 802.11REVmc protocol).

In case you want to verify that the configuration is set to ASAP mode:
check the file, by running “cat /etc/modprobe.d/iwlwifi.conf”
The file should contain the following lines:
options iwlmvm power_scheme=1
options iwlwifi ftm_resp_asap=1

= FTMR Configuration: Changing channel and BW =
The “out of the box” configuration of the FTM Responder software is set to
5Ghz band CH48 , 80Mhz Channel Bandwidth.

For 5Ghz band, it is recommended to use channels 36, 40, 44, 48. Other
channels that allowed per country regulation are subject to WW regulatory
requirements.
Note that in order to comply WW regulatory, some channels are not
supported (e.g. DFS channels are not supported), or channels are per
Country regulation.

Modifying channel and BW is possible and done by editing hostapd.conf
that resides within the GalileGen2 FTM Responder device.

File location: /etc/hostapd.conf

== Change SoftAP channel ==
a. Edit line:
# If CONFIG_ACS build option is enabled, the channel can be selected
# automatically at run time by setting channel=acs_survey or channel=0, both of
# which will enable the ACS survey based algorithm.
channel=48
Change the number to the desired channel
b. Edit line:
ht_capab=[SMPS-DISABLED][HT40=]
Change the sign (HT40+/-) according to table A (next page).

== Change channel bandwidth ==
=== For 80 MHz ===
<pre>
a.
# ieee80211ac: Whether IEEE 802.11ac (VHT) is enabled
# 0 = disabled (default)
# 1 = enabled
# Note: You will also need to enable WMM for full VHT functionality.
ieee80211ac=1
b.
# 0 = 20 or 40 MHz operating Channel width
# 1 = 80 MHz channel width
# 2 = 160 MHz channel width
# 3 = 80+80 MHz channel width
vht_oper_chwidth=1
</pre>
=== For 40 MHz ===
<pre>
a.
# ieee80211ac: Whether IEEE 802.11ac (VHT) is enabled
# 0 = disabled (default)
# 1 = enabled
# Note: You will also need to enable WMM for full VHT functionality.
ieee80211ac=0

b.
# 0 = 20 or 40 MHz operating Channel width
# 1 = 80 MHz channel width
# 2 = 160 MHz channel width
# 3 = 80+80 MHz channel width
vht_oper_chwidth=0
</pre>
=== For 20 MHz ===
edit same as for 40 MHz, and also<br>
<pre>
c.
ht_capab=[SORT-GI-20]
d.
require_ht=0
</pre>

=== Table A: HT Capability Signs ===

Channel HT Sign
36 +
40 -
44 +
48 -
52 +
56 -
60 +
64 -
68 +
72 -
76 +
80 -
84 +
88 -
92 +
96 -
100 +
104 -
108 +
112 -
116 +
120 -
124 +
128 -
132 +
136 -
140 +
144 -
149 +
153 -
157 +
161 -
165 +
169 -
173 +
177 -
57
edits