Difference between revisions of "Domnev"

From Teltonika Networks Wiki
 
(17 intermediate revisions by the same user not shown)
Line 1: Line 1:
<p style="color:red">The information on this page is updated in accordance with the [https://wiki.teltonika-networks.com/view/FW_%26_SDK_Downloads'''00.07.4'''] firmware version .</p>
+
<p style="color:red">The information on this page is updated in accordance with the [https://wiki.teltonika-networks.com/view/FW_%26_SDK_Downloads'''00.07.08'''] firmware version .</p>
==Introduction==
+
__TOC__
Normally we configure IPsec for LAN-to-LAN communication which is also known as split-tunnel VPN when only specific hosts should be reachable via VPN tunnel. However, we may also take a different approach and configure VPN tunnel using full-tunnel method. This means that any non-directly connected network (i.e. lan interface) will be reachable only via IPsec tunnel and not via typical default route.
+
==Summary==
 
+
This article contains instructions on how to send M-Bus data to the server using various protocols.
==Configuration overview and prerequisites==
 
  
 +
==Configuration overview & prerequisites==
 
Before we begin, let's take a look at the configuration that we are attempting to achieve and the prerequisites that make it possible.
 
Before we begin, let's take a look at the configuration that we are attempting to achieve and the prerequisites that make it possible.
  
 
'''Prerequisites''':
 
'''Prerequisites''':
* Two RUT/RUTX series routers with RUTOS firmware;
+
* TRB143;
* An end device (PC, Laptop) for configuration;
+
* M-Bus device;
 +
* Server;
 +
* An end device (PC, Laptop, Tablet, Smartphone) for configuration;
 +
 
 +
 
 +
{{Template:Networking_rutos_manual_basic_advanced_webui_disclaimer
 +
| series = RUTX
 +
}}
 +
 
 +
 
 +
==Adding M-Bus devices==
 +
To add a new device to the configuration press [[File:Add Button.png|60x90px]] button which is shown below.
 +
 
 +
[[File:Mbus adding new device.png||border|class=tlt-border]]
 +
 
 +
===Device configuration===
 +
----
 +
You will be granted to a new window. Configure your M-Bus device accordingly:
  
If you're having trouble finding any page or some of the parameters described here on your device's WebUI, you should turn on '''"Advanced WebUI"''' mode. You can do that by '''clicking''' the '''"Basic"''' button '''under''' '''"Mode,"''' which is located at the top-right corner of the WebUI.
+
# '''Name''': Enter the desired name of the M-Bus device
[[File:Networking rut9 manual webui basic advanced mode.gif|border|center|class=tlt-border|1102x52px]]
+
# '''Address type''': select which M-Bus address will be used
 +
# '''Primary/Secondary address''': specify M-Bus address
  
==Topology==
+
[[File:Mbus adding new device configuration v3.png|border|class=tlt-border]]
  
[[File:IPsec TLT to TLT Topology.png|border|center|class=tlt-border|839x399px]]
+
Test if the M-Bus device is reachable by a specified primary/secondary address. To do so click on [[File:Ping_device_option_mbus.png|110x110px]]. You might get on of two outputs:
  
'''RUT1''' - RUTX12 as a '''hub'''. A hub is a server, to which our spoke will be connecting (IPsec responder). It will be our "default gateway" for the spoke device. RUTX12 has a LAN subnet of 192.168.11.0/24 configured on it, which should be reachable by the '''spoke'''.
+
* If you have specified correct primary/secondary address, you will receive:
 +
[[File:Mbus device pingable v2.png|border|class=tlt-border|300px]]
  
'''RUT2''' - RUT955 as a '''spoke'''. A spoke is a client, that will be connected to the spoke (IPsec initiator). It will be connected to a '''hub''' for basic internet access. RUT955 has a LAN subnet of 192.168.9.0/24 configured on it.
+
* If you have specified incorrect primary/secondary address, you will receive (if you do not know what address should be used, refer to the Scanning for available M-Bus devices (PRIDET URL) secion:
 +
[[File:Mbus device not pingable v2.png|border|class=tlt-border|300px]]
  
==RUT1 (Hub) configuration==
+
Once finished, save the configuration by clicking [[File:Savenapply button.png|Savenapply button.png]].
Start by configuring the hub (RUT1) device. Login to the WebUI, navigate to '''Services → VPN → IPsec''' and '''add a new IPsec instance'''. Configure everything as follows.
 
  
'''Note:''' '''''Not specified fields can be left as is or changed according to your needs.'''''
+
===Scanning for available M-Bus devices===
===Instance configuration===
 
 
----
 
----
<table class="nd-othertables_2">
 
    <tr>
 
        <th width=330; style="border-bottom: 1px solid white;></th>
 
        <th width=800; style="border-bottom: 1px solid white"; rowspan=2>[[File:IPsec HUB.png|border|class=tlt-border|755x406px|right]]</th>
 
    </tr>
 
    <tr>
 
        <td style="border-bottom: 4px solid white>
 
# '''''Enable''''' instance;
 
# Authentication method - '''''Pre-shared key;'''''
 
# Pre-shared key - '''''your desired password;'''''
 
        </td>
 
    </tr>
 
</table>
 
  
===Connection configuration===
+
If you are not sure what address your M-Bus devices have, you can try scanning for the available M-Bus devices. To do so click on [[File:Scan button.png]] button.
 +
 
 +
====Scan settings====
 
----
 
----
 +
You will be granted to a new window. Configure scan settings accordingly:
  
<table class="nd-othertables_2">
+
# '''Scan type''': select which M-Bus address will be scanned
    <tr>
+
# '''Scan range''': From what M-Bus address scanning will start and M-Bus address until scanning will be performed.
        <th width=330; style="border-bottom: 1px solid white;></th>
+
[[File:Mbus scan.png|border|class=tlt-border]]
        <th width=800; style="border-bottom: 1px solid white;" rowspan=2>[[File:IPsec HUB Connection.png|border|class=tlt-border|753x368px|right]]</th>
 
    </tr>
 
    <tr>
 
        <td style="border-bottom: 4px solid white>
 
# Mode - '''''Start;'''''
 
# Type - '''''Tunnel;'''''
 
# Local subnet - '''''0.0.0.0/.0;'''''
 
# Key exchange - '''''IKEv2;'''''
 
        </td>
 
    </tr>
 
</table>
 
  
----
+
To start the scan click on [[File:Start scan button.png]] button.
<table class="nd-othertables_2">
 
    <tr>
 
        <th width=330; style="border-bottom: 1px solid white;></th>
 
        <th width=800; style="border-bottom: 1px solid white;" rowspan=2>[[File:IPsec HUB Connection Advanced.png|border|class=tlt-border|752x541px|right]]</th>
 
    </tr>
 
    <tr>
 
        <td style="border-bottom: 4px solid white>
 
# '''''Enable''''' '''''Local firewall;'''''
 
# Remote source IP - '''''10.20.30.0/24;'''''
 
# Remote DNS '''''9.9.9.9;'''''
 
        </td>
 
    </tr>
 
</table>
 
  
===Proposal configuration===
+
====Found devices====
 
----
 
----
 +
Once the scan is finished you should see the list of M-Bus devices that TRB143 were able to find:
  
<table class="nd-othertables_2">
+
[[File:Mbus scanned devices add.png|border|class=tlt-border]]
    <tr>
 
        <th width=330; style="border-bottom: 1px solid white;></th>
 
        <th width=800; style="border-bottom: 1px solid white;" rowspan=2>[[File:IPsec Phase1.png|border|class=tlt-border|742x254px|right]]</th>
 
    </tr>
 
    <tr>
 
        <td style="border-bottom: 4px solid white>
 
# Encryption - '''''AES256;'''''
 
# Authentication - '''''SHA512;'''''
 
# DH group - '''''ECP521;'''''
 
        </td>
 
    </tr>
 
</table>
 
  
----
+
You can either [[File:Pencil2.png]] '''(1)''' M-Bus devices primary address or [[File:Add Button.png|60x90px]] '''(2)''' to the M-Bus devices list.
<table class="nd-othertables_2">
 
    <tr>
 
        <th width=330; style="border-bottom: 1px solid white;></th>
 
        <th width=800; style="border-bottom: 1px solid white;" rowspan=2>[[File:IPsec Phase2.png|border|class=tlt-border|748x257px|right]]</th>
 
    </tr>
 
    <tr>
 
        <td style="border-bottom: 4px solid white>
 
# Encryption - '''''AES128;'''''
 
# Authentication - '''''SHA256;'''''
 
# DH group - '''''ECP521;'''''
 
        </td>
 
    </tr>
 
</table>
 
  
==RUT2 (Spoke) configuration==
+
==Gathering M-Bus data==
Login to the RUT2 WebUI, navigate to '''Services → VPN → IPsec''' and '''add a new IPsec instance.''' Configure everything as follows.
 
===Instance configuration===
 
----
 
<table class="nd-othertables_2">
 
    <tr>
 
        <th width=330; style="border-bottom: 1px solid white;></th>
 
        <th width=800; style="border-bottom: 1px solid white;" rowspan=2>[[File:IPsec SPOKE.png|border|class=tlt-border|742x399px|right]]</th>
 
    </tr>
 
    <tr>
 
        <td style="border-bottom: 4px solid white>
 
# '''''Enable''''' instance;
 
# Remote endpoint - '''''RUT1 public IP;'''''
 
# Authentication method - '''''Pre-shared key;'''''
 
# Pre-shared key - the '''''same password''''' you have '''''set on''''' '''''RUT1''''' when configuring '''''HUB instance;'''''
 
        </td>
 
    </tr>
 
</table>
 
  
===Connection configuration===
+
If the device successfully added to the list, under the General settings you should see that the Status changes to <span style="color:green">Active</span>.
----
 
  
<table class="nd-othertables_2">
+
[[File:Mbus status active v2.png|border|class=tlt-border]]
    <tr>
 
        <th width=330; style="border-bottom: 1px solid white;></th>
 
        <th width=800; style="border-bottom: 1px solid white;" rowspan=2>[[File:IPsec SPOKE Connection.png|border|class=tlt-border|761x280px|right]]</th>
 
    </tr>
 
    <tr>
 
        <td style="border-bottom: 4px solid white>
 
# Mode - '''''Start;'''''
 
# Type - '''''Tunnel;'''''
 
# '''''Enable''''' '''''default route;'''''
 
# Key exchange - '''''IKEv2;'''''
 
        </td>
 
    </tr>
 
</table>
 
  
===Proposal configuration===
+
===Data collecting groups===
 
----
 
----
<table class="nd-othertables_2">
+
To reach data collecting groups configuration press [[File:Pencil2.png]] button. [[File:Add Button.png|60x90px]] button lets you to create a new instance.
    <tr>
 
        <th width=330; style="border-bottom: 1px solid white;></th>
 
        <th width=800; style="border-bottom: 1px solid white;" rowspan=2>[[File:IPsec Phase1.png|border|class=tlt-border|742x254px|right]]</th>
 
    </tr>
 
    <tr>
 
        <td style="border-bottom: 4px solid white>
 
# Encryption - '''''AES256;'''''
 
# Authentication - '''''SHA512;'''''
 
# DH group - '''''ECP521;'''''
 
        </td>
 
    </tr>
 
</table>
 
  
 +
[[File:Mbus data collect overview.png|border|class=tlt-border]]
 +
 +
====Data collecting group instance====
 
----
 
----
<table class="nd-othertables_2">
 
    <tr>
 
        <th width=330; style="border-bottom: 1px solid white;></th>
 
        <th width=800; style="border-bottom: 1px solid white;" rowspan=2>[[File:IPsec Phase2.png|border|class=tlt-border|748x257px|right]]</th>
 
    </tr>
 
    <tr>
 
        <td style="border-bottom: 4px solid white>
 
# Encryption - '''''AES128;'''''
 
# Authentication - '''''SHA256;'''''
 
# DH group - '''''ECP521;'''''
 
        </td>
 
    </tr>
 
</table>
 
 
==Testing the configuration==
 
If you've followed all the steps presented above, your configuration should be finished. But as with any other configuration, it is always wise to test the setup in order to make sure that it works properly.
 
  
Using the <code><span class="highlight">'''ipsec status'''</span></code> command we can see that IPsec tunnel is successfully established on both routers. The command output on a '''hub (RUT1)''' device:
+
Each data collection group contains the following information. Configure device accordingly:
  
[[File:IPsec_statusHUB_new.png|border|class=tlt-border|776x114px|center]]
+
# '''Enabled''': on
 +
# '''Name''': desired name of the instance
 +
# '''Period''': desired time duration between data retrievals
 +
# '''Data type''': desired data type to process the received data. You can choose from JSON, XML, ASCII, Hexadecimal and Binary formats.
  
The same command output on '''spoke (RUT2)''' device:
+
You can check if your configuration works accordingly by pressing the [[File:Mbus test button.png]] button. You should see the data in a pop-up field.
  
[[File:IPsec status SPOKE.png|border|class=tlt-border|827x158px|center]]
+
[[File:Mbus data collect group v2.png|border|class=tlt-border]]
  
Also, as the hub should be reachable by spoke, we can try pinging the hub using <code><span class="highlight" >'''ping 192.168.11.1'''</span></code>:
 
  
[[File:Ping to hub.png|border|class=tlt-border|506x157px|center]]
+
==See Also==
  
== See also ==
+
==External links==
[[RUTX12_VPN#IPsec|IPsec on Teltonika Networks devices]]
+
[https://flespi.io/#/ Flespi.io]
== External links ==
 
[https://openwrt.org/docs/guide-user/services/vpn/strongswan/basics OpenWrt IPsec basics]
 

Latest revision as of 14:06, 24 July 2024

The information on this page is updated in accordance with the 00.07.08 firmware version .

Summary

This article contains instructions on how to send M-Bus data to the server using various protocols.

Configuration overview & prerequisites

Before we begin, let's take a look at the configuration that we are attempting to achieve and the prerequisites that make it possible.

Prerequisites:

  • TRB143;
  • M-Bus device;
  • Server;
  • An end device (PC, Laptop, Tablet, Smartphone) for configuration;


If you're having trouble finding this page or some of the parameters described here on your device's WebUI, you should turn on "Advanced WebUI" mode. You can do that by clicking the "Advanced" button, located at the top of the WebUI.

Networking rutos manual webui basic advanced mode 75.gif


Adding M-Bus devices

To add a new device to the configuration press Add Button.png button which is shown below.

Mbus adding new device.png

Device configuration


You will be granted to a new window. Configure your M-Bus device accordingly:

  1. Name: Enter the desired name of the M-Bus device
  2. Address type: select which M-Bus address will be used
  3. Primary/Secondary address: specify M-Bus address

Mbus adding new device configuration v3.png

Test if the M-Bus device is reachable by a specified primary/secondary address. To do so click on Ping device option mbus.png. You might get on of two outputs:

  • If you have specified correct primary/secondary address, you will receive:

Mbus device pingable v2.png

  • If you have specified incorrect primary/secondary address, you will receive (if you do not know what address should be used, refer to the Scanning for available M-Bus devices (PRIDET URL) secion:

Mbus device not pingable v2.png

Once finished, save the configuration by clicking Savenapply button.png.

Scanning for available M-Bus devices


If you are not sure what address your M-Bus devices have, you can try scanning for the available M-Bus devices. To do so click on Scan button.png button.

Scan settings


You will be granted to a new window. Configure scan settings accordingly:

  1. Scan type: select which M-Bus address will be scanned
  2. Scan range: From what M-Bus address scanning will start and M-Bus address until scanning will be performed.

Mbus scan.png

To start the scan click on Start scan button.png button.

Found devices


Once the scan is finished you should see the list of M-Bus devices that TRB143 were able to find:

Mbus scanned devices add.png

You can either Pencil2.png (1) M-Bus devices primary address or Add Button.png (2) to the M-Bus devices list.

Gathering M-Bus data

If the device successfully added to the list, under the General settings you should see that the Status changes to Active.

Mbus status active v2.png

Data collecting groups


To reach data collecting groups configuration press Pencil2.png button. Add Button.png button lets you to create a new instance.

Mbus data collect overview.png

Data collecting group instance


Each data collection group contains the following information. Configure device accordingly:

  1. Enabled: on
  2. Name: desired name of the instance
  3. Period: desired time duration between data retrievals
  4. Data type: desired data type to process the received data. You can choose from JSON, XML, ASCII, Hexadecimal and Binary formats.

You can check if your configuration works accordingly by pressing the Mbus test button.png button. You should see the data in a pop-up field.

Mbus data collect group v2.png


See Also

External links

Flespi.io