https://fit-pc.com/wiki/api.php?action=feedcontributions&user=Valentin&feedformat=atomfit-PC wiki - User contributions [en]2024-03-29T10:19:11ZUser contributionsMediaWiki 1.25.2https://fit-pc.com/wiki/index.php?title=WiFi_Indoor_Location_Device_(WILD)_software&diff=7110WiFi Indoor Location Device (WILD) software2019-04-29T04:43:37Z<p>Valentin: /* Boot */</p>
<hr />
<div>= Overview =<br />
The Wi-Fi location technology is based on a protocol specified in 802.11mc-FTM (IEEE 802.11mc-2016 technical Specification) which defines the Fine-Timing-Measurement (FTM) procedure between a mobile device (FTM '''initiator''') and a network infrastructure device (FTM '''responder''' / FTMR)<br><br />
The protocol allows:<br />
* Initiator to exchange FTM packets without the need to be associated with a Wi-Fi Access Point.<br />
* Co-existance of SoftAP functionality and FTM ranging in both initiator and responder.<br />
<br />
== Hardware platform ==<br />
WILD is based on Compulab fitlet2 with Intel AC8260 WiFi module<br />
<br />
= Getting started =<br />
== Deployment ==<br />
CopmpuLab provides a raw image that can be deployed onto the following bootable media.<br />
* SD-Card<br />
* USB flash disk<br />
* Internal SATA SSD / HDD (not covered by this man page)<br />
* Internal eMMC (not covered by this man page)<br />
CompuLab installation procedure must be invoked in order to deploy the image onto a removable media.<br />
# Download the latest WILD image - see [[WILD revision notes]] and consult associated readme.<br />
# To deploy on a desktop PC:<br />
{| border="2" cellpadding="0" width="100%" align="center" <br />
|-<br />
! style="font-size: 125%; background-color: #eeeeee;" align="left" width="15%" | OS<br />
! style="font-size: 125%; background-color: #eeeeee;" align="left" width="85%" | How To<br />
|-<br />
| align="" |<br />
Linux<br />
| align="" |<br />
* Make sure that the removable device was recognized by the host. Issue:<br />
udevadm monitor --subsystem-match=block --kernel<br />
* Insert the device, wait for the udevadm report:<br />
udevadm monitor --subsystem-match=block<br />
monitor will print the received events for:<br />
UDEV - the event which udev sends out after rule processing<br />
KERNEL - the kernel uevent<br />
KERNEL[37893.873104] add /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/host3/target3:0:0/3:0:0:0/block/sdc (block)<br />
KERNEL[37893.873136] add /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/host3/target3:0:0/3:0:0:0/block/sdc/sdc1 (block)<br />
KERNEL[37893.873161] add /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/host3/target3:0:0/3:0:0:0/block/sdc/sdc2 (block)<br />
* The device was recognized as '''/dev/sdc'''.<br />
* Terminate the '''udevadm''' session; press '''Ctrl-C'''; continue to the next step.<br />
* Issue this command:<br />
'''<span style="color:#FF0000">Important:</span>'''<br /><br />
The '''dd''' command will destroy all data stored on the '''/dev/sdc'''.<br />
xz -dc /path/to/4G-wild.img.xz | sudo dd of=/dev/sdc bs=1M status=progress<br />
'''<span style="color:#FF0000">Important:</span>'''<br /><br />
The device name in the command above is just an example. Take a real device name from the udevadm report on your desktop.<br />
|-<br />
| align="" |<br />
Windows<br />
| align="" |<br />
Make use of '''Rufus'''.<br />
Refer to the vendor site for details: https://rufus.akeo.ie/<br />
|}<br />
<br />
== Boot ==<br />
* Allow the device to boot from the bootable FTM media.<br />
* Login with one of the default users: <br />
{| border="2" cellpadding="0" width="100%" align="center" <br />
|-<br />
! style="font-size: 125%; background-color: #eeeeee;" align="left" width="50%" | User Name<br />
! style="font-size: 125%; background-color: #eeeeee;" align="left" width="50%" | Password<br />
|-<br />
| align="" |<br />
compulab<br />
| align="" |<br />
compulab<br />
| align="" |<br />
|}<br />
<br />
* To acquire '''root''' credentials:<br />
sudo -i<br />
== ftm-services ==<br />
* Intro<br />
'''ftm-services''' is a set of the CompuLab scripts for managing FTM devices.<br />
* History<br />
{| border="2" cellpadding="0" width="100%" align="center" <br />
|-<br />
! style="font-size: 125%; background-color: #eeeeee;" align="left" width="20%" | WILD Version<br />
! style="font-size: 125%; background-color: #eeeeee;" align="left" width="80%" | Description<br />
|-<br />
| align="" |<br />
< 0.70<br />
| align="" |<br />
Delivered as a set of services installed onto the rootfs, but w/out being registered as a deb package in the Debian package manager. <br />
| align="" |<br />
|-<br />
| align="" |<br />
>= 0.70<br />
| align="" |<br />
Starting from the 0.70 version these services come as a deb package with the same name.<br />
| align="" |<br />
|}<br />
* Install/Update procedure<br />
cd /tmp<br />
wget https://www.fit-iot.com/files/download/wild/0.7.2/ftm-services_0.7.2.deb<br />
sudo dpkg -i /tmp/ftm-services_0.7.2.deb<br />
<br />
= Commands =<br />
<br />
== wild ==<br />
This is an FTM management command. Refer to the command man page for details.<br />
wild command is available in WILD version 0.7 and later.<br />
<pre><br />
man wild<br />
</pre><br />
<br />
=== Get WILD version ===<br />
<pre><br />
wild -v<br />
</pre><br />
=== Set WILD to initiator mode ===<br />
<pre><br />
wild -mi<br />
</pre><br />
=== Set WILD to responder mode ===<br />
<pre><br />
wild -mr<br />
</pre><br />
=== Set WILD to off mode ===<br />
<pre><br />
wild -mo<br />
</pre><br />
Neither initiator or responder commands are available in this mode.<br />
<br />
== ftm-role (depreciated) ==<br />
See [[WILD depreciated commands]]<br />
<br />
== ftm-options ==<br />
When in '''client''' mode, scan responders and enable / disable specific responders for ranging requests<br />
<pre><br />
ftm-options<br />
</pre><br />
<br />
== ftm-show ==<br />
* '''Client''': show the results of ranging request.<br />
* '''Responder''': show the FTM requests statistics.<br />
<pre><br />
ftm-show<br />
</pre><br />
<br />
= FTMR (FTM Responder) =<br />
== Configuration files ==<br />
=== hostapd configuration file ===<br />
* /etc/hostapd.conf<br />
Used for setting FTMR properties e.g.<br />
# SSID - to brodcast when in '''responder''' mode<br />
# Channel and bandwidth<br />
=== Change channel bandwidth ===<br />
{| border="2" cellpadding="0" width="100%" align="center" <br />
|-<br />
! style="font-size: 125%; background-color: #eeeeee;" align="left" width="33%" | 80MHz<br />
! style="font-size: 125%; background-color: #eeeeee;" align="left" width="33%" | 40MHz<br />
! style="font-size: 125%; background-color: #eeeeee;" align="left" width="33%" | 20MHz<br />
|-<br />
| align="" |<br />
ieee80211ac=1<br><br />
vht_oper_chwidth=1<br><br />
| align="" |<br />
ieee80211ac=0<br><br />
vht_oper_chwidth=0<br><br />
| align="" |<br />
ieee80211ac=0<br><br />
vht_oper_chwidth=0<br><br />
ht_capab=[SORT-GI-20]<br><br />
require_ht=0<br><br />
|}<br />
<br />
=== Change band ===<br />
{| border="2" cellpadding="0" width="100%" align="center" <br />
|-<br />
! style="font-size: 125%; background-color: #eeeeee;" align="left" width="50%" | 2.4GHz<br />
! style="font-size: 125%; background-color: #eeeeee;" align="left" width="50%" | 5.0GHz<br />
|-<br />
| align="" |<br />
hw_mode=g<br><br />
ieee80211n=1<br><br />
| align="" |<br />
hw_mode=a<br><br />
ieee80211n=1<br><br />
ieee80211ac=1<br><br />
|}<br />
<br />
For more information about the ''hostapd.conf'' parameters refer to: https://w1.fi/cgit/hostap/plain/hostapd/hostapd.conf<br />
<br />
=== Configuration Manual ===<br />
For more information refer to: [[FTMr_configuration|FTMr configuration]]<br />
<br />
== FTMR Network Configuration ==<br />
* Interfaces<br />
The device network configuration described by '''/etc/network/interfaces'''<br><br />
Below is an configuration example that configures the '''br0''' at the boot time.<br><br />
<pre><br />
# interfaces(5) file used by ifup(8) and ifdown(8)<br />
# Include files from /etc/network/interfaces.d:<br />
source-directory /etc/network/interfaces.d<br />
<br />
auto lo<br />
iface lo inet loopback<br />
<br />
# closest to the edge<br />
# a spare network interface (can be disconnected)<br />
# Roles:<br />
# 1: a generic network interface<br />
auto enp2s0<br />
allow-hotplug enp2s0<br />
iface enp2s0 inet manual<br />
<br />
# closest to the power plug<br />
# Roles:<br />
# 1: a part of bridge<br />
# 2: a generic network interface<br />
auto enp3s0<br />
allow-hotplug enp3s0<br />
iface enp3s0 inet dhcp<br />
<br />
auto wlan0<br />
allow-hotplug wlan0<br />
iface wlan0 inet manual<br />
<br />
# Bridge Setup<br />
# This is a bridge interface<br />
# gets turned on when device is a responder<br />
# auto br0<br />
iface br0 inet dhcp<br />
bridge_ports wlan0 enp3s0<br />
</pre><br />
* Bridge configuration<br />
Make use of the '''brctl''' for details.<br />
<pre><br />
brctl show<br />
bridge name bridge id STP enabled interfaces<br />
br0 8000.0001c01fd60c no enp3s0<br />
wlan0<br />
</pre><br />
<br />
== FTMR Backhaul ==<br />
All FTM device has two wired interfaces.<br><br />
'''<span style="color:#FF0000">Important:</span>'''<br /><br />
The wired interfaces configured as '''auto & dhcp''' must be connected to the LAN at the boot time.<br><br />
Otherwise the device will experience a boot delay.<br />
<br />
== FTMR Transmit Location Data ==<br />
* Configuration file: '''/opt/compulab/service/ftm-common'''<br />
Contains the SERVERS list to send the scan results file :'''/opt/compulab/www/results.al'''l<br />
<pre><br />
SERVERS=(http://localhost/cpl/curl.php http://wild-server/hard/curl.php)<br />
</pre><br />
* FTM ranged service: '''/opt/compulab/service/ftm-range.main'''<br />
The service walks through the SERVERSs' list and send the scan results to each one:<br />
<pre><br />
for SERVER in ${SERVERS[@]};do<br />
curl -d @${iw_scan}/results.all ${SERVER} &>/dev/null<br />
done<br />
</pre><br />
<br />
== FTMR SoftAP ==<br />
Intel 8260 can work as an FTMR & a SoftAP simultaneously.<br />
<br />
=== SoftAP services ===<br />
There are two services that must be configured & run in order to provide the SoftAP functionality:<br />
<br />
* bridge<br />
'''FTM bridge''' service is in charge of configuring a bridge between '''wlp1s0''' (i8260) and '''enp3s0''' interfaces.<br><br />
It allows all wireless interface requests to get forwarded to the '''enp3s0'''.<br>The '''enp3s0''' interface must be connected to the LAN.<br><br />
'''FTM bridge''' service starts automatically while in '''responder''' mode. In order to control it manually: '''start/stop/status/disable''', issue:<br />
<pre>systemctl start/stop/status/disable ftm-br</pre><br />
<br />
* hostapd<br />
The '''hostapd''' daemon turns the device into a '''SoftAP''' while in a '''responder''' mode.<br />
<br><br><br />
How to get connected to the '''SoftAP''' wireless network:<br />
# Scan wireless networks;<br />
# Try to get connected to a network with name '''COMPULAB_WILD''' password '''indoorlocation'''.<br />
# In case that the bridge service is up and running the wireless clients will get connected to the LAN.<br />
<br />
'''SoftAP''' know issues:<br />
<br />
# The backhaul interface '''enp3s0''' is down. Wireless clients can't get connected to the '''SoftAP'''. The client software reports on '''Connecting''' state.<br />
# '''ftm-br''' service is stopped. Wireless clients can't get connected to the '''SoftAP'''. The client software reports on '''Connecting''' state.<br />
<br />
= FTMI (FTM Initiator) =<br />
== FTM services configuration file (initiator/client mode)==<br />
* /opt/compulab/service/ftm-common<br />
{| border="2" cellpadding="0" width="100%" align="center" <br />
|-<br />
! style="font-size: 125%; background-color: #eeeeee;" align="left" width="15%" | Field<br />
! style="font-size: 125%; background-color: #eeeeee;" align="left" width="85%" | Description<br />
|-<br />
| align="" |<br />
FTM_SSID<br />
| align="" |<br />
List of the AP SSIDs to scan & send range requests when in '''client''' mode.<br />
Match condition 'FTM_SSID[x] ~ discovered_ssid'.<br />
For instance the hostapd.conf file SSID="COMPULAB-"+serial_number, then the FTM_SSID must be FTM_SSID="COMPULAB-".<br />
The match condition turns 'true' and '''client''' takes this '''responder''' into account.<br />
|-<br />
| align="" |<br />
BW=80; TOF="bw=${BW} cf=5240 cf1=5210 spb=2 asap"<br />
| align="" |<br />
Template of a TOF string. The '''ftm-range''' service makes use of this when in '''client''' mode.<br />
BW=80 works for both 40 MHz & 80 MHz bandwidth modes.<br />
BW=40 does not work at all. The '''client''' receives empty replies from the '''responders''' if BW=40.<br />
|}<br />
<br />
= See Also =<br />
* [[WiFi Indoor Location Device (WILD) | WILD technical documentation root]]<br />
* [[WILD revision notes]]<br />
* [https://fit-iot.com/web/products/wild WILD homepage]<br />
<br />
[[Category:WILD]]</div>Valentinhttps://fit-pc.com/wiki/index.php?title=WiFi_Indoor_Location_Device_(WILD)_software&diff=7029WiFi Indoor Location Device (WILD) software2019-03-21T12:39:32Z<p>Valentin: /* Utilities */</p>
<hr />
<div>= Overview =<br />
The Wi-Fi location technology is based on a protocol specified in 802.11mc-FTM (IEEE 802.11mc-2016 technical Specification) which defines the Fine-Timing-Measurement (FTM) procedure between a mobile device (FTM '''initiator''') and a network infrastructure device (FTM '''responder''' / FTMR)<br><br />
The protocol allows:<br />
* Initiator to exchange FTM packets without the need to be associated with a Wi-Fi Access Point.<br />
* Co-existance of SoftAP functionality and FTM ranging in both initiator and responder.<br />
<br />
== Hardware platform ==<br />
WILD is based on Compulab fitlet2 with Intel AC8260 WiFi module<br />
<br />
= Getting started =<br />
== Deployment ==<br />
CopmpuLab provides a raw image that can be deployed onto the following bootable media.<br />
* SD-Card<br />
* USB flash disk<br />
* Internal SATA SSD / HDD (not covered by this man page)<br />
* Internal eMMC (not covered by this man page)<br />
CompuLab installation procedure must be invoked in order to deploy the image onto a removable media.<br />
# Download the latest [https://www.fit-iot.com/files/download/wild/4G-wild.img.xz CompuLab WILD Image].<br />
# To deploy on a desktop PC:<br />
{| border="2" cellpadding="0" width="100%" align="center" <br />
|-<br />
! style="font-size: 125%; background-color: #eeeeee;" align="left" width="15%" | OS<br />
! style="font-size: 125%; background-color: #eeeeee;" align="left" width="85%" | How To<br />
|-<br />
| align="" |<br />
Linux<br />
| align="" |<br />
* Make sure that the removable device was recognized by the host. Issue:<br />
udevadm monitor --subsystem-match=block --kernel<br />
* Insert the device, wait for the udevadm report:<br />
udevadm monitor --subsystem-match=block<br />
monitor will print the received events for:<br />
UDEV - the event which udev sends out after rule processing<br />
KERNEL - the kernel uevent<br />
KERNEL[37893.873104] add /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/host3/target3:0:0/3:0:0:0/block/sdc (block)<br />
KERNEL[37893.873136] add /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/host3/target3:0:0/3:0:0:0/block/sdc/sdc1 (block)<br />
KERNEL[37893.873161] add /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/host3/target3:0:0/3:0:0:0/block/sdc/sdc2 (block)<br />
* The device was recognized as '''/dev/sdc'''.<br />
* Terminate the '''udevadm''' session; press '''Ctrl-C'''; continue to the next step.<br />
* Issue this command:<br />
'''<span style="color:#FF0000">Important:</span>'''<br /><br />
The '''dd''' command will destroy all data stored on the '''/dev/sdc'''.<br />
xz -dc /path/to/4G-wild.img.xz | sudo dd of=/dev/sdc bs=1M status=progress<br />
'''<span style="color:#FF0000">Important:</span>'''<br /><br />
The device name in the command above is just an example. Take a real device name from the udevadm report on your desktop.<br />
|-<br />
| align="" |<br />
Windows<br />
| align="" |<br />
Make use of '''Rufus'''.<br />
Refer to the vendor site for details: https://rufus.akeo.ie/<br />
|}<br />
<br />
== Boot ==<br />
* Allow the device to boot from the bootable FTM media.<br />
* Login with one of the default users: <br />
{| border="2" cellpadding="0" width="100%" align="center" <br />
|-<br />
! style="font-size: 125%; background-color: #eeeeee;" align="left" width="50%" | User Name<br />
! style="font-size: 125%; background-color: #eeeeee;" align="left" width="50%" | Password<br />
|-<br />
| align="" |<br />
support<br />
| align="" |<br />
support<br />
| align="" |<br />
|}<br />
<br />
* To acquire '''root''' credentials:<br />
sudo -i<br />
<br />
= Utilities =<br />
== ftm-role ==<br />
Select WILD mode (initiator / responder)<br />
<pre><br />
ftm-role<br />
</pre><br />
* '''Client''': set WILD to initiator mode<br />
* '''Responder''': set WILD to responder mode (default)<br />
* '''Dumb''': silent mode with no FTM activity<br />
<br />
== ftm-options ==<br />
When in '''client''' mode, scan responders and enable / disable specific responders for ranging requests<br />
<pre><br />
ftm-options<br />
</pre><br />
<br />
== ftm-show ==<br />
* '''Client''': show the results of ranging request.<br />
* '''Responder''': show the FTM requests statistics.<br />
<pre><br />
ftm-show<br />
</pre><br />
<br />
== wild ==<br />
This is an FTM management command. Refer to the command man page for details.<br />
<pre><br />
man wild<br />
</pre><br />
<br />
=== Useful commands ===<br />
* Get version<br />
<pre><br />
wild -v<br />
</pre><br />
* Set client mode<br />
<pre><br />
wild -mi<br />
</pre><br />
* Set responder mode<br />
<pre><br />
wild -mr<br />
</pre><br />
* Set off mode<br />
<pre><br />
wild -mo<br />
</pre><br />
<br />
= FTMR (FTM Responder) =<br />
== Configuration files ==<br />
=== hostapd configuration file ===<br />
* /etc/hostapd.conf<br />
Used for setting FTMR properties e.g.<br />
# SSID - to brodcast when in '''responder''' mode<br />
# Channel and bandwidth<br />
=== Change channel bandwidth ===<br />
{| border="2" cellpadding="0" width="100%" align="center" <br />
|-<br />
! style="font-size: 125%; background-color: #eeeeee;" align="left" width="33%" | 80MHz<br />
! style="font-size: 125%; background-color: #eeeeee;" align="left" width="33%" | 40MHz<br />
! style="font-size: 125%; background-color: #eeeeee;" align="left" width="33%" | 20MHz<br />
|-<br />
| align="" |<br />
ieee80211ac=1<br><br />
vht_oper_chwidth=1<br><br />
| align="" |<br />
ieee80211ac=0<br><br />
vht_oper_chwidth=0<br><br />
| align="" |<br />
ieee80211ac=0<br><br />
vht_oper_chwidth=0<br><br />
ht_capab=[SORT-GI-20]<br><br />
require_ht=0<br><br />
|}<br />
<br />
=== Change band ===<br />
{| border="2" cellpadding="0" width="100%" align="center" <br />
|-<br />
! style="font-size: 125%; background-color: #eeeeee;" align="left" width="50%" | 2.4GHz<br />
! style="font-size: 125%; background-color: #eeeeee;" align="left" width="50%" | 5.0GHz<br />
|-<br />
| align="" |<br />
hw_mode=g<br><br />
ieee80211n=1<br><br />
| align="" |<br />
hw_mode=a<br><br />
ieee80211n=1<br><br />
ieee80211ac=1<br><br />
|}<br />
<br />
For more information about the ''hostapd.conf'' parameters refer to: https://w1.fi/cgit/hostap/plain/hostapd/hostapd.conf<br />
<br />
=== Configuration Manual ===<br />
For more information refer to: [[FTMr_configuration|FTMr configuration]]<br />
<br />
== FTMR Network Configuration ==<br />
* Interfaces<br />
The device network configuration described by '''/etc/network/interfaces'''<br><br />
Below is an configuration example that configures the '''br0''' at the boot time.<br><br />
<pre><br />
# interfaces(5) file used by ifup(8) and ifdown(8)<br />
# Include files from /etc/network/interfaces.d:<br />
source-directory /etc/network/interfaces.d<br />
<br />
auto lo<br />
iface lo inet loopback<br />
<br />
# closest to the edge<br />
# a spare network interface (can be disconnected)<br />
# Roles:<br />
# 1: a generic network interface<br />
auto enp2s0<br />
allow-hotplug enp2s0<br />
iface enp2s0 inet manual<br />
<br />
# closest to the power plug<br />
# Roles:<br />
# 1: a part of bridge<br />
# 2: a generic network interface<br />
auto enp3s0<br />
allow-hotplug enp3s0<br />
iface enp3s0 inet dhcp<br />
<br />
auto wlan0<br />
allow-hotplug wlan0<br />
iface wlan0 inet manual<br />
<br />
# Bridge Setup<br />
# This is a bridge interface<br />
# gets turned on when device is a responder<br />
# auto br0<br />
iface br0 inet dhcp<br />
bridge_ports wlan0 enp3s0<br />
</pre><br />
* Bridge configuration<br />
Make use of the '''brctl''' for details.<br />
<pre><br />
brctl show<br />
bridge name bridge id STP enabled interfaces<br />
br0 8000.0001c01fd60c no enp3s0<br />
wlan0<br />
</pre><br />
<br />
== FTMR Backhaul ==<br />
All FTM device has two wired interfaces.<br><br />
'''<span style="color:#FF0000">Important:</span>'''<br /><br />
The wired interfaces configured as '''auto & dhcp''' must be connected to the LAN at the boot time.<br><br />
Otherwise the device will experience a boot delay.<br />
<br />
== FTMR Transmit Location Data ==<br />
* Configuration file: '''/opt/compulab/service/ftm-common'''<br />
Contains the SERVERS list to send the scan results file :'''/opt/compulab/www/results.al'''l<br />
<pre><br />
SERVERS=(http://localhost/cpl/curl.php http://wild-server/hard/curl.php)<br />
</pre><br />
* FTM ranged service: '''/opt/compulab/service/ftm-range.main'''<br />
The service walks through the SERVERSs' list and send the scan results to each one:<br />
<pre><br />
for SERVER in ${SERVERS[@]};do<br />
curl -d @${iw_scan}/results.all ${SERVER} &>/dev/null<br />
done<br />
</pre><br />
<br />
== FTMR SoftAP ==<br />
Intel 8260 can work as an FTMR & a SoftAP simultaneously.<br />
<br />
=== SoftAP services ===<br />
There are two services that must be configured & run in order to provide the SoftAP functionality:<br />
<br />
* bridge<br />
'''FTM bridge''' service is in charge of configuring a bridge between '''wlp1s0''' (i8260) and '''enp3s0''' interfaces.<br><br />
It allows all wireless interface requests to get forwarded to the '''enp3s0'''.<br>The '''enp3s0''' interface must be connected to the LAN.<br><br />
'''FTM bridge''' service starts automatically while in '''responder''' mode. In order to control it manually: '''start/stop/status/disable''', issue:<br />
<pre>systemctl start/stop/status/disable ftm-br</pre><br />
<br />
* hostapd<br />
The '''hostapd''' daemon turns the device into a '''SoftAP''' while in a '''responder''' mode.<br />
<br><br><br />
How to get connected to the '''SoftAP''' wireless network:<br />
# Scan wireless networks;<br />
# Try to get connected to a network with name '''COMPULAB_WILD''' password '''indoorlocation'''.<br />
# In case that the bridge service is up and running the wireless clients will get connected to the LAN.<br />
<br />
'''SoftAP''' know issues:<br />
<br />
# The backhaul interface '''enp3s0''' is down. Wireless clients can't get connected to the '''SoftAP'''. The client software reports on '''Connecting''' state.<br />
# '''ftm-br''' service is stopped. Wireless clients can't get connected to the '''SoftAP'''. The client software reports on '''Connecting''' state.<br />
<br />
= FTMI (FTM Initiator) =<br />
== FTM services configuration file (initiator/client mode)==<br />
* /opt/compulab/service/ftm-common<br />
{| border="2" cellpadding="0" width="100%" align="center" <br />
|-<br />
! style="font-size: 125%; background-color: #eeeeee;" align="left" width="15%" | Field<br />
! style="font-size: 125%; background-color: #eeeeee;" align="left" width="85%" | Description<br />
|-<br />
| align="" |<br />
FTM_SSID<br />
| align="" |<br />
List of the AP SSIDs to scan & send range requests when in '''client''' mode.<br />
Match condition 'FTM_SSID[x] ~ discovered_ssid'.<br />
For instance the hostapd.conf file SSID="COMPULAB-"+serial_number, then the FTM_SSID must be FTM_SSID="COMPULAB-".<br />
The match condition turns 'true' and '''client''' takes this '''responder''' into account.<br />
|-<br />
| align="" |<br />
BW=80; TOF="bw=${BW} cf=5240 cf1=5210 spb=2 asap"<br />
| align="" |<br />
Template of a TOF string. The '''ftm-range''' service makes use of this when in '''client''' mode.<br />
BW=80 works for both 40 MHz & 80 MHz bandwidth modes.<br />
BW=40 does not work at all. The '''client''' receives empty replies from the '''responders''' if BW=40.<br />
|}<br />
<br />
= See Also =<br />
* [[WiFi Indoor Location Device (WILD) | WILD technical documentation root]]<br />
* [https://fit-iot.com/web/products/wild WILD homepage]</div>Valentinhttps://fit-pc.com/wiki/index.php?title=WiFi_Indoor_Location_Device_(WILD)_software&diff=6971WiFi Indoor Location Device (WILD) software2019-02-27T06:57:47Z<p>Valentin: /* FTMR Backhaul */</p>
<hr />
<div>= Overview =<br />
The Wi-Fi location technology is based on a protocol specified in 802.11mc-FTM (IEEE 802.11mc-2016 technical Specification) which defines the Fine-Timing-Measurement (FTM) procedure between a mobile device (FTM '''initiator''') and a network infrastructure device (FTM '''responder''' / FTMR)<br><br />
The protocol allows:<br />
* Initiator to exchange FTM packets without the need to be associated with a Wi-Fi Access Point.<br />
* Co-existance of SoftAP functionality and FTM ranging in both initiator and responder.<br />
<br />
== Hardware platform ==<br />
WILD is based on Compulab fitlet2 with Intel AC8260 WiFi module<br />
<br />
= Getting started =<br />
== Deployment ==<br />
CopmpuLab provides a raw image that can be deployed onto the following bootable media.<br />
* SD-Card<br />
* USB flash disk<br />
* Internal SATA SSD / HDD (not covered by this man page)<br />
* Internal eMMC (not covered by this man page)<br />
CompuLab installation procedure must be invoked in order to deploy the image onto a removable media.<br />
# Download the latest [https://www.fit-iot.com/files/download/wild/4G-wild.img.xz CompuLab WILD Image].<br />
# To deploy on a desktop PC:<br />
{| border="2" cellpadding="0" width="100%" align="center" <br />
|-<br />
! style="font-size: 125%; background-color: #eeeeee;" align="left" width="15%" | OS<br />
! style="font-size: 125%; background-color: #eeeeee;" align="left" width="85%" | How To<br />
|-<br />
| align="" |<br />
Linux<br />
| align="" |<br />
* Make sure that the removable device was recognized by the host. Issue:<br />
udevadm monitor --subsystem-match=block --kernel<br />
* Insert the device, wait for the udevadm report:<br />
udevadm monitor --subsystem-match=block<br />
monitor will print the received events for:<br />
UDEV - the event which udev sends out after rule processing<br />
KERNEL - the kernel uevent<br />
KERNEL[37893.873104] add /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/host3/target3:0:0/3:0:0:0/block/sdc (block)<br />
KERNEL[37893.873136] add /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/host3/target3:0:0/3:0:0:0/block/sdc/sdc1 (block)<br />
KERNEL[37893.873161] add /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/host3/target3:0:0/3:0:0:0/block/sdc/sdc2 (block)<br />
* The device was recognized as '''/dev/sdc'''.<br />
* Terminate the '''udevadm''' session; press '''Ctrl-C'''; continue to the next step.<br />
* Issue this command:<br />
'''<span style="color:#FF0000">Important:</span>'''<br /><br />
The '''dd''' command will destroy all data stored on the '''/dev/sdc'''.<br />
xz -dc /path/to/4G-wild.img.xz | sudo dd of=/dev/sdc bs=1M status=progress<br />
'''<span style="color:#FF0000">Important:</span>'''<br /><br />
The device name in the command above is just an example. Take a real device name from the udevadm report on your desktop.<br />
|-<br />
| align="" |<br />
Windows<br />
| align="" |<br />
Make use of '''Rufus'''.<br />
Refer to the vendor site for details: https://rufus.akeo.ie/<br />
|}<br />
<br />
== Boot ==<br />
* Allow the device to boot from the bootable FTM media.<br />
* Login with one of the default users: <br />
{| border="2" cellpadding="0" width="100%" align="center" <br />
|-<br />
! style="font-size: 125%; background-color: #eeeeee;" align="left" width="50%" | User Name<br />
! style="font-size: 125%; background-color: #eeeeee;" align="left" width="50%" | Password<br />
|-<br />
| align="" |<br />
support<br />
| align="" |<br />
support<br />
| align="" |<br />
|-<br />
| align="" |<br />
compulab<br />
| align="" |<br />
compulab<br />
| align="" |<br />
|}<br />
'''<span style="color:#FF0000">Important:</span>''' the '''compulab''' login can be not available in all WILD image revisions.<br />
<br />
* To acquire '''root''' credentials:<br />
sudo -i<br />
<br />
= Utilities =<br />
== ftm-role ==<br />
Select WILD mode (initiator / responder)<br />
<pre><br />
ftm-role<br />
</pre><br />
* '''Client''': set WILD to initiator mode<br />
* '''Responder''': set WILD to responder mode (default)<br />
* '''Dumb''': silent mode with no FTM activity<br />
<br />
== ftm-options ==<br />
When in '''client''' mode, scan responders and enable / disable specific responders for ranging requests<br />
<pre><br />
ftm-options<br />
</pre><br />
<br />
== ftm-show ==<br />
* '''Client''': show the results of ranging request.<br />
* '''Responder''': show the FTM requests statistics.<br />
<pre><br />
ftm-show<br />
</pre><br />
<br />
= FTMR (FTM Responder) =<br />
== Configuration files ==<br />
=== hostapd configuration file ===<br />
* /etc/hostapd.conf<br />
Used for setting FTMR properties e.g.<br />
# SSID - to brodcast when in '''responder''' mode<br />
# Channel and bandwidth<br />
=== Change channel bandwidth ===<br />
{| border="2" cellpadding="0" width="100%" align="center" <br />
|-<br />
! style="font-size: 125%; background-color: #eeeeee;" align="left" width="33%" | 80MHz<br />
! style="font-size: 125%; background-color: #eeeeee;" align="left" width="33%" | 40MHz<br />
! style="font-size: 125%; background-color: #eeeeee;" align="left" width="33%" | 20MHz<br />
|-<br />
| align="" |<br />
ieee80211ac=1<br><br />
vht_oper_chwidth=1<br><br />
| align="" |<br />
ieee80211ac=0<br><br />
vht_oper_chwidth=0<br><br />
| align="" |<br />
ieee80211ac=0<br><br />
vht_oper_chwidth=0<br><br />
ht_capab=[SORT-GI-20]<br><br />
require_ht=0<br><br />
|}<br />
<br />
=== Change band ===<br />
{| border="2" cellpadding="0" width="100%" align="center" <br />
|-<br />
! style="font-size: 125%; background-color: #eeeeee;" align="left" width="50%" | 2.4GHz<br />
! style="font-size: 125%; background-color: #eeeeee;" align="left" width="50%" | 5.0GHz<br />
|-<br />
| align="" |<br />
hw_mode=g<br><br />
ieee80211n=1<br><br />
| align="" |<br />
hw_mode=a<br><br />
ieee80211n=1<br><br />
ieee80211ac=1<br><br />
|}<br />
<br />
For more information about the ''hostapd.conf'' parameters refer to: https://w1.fi/cgit/hostap/plain/hostapd/hostapd.conf<br />
<br />
=== Configuration Manual ===<br />
For more information refer to: [[FTMr_configuration|FTMr configuration]]<br />
<br />
== FTMR Network Configuration ==<br />
* Interfaces<br />
The device network configuration described by '''/etc/network/interfaces'''<br><br />
Below is an configuration example that configures the '''br0''' at the boot time.<br><br />
<pre><br />
# interfaces(5) file used by ifup(8) and ifdown(8)<br />
# Include files from /etc/network/interfaces.d:<br />
source-directory /etc/network/interfaces.d<br />
<br />
auto lo<br />
iface lo inet loopback<br />
<br />
# closest to the edge<br />
# a spare network interface (can be disconnected)<br />
# Roles:<br />
# 1: a generic network interface<br />
auto enp2s0<br />
allow-hotplug enp2s0<br />
iface enp2s0 inet manual<br />
<br />
# closest to the power plug<br />
# Roles:<br />
# 1: a part of bridge<br />
# 2: a generic network interface<br />
auto enp3s0<br />
allow-hotplug enp3s0<br />
iface enp3s0 inet dhcp<br />
<br />
auto wlan0<br />
allow-hotplug wlan0<br />
iface wlan0 inet manual<br />
<br />
# Bridge Setup<br />
# This is a bridge interface<br />
# gets turned on when device is a responder<br />
# auto br0<br />
iface br0 inet dhcp<br />
bridge_ports wlan0 enp3s0<br />
</pre><br />
* Bridge configuration<br />
Make use of the '''brctl''' for details.<br />
<pre><br />
brctl show<br />
bridge name bridge id STP enabled interfaces<br />
br0 8000.0001c01fd60c no enp3s0<br />
wlan0<br />
</pre><br />
<br />
== FTMR Backhaul ==<br />
All FTM device has two wired interfaces.<br><br />
'''<span style="color:#FF0000">Important:</span>'''<br /><br />
The wired interfaces configured as '''auto & dhcp''' must be connected to the LAN at the boot time.<br><br />
Otherwise the device will experience a boot delay.<br />
<br />
== FTMR Transmit Location Data ==<br />
* Configuration file: '''/opt/compulab/service/ftm-common'''<br />
Contains the SERVERS list to send the scan results file :'''/opt/compulab/www/results.al'''l<br />
<pre><br />
SERVERS=(http://localhost/cpl/curl.php http://wild-server/hard/curl.php)<br />
</pre><br />
* FTM ranged service: '''/opt/compulab/service/ftm-range.main'''<br />
The service walks through the SERVERSs' list and send the scan results to each one:<br />
<pre><br />
for SERVER in ${SERVERS[@]};do<br />
curl -d @${iw_scan}/results.all ${SERVER} &>/dev/null<br />
done<br />
</pre><br />
<br />
== FTMR SoftAP ==<br />
Intel 8260 can work as an FTMR & a SoftAP simultaneously.<br />
<br />
=== SoftAP services ===<br />
There are two services that must be configured & run in order to provide the SoftAP functionality:<br />
<br />
* bridge<br />
'''FTM bridge''' service is in charge of configuring a bridge between '''wlp1s0''' (i8260) and '''enp3s0''' interfaces.<br><br />
It allows all wireless interface requests to get forwarded to the '''enp3s0'''.<br>The '''enp3s0''' interface must be connected to the LAN.<br><br />
'''FTM bridge''' service starts automatically while in '''responder''' mode. In order to control it manually: '''start/stop/status/disable''', issue:<br />
<pre>systemctl start/stop/status/disable ftm-br</pre><br />
<br />
* hostapd<br />
The '''hostapd''' daemon turns the device into a '''SoftAP''' while in a '''responder''' mode.<br />
<br><br><br />
How to get connected to the '''SoftAP''' wireless network:<br />
# Scan wireless networks;<br />
# Try to get connected to a network with name '''COMPULAB_WILD''' password '''indoorlocation'''.<br />
# In case that the bridge service is up and running the wireless clients will get connected to the LAN.<br />
<br />
'''SoftAP''' know issues:<br />
<br />
# The backhaul interface '''enp3s0''' is down. Wireless clients can't get connected to the '''SoftAP'''. The client software reports on '''Connecting''' state.<br />
# '''ftm-br''' service is stopped. Wireless clients can't get connected to the '''SoftAP'''. The client software reports on '''Connecting''' state.<br />
<br />
= FTMI (FTM Initiator) =<br />
== FTM services configuration file (initiator/client mode)==<br />
* /opt/compulab/service/ftm-common<br />
{| border="2" cellpadding="0" width="100%" align="center" <br />
|-<br />
! style="font-size: 125%; background-color: #eeeeee;" align="left" width="15%" | Field<br />
! style="font-size: 125%; background-color: #eeeeee;" align="left" width="85%" | Description<br />
|-<br />
| align="" |<br />
FTM_SSID<br />
| align="" |<br />
List of the AP SSIDs to scan & send range requests when in '''client''' mode.<br />
Match condition 'FTM_SSID[x] ~ discovered_ssid'.<br />
For instance the hostapd.conf file SSID="COMPULAB-"+serial_number, then the FTM_SSID must be FTM_SSID="COMPULAB-".<br />
The match condition turns 'true' and '''client''' takes this '''responder''' into account.<br />
|-<br />
| align="" |<br />
BW=80; TOF="bw=${BW} cf=5240 cf1=5210 spb=2 asap"<br />
| align="" |<br />
Template of a TOF string. The '''ftm-range''' service makes use of this when in '''client''' mode.<br />
BW=80 works for both 40 MHz & 80 MHz bandwidth modes.<br />
BW=40 does not work at all. The '''client''' receives empty replies from the '''responders''' if BW=40.<br />
|}<br />
<br />
= See Also =<br />
* [[WiFi Indoor Location Device (WILD) | WILD technical documentation root]]<br />
* [https://fit-iot.com/web/products/wild WILD homepage]</div>Valentinhttps://fit-pc.com/wiki/index.php?title=WiFi_Indoor_Location_Device_(WILD)_software&diff=6829WiFi Indoor Location Device (WILD) software2018-12-17T15:23:41Z<p>Valentin: </p>
<hr />
<div></div>Valentinhttps://fit-pc.com/wiki/index.php?title=WiFi_Indoor_Location_Device_(WILD)_software&diff=6828WiFi Indoor Location Device (WILD) software2018-12-17T15:16:40Z<p>Valentin: </p>
<hr />
<div></div>Valentinhttps://fit-pc.com/wiki/index.php?title=WiFi_Indoor_Location_Device_(WILD)_software&diff=6775WiFi Indoor Location Device (WILD) software2018-12-03T05:53:38Z<p>Valentin: </p>
<hr />
<div></div>Valentinhttps://fit-pc.com/wiki/index.php?title=WiFi_Indoor_Location_Device_(WILD)_software&diff=6774WiFi Indoor Location Device (WILD) software2018-12-03T05:52:41Z<p>Valentin: </p>
<hr />
<div></div>Valentinhttps://fit-pc.com/wiki/index.php?title=WiFi_Indoor_Location_Device_(WILD)_software&diff=6773WiFi Indoor Location Device (WILD) software2018-12-03T05:50:57Z<p>Valentin: </p>
<hr />
<div></div>Valentinhttps://fit-pc.com/wiki/index.php?title=FTMr_configuration&diff=6772FTMr configuration2018-12-03T05:45:49Z<p>Valentin: </p>
<hr />
<div>= Configuration overview =<br />
The FTM Responder device is pre-assemble with software image on SD Card<br />
installed on the FTMR device (e.g. Compulab Fitlet2).<br />
<br />
The software image based on Yocto BSP for Intel E3900 is pre compiled<br />
with Intel AC8260 WIFI driver supporting 11mcFTM Responder mode,<br />
Bluetooth driver for AC8260 and set of network services to enable out of<br />
the box operation. A user can deploy the device with default setting, apply<br />
power and the FTMR device will boot automatically and start operate. You<br />
will be able to scan with your mobile and detect the FTM Responder device<br />
as well measure FTM Ranges from our mobile few minutes after FTMR is<br />
power on. For transferring data via FTMR device, please refer to the above<br />
chapters describing network topology deployment and backhauling mode<br />
and configuration. If there is no backhaul connected to the FTMR device, the<br />
FTMR device will automatically serve responding to Wi-Fi location range<br />
measurements request sent by mobile devices supporting 11mcFTM and<br />
certified by the WIFI Alliance for Wi-Fi Location .<br />
<br />
The following sub chapters describe the out of the box configuration as well<br />
parameters that the user can change within the FTM Responder device.<br />
<br />
In order to connect to the FTM Responder device you shall use remote PC<br />
connect to the FTMR via SSH.<br />
<br />
Note: Changing parameters within FTM Responder is only for qualified<br />
technician who is familiar with FTMR device technical details.<br />
<br />
= Out of the Box Configuration =<br />
1) Wi-Fi Backhaul (BH) – Association with a Wi-Fi network:<br />
<br />
The FTM Responder device will search automatically for an access point (AP)<br />
named “INTC_FTMR1”, with password “WCSLCDFTMR”, operating at 5GHz<br />
band.<br />
If such an external access point detected, the FTM Responder will connect<br />
and associate to the Access Point and use the AP’s Wi-Fi channel for FTM<br />
and SoftAP. In case the FTMR device does not detect the external access<br />
point configured for FTMR Wi-Fi Backhauling, the FTM Responder device will<br />
restart its Backhauling interface and try to reactivate it every 15 minutes,<br />
searching for an External Access point with SSID defined in the FTMR file<br />
/etc/wpa_supplicant.conf.<br />
<br />
2) FTM Responder device Wi-Fi SoftAP : a Wi-Fi interface enabling for<br />
mobile devices to associate and transfer data over Wi-Fi network created<br />
by the FTM Responder device:<br />
<br />
Channel is set according to Backhauling of the external Access point that the<br />
FTMR will be associated (in case of Wi-Fi backhaul mode). Note: If the<br />
external Access point with specific SSID defined for FTMR Wi-Fi Backhauling<br />
is not in the RF range of standard radio signal between the External Access<br />
point / Router and FTMR the FTMR will not associate automatically to the<br />
external Wi-Fi Access point.<br />
In case the FTMR is not associated after boot to external Access point (Wi-Fi<br />
Backhauling),the SoftAP and FTM Wi-Fi channel set in /etc/hostapd.conf will<br />
be used. Default channel defined in the hostapd.conf for “out of the box” is<br />
CH48 (Freq. 5240 MHz).<br />
<br />
i. Channel Bandwidth (BW) : 80MHz.<br />
ii. SSID#1 (SoftAP) : DO_NOT_CONNECT<br />
note: this is the SSID that a mobile device can be associate in<br />
order to transfer data over Wi-Fi via the FTM Responder device in<br />
case a backhauling is connected to the FTMR device.<br />
You can change SSID#1 name to another name in all the<br />
hostapd.conf files within all the FTMR responder devices in case<br />
you prefer to use other SSID#1 name.<br />
iii. Password (for SSID#1): responders<br />
<br />
Out of the box values (in the hostapd.conf file):<br />
<br />
Parameter name |Out of the box value<br />
--------------------|--------------------<br />
Interface wlp1s0<br />
Channel 48<br />
vht_oper_chwidth 1 (80 MHz)<br />
(channel BW)<br />
SSID (#1, SoftAP) DO_NOT_CONNECT<br />
ht_capab [SMPS-DISABLED][HT40-]<br />
hw_mode A<br />
<br />
= FTM Responder: Configuring parameters =<br />
In case there is a need to configure the FTMR parameters, this can be by<br />
configuring the following files.<br />
<br />
There are 3 files that the a qualified technician and System integrator who<br />
deploy FTM Responder devices in a venue can edit, in order to set the<br />
deployment parameters different than the out of the box deployment:<br />
<br />
1) WPA_supplicant.conf<br />
<br />
This file holds the data on the SSID (SSID#2 of the External Access point<br />
allocated for Wi-Fi Backhauling) and Password of the external Access<br />
point that the FTMR to be associated in order to establish a Wi-Fi<br />
backhaul network connection between the FTMR and the external<br />
nearby access point.<br />
Note: in case you want to ensure No automatic connection of Wi-Fi<br />
Backhauling established, you can define a SSID#2 with a name that the<br />
FTMR will never be able to associate to external Access Point<br />
<br />
File is located at /etc/wpa_supplicant.conf<br />
<br />
Parameter Out of the Box<br />
WiFi BH SSID (#2) INTC_FTMR1 <br />
WiFi BH Password WCSLCDFTMR <br />
<br />
2) Hostapd.conf<br />
<br />
This file holds all parameters of the SoftAP that is visible to the user from<br />
the responders network.<br />
<br />
File is located at /etc/hostapd.conf.<br />
<br />
Parameter Out of the Box settings<br />
interface wlp1s0 <br />
channel 48 <br />
vht_oper_chwidth 1 (80 MHz) <br />
(channel BW)<br />
SSID (#1, SoftAP) DO_NOT_CONNECT <br />
ht_capab [SMPS-DISABLED][HT40-]<br />
hw_mode a <br />
<br />
<br />
3) Iwlwifi.conf<br />
<br />
In this file, it is possible to enable / disable the Wi-Fi Firmware behavior,<br />
using some parameters<br />
<br />
File is located at /etc/modprobe.d/iwlwifi.conf.<br />
<br />
Parameter Out of the Box settings<br />
CAM mode options iwlmvm power_scheme=1<br />
enabled<br />
ASAP mode options iwlwifi ftm_resp_asap=1<br />
enabled<br />
Read options iwlwifi nvm_file="nvm-sfp-b2-open.bin” - COMMENTED<br />
configurations <br />
from bin file is<br />
disabled<br />
<br />
The end 2 end topology to serve multi-client by single FTM Responder<br />
optimize when FTM Responder are set to operate in ASAP mode (this<br />
mode is define in the 802.11REVmc protocol).<br />
<br />
In case you want to verify that the configuration is set to ASAP mode:<br />
check the file, by running “cat /etc/modprobe.d/iwlwifi.conf”<br />
The file should contain the following lines:<br />
options iwlmvm power_scheme=1<br />
options iwlwifi ftm_resp_asap=1<br />
<br />
= FTMR Configuration: Changing channel and BW =<br />
The “out of the box” configuration of the FTM Responder software is set to<br />
5Ghz band CH48 , 80Mhz Channel Bandwidth.<br />
<br />
For 5Ghz band, it is recommended to use channels 36, 40, 44, 48. Other<br />
channels that allowed per country regulation are subject to WW regulatory<br />
requirements.<br />
Note that in order to comply WW regulatory, some channels are not<br />
supported (e.g. DFS channels are not supported), or channels are per<br />
Country regulation.<br />
<br />
Modifying channel and BW is possible and done by editing hostapd.conf<br />
that resides within the GalileGen2 FTM Responder device.<br />
<br />
File location: /etc/hostapd.conf<br />
<br />
== Change SoftAP channel ==<br />
a. Edit line:<br />
# If CONFIG_ACS build option is enabled, the channel can be selected<br />
# automatically at run time by setting channel=acs_survey or channel=0, both of<br />
# which will enable the ACS survey based algorithm.<br />
channel=48<br />
Change the number to the desired channel<br />
b. Edit line:<br />
ht_capab=[SMPS-DISABLED][HT40=]<br />
Change the sign (HT40+/-) according to table A (next page).<br />
<br />
== Change channel bandwidth ==<br />
=== For 80 MHz ===<br />
<pre><br />
a.<br />
# ieee80211ac: Whether IEEE 802.11ac (VHT) is enabled<br />
# 0 = disabled (default)<br />
# 1 = enabled<br />
# Note: You will also need to enable WMM for full VHT functionality.<br />
ieee80211ac=1<br />
b.<br />
# 0 = 20 or 40 MHz operating Channel width<br />
# 1 = 80 MHz channel width<br />
# 2 = 160 MHz channel width<br />
# 3 = 80+80 MHz channel width<br />
vht_oper_chwidth=1<br />
</pre><br />
=== For 40 MHz ===<br />
<pre><br />
a.<br />
# ieee80211ac: Whether IEEE 802.11ac (VHT) is enabled<br />
# 0 = disabled (default)<br />
# 1 = enabled<br />
# Note: You will also need to enable WMM for full VHT functionality.<br />
ieee80211ac=0<br />
<br />
b.<br />
# 0 = 20 or 40 MHz operating Channel width<br />
# 1 = 80 MHz channel width<br />
# 2 = 160 MHz channel width<br />
# 3 = 80+80 MHz channel width<br />
vht_oper_chwidth=0<br />
</pre><br />
=== For 20 MHz ===<br />
edit same as for 40 MHz, and also<br><br />
<pre><br />
c.<br />
ht_capab=[SORT-GI-20]<br />
d.<br />
require_ht=0<br />
</pre><br />
<br />
=== Table A: HT Capability Signs ===<br />
<br />
Channel HT Sign<br />
36 +<br />
40 -<br />
44 +<br />
48 -<br />
52 +<br />
56 -<br />
60 +<br />
64 -<br />
68 +<br />
72 -<br />
76 +<br />
80 -<br />
84 +<br />
88 -<br />
92 +<br />
96 -<br />
100 +<br />
104 -<br />
108 +<br />
112 -<br />
116 +<br />
120 -<br />
124 +<br />
128 -<br />
132 +<br />
136 -<br />
140 +<br />
144 -<br />
149 +<br />
153 -<br />
157 +<br />
161 -<br />
165 +<br />
169 -<br />
173 +<br />
177 -</div>Valentinhttps://fit-pc.com/wiki/index.php?title=WiFi_Indoor_Location_Device_(WILD)_software&diff=6770WiFi Indoor Location Device (WILD) software2018-11-28T13:30:54Z<p>Valentin: </p>
<hr />
<div></div>Valentinhttps://fit-pc.com/wiki/index.php?title=FTMr_configuration&diff=6769FTMr configuration2018-11-28T13:27:31Z<p>Valentin: 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..."</p>
<hr />
<div>= Configuration overview =<br />
The FTM Responder device is pre-assemble with software image on SD Card<br />
installed on the FTMR device (e.g. Compulab Fitlet2).<br />
<br />
The software image based on Yocto BSP for Intel E3900 is pre compiled<br />
with Intel AC8260 WIFI driver supporting 11mcFTM Responder mode,<br />
Bluetooth driver for AC8260 and set of network services to enable out of<br />
the box operation. A user can deploy the device with default setting, apply<br />
power and the FTMR device will boot automatically and start operate. You<br />
will be able to scan with your mobile and detect the FTM Responder device<br />
as well measure FTM Ranges from our mobile few minutes after FTMR is<br />
power on. For transferring data via FTMR device, please refer to the above<br />
chapters describing network topology deployment and backhauling mode<br />
and configuration. If there is no backhaul connected to the FTMR device, the<br />
FTMR device will automatically serve responding to Wi-Fi location range<br />
measurements request sent by mobile devices supporting 11mcFTM and<br />
certified by the WIFI Alliance for Wi-Fi Location .<br />
<br />
The following sub chapters describe the out of the box configuration as well<br />
parameters that the user can change within the FTM Responder device.<br />
<br />
In order to connect to the FTM Responder device you shall use remote PC<br />
connect to the FTMR via SSH.<br />
<br />
Note: Changing parameters within FTM Responder is only for qualified<br />
technician who is familiar with FTMR device technical details.<br />
<br />
= Out of the Box Configuration =<br />
1) Wi-Fi Backhaul (BH) – Association with a Wi-Fi network:<br />
<br />
The FTM Responder device will search automatically for an access point (AP)<br />
named “INTC_FTMR1”, with password “WCSLCDFTMR”, operating at 5GHz<br />
band.<br />
If such an external access point detected, the FTM Responder will connect<br />
and associate to the Access Point and use the AP’s Wi-Fi channel for FTM<br />
and SoftAP. In case the FTMR device does not detect the external access<br />
point configured for FTMR Wi-Fi Backhauling, the FTM Responder device will<br />
restart its Backhauling interface and try to reactivate it every 15 minutes,<br />
searching for an External Access point with SSID defined in the FTMR file<br />
/etc/wpa_supplicant.conf.<br />
<br />
2) FTM Responder device Wi-Fi SoftAP : a Wi-Fi interface enabling for<br />
mobile devices to associate and transfer data over Wi-Fi network created<br />
by the FTM Responder device:<br />
<br />
Channel is set according to Backhauling of the external Access point that the<br />
FTMR will be associated (in case of Wi-Fi backhaul mode). Note: If the<br />
external Access point with specific SSID defined for FTMR Wi-Fi Backhauling<br />
is not in the RF range of standard radio signal between the External Access<br />
point / Router and FTMR the FTMR will not associate automatically to the<br />
external Wi-Fi Access point.<br />
In case the FTMR is not associated after boot to external Access point (Wi-Fi<br />
Backhauling),the SoftAP and FTM Wi-Fi channel set in /etc/hostapd.conf will<br />
be used. Default channel defined in the hostapd.conf for “out of the box” is<br />
CH48 (Freq. 5240 MHz).<br />
<br />
i. Channel Bandwidth (BW) : 80MHz.<br />
ii. SSID#1 (SoftAP) : DO_NOT_CONNECT<br />
note: this is the SSID that a mobile device can be associate in<br />
order to transfer data over Wi-Fi via the FTM Responder device in<br />
case a backhauling is connected to the FTMR device.<br />
You can change SSID#1 name to another name in all the<br />
hostapd.conf files within all the FTMR responder devices in case<br />
you prefer to use other SSID#1 name.<br />
iii. Password (for SSID#1): responders<br />
<br />
Out of the box values (in the hostapd.conf file):<br />
<br />
Parameter name |Out of the box value<br />
--------------------|--------------------<br />
Interface wlp1s0<br />
Channel 48<br />
vht_oper_chwidth 1 (80 MHz)<br />
(channel BW)<br />
SSID (#1, SoftAP) DO_NOT_CONNECT<br />
ht_capab [SMPS-DISABLED][HT40-]<br />
Hw_mode A<br />
<br />
= FTM Responder: Configuring parameters =<br />
In case there is a need to configure the FTMR parameters, this can be by<br />
configuring the following files.<br />
<br />
There are 3 files that the a qualified technician and System integrator who<br />
deploy FTM Responder devices in a venue can edit, in order to set the<br />
deployment parameters different than the out of the box deployment:<br />
<br />
1) WPA_supplicant.conf<br />
<br />
This file holds the data on the SSID (SSID#2 of the External Access point<br />
allocated for Wi-Fi Backhauling) and Password of the external Access<br />
point that the FTMR to be associated in order to establish a Wi-Fi<br />
backhaul network connection between the FTMR and the external<br />
nearby access point.<br />
Note: in case you want to ensure No automatic connection of Wi-Fi<br />
Backhauling established, you can define a SSID#2 with a name that the<br />
FTMR will never be able to associate to external Access Point<br />
<br />
File is located at /etc/wpa_supplicant.conf<br />
<br />
Parameter Out of the Box<br />
WiFi BH SSID (#2) INTC_FTMR1 <br />
WiFi BH Password WCSLCDFTMR <br />
<br />
2) Hostapd.conf<br />
<br />
This file holds all parameters of the SoftAP that is visible to the user from<br />
the responders network.<br />
<br />
File is located at /etc/hostapd.conf.<br />
<br />
Parameter Out of the Box settings<br />
interface wlp1s0 <br />
channel 48 <br />
vht_oper_chwidth 1 (80 MHz) <br />
(channel BW)<br />
SSID (#1, SoftAP) DO_NOT_CONNECT <br />
ht_capab [SMPS-DISABLED][HT40-]<br />
Hw_mode a <br />
<br />
<br />
3) Iwlwifi.conf<br />
<br />
In this file, it is possible to enable / disable the Wi-Fi Firmware behavior,<br />
using some parameters<br />
<br />
File is located at /etc/modprobe.d/iwlwifi.conf.<br />
<br />
Parameter Out of the Box settings<br />
CAM mode options iwlmvm power_scheme=1<br />
enabled<br />
ASAP mode options iwlwifi ftm_resp_asap=1<br />
enabled<br />
Read options iwlwifi nvm_file="nvm-sfp-b2-open.bin” - COMMENTED<br />
configurations <br />
from bin file is<br />
disabled<br />
<br />
The end 2 end topology to serve multi-client by single FTM Responder<br />
optimize when FTM Responder are set to operate in ASAP mode (this<br />
mode is define in the 802.11REVmc protocol).<br />
<br />
In case you want to verify that the configuration is set to ASAP mode:<br />
check the file, by running “cat /etc/modprobe.d/iwlwifi.conf”<br />
The file should contain the following lines:<br />
options iwlmvm power_scheme=1<br />
options iwlwifi ftm_resp_asap=1<br />
<br />
= FTMR Configuration: Changing channel and BW =<br />
The “out of the box” configuration of the FTM Responder software is set to<br />
5Ghz band CH48 , 80Mhz Channel Bandwidth.<br />
<br />
For 5Ghz band, it is recommended to use channels 36, 40, 44, 48. Other<br />
channels that allowed per country regulation are subject to WW regulatory<br />
requirements.<br />
Note that in order to comply WW regulatory, some channels are not<br />
supported (e.g. DFS channels are not supported), or channels are per<br />
Country regulation.<br />
<br />
Modifying channel and BW is possible and done by editing hostapd.conf<br />
that resides within the GalileGen2 FTM Responder device.<br />
<br />
File location: /etc/hostapd.conf<br />
<br />
== Change SoftAP channel ==<br />
a. Edit line:<br />
# If CONFIG_ACS build option is enabled, the channel can be selected<br />
# automatically at run time by setting channel=acs_survey or channel=0, both of<br />
# which will enable the ACS survey based algorithm.<br />
channel=48<br />
Change the number to the desired channel<br />
b. Edit line:<br />
ht_capab=[SMPS-DISABLED][HT40=]<br />
Change the sign (HT40+/-) according to table A (next page).<br />
<br />
== Change channel bandwidth ==<br />
=== For 80 MHz ===<br />
<pre><br />
a.<br />
# ieee80211ac: Whether IEEE 802.11ac (VHT) is enabled<br />
# 0 = disabled (default)<br />
# 1 = enabled<br />
# Note: You will also need to enable WMM for full VHT functionality.<br />
ieee80211ac=1<br />
b.<br />
# 0 = 20 or 40 MHz operating Channel width<br />
# 1 = 80 MHz channel width<br />
# 2 = 160 MHz channel width<br />
# 3 = 80+80 MHz channel width<br />
vht_oper_chwidth=1<br />
</pre><br />
=== For 40 MHz ===<br />
<pre><br />
a.<br />
# ieee80211ac: Whether IEEE 802.11ac (VHT) is enabled<br />
# 0 = disabled (default)<br />
# 1 = enabled<br />
# Note: You will also need to enable WMM for full VHT functionality.<br />
ieee80211ac=0<br />
<br />
b.<br />
# 0 = 20 or 40 MHz operating Channel width<br />
# 1 = 80 MHz channel width<br />
# 2 = 160 MHz channel width<br />
# 3 = 80+80 MHz channel width<br />
vht_oper_chwidth=0<br />
</pre><br />
=== For 20 MHz ===<br />
edit same as for 40 MHz, and also<br><br />
<pre><br />
c.<br />
ht_capab=[SORT-GI-20]<br />
d.<br />
require_ht=0<br />
</pre><br />
<br />
=== Table A: HT Capability Signs ===<br />
<br />
Channel HT Sign<br />
36 +<br />
40 -<br />
44 +<br />
48 -<br />
52 +<br />
56 -<br />
60 +<br />
64 -<br />
68 +<br />
72 -<br />
76 +<br />
80 -<br />
84 +<br />
88 -<br />
92 +<br />
96 -<br />
100 +<br />
104 -<br />
108 +<br />
112 -<br />
116 +<br />
120 -<br />
124 +<br />
128 -<br />
132 +<br />
136 -<br />
140 +<br />
144 -<br />
149 +<br />
153 -<br />
157 +<br />
161 -<br />
165 +<br />
169 -<br />
173 +<br />
177 -</div>Valentinhttps://fit-pc.com/wiki/index.php?title=WiFi_Indoor_Location_Device_(WILD)_software&diff=6768WiFi Indoor Location Device (WILD) software2018-11-28T13:06:33Z<p>Valentin: </p>
<hr />
<div></div>Valentinhttps://fit-pc.com/wiki/index.php?title=WiFi_Indoor_Location_Device_(WILD)_software&diff=6767WiFi Indoor Location Device (WILD) software2018-11-28T12:44:37Z<p>Valentin: </p>
<hr />
<div></div>Valentinhttps://fit-pc.com/wiki/index.php?title=WiFi_Indoor_Location_Device_(WILD)_software&diff=6728WiFi Indoor Location Device (WILD) software2018-11-20T07:47:45Z<p>Valentin: </p>
<hr />
<div></div>Valentinhttps://fit-pc.com/wiki/index.php?title=WiFi_Indoor_Location_Device_(WILD)_software&diff=6727WiFi Indoor Location Device (WILD) software2018-11-20T07:44:28Z<p>Valentin: </p>
<hr />
<div></div>Valentinhttps://fit-pc.com/wiki/index.php?title=WiFi_Indoor_Location_Device_(WILD)_software&diff=6551WiFi Indoor Location Device (WILD) software2018-10-12T10:18:24Z<p>Valentin: </p>
<hr />
<div></div>Valentinhttps://fit-pc.com/wiki/index.php?title=WiFi_Indoor_Location_Device_(WILD)_software&diff=6550WiFi Indoor Location Device (WILD) software2018-10-12T10:17:51Z<p>Valentin: </p>
<hr />
<div></div>Valentinhttps://fit-pc.com/wiki/index.php?title=WiFi_Indoor_Location_Device_(WILD)_software&diff=6549WiFi Indoor Location Device (WILD) software2018-10-12T10:16:38Z<p>Valentin: </p>
<hr />
<div></div>Valentinhttps://fit-pc.com/wiki/index.php?title=WiFi_Indoor_Location_Device_(WILD)_software&diff=6548WiFi Indoor Location Device (WILD) software2018-10-12T10:14:17Z<p>Valentin: </p>
<hr />
<div></div>Valentinhttps://fit-pc.com/wiki/index.php?title=WiFi_Indoor_Location_Device_(WILD)_software&diff=6547WiFi Indoor Location Device (WILD) software2018-10-12T10:13:55Z<p>Valentin: </p>
<hr />
<div></div>Valentinhttps://fit-pc.com/wiki/index.php?title=WiFi_Indoor_Location_Device_(WILD)_software&diff=6546WiFi Indoor Location Device (WILD) software2018-10-12T09:24:15Z<p>Valentin: </p>
<hr />
<div></div>Valentinhttps://fit-pc.com/wiki/index.php?title=WiFi_Indoor_Location_Device_(WILD)_software&diff=6476WiFi Indoor Location Device (WILD) software2018-10-09T10:50:13Z<p>Valentin: </p>
<hr />
<div></div>Valentinhttps://fit-pc.com/wiki/index.php?title=WiFi_Indoor_Location_Device_(WILD)_software&diff=6466WiFi Indoor Location Device (WILD) software2018-10-09T08:42:47Z<p>Valentin: </p>
<hr />
<div></div>Valentinhttps://fit-pc.com/wiki/index.php?title=WiFi_Indoor_Location_Device_(WILD)_software&diff=6243WiFi Indoor Location Device (WILD) software2018-09-12T14:52:38Z<p>Valentin: </p>
<hr />
<div></div>Valentinhttps://fit-pc.com/wiki/index.php?title=WiFi_Indoor_Location_Device_(WILD)_software&diff=6242WiFi Indoor Location Device (WILD) software2018-09-12T14:40:05Z<p>Valentin: </p>
<hr />
<div></div>Valentinhttps://fit-pc.com/wiki/index.php?title=WiFi_Indoor_Location_Device_(WILD)_software&diff=6134WiFi Indoor Location Device (WILD) software2018-09-04T06:50:16Z<p>Valentin: </p>
<hr />
<div></div>Valentinhttps://fit-pc.com/wiki/index.php?title=WiFi_Indoor_Location_Device_(WILD)_software&diff=6114WiFi Indoor Location Device (WILD) software2018-08-30T13:05:05Z<p>Valentin: </p>
<hr />
<div></div>Valentinhttps://fit-pc.com/wiki/index.php?title=WiFi_Indoor_Location_Device_(WILD)_software&diff=6113WiFi Indoor Location Device (WILD) software2018-08-30T11:26:25Z<p>Valentin: </p>
<hr />
<div></div>Valentinhttps://fit-pc.com/wiki/index.php?title=WiFi_Indoor_Location_Device_(WILD)_software&diff=6099WiFi Indoor Location Device (WILD) software2018-08-17T08:53:40Z<p>Valentin: </p>
<hr />
<div></div>Valentinhttps://fit-pc.com/wiki/index.php?title=WiFi_Indoor_Location_Device_(WILD)_software&diff=6091WiFi Indoor Location Device (WILD) software2018-08-16T06:42:52Z<p>Valentin: </p>
<hr />
<div></div>Valentinhttps://fit-pc.com/wiki/index.php?title=WiFi_Indoor_Location_Device_(WILD)_software&diff=6090WiFi Indoor Location Device (WILD) software2018-08-16T06:20:38Z<p>Valentin: </p>
<hr />
<div></div>Valentinhttps://fit-pc.com/wiki/index.php?title=WiFi_Indoor_Location_Device_(WILD)_software&diff=6089WiFi Indoor Location Device (WILD) software2018-08-16T06:20:09Z<p>Valentin: </p>
<hr />
<div></div>Valentinhttps://fit-pc.com/wiki/index.php?title=WiFi_Indoor_Location_Device_(WILD)_software&diff=6055WiFi Indoor Location Device (WILD) software2018-08-09T14:46:22Z<p>Valentin: </p>
<hr />
<div></div>Valentinhttps://fit-pc.com/wiki/index.php?title=WiFi_Indoor_Location_Device_(WILD)_software&diff=6054WiFi Indoor Location Device (WILD) software2018-08-09T14:43:47Z<p>Valentin: </p>
<hr />
<div></div>Valentinhttps://fit-pc.com/wiki/index.php?title=WiFi_Indoor_Location_Device_(WILD)_software&diff=6053WiFi Indoor Location Device (WILD) software2018-08-09T14:41:44Z<p>Valentin: </p>
<hr />
<div></div>Valentinhttps://fit-pc.com/wiki/index.php?title=WiFi_Indoor_Location_Device_(WILD)_software&diff=6052WiFi Indoor Location Device (WILD) software2018-08-09T14:09:22Z<p>Valentin: </p>
<hr />
<div></div>Valentinhttps://fit-pc.com/wiki/index.php?title=Airtop2_Supported_Features&diff=5977Airtop2 Supported Features2018-07-16T08:05:36Z<p>Valentin: </p>
<hr />
<div>The table below specifies Airtop2 current and planned support coverage. This page is updated on any significant change of support availability.<br />
<!-- This is a key--><br />
{{Key}}<br />
<br />
{| class="wikitable"<br />
! Feature<br />
! style="text-align: center;" | Windows 10<br />
! style="text-align: center;" | Linux<br />
|-<br />
| DDR4 SDRAM memory<br />
| style="text-align: center;" | Yes<br />
| style="text-align: center;" | Yes<br />
|-<br />
| ECC<br />
| style="text-align: center;" | Yes<sup>1</sup><br />
| style="text-align: center;" | Yes<sup>1</sup><br />
|-<br />
| HDMI video port<br />
| style="text-align: center;" | Yes<br />
| style="text-align: center;" | Yes<br />
|-<br />
| DisplayPort video port<br />
| style="text-align: center;" | Yes<br />
| style="text-align: center;" | Yes<br />
|-<br />
| Analog audio in/out<br />
| style="text-align: center;" | Yes<br />
| style="text-align: center;" | Yes<br />
|-<br />
| Digital audio out<br />
| style="text-align: center;" | {{TBD}}<br />
| style="text-align: center;" | Yes<br />
|-<br />
| LAN<br />
| style="text-align: center;" | Yes<br />
| style="text-align: center;" | Yes<br />
|-<br />
| Wireless LAN<br />
| style="text-align: center;" | Yes<sup>2</sup><br />
| style="text-align: center;" | Yes<sup>2</sup><br />
|-<br />
| Bluetooth<br />
| style="text-align: center;" | Yes<sup>2</sup><br />
| style="text-align: center;" | Yes<sup>2</sup><br />
|-<br />
| Cellular comms<br />
| style="text-align: center;" | Yes<sup>2</sup><br />
| style="text-align: center;" | Yes<sup>2</sup><br />
|-<br />
| USB 3.0 ports<br />
| style="text-align: center;" | Yes<br />
| style="text-align: center;" | Yes<br />
|-<br />
| USB 2.0 ports<br />
| style="text-align: center;" | Yes<sup>3</sup><br />
| style="text-align: center;" | Yes<sup>3</sup><br />
|-<br />
| Serial interface<br />
| style="text-align: center;" | Yes<sup>4</sup><br />
| style="text-align: center;" | Yes<sup>7</sup><br />
|-<br />
| RAID functionality (Intel RST)<br />
| style="text-align: center;" | Yes <sup>4</sup><br />
| style="text-align: center;" | {{No}}<br />
|-<br />
| 2.5'' HDD/SSD slot<br />
| style="text-align: center;" | Yes<br />
| style="text-align: center;" | Yes<br />
|-<br />
| mSATA SSD slot<br />
| style="text-align: center;" | Yes<br />
| style="text-align: center;" | Yes<br />
|-<br />
| eSATA port<br />
| style="text-align: center;" | N/A<br />
| style="text-align: center;" | N/A<br />
|-<br />
| SD-card R/W<br />
| style="text-align: center;" | Yes<sup>5</sup><br />
| style="text-align: center;" | Yes<sup>5</sup><br />
|-<br />
| PCI Express slot x16<br />
| style="text-align: center;" | Yes<br />
| style="text-align: center;" | Yes<br />
|-<br />
| mini PCIe slot<br />
| style="text-align: center;" | Yes<sup>5</sup><br />
| style="text-align: center;" | Yes<sup>5</sup><br />
|-<br />
| Auto-On<br />
| style="text-align: center;" | Yes<br />
| style="text-align: center;" | Yes<br />
|-<br />
| Wake-on-LAN<br />
| style="text-align: center;" | {{TBD}}<br />
| style="text-align: center;" | {{TBD}}<br />
|-<br />
| Wake-on-Timer<br />
| style="text-align: center;" | Yes<br />
| style="text-align: center;" | Yes<br />
|-<br />
| PXE UEFI Boot<br />
| style="text-align: center;" | {{TBD}}<br />
| style="text-align: center;" | {{TBD}}<br />
|-<br />
| Watchdog<br />
| style="text-align: center;" | {{TBD}}<br />
| style="text-align: center;" | Yes<sup>7</sup><br />
|-<br />
| Remote power button<br />
| style="text-align: center;" | Yes<br />
| style="text-align: center;" | Yes<br />
|-<br />
| TPM 2.0<br />
| style="text-align: center;" | Yes<br />
| style="text-align: center;" | Yes<br />
|-<br />
| M.2 NVMe<br />
| style="text-align: center;" | Yes<br />
| style="text-align: center;" | Yes<br />
|-<br />
| M.2 SATA<br />
| style="text-align: center;" | Yes<br />
| style="text-align: center;" | Yes<br />
|-<br />
| M.2 E-key<br />
| style="text-align: center;" | Yes<br />
| style="text-align: center;" | Yes<br />
|-<br />
| M.2 B-key<br />
| style="text-align: center;" | Yes<br />
| style="text-align: center;" | Yes<br />
|-<br />
| PCI Express slot x16<br />
| style="text-align: center;" | Yes<sup>6</sup><br />
| style="text-align: center;" | Yes<sup>6</sup><br />
|-<br />
| GPIOS<br />
| style="text-align: center;" | {{No}}<br />
| style="text-align: center;" | {{No}}<br />
|}<br />
Notes:<br />
<br />
# Only with supported CPU (Xeon)<br />
# Additional module required<br />
# Supported at the USB3.0 ports.<br />
# Limited functionality determined by Intel<br />
# Only with FM-AT2 FACE Module<br />
# At the expense of discrete GPU<br />
# Test environment: Debian 9; linux-image-4.17.5<br />
<br />
<br><br />
Last update: 04-APR-2018</div>Valentinhttps://fit-pc.com/wiki/index.php?title=Compulab_indoor_positioning_support&diff=5750Compulab indoor positioning support2018-05-28T11:56:13Z<p>Valentin: /* FTMi with a Wan Connection */</p>
<hr />
<div>= Support =<br />
== FTMi with a Wan Connection ==<br />
This step is require for installing a missing '''''openssh-server''''' package onto the FTMi.<br />
<br><br />
The '''''openssh-server''''' will provide an '''''ssh''''' connection to the device at the time of the support session.<br />
<br><br />
[[File:FTMiWan.png]]<br />
<br>This manual explains:<br />
# how to connect an FTMi device to WAN by means of USB Tethering<br />
# how to install the 'openssh-server' onto an FTMi device<br />
# how to add 'support' user account to the system<br />
<br />
=== USB Tethering ===<br />
* Get connected to the FTMi console and acquire 'root' credentials:<br />
sudo -i<br />
<br />
* Issue '''''udevadm''''' command in to monitor how a new interface gets shown up in the system. Issue:<br />
udevadm monitor --subsystem=net<br />
monitor will print the received events for:<br />
UDEV - the event which udev sends out after rule processing<br />
KERNEL - the kernel uevent<br />
<br />
* Leave this session opened and go to the next step.<br />
<br />
* Connect the HotSpot to the FTMi by using a USB cable.<br />
** Make the mobile phone work as an HotSpot USB tethering device. Refer to the mobile device manual for more information.<br />
<br />
* As soon as the HotSpot starts working the FTMi '''''udevadm''''' session window must have lines like this:<br />
<br />
KERNEL[268300.034329] add /devices/pci0000:00/0000:00:15.0/usb1/1-5/1-5:1.0/net/usb0 (net)<br />
KERNEL[268300.054913] move /devices/pci0000:00/0000:00:15.0/usb1/1-5/1-5:1.0/net/enp0s21f0u5 (net)<br />
UDEV [268300.085456] add /devices/pci0000:00/0000:00:15.0/usb1/1-5/1-5:1.0/net/enp0s21f0u5 (net)<br />
UDEV [268300.093461] move /devices/pci0000:00/0000:00:15.0/usb1/1-5/1-5:1.0/net/enp0s21f0u5 (net)<br />
<br />
* As soon as these line turn out terminate the '''''udevadm''''' session, press 'Ctrl+C'<br />
<br />
'''Note:'''<br />
A new network interface name is enp0s21f0u5. The interface name can be differ from the name in this manual.<br />
<br />
* Acquire an ip address for this interface.<br />
ifconfig enp0s21f0u5 up<br />
dhclient enp0s21f0u5<br />
<br />
=== Install 'openssh-server' ===<br />
<br />
* Install ssh server<br />
apt-get update<br />
apt-get install openssh-server<br />
<br />
* Add a 'support' user. Use the '''''adduser''''' command to add a new user to your system.<br />
adduser support<br />
Adding user `support' ...<br />
Adding new group `support' (1001) ...<br />
Adding new user `support' (1001) with group `support' ...<br />
Creating home directory `/home/support' ...<br />
Copying files from `/etc/skel' ...<br />
Enter new UNIX password: support<br />
Retype new UNIX password: support<br />
passwd: password updated successfully<br />
Changing the user information for support<br />
Enter the new value, or press ENTER for the default<br />
Full Name []:<br />
Room Number []:<br />
Work Phone []:<br />
Home Phone []:<br />
Other []:<br />
Is the information correct? [Y/n] Y<br />
<br />
* Use the '''''usermod''''' command to add the user to the sudo group.<br />
usermod -aG sudo support<br />
<br />
== Support Setup Topology ==<br />
[[File:SupportSetupTop.png]]<br />
<br><br />
=== Validate the ssh connection to FTMi ===<br />
* Get connected to the FTMi console and acquire 'root' credentials:<br />
sudo -i<br />
* Make sure that a wired interface has a valid ip address provided by the 'standalone router'<br />
* Get back to th PC and try getting connected to the FTMi. Issue:<br />
ssh support@ftmi-ip-address<br />
=== Prepare WebEx Session ===<br />
* As soon as the ssh connection were provided install all required WebEx applications on the PC and send the invitation.</div>Valentinhttps://fit-pc.com/wiki/index.php?title=Compulab_indoor_positioning_support&diff=5749Compulab indoor positioning support2018-05-28T11:54:29Z<p>Valentin: /* Support Setup Topology */</p>
<hr />
<div>= Support =<br />
== FTMi with a Wan Connection ==<br />
This step is require for installing a missing '''''openssh-server''''' package onto the FTMi.<br />
<br><br />
The '''''openssh-server''''' will provide an '''''ssh''''' connection to the device at the time of the support session.<br />
<br><br />
[[File:FTMiWithWanA6.png]]<br />
<br>This manual explains:<br />
# how to connect an FTMi device to WAN by means of USB Tethering<br />
# how to install the 'openssh-server' onto an FTMi device<br />
# how to add 'support' user account to the system<br />
<br />
=== USB Tethering ===<br />
* Get connected to the FTMi console and acquire 'root' credentials:<br />
sudo -i<br />
<br />
* Issue '''''udevadm''''' command in to monitor how a new interface gets shown up in the system. Issue:<br />
udevadm monitor --subsystem=net<br />
monitor will print the received events for:<br />
UDEV - the event which udev sends out after rule processing<br />
KERNEL - the kernel uevent<br />
<br />
* Leave this session opened and go to the next step.<br />
<br />
* Connect the HotSpot to the FTMi by using a USB cable.<br />
** Make the mobile phone work as an HotSpot USB tethering device. Refer to the mobile device manual for more information.<br />
<br />
* As soon as the HotSpot starts working the FTMi '''''udevadm''''' session window must have lines like this:<br />
<br />
KERNEL[268300.034329] add /devices/pci0000:00/0000:00:15.0/usb1/1-5/1-5:1.0/net/usb0 (net)<br />
KERNEL[268300.054913] move /devices/pci0000:00/0000:00:15.0/usb1/1-5/1-5:1.0/net/enp0s21f0u5 (net)<br />
UDEV [268300.085456] add /devices/pci0000:00/0000:00:15.0/usb1/1-5/1-5:1.0/net/enp0s21f0u5 (net)<br />
UDEV [268300.093461] move /devices/pci0000:00/0000:00:15.0/usb1/1-5/1-5:1.0/net/enp0s21f0u5 (net)<br />
<br />
* As soon as these line turn out terminate the '''''udevadm''''' session, press 'Ctrl+C'<br />
<br />
'''Note:'''<br />
A new network interface name is enp0s21f0u5. The interface name can be differ from the name in this manual.<br />
<br />
* Acquire an ip address for this interface.<br />
ifconfig enp0s21f0u5 up<br />
dhclient enp0s21f0u5<br />
<br />
=== Install 'openssh-server' ===<br />
<br />
* Install ssh server<br />
apt-get update<br />
apt-get install openssh-server<br />
<br />
* Add a 'support' user. Use the '''''adduser''''' command to add a new user to your system.<br />
adduser support<br />
Adding user `support' ...<br />
Adding new group `support' (1001) ...<br />
Adding new user `support' (1001) with group `support' ...<br />
Creating home directory `/home/support' ...<br />
Copying files from `/etc/skel' ...<br />
Enter new UNIX password: support<br />
Retype new UNIX password: support<br />
passwd: password updated successfully<br />
Changing the user information for support<br />
Enter the new value, or press ENTER for the default<br />
Full Name []:<br />
Room Number []:<br />
Work Phone []:<br />
Home Phone []:<br />
Other []:<br />
Is the information correct? [Y/n] Y<br />
<br />
* Use the '''''usermod''''' command to add the user to the sudo group.<br />
usermod -aG sudo support<br />
<br />
== Support Setup Topology ==<br />
[[File:SupportSetupTop.png]]<br />
<br><br />
=== Validate the ssh connection to FTMi ===<br />
* Get connected to the FTMi console and acquire 'root' credentials:<br />
sudo -i<br />
* Make sure that a wired interface has a valid ip address provided by the 'standalone router'<br />
* Get back to th PC and try getting connected to the FTMi. Issue:<br />
ssh support@ftmi-ip-address<br />
=== Prepare WebEx Session ===<br />
* As soon as the ssh connection were provided install all required WebEx applications on the PC and send the invitation.</div>Valentinhttps://fit-pc.com/wiki/index.php?title=Compulab_indoor_positioning_support&diff=5748Compulab indoor positioning support2018-05-28T11:33:57Z<p>Valentin: /* FTMi with a Wan Connection */</p>
<hr />
<div>= Support =<br />
== FTMi with a Wan Connection ==<br />
This step is require for installing a missing '''''openssh-server''''' package onto the FTMi.<br />
<br><br />
The '''''openssh-server''''' will provide an '''''ssh''''' connection to the device at the time of the support session.<br />
<br><br />
[[File:FTMiWithWanA6.png]]<br />
<br>This manual explains:<br />
# how to connect an FTMi device to WAN by means of USB Tethering<br />
# how to install the 'openssh-server' onto an FTMi device<br />
# how to add 'support' user account to the system<br />
<br />
=== USB Tethering ===<br />
* Get connected to the FTMi console and acquire 'root' credentials:<br />
sudo -i<br />
<br />
* Issue '''''udevadm''''' command in to monitor how a new interface gets shown up in the system. Issue:<br />
udevadm monitor --subsystem=net<br />
monitor will print the received events for:<br />
UDEV - the event which udev sends out after rule processing<br />
KERNEL - the kernel uevent<br />
<br />
* Leave this session opened and go to the next step.<br />
<br />
* Connect the HotSpot to the FTMi by using a USB cable.<br />
** Make the mobile phone work as an HotSpot USB tethering device. Refer to the mobile device manual for more information.<br />
<br />
* As soon as the HotSpot starts working the FTMi '''''udevadm''''' session window must have lines like this:<br />
<br />
KERNEL[268300.034329] add /devices/pci0000:00/0000:00:15.0/usb1/1-5/1-5:1.0/net/usb0 (net)<br />
KERNEL[268300.054913] move /devices/pci0000:00/0000:00:15.0/usb1/1-5/1-5:1.0/net/enp0s21f0u5 (net)<br />
UDEV [268300.085456] add /devices/pci0000:00/0000:00:15.0/usb1/1-5/1-5:1.0/net/enp0s21f0u5 (net)<br />
UDEV [268300.093461] move /devices/pci0000:00/0000:00:15.0/usb1/1-5/1-5:1.0/net/enp0s21f0u5 (net)<br />
<br />
* As soon as these line turn out terminate the '''''udevadm''''' session, press 'Ctrl+C'<br />
<br />
'''Note:'''<br />
A new network interface name is enp0s21f0u5. The interface name can be differ from the name in this manual.<br />
<br />
* Acquire an ip address for this interface.<br />
ifconfig enp0s21f0u5 up<br />
dhclient enp0s21f0u5<br />
<br />
=== Install 'openssh-server' ===<br />
<br />
* Install ssh server<br />
apt-get update<br />
apt-get install openssh-server<br />
<br />
* Add a 'support' user. Use the '''''adduser''''' command to add a new user to your system.<br />
adduser support<br />
Adding user `support' ...<br />
Adding new group `support' (1001) ...<br />
Adding new user `support' (1001) with group `support' ...<br />
Creating home directory `/home/support' ...<br />
Copying files from `/etc/skel' ...<br />
Enter new UNIX password: support<br />
Retype new UNIX password: support<br />
passwd: password updated successfully<br />
Changing the user information for support<br />
Enter the new value, or press ENTER for the default<br />
Full Name []:<br />
Room Number []:<br />
Work Phone []:<br />
Home Phone []:<br />
Other []:<br />
Is the information correct? [Y/n] Y<br />
<br />
* Use the '''''usermod''''' command to add the user to the sudo group.<br />
usermod -aG sudo support<br />
<br />
== Support Setup Topology ==<br />
[[File:SupportSetupTop.png]]<br />
<br><br />
* Get connected to the FTMi console and acquire 'root' credentials:<br />
sudo -i<br />
* Make sure that a wired interface has a valid ip address provided by the 'standalone router'<br />
* Get back to th PC and try getting connected to the FTMi. Issue:<br />
ssh support@ftmi-ip-address-form-the-step-1<br />
* As soon as the ssh connection were provided install all required WebEx applications on the PC and send the invitation.</div>Valentinhttps://fit-pc.com/wiki/index.php?title=File:FTMiWithWanA6.png&diff=5747File:FTMiWithWanA6.png2018-05-28T11:30:09Z<p>Valentin: FTMiWithWanA6</p>
<hr />
<div>FTMiWithWanA6</div>Valentinhttps://fit-pc.com/wiki/index.php?title=Compulab_indoor_positioning_support&diff=5746Compulab indoor positioning support2018-05-28T11:15:35Z<p>Valentin: /* FTMi with a Wan Connection */</p>
<hr />
<div>= Support =<br />
== FTMi with a Wan Connection ==<br />
This step is require for installing a missing '''''openssh-server''''' package onto the FTMi.<br />
<br><br />
The '''''openssh-server''''' will provide an '''''ssh''''' connection to the device at the time of the support session.<br />
<br><br />
[[File:FTMiWan.png]]<br />
<br>This manual explains:<br />
# how to connect an FTMi device to WAN by means of USB Tethering<br />
# how to install the 'openssh-server' onto an FTMi device<br />
# how to add 'support' user account to the system<br />
<br />
=== USB Tethering ===<br />
* Get connected to the FTMi console and acquire 'root' credentials:<br />
sudo -i<br />
<br />
* Issue '''''udevadm''''' command in to monitor how a new interface gets shown up in the system. Issue:<br />
udevadm monitor --subsystem=net<br />
monitor will print the received events for:<br />
UDEV - the event which udev sends out after rule processing<br />
KERNEL - the kernel uevent<br />
<br />
* Leave this session opened and go to the next step.<br />
<br />
* Connect the HotSpot to the FTMi by using a USB cable.<br />
** Make the mobile phone work as an HotSpot USB tethering device. Refer to the mobile device manual for more information.<br />
<br />
* As soon as the HotSpot starts working the FTMi '''''udevadm''''' session window must have lines like this:<br />
<br />
KERNEL[268300.034329] add /devices/pci0000:00/0000:00:15.0/usb1/1-5/1-5:1.0/net/usb0 (net)<br />
KERNEL[268300.054913] move /devices/pci0000:00/0000:00:15.0/usb1/1-5/1-5:1.0/net/enp0s21f0u5 (net)<br />
UDEV [268300.085456] add /devices/pci0000:00/0000:00:15.0/usb1/1-5/1-5:1.0/net/enp0s21f0u5 (net)<br />
UDEV [268300.093461] move /devices/pci0000:00/0000:00:15.0/usb1/1-5/1-5:1.0/net/enp0s21f0u5 (net)<br />
<br />
* As soon as these line turn out terminate the '''''udevadm''''' session, press 'Ctrl+C'<br />
<br />
'''Note:'''<br />
A new network interface name is enp0s21f0u5. The interface name can be differ from the name in this manual.<br />
<br />
* Acquire an ip address for this interface.<br />
ifconfig enp0s21f0u5 up<br />
dhclient enp0s21f0u5<br />
<br />
=== Install 'openssh-server' ===<br />
<br />
* Install ssh server<br />
apt-get update<br />
apt-get install openssh-server<br />
<br />
* Add a 'support' user. Use the '''''adduser''''' command to add a new user to your system.<br />
adduser support<br />
Adding user `support' ...<br />
Adding new group `support' (1001) ...<br />
Adding new user `support' (1001) with group `support' ...<br />
Creating home directory `/home/support' ...<br />
Copying files from `/etc/skel' ...<br />
Enter new UNIX password: support<br />
Retype new UNIX password: support<br />
passwd: password updated successfully<br />
Changing the user information for support<br />
Enter the new value, or press ENTER for the default<br />
Full Name []:<br />
Room Number []:<br />
Work Phone []:<br />
Home Phone []:<br />
Other []:<br />
Is the information correct? [Y/n] Y<br />
<br />
* Use the '''''usermod''''' command to add the user to the sudo group.<br />
usermod -aG sudo support<br />
<br />
== Support Setup Topology ==<br />
[[File:SupportSetupTop.png]]<br />
<br><br />
* Get connected to the FTMi console and acquire 'root' credentials:<br />
sudo -i<br />
* Make sure that a wired interface has a valid ip address provided by the 'standalone router'<br />
* Get back to th PC and try getting connected to the FTMi. Issue:<br />
ssh support@ftmi-ip-address-form-the-step-1<br />
* As soon as the ssh connection were provided install all required WebEx applications on the PC and send the invitation.</div>Valentinhttps://fit-pc.com/wiki/index.php?title=Compulab_indoor_positioning_support&diff=5742Compulab indoor positioning support2018-05-27T13:18:57Z<p>Valentin: /* Support Setup Topology */</p>
<hr />
<div>= Support =<br />
== FTMi with a Wan Connection ==<br />
[[File:FTMiWan.png]]<br />
<br>This manual explains:<br />
# how to connect an FTMi device to WAN by means of USB Tethering<br />
# how to install the 'openssh-server' onto an FTMi device<br />
# how to add 'support' user account to the system<br />
<br />
=== USB Tethering ===<br />
* Get connected to the FTMi console and acquire 'root' credentials:<br />
sudo -i<br />
<br />
* Issue '''''udevadm''''' command in to monitor how a new interface gets shown up in the system. Issue:<br />
udevadm monitor --subsystem=net<br />
monitor will print the received events for:<br />
UDEV - the event which udev sends out after rule processing<br />
KERNEL - the kernel uevent<br />
<br />
* Leave this session opened and go to the next step.<br />
<br />
* Connect the HotSpot to the FTMi by using a USB cable.<br />
** Make the mobile phone work as an HotSpot USB tethering device. Refer to the mobile device manual for more information.<br />
<br />
* As soon as the HotSpot starts working the FTMi '''''udevadm''''' session window must have lines like this:<br />
<br />
KERNEL[268300.034329] add /devices/pci0000:00/0000:00:15.0/usb1/1-5/1-5:1.0/net/usb0 (net)<br />
KERNEL[268300.054913] move /devices/pci0000:00/0000:00:15.0/usb1/1-5/1-5:1.0/net/enp0s21f0u5 (net)<br />
UDEV [268300.085456] add /devices/pci0000:00/0000:00:15.0/usb1/1-5/1-5:1.0/net/enp0s21f0u5 (net)<br />
UDEV [268300.093461] move /devices/pci0000:00/0000:00:15.0/usb1/1-5/1-5:1.0/net/enp0s21f0u5 (net)<br />
<br />
* As soon as these line turn out terminate the '''''udevadm''''' session, press 'Ctrl+C'<br />
<br />
'''Note:'''<br />
A new network interface name is enp0s21f0u5. The interface name can be differ from the name in this manual.<br />
<br />
* Acquire an ip address for this interface.<br />
ifconfig enp0s21f0u5 up<br />
dhclient enp0s21f0u5<br />
<br />
=== Install 'openssh-server' ===<br />
<br />
* Install ssh server<br />
apt-get update<br />
apt-get install openssh-server<br />
<br />
* Add a 'support' user. Use the '''''adduser''''' command to add a new user to your system.<br />
adduser support<br />
Adding user `support' ...<br />
Adding new group `support' (1001) ...<br />
Adding new user `support' (1001) with group `support' ...<br />
Creating home directory `/home/support' ...<br />
Copying files from `/etc/skel' ...<br />
Enter new UNIX password: support<br />
Retype new UNIX password: support<br />
passwd: password updated successfully<br />
Changing the user information for support<br />
Enter the new value, or press ENTER for the default<br />
Full Name []:<br />
Room Number []:<br />
Work Phone []:<br />
Home Phone []:<br />
Other []:<br />
Is the information correct? [Y/n] Y<br />
<br />
* Use the '''''usermod''''' command to add the user to the sudo group.<br />
usermod -aG sudo support<br />
<br />
== Support Setup Topology ==<br />
[[File:SupportSetupTop.png]]<br />
<br><br />
* Get connected to the FTMi console and acquire 'root' credentials:<br />
sudo -i<br />
* Make sure that a wired interface has a valid ip address provided by the 'standalone router'<br />
* Get back to th PC and try getting connected to the FTMi. Issue:<br />
ssh support@ftmi-ip-address-form-the-step-1<br />
* As soon as the ssh connection were provided install all required WebEx applications on the PC and send the invitation.</div>Valentinhttps://fit-pc.com/wiki/index.php?title=Compulab_indoor_positioning_support&diff=5741Compulab indoor positioning support2018-05-27T13:18:03Z<p>Valentin: /* FTMi with a Wan Connection */</p>
<hr />
<div>= Support =<br />
== FTMi with a Wan Connection ==<br />
[[File:FTMiWan.png]]<br />
<br>This manual explains:<br />
# how to connect an FTMi device to WAN by means of USB Tethering<br />
# how to install the 'openssh-server' onto an FTMi device<br />
# how to add 'support' user account to the system<br />
<br />
=== USB Tethering ===<br />
* Get connected to the FTMi console and acquire 'root' credentials:<br />
sudo -i<br />
<br />
* Issue '''''udevadm''''' command in to monitor how a new interface gets shown up in the system. Issue:<br />
udevadm monitor --subsystem=net<br />
monitor will print the received events for:<br />
UDEV - the event which udev sends out after rule processing<br />
KERNEL - the kernel uevent<br />
<br />
* Leave this session opened and go to the next step.<br />
<br />
* Connect the HotSpot to the FTMi by using a USB cable.<br />
** Make the mobile phone work as an HotSpot USB tethering device. Refer to the mobile device manual for more information.<br />
<br />
* As soon as the HotSpot starts working the FTMi '''''udevadm''''' session window must have lines like this:<br />
<br />
KERNEL[268300.034329] add /devices/pci0000:00/0000:00:15.0/usb1/1-5/1-5:1.0/net/usb0 (net)<br />
KERNEL[268300.054913] move /devices/pci0000:00/0000:00:15.0/usb1/1-5/1-5:1.0/net/enp0s21f0u5 (net)<br />
UDEV [268300.085456] add /devices/pci0000:00/0000:00:15.0/usb1/1-5/1-5:1.0/net/enp0s21f0u5 (net)<br />
UDEV [268300.093461] move /devices/pci0000:00/0000:00:15.0/usb1/1-5/1-5:1.0/net/enp0s21f0u5 (net)<br />
<br />
* As soon as these line turn out terminate the '''''udevadm''''' session, press 'Ctrl+C'<br />
<br />
'''Note:'''<br />
A new network interface name is enp0s21f0u5. The interface name can be differ from the name in this manual.<br />
<br />
* Acquire an ip address for this interface.<br />
ifconfig enp0s21f0u5 up<br />
dhclient enp0s21f0u5<br />
<br />
=== Install 'openssh-server' ===<br />
<br />
* Install ssh server<br />
apt-get update<br />
apt-get install openssh-server<br />
<br />
* Add a 'support' user. Use the '''''adduser''''' command to add a new user to your system.<br />
adduser support<br />
Adding user `support' ...<br />
Adding new group `support' (1001) ...<br />
Adding new user `support' (1001) with group `support' ...<br />
Creating home directory `/home/support' ...<br />
Copying files from `/etc/skel' ...<br />
Enter new UNIX password: support<br />
Retype new UNIX password: support<br />
passwd: password updated successfully<br />
Changing the user information for support<br />
Enter the new value, or press ENTER for the default<br />
Full Name []:<br />
Room Number []:<br />
Work Phone []:<br />
Home Phone []:<br />
Other []:<br />
Is the information correct? [Y/n] Y<br />
<br />
* Use the '''''usermod''''' command to add the user to the sudo group.<br />
usermod -aG sudo support<br />
<br />
== Support Setup Topology ==<br />
<br />
* Get connected to the FTMi console and acquire 'root' credentials:<br />
sudo -i<br />
* Make sure that a wired interface has a valid ip address provided by the 'standalone router'<br />
* Get back to th PC and try getting connected to the FTMi. Issue:<br />
ssh support@ftmi-ip-address-form-the-step-1<br />
* As soon as the ssh connection were provided install all required WebEx applications on the PC and send the invitation.</div>Valentinhttps://fit-pc.com/wiki/index.php?title=File:SupportSetupTop.png&diff=5740File:SupportSetupTop.png2018-05-27T13:15:29Z<p>Valentin: SupportSetupTop</p>
<hr />
<div>SupportSetupTop</div>Valentinhttps://fit-pc.com/wiki/index.php?title=File:FTMiWan.png&diff=5739File:FTMiWan.png2018-05-27T13:15:00Z<p>Valentin: FTMiWan</p>
<hr />
<div>FTMiWan</div>Valentinhttps://fit-pc.com/wiki/index.php?title=Compulab_indoor_positioning_support&diff=5738Compulab indoor positioning support2018-05-27T13:07:20Z<p>Valentin: Created page with "= Support = == FTMi with a Wan Connection == This manual explains: # connect an FTMi device to WAN by means of USB Tethering # how to install the 'openssh-server' onto an FTMi..."</p>
<hr />
<div>= Support =<br />
== FTMi with a Wan Connection ==<br />
This manual explains:<br />
# connect an FTMi device to WAN by means of USB Tethering<br />
# how to install the 'openssh-server' onto an FTMi device<br />
# how to add 'support' user account to the system<br />
<br />
=== USB Tethering ===<br />
* Get connected to the FTMi console and acquire 'root' credentials:<br />
sudo -i<br />
<br />
* Issue '''''udevadm''''' command in to monitor how a new interface gets shown up in the system. Issue:<br />
udevadm monitor --subsystem=net<br />
monitor will print the received events for:<br />
UDEV - the event which udev sends out after rule processing<br />
KERNEL - the kernel uevent<br />
<br />
* Leave this session opened and go to the next step.<br />
<br />
* Connect the HotSpot to the FTMi by using a USB cable.<br />
** Make the mobile phone work as an HotSpot USB tethering device. Refer to the mobile device manual for more information.<br />
<br />
* As soon as the HotSpot starts working the FTMi '''''udevadm''''' session window must have lines like this:<br />
<br />
KERNEL[268300.034329] add /devices/pci0000:00/0000:00:15.0/usb1/1-5/1-5:1.0/net/usb0 (net)<br />
KERNEL[268300.054913] move /devices/pci0000:00/0000:00:15.0/usb1/1-5/1-5:1.0/net/enp0s21f0u5 (net)<br />
UDEV [268300.085456] add /devices/pci0000:00/0000:00:15.0/usb1/1-5/1-5:1.0/net/enp0s21f0u5 (net)<br />
UDEV [268300.093461] move /devices/pci0000:00/0000:00:15.0/usb1/1-5/1-5:1.0/net/enp0s21f0u5 (net)<br />
<br />
* As soon as these line turn out terminate the '''''udevadm''''' session, press 'Ctrl+C'<br />
<br />
'''Note:'''<br />
A new network interface name is enp0s21f0u5. The interface name can be differ from the name in this manual.<br />
<br />
* Acquire an ip address for this interface.<br />
ifconfig enp0s21f0u5 up<br />
dhclient enp0s21f0u5<br />
<br />
=== Install 'openssh-server' ===<br />
<br />
* Install ssh server<br />
apt-get update<br />
apt-get install openssh-server<br />
<br />
* Add a 'support' user. Use the '''''adduser''''' command to add a new user to your system.<br />
adduser support<br />
Adding user `support' ...<br />
Adding new group `support' (1001) ...<br />
Adding new user `support' (1001) with group `support' ...<br />
Creating home directory `/home/support' ...<br />
Copying files from `/etc/skel' ...<br />
Enter new UNIX password: support<br />
Retype new UNIX password: support<br />
passwd: password updated successfully<br />
Changing the user information for support<br />
Enter the new value, or press ENTER for the default<br />
Full Name []:<br />
Room Number []:<br />
Work Phone []:<br />
Home Phone []:<br />
Other []:<br />
Is the information correct? [Y/n] Y<br />
<br />
* Use the '''''usermod''''' command to add the user to the sudo group.<br />
usermod -aG sudo support<br />
<br />
== Support Setup Topology ==<br />
<br />
* Get connected to the FTMi console and acquire 'root' credentials:<br />
sudo -i<br />
* Make sure that a wired interface has a valid ip address provided by the 'standalone router'<br />
* Get back to th PC and try getting connected to the FTMi. Issue:<br />
ssh support@ftmi-ip-address-form-the-step-1<br />
* As soon as the ssh connection were provided install all required WebEx applications on the PC and send the invitation.</div>Valentinhttps://fit-pc.com/wiki/index.php?title=Compulab_indoor_positioning&diff=5737Compulab indoor positioning2018-05-25T05:14:27Z<p>Valentin: /* High Level Architecture (Ethernet Backhauling) */</p>
<hr />
<div></div>Valentinhttps://fit-pc.com/wiki/index.php?title=File:Ftmr00.png&diff=5736File:Ftmr00.png2018-05-25T05:13:33Z<p>Valentin: High Level Architecture (Ethernet Backhauling)</p>
<hr />
<div>High Level Architecture (Ethernet Backhauling)</div>Valentinhttps://fit-pc.com/wiki/index.php?title=Compulab_indoor_positioning&diff=5735Compulab indoor positioning2018-05-25T05:10:51Z<p>Valentin: /* FTM Initiator Software */</p>
<hr />
<div></div>Valentin