# 8.6 Services

Services tab shows the services of the device and contains the following subsections:

[![image-1601563935032.png](https://wiki.elseta.com/uploads/images/gallery/2020-10/scaled-1680-/image-1601563935032.png)](https://wiki.elseta.com/uploads/images/gallery/2020-10/image-1601563935032.png)

Services tab shows the services of the device and contains the following subsections:

- TELEMETRY AGENT: device telemetry sending to a remote server;
- IPSEC: encrypted virtual private network (VPN) configuration.
- API: application programming interface configuration.
- OPENVPN: shows the open-source software application that implements virtual private network (VPN).
- SER2NET: network-to-serial proxy;

### Telemetry agent

Having data about the device helps to easily maintain it. Telemetry agent gathers information in a compact and easily decodable way. It uses UDP packets therefore only small overhead is introduced.

However, UDP does not guarantee the arrival of sent packets therefore not every message might reach the server saving these messages.

To start using Telemetry agent a user should configure and enable it. Four options are available:

- Enable agent;
- Server address;
- Port (UDP);
- Period (s).

Every time timer of period length expires, a message is sent to a server of configured server if service is enabled .

<p class="callout warning">Telemetry agent doesn’t start as a service if Enable agent checkbox is unchecked.</p>

<p class="callout info">Enabling agent and saving the configuration automatically starts the process with the new configuration.</p>

### IPsec

#### Background

WCC Lite supports ipsec vpn, thus is able to deliver data securely over encrypted link. To establish ipsec vpn, a connection definition must be created by entering appropriate configuration settings.

For advanced connection description auxiliary settings sets can be defined. They can be joined to the connection and can be reusable several times according to the need. Each configuration record is identified by a unique name, which is assigned in time of creation. The following diagram shows relations between connection and auxiliary sets.

[![image-1601564177757.png](https://wiki.elseta.com/uploads/images/gallery/2020-10/scaled-1680-/image-1601564177757.png)](https://wiki.elseta.com/uploads/images/gallery/2020-10/image-1601564177757.png)

#### Ipsec settings

##### Connection description

Options supported by WCC lite is described below.

<table border="1" id="bkmrk-item-type-descriptio" style="border-collapse: collapse; width: 100%; height: 948.05px;"><tbody><tr style="height: 29.6px;"><td style="width: 20.6173%; height: 29.6px;">Item</td><td style="width: 22.5926%; height: 29.6px;">Type</td><td style="width: 56.7901%; height: 29.6px;">Description</td></tr><tr style="height: 29.6px;"><td style="width: 20.6173%; height: 29.6px;">Gateway</td><td style="width: 22.5926%; height: 29.6px;">string</td><td style="width: 56.7901%; height: 29.6px;">Host name or IP address of the remote peer.</td></tr><tr style="height: 80px;"><td style="width: 20.6173%; height: 80px;">Type</td><td style="width: 22.5926%; height: 80px;">selector</td><td style="width: 56.7901%; height: 80px;">Tunnel mode: full packet encryption, covers host-to-host,

host-to-subnet, subnet-to-subnet situations or transport

mode: ip payload encryption, secures host-to-host data only.

</td></tr><tr style="height: 57.6px;"><td style="width: 20.6173%; height: 57.6px;">Local subnet</td><td style="width: 22.5926%; height: 57.6px;">string</td><td style="width: 56.7901%; height: 57.6px;">Specifies local network, in form network/netmask, for

example 192.168.11.0/24

</td></tr><tr style="height: 29.6px;"><td style="width: 20.6173%; height: 29.6px;">Remote subnet</td><td style="width: 22.5926%; height: 29.6px;">string</td><td style="width: 56.7901%; height: 29.6px;">Specifies remote network at another side of a tunnel.</td></tr><tr style="height: 29.6px;"><td style="width: 20.6173%; height: 29.6px;">Authentication</td><td style="width: 22.5926%; height: 29.6px;">selector</td><td style="width: 56.7901%; height: 29.6px;">Pre-shared key or RSA certificate</td></tr><tr style="height: 29.6px;"><td style="width: 20.6173%; height: 29.6px;">Pre-shared key</td><td style="width: 22.5926%; height: 29.6px;">string</td><td style="width: 56.7901%; height: 29.6px;">Available if Authentication set to Pre-shared key</td></tr><tr style="height: 57.6px;"><td style="width: 20.6173%; height: 57.6px;">Certificate set </td><td style="width: 22.5926%; height: 57.6px;">selector</td><td style="width: 56.7901%; height: 57.6px;">Available if Authentication set to RSA certificate. Selectable

from configured auxiliary set.

</td></tr><tr style="height: 57.6px;"><td style="width: 20.6173%; height: 57.6px;">Phase 1 proposal

(IKE)

</td><td style="width: 22.5926%; height: 57.6px;">selector</td><td style="width: 56.7901%; height: 57.6px;">Authentication-encryption schema, selectable from

configured auxiliary set.

</td></tr><tr style="height: 57.6px;"><td style="width: 20.6173%; height: 57.6px;">Phase 2 proposal

(ESP)

</td><td style="width: 22.5926%; height: 57.6px;">selector</td><td style="width: 56.7901%; height: 57.6px;">Authentication-encryption schema, selectable from

configured auxiliary set.

</td></tr><tr style="height: 35.2px;"><td style="width: 20.6173%; height: 35.2px;">Local ID

</td><td style="width: 22.5926%; height: 35.2px;">string</td><td style="width: 56.7901%; height: 35.2px;">Specifies the identity of the local endpoint

</td></tr><tr style="height: 43px;"><td style="width: 20.6173%; height: 43px;">Remote ID

</td><td style="width: 22.5926%; height: 43px;">string</td><td style="width: 56.7901%; height: 43px;">Specifies the identity of the remote endpoint

</td></tr><tr style="height: 35.2px;"><td style="width: 20.6173%; height: 35.2px;">Key exchange

</td><td style="width: 22.5926%; height: 35.2px;">selector

</td><td style="width: 56.7901%; height: 35.2px;">Sets method of key exchange IKEv2 or IKEv1. Default IKEv2.

</td></tr><tr style="height: 35.2px;"><td style="width: 20.6173%; height: 35.2px;">Exchange mode

</td><td style="width: 22.5926%; height: 35.2px;">selector

</td><td style="width: 56.7901%; height: 35.2px;">Main or aggressive. Available if key exchange is set to IKEv1.

</td></tr><tr style="height: 35.2px;"><td style="width: 20.6173%; height: 35.2px;">Use compression

</td><td style="width: 22.5926%; height: 35.2px;">checkbox</td><td style="width: 56.7901%; height: 35.2px;">If selected a compression ability will be proposed to the peer.

</td></tr><tr style="height: 142.65px;"><td style="width: 20.6173%; height: 142.65px;">DPD action

</td><td style="width: 22.5926%; height: 142.65px;">selector

</td><td style="width: 56.7901%; height: 142.65px;">Controls the use of dead peer detection protocol, values:

- none – default, disables sending of DPD messages.
- clear – the connection closed with no action.
- hold – keeps description, tries re-negotiate connection on demand.
- restart – will try to re-negotiate immediately.

</td></tr><tr style="height: 35.2px;"><td style="width: 20.6173%; height: 35.2px;">DPD delay

</td><td style="width: 22.5926%; height: 35.2px;">string</td><td style="width: 56.7901%; height: 35.2px;">Time interval in seconds between peer check. Default 30.

</td></tr><tr style="height: 57.6px;"><td style="width: 20.6173%; height: 57.6px;">DPD timeout

</td><td style="width: 22.5926%; height: 57.6px;">string</td><td style="width: 56.7901%; height: 57.6px;">Time in seconds after which peer consider to be unusable. IKEv1 only. Default 150.

</td></tr><tr style="height: 35.2px;"><td style="width: 20.6173%; height: 35.2px;">Key lifetime

</td><td style="width: 22.5926%; height: 35.2px;">string</td><td style="width: 56.7901%; height: 35.2px;">Lifetime of data channel in seconds . Default 10800.

</td></tr><tr style="height: 35.2px;"><td style="width: 20.6173%; height: 35.2px;">IKE lifetime

</td><td style="width: 22.5926%; height: 35.2px;">string</td><td style="width: 56.7901%; height: 35.2px;">Lifetime of keying channel in seconds. Default 3600.

</td></tr></tbody></table>

##### Auxiliary settings

Phase 1 proposals - IKE/ISAKMP cipher suite components:

<table border="1" id="bkmrk-item-type-descriptio-0" style="border-collapse: collapse; width: 100%; height: 116px;"><tbody><tr style="height: 29px;"><td style="width: 20.8025%; height: 29px;">Item</td><td style="width: 12.037%; height: 29px;">Type</td><td style="width: 51.7901%; height: 29px;">Description</td><td style="width: 15.3704%; height: 29px;">Note</td></tr><tr style="height: 29px;"><td style="width: 20.8025%; height: 29px;">Encryption algorithm

</td><td style="width: 12.037%; height: 29px;">selector

</td><td style="width: 51.7901%; height: 29px;">Encryption algorithm – 3DES, AES128, AES192, AES256.

</td><td style="width: 15.3704%; height: 29px;">required</td></tr><tr style="height: 29px;"><td style="width: 20.8025%; height: 29px;">Hash algorithm

</td><td style="width: 12.037%; height: 29px;">selector

</td><td style="width: 51.7901%; height: 29px;">Hash algorithm – MD5, SHA1, SHA256, SHA384 or SHA512.

</td><td style="width: 15.3704%; height: 29px;">required</td></tr><tr style="height: 29px;"><td style="width: 20.8025%; height: 29px;">DH exponentiation

</td><td style="width: 12.037%; height: 29px;">selector

</td><td style="width: 51.7901%; height: 29px;">Specifies Diffie-Hellman groups – 1,2,5,14,15,16,18

</td><td style="width: 15.3704%; height: 29px;">required</td></tr></tbody></table>

Phase 2 proposals - ESP cipher suite components:

<table border="1" id="bkmrk-item-type-descriptio-1" style="border-collapse: collapse; width: 100%; height: 116px;"><tbody><tr style="height: 29px;"><td style="width: 20.8025%; height: 29px;">Item</td><td style="width: 12.037%; height: 29px;">Type</td><td style="width: 51.7901%; height: 29px;">Description</td><td style="width: 15.3704%; height: 29px;">Note</td></tr><tr style="height: 29px;"><td style="width: 20.8025%; height: 29px;">Encryption algorithm

</td><td style="width: 12.037%; height: 29px;">selector

</td><td style="width: 51.7901%; height: 29px;">Encryption algorithm – 3DES, AES128, AES192, AES256.

</td><td style="width: 15.3704%; height: 29px;">required</td></tr><tr style="height: 29px;"><td style="width: 20.8025%; height: 29px;">Hash algorithm

</td><td style="width: 12.037%; height: 29px;">selector

</td><td style="width: 51.7901%; height: 29px;">Hash algorithm – MD5, SHA1, SHA256, SHA384 or SHA512.

</td><td style="width: 15.3704%; height: 29px;">required</td></tr><tr style="height: 29px;"><td style="width: 20.8025%; height: 29px;">DH exponentiation

</td><td style="width: 12.037%; height: 29px;">selector

</td><td style="width: 51.7901%; height: 29px;">Specifies Diffie-Hellman groups – 1,2,5,14,15,16,18

</td><td style="width: 15.3704%; height: 29px;">optional</td></tr></tbody></table>

<p class="callout info">The following specification and topology map corresponds to settings used in further configuration walk-through example.</p>

#### Creating a connection description

##### Site-to-Site VPN scenario

[![image-1601565165686.png](https://wiki.elseta.com/uploads/images/gallery/2020-10/scaled-1680-/image-1601565165686.png)](https://wiki.elseta.com/uploads/images/gallery/2020-10/image-1601565165686.png)

##### VPN connection details

Tunnel: demoo

```demoo
IPSec peer: ipsec.vpn.net
Pre-shared key: thebigsecret
Mode: tunnel
Remote network: 10.10.10.10/24
Local network: 10.10.12.0/24
Local ID: wcclite
IKE authentication: aes256
IKE hash: sha256
IKE DH group: 5 (modp1536)
ESP authentication: aes128
ESP hash: sha1
```

<p class="callout info">If auxiliary data is needed, it is recommended to check or define it first.</p>

##### Creation of Phase 1 proposal

- Enter section “Phase 1 proposals”.
- Create a new record by assigning new name, for example “aes256-sha256-dh5” and click the button “Add”.
- Choose corresponding values: encryption, hash algorithm and DH exponentiation.
- Push “save” to save the data.

[![image-1601568023894.png](https://wiki.elseta.com/uploads/images/gallery/2020-10/scaled-1680-/image-1601568023894.png)](https://wiki.elseta.com/uploads/images/gallery/2020-10/image-1601568023894.png)

##### Creation of Phase 2 proposal

- Enter section “Phase 2 proposals”.
- Create a new record by assign new name for example “aes128-sha1” and click the button “Add”.
- Choose corresponding values: encryption, hash algorithm.
- Push “save” to save the data.

[![image-1601568071003.png](https://wiki.elseta.com/uploads/images/gallery/2020-10/scaled-1680-/image-1601568071003.png)](https://wiki.elseta.com/uploads/images/gallery/2020-10/image-1601568071003.png)

##### Creation of tunnel definition

Enter section connections

- Create a new record by assigning new name (e.g.“demo0”) and clicking “Add”.
- Call a detail form by pushing the button “edit”.
- Enter peer address into “Gateway”: “ipsec.vpn.net”.
- Ensure “Type” is set to: “Tunnel”.
- Fill local subnet to: 10.10.12.0/24.
- Fill remote subnet to: 10.10.10.0/24.
- Make sure authentication is set to: “Shared secret”.
- Enter Pre-shared key (PSK): thebigsecret.
- “Phase 1 proposal (IKE)”, choose a value: aes256\_sha256\_dh5.
- “Phase 2 proposal (ESP)”, choose a value: aes128\_sha1.
- Locate combo box “additional field”, select “Local ID”, then set value to: wcclite.
- Push “Save”.

[![image-1601568148856.png](https://wiki.elseta.com/uploads/images/gallery/2020-10/scaled-1680-/image-1601568148856.png)](https://wiki.elseta.com/uploads/images/gallery/2020-10/image-1601568148856.png)

##### Activating the tunnel

- Return to the section “connections”.
- Check the checkbox “Enabled”.
- Push the button “save &amp; apply”.
- Examine indicator “configured”, it should be “yes”, if not, review settings just entered.
- The tunnel should be prepared for operation and will be established on demand.
- Optionally, it is possible to establish tunnel operation by pressing button “start”.

[![image-1601568201450.png](https://wiki.elseta.com/uploads/images/gallery/2020-10/scaled-1680-/image-1601568201450.png)](https://wiki.elseta.com/uploads/images/gallery/2020-10/image-1601568201450.png)

### L2TP/IPsec

Because of the lack of confidentiality inherent in the L2TP protocol, it is often implemented along with IPsec. This is referred to as L2TP/IPsec, and is standardized in IETFRFC 3193. The process of setting up an L2TP/IPsec VPN is as follows:

- Negotiation of IPsec security association (SA), typically through Internet key exchange (IKE). This is carried out over UDP port 500, and commonly uses either a shared password (so-called ”pre-shared keys”), public keys, or X.509 certificates on both ends, although other keying methods exist.
- Establishment of Encapsulating Security Payload (ESP) communication in transport mode. The IP protocol number for ESP is 50 (compare TCP’s 6 and UDP’s 17). At this point, a secure channel has been established, but no tunneling is taking place.
- Negotiation and establishment of L2TP tunnel between the SA endpoints. The actual negotiation of parameters takes place over the SA’s secure channel, within the IPsec encryption. L2TP uses UDP port 1701.

When the process is complete, L2TP packets between the endpoints are encapsulated by IPsec. Since the L2TP packet itself is wrapped and hidden within the IPsec packet, no information about the internal private network can be gathered from the encrypted packet. Also, it is not necessary to open UDP port 1701 on firewalls between the endpoints, since the inner packets are not acted upon until after IPsec data has been decrypted and stripped, which only takes place at the endpoints. A potential point of confusion in L2TP/IPsec is the use of the terms tunnel and secure channel. The term tunnel refers to a channel which allows untouched packets of one network to be transported over another network. In the case of L2TP/PPP, it allows L2TP/PPP packets to be transported over IP. A secure channel refers to a connection within which the confidentiality of all data is guaranteed. In L2TP/IPsec, first IPsec provides a secure channel, then L2TP provides a tunnel.

### API

The firmware of the WCC Lite features a built-in API which is accessible via the web interface.

<p class="callout warning">As of version 1.2.11, it does not implement any access restriction features apart from those provided by the firewall functionality.</p>

Individual API endpoints can be enabled or disabled via the web configuration interface at Services-&gt;API.

<p class="callout info">All endpoints are disabled by default.</p>

Available API endpoints are shown in the table below.

Table. Available API endpoints:

<table border="1" id="bkmrk-endpoint-description" style="border-collapse: collapse; width: 100%; height: 290px;"><tbody><tr style="height: 29px;"><td style="width: 24.8148%; height: 29px;">Endpoint</td><td style="width: 75.1852%; height: 29px;">Description</td></tr><tr style="height: 29px;"><td style="width: 24.8148%; height: 29px;">/api/version

</td><td style="width: 75.1852%; height: 29px;">Version of the API

</td></tr><tr style="height: 29px;"><td style="width: 24.8148%; height: 29px;">/api/actions

</td><td style="width: 75.1852%; height: 29px;">List of available points</td></tr><tr style="height: 29px;"><td style="width: 24.8148%; height: 29px;">/api/syncVersion</td><td style="width: 75.1852%; height: 29px;">Version of the sync service

</td></tr><tr style="height: 29px;"><td style="width: 24.8148%; height: 29px;">/api/sync

</td><td style="width: 75.1852%; height: 29px;">Protocol hub configuration sync (name=”file”)\*

</td></tr><tr style="height: 29px;"><td style="width: 24.8148%; height: 29px;">/api/syslog

</td><td style="width: 75.1852%; height: 29px;">Prints out the syslog

</td></tr><tr style="height: 29px;"><td style="width: 24.8148%; height: 29px;">/api/systemInfo

</td><td style="width: 75.1852%; height: 29px;">General system info

</td></tr><tr style="height: 29px;"><td style="width: 24.8148%; height: 29px;">/api/gsmInfo

</td><td style="width: 75.1852%; height: 29px;">GSM modem information

</td></tr><tr style="height: 29px;"><td style="width: 24.8148%; height: 29px;">/api/devices

</td><td style="width: 75.1852%; height: 29px;">List of configured devices

</td></tr><tr><td style="width: 24.8148%;">/api/device/info

</td><td style="width: 75.1852%;">Device information (name=”device\_alias”)\*\*

</td></tr><tr><td style="width: 24.8148%;">/api/device/tags

</td><td style="width: 75.1852%;">List of tags on particular device (name=”device\_alias”)\*\*

</td></tr><tr><td style="width: 24.8148%;">/api/device/tag/value

</td><td style="width: 75.1852%;">Tag value (name=”device\_alias”, name=”signal\_alias”)\*\*

</td></tr><tr><td style="width: 24.8148%;">/api/tags

</td><td style="width: 75.1852%;">List of configured tags

</td></tr><tr style="height: 29px;"><td style="width: 24.8148%; height: 29px;">/api/sysupgrade

</td><td style="width: 75.1852%; height: 29px;">Firmware upgrade (name=”file”)\*

</td></tr></tbody></table>

\* Endpoints accepting files

\*\* Endpoints accepting field data

The API accepts data and files as POST requests encoded as ”multipart/form-data”.

### OpenVPN

#### OpenVPN Instances

The primary goal is to get a working WCC Lite tunnel and establish a basic platform for further customization. Most users will require further configuration tailored to their individual needs. If you are creating an OpenVPN server (either type), you must create security certificates using the instructions below. If you are using OpenVPN as a client, the required certificates should have been provided with your configuration details. OpenVPN can be configured either by using WCC Lite Web interface or uploading the OVPN file containing necessary parameters. OpenVPN will automatically attempt to load all \*.conf files placed in the /etc/openvpn folder. Several OpenVPN recipes are suggested containing most used configurations that may only require minor changes. If a user intends setting up OpenVPN without OVPN file, it is highly advised to use these recipes and tweaking them up to individual needs.

[![image-1689162191122.png](https://wiki.elseta.com/uploads/images/gallery/2023-07/scaled-1680-/image-1689162191122.png)](https://wiki.elseta.com/uploads/images/gallery/2023-07/image-1689162191122.png)

OpenVPN instances page contains parameters to be configured.

<span style="text-decoration: underline;">Enabled</span>: Flag to specify if a particular configuration should be enabled;

<span style="text-decoration: underline;">Started</span>: Specifies if a particular configuration has been started by OpenVPN;

<span style="text-decoration: underline;">Start/Stop:</span> Button to manually start or stop any configured tunnels;

<span style="text-decoration: underline;">Port</span>: Specifies the listening port of this service;

<span style="text-decoration: underline;">Protocol</span>: A standard that defines how to establish and maintain a network connection: UDP - User Datagram Protocol, TCP - Transmission Control Protocol.

More parameters for every instance can be changed by pressing Edit button, configuration can be removed with Delete button. Pressing Edit takes the user to main configuration screen containing the options usually used in particular OpenVPN recipes. To do more specific changes user should further select Switch to advanced configuration.

OVPN files contain configuration in a textual form therefore changing parameters requires having prior knowledge about different OpenVPN parameters. It is advised to used OVPN files, however, if configuration has been pre-built beforehand and is used without further changes.

### ser2net

The ser2net daemon allows telnet and tcp sessions to be established with a device’s serial ports. The program comes up normally as a daemon, opens the TCP ports specified in the configuration file, and waits for connections. Once a connection occurs, the program attempts to set up the connection and open the serial port. If another user is already using the connection or serial port, the connection is refused with an error message.

### SNMP

SNMP (Simple Network Management Protocol) is an internet-standard protocol for managing devices on IP networks. SNMP exposes management data in the form of a hierarchy of variables in a MIB (Management Information Base).  
WCC Lite supports SNMP service which is not added to default build of firmware but can be installed as a module. It enables user to collect data on various parameters of system:  
• CPU time - time spent for calculations of various processes:  
user - time for user processes;  
system - time for system processes;  
idle - time spent idling;  
interrupts - time spent handling interrupts.  
• CPU load average - CPU load average for 1, 5 and 15 minutes respectively;  
• Disk usage:  
total - total amount of storage in the device (in kB)  
available - amount of storage available to store data (in kB)  
used - amount of storage used in the device (in KB)  
blocks used percentage - blocks (sectors) used to store data in a disk (in kB)  
inodes used percentage - the inode (index node) is a data structure in a Unix-style file system that describes a file-system object such as a file or a directory. Each inode stores the attributes and disk block location(s) of the object’s data.  
• Memory usage - RAM usage statistics:  
total - total amount of RAM in the device (in kB);  
available - unused amount of RAM in the device (in kB);  
shared - shared amount of RAM between multiple processes (in kB);  
buffered - refers to an electronic buffer placed between the memory and the memory controller;  
cached - a portion of memory made of high-speed static RAM (SRAM) instead of the slower dynamic RAM (DRAM) used for main memory;  
• Network interfaces:  
MTU - maximum transmission unit to be sent over network;  
speed - rate of network transmission;  
physical address - unique MAC address assigned to a device;  
tx/rx: byte, packet, drop, error count;  
• System properties:  
uptime - time since the device was turned on;  
process uptime - time since the process has been started;  
hostname - a label that is assigned to a device connected to a computer network;  
name - name of the device (if defined);  
location - location of the device (if defined).