Domnev: Difference between revisions

From Teltonika Networks Wiki
No edit summary
No edit summary
 
(33 intermediate revisions by the same user not shown)
Line 1: Line 1:
<p style="color:red">The information in this page is updated in accordance with [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__
 
==Summary==
==Configuration overview and prerequisites==
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.
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==
The '''[[TRB143_M-Bus|M-Bus Settings]]''' section is used to configure the general service functionality. To set up a new M-Bus instance, go to '''Services → M-Bus → Client'''. 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:
 
# '''Name''': Enter the desired name of the M-Bus device
# '''Address type''': select which M-Bus address will be used
# '''Primary/Secondary address''': specify M-Bus address
 
[[File:Mbus adding new device configuration v3.png|border|class=tlt-border]]
 
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:


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.
* If you have specified correct primary/secondary address, you will receive:
[[File:Networking rut9 manual webui basic advanced mode.gif|border|center|class=tlt-border|1102x52px]]
[[File:Mbus device pingable v2.png|border|class=tlt-border|300px]]


==Topology==
* 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 - RUTX11 as a hub. It will be our "default gateway" for spoke device. RUTX11 has a LAN subnet of 192.168.11.0/24 configured on it, which should be reachable by the spoke.
Once finished, save the configuration by clicking [[File:Savenapply button.png|Savenapply button.png]].


RUT2 - RUT955 as a spoke. It will be connecting to a hub for basic internet access. RUT955 has a lan subnet of 192.168.9.0/24 configured on it, which should be reachable by the hub.
===Scanning for available M-Bus devices===
----


==RUT1 (Hub) 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.
Start by configuring 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.'''''
====Scan settings====
===Instance configuration===
----
----
<table class="nd-othertables_2">
You will be granted to a new window. Configure scan settings accordingly:
    <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===
# '''Scan type''': select which M-Bus address will be scanned
# '''Scan range''': From what M-Bus address scanning will start and M-Bus address until scanning will be performed.
[[File:Mbus scan.png|border|class=tlt-border]]
 
To start the scan click on [[File: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:


<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 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>


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.
==Gathering M-Bus data==
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>.
[[File:Mbus status active v2.png|border|class=tlt-border]]
===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>
[[File:Mbus data collect overview.png|border|class=tlt-border]]
        <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===
====Data collecting group instance====
----
----


<table class="nd-othertables_2">
Each data collection group contains the following information. Configure device accordingly:
    <tr>
 
        <th width=330; style="border-bottom: 1px solid white;></th>
# '''Enabled''': on
        <th width=800; style="border-bottom: 1px solid white;" rowspan=2>[[File:IPsec Phase1.png|border|class=tlt-border|742x254px|right]]</th>
# '''Name''': desired name of the instance
    </tr>
# '''Period''': desired time duration between data retrievals
    <tr>
# '''Data type''': desired data type to process the received data. Depending on your needs you can select between 5 different data types: '''JSON, XML, ASCII, Hexadecimal''' and '''Binary'''.
        <td style="border-bottom: 4px solid white>
 
# Encryption - '''''AES256;'''''
[[File:Mbus data collect group v2.png|border|class=tlt-border]]
# Authentication - '''''SHA512;'''''
# DH group - '''''ECP521;'''''
        </td>
    </tr>
</table>


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:Mbus TEST output.png|border|class=tlt-border]]
====Group values====
----
----
<table class="nd-othertables_2">
To reach group values configuration press [[File:Pencil2.png]] button:
    <tr>
 
        <th width=330; style="border-bottom: 1px solid white;></th>
[[File:Mbus edit group values.png|border|class=tlt-border]]
        <th width=800; style="border-bottom: 1px solid white;" rowspan=2>[[File:IPsec Phase2.png|border|class=tlt-border|748x257px|right]]</th>
 
    </tr>
There you can adjust additional settings:
    <tr>
 
        <td style="border-bottom: 4px solid white>
# '''Enable''': Enable/disable data group value.
# Encryption - '''''AES128;'''''
# '''FCB toggle''': FCB (Frame Count-Bit), one-bit counter for reliable server-client communication.
# Authentication - '''''SHA256;'''''
# '''Manufacturer information''': Select to include manufacturer information in the payload.
# DH group - '''''ECP521;'''''
# '''Selected parameters''': Select to include the all parameters saved from device, or a custom subset of them. If the custom is selected you can specify '''frame''', '''record''' numbers and also a '''paramater'''  
        </td>
 
    </tr>
[[File:Mbus device groupsa.png|border|class=tlt-border]]
</table>
 
 
==Sending data to the server==
The '''[[TRB143_Data_to_Server|Data to Server]]''' feature provides you with the possibility to set up data senders that collect data from various sources and periodically send it to remote servers. This section will walk you through configuring the Data to Server to send M-Bus data to the desired HTTP or MQTT server.


==RUT2 (Spoke) configuration==
===Data to Server configuration===
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">
To set up Data to Server, navigate to Services → Data to Server. Enter desired name of the instnace and hit [[File:Add Button.png|60x90px]] button which is shown below.
    <tr>
 
        <th width=330; style="border-bottom: 1px solid white;></th>
[[File:Mbus data to server create.png|border|class=tlt-border]]
        <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===
===Data configuration===
----
----


<table class="nd-othertables_2">
Each data collection group contains the following information. Configure device accordingly:
    <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>


===Proposalconfiguration===
# '''Name''': desired name of the instance
# '''Type''': M-Bus data
# '''Format''': custom or JSON depending on a need.
 
[[File:Mbus data to server configuration.png|border|class=tlt-border]]
 
 
Once finished configuring Data configuration tab click on [[File:Mbus data to server collection edit.png|160x160px]] button.
 
===Collection 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 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 to server collection configuration.png|border|class=tlt-border]]
Once finished configuring Collection configuration tab click on [[File:Mbus data to server server button.png|160x160px]] button.
===Server configuration===
----
----
<table class="nd-othertables_2">
This section contains information on how to configure MQTT and HTTP servers information.
    <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 configuration==
====HTTP configuration====
After we establish the tunnel, we may observe the following information:
===RUT1 (Hub) side===
----
----
<pre>ipsec status all</pre>


<pre>
# '''Type''': HTTP
root@Teltonika-RUTX12:~# ipsec statusall
# '''Server address''': desired server address
Status of IKE charon daemon (strongSwan 5.9.2, Linux 5.4.231, armv7l):
  uptime: 74 minutes, since Mar 21 08:52:39 2023
  worker threads: 11 of 16 idle, 5/0/0/0 working, job queue: 0/0/0/0, scheduled: 2
  loaded plugins: charon aes des sha2 sha1 md4 md5 random nonce x509 revocation constraints pubkey pkcs1 pkcs8 pgp pem openssl gmp xcbc hmac kernel-netlink socket-default stroke vici updown eap-identity eap-mschapv2 xauth-generic
Virtual IP pools (size/online/offline):
  10.20.30.0/24: 254/1/0
Listening IP addresses:
  84.xxx.xxx.xxx
  192.168.11.1
  fd93:51e6:6fe8::1
Connections:
  HUB-HUB_c:  %any...%any  IKEv2
  HUB-HUB_c:  local:  uses pre-shared key authentication
  HUB-HUB_c:  remote: uses pre-shared key authentication
  HUB-HUB_c:  child:  0.0.0.0/0 === dynamic TUNNEL
Security Associations (1 up, 0 connecting):
  HUB-HUB_c[2]: ESTABLISHED 74 minutes ago, 84.xxx.xxx.xxx[84.xxx.xxx.xxx]...88.xxx.xxx.xxx[192.168.86.197]
  HUB-HUB_c[2]: IKEv2 SPIs: ded11f31c20352dc_i 58ebc8d96264c21e_r*, pre-shared key reauthentication in 89 minutes
  HUB-HUB_c[2]: IKE proposal: AES_CBC_256/HMAC_SHA2_512_256/PRF_HMAC_SHA2_512/ECP_521
  HUB-HUB_c{3}:  INSTALLED, TUNNEL, reqid 1, ESP in UDP SPIs: c27cb140_i c7382615_o
  HUB-HUB_c{3}: AES_CBC_128/HMAC_SHA2_256_128/ECP_521, 215536 bytes_i (1981 pkts, 1s ago), 126021 bytes_o (499 pkts, 1s ago), rekeying in 14 minutes
  HUB-HUB_c{3}:  0.0.0.0/0 === 10.20.30.1/32
</pre>


<pre> /tmp/ipsec/ipsec.conf </pre> command output:
'''Note''': not specified fields are optional.
<pre>
root@Teltonika-RUTX12:~# cat /tmp/ipsec/ipsec.conf
# generated by /etc/init.d/ipsec
version 2


conn HUB-HUB_c
[[File:Mbus data to server HTTP configuration.png|border|class=tlt-border]]
  left=%any
  right=%any
  leftfirewall=yes
  rightfirewall=no
  ikelifetime=3h
  lifetime=1h
  margintime=9m
  keyingtries=3
  dpdaction=none
  dpddelay=30s
  dpdtimeout=90s
  leftauth=psk
  rightauth=psk
  rightsourceip=10.20.30.0/24
  auto=start
  leftsubnet=0.0.0.0/0
  rightdns=9.9.9.9
  aggressive=no
  forceencaps=no
  type=tunnel
  keyexchange=ikev2
  esp=aes128-sha256-ecp521!
  ike=aes256-sha512-ecp521!
</pre>


===RUT2 (Spoke) side===
====MQTT configuration====
----
----


<pre>
# '''Type''': MQTT
root@Teltonika-RUT955:~# ipsec statusall
# '''Server address''': desired server address
Status of IKE charon daemon (strongSwan 5.9.2, Linux 5.4.229, mips):
# '''Topic''': MQTT topic to be used for publishing the data.
  uptime: 23 hours, since Mar 20 12:21:06 2023
  worker threads: 11 of 16 idle, 5/0/0/0 working, job queue: 0/0/0/0, scheduled: 9
  loaded plugins: charon aes des sha2 sha1 md4 md5 random nonce x509 revocation constraints pubkey pkcs1 pkcs8 pgp pem openssl gmp xcbc hmac kernel-netlink socket-default stroke vici updown eap-identity eap-mschapv2 xauth-generic
Listening IP addresses:
  192.168.86.197
  192.168.9.1
  fd35:98cd:61f0::1
Connections:
passth_SPOKE_ph2_1_lan:  %any...%any  IKEv1/2
passth_SPOKE_ph2_1_lan:  local:  uses public key authentication
passth_SPOKE_ph2_1_lan:  remote: uses public key authentication
passth_SPOKE_ph2_1_lan:  child: 192.168.9.0/24 === 192.168.9.0/24 PASS
SPOKE-SPOKE_c:  %any...84.15.162.30  IKEv2
SPOKE-SPOKE_c:  local:  uses pre-shared key authentication
SPOKE-SPOKE_c:  remote: [84.15.162.30] uses pre-shared key authentication
SPOKE-SPOKE_c:  child:  dynamic === 0.0.0.0/0 TUNNEL
Shunted Connections:
passth_SPOKE_ph2_1_lan:  192.168.9.0/24 === 192.168.9.0/24 PASS
Security Associations (1 up, 0 connecting):
SPOKE-SPOKE_c[431]: ESTABLISHED 77 minutes ago, 192.168.86.197[192.168.86.197]...84.15.162.30[84.15.162.30]
SPOKE-SPOKE_c[431]: IKEv2 SPIs: ded11f31c20352dc_i* 58ebc8d96264c21e_r, pre-shared key reauthentication in 77 minutes
SPOKE-SPOKE_c[431]: IKE proposal: AES_CBC_256/HMAC_SHA2_512_256/PRF_HMAC_SHA2_512/ECP_521
SPOKE-SPOKE_c{14}:  INSTALLED, TUNNEL, reqid 1, ESP in UDP SPIs: c7382615_i c27cb140_o
SPOKE-SPOKE_c{14}:  AES_CBC_128/HMAC_SHA2_256_128/ECP_521, 136768 bytes_i (536 pkts, 6s ago), 235975 bytes_o (2169 pkts, 1s ago), rekeying in 13 minutes
SPOKE-SPOKE_c{14}:  10.20.30.1/32 === 0.0.0.0/0
</pre>


'''Note''': not specified fields are optional.


<pre>
[[File:Mbus data to server MQTT configuration.png|border|class=tlt-border]]
root@Teltonika-RUT955:~# cat /tmp/ipsec/ipsec.conf
# generated by /etc/init.d/ipsec
version 2


conn passth_SPOKE_ph2_1_lan
Once finished configuring Server configuration tab click on [[File:Savenapply button.png|Savenapply button.png]] button.
  type=passthrough
  leftsubnet=192.168.9.1/24
  rightsubnet=192.168.9.1/24
  auto=route
 
conn SPOKE-SPOKE_c
  left=%any
  right=84.15.162.30
  leftsourceip=%config
  leftfirewall=yes
  rightfirewall=no
  ikelifetime=3h
  lifetime=1h
  margintime=9m
  keyingtries=3
  dpdaction=none
  dpddelay=30s
  dpdtimeout=90s
  leftauth=psk
  rightauth=psk
  rightsubnet=0.0.0.0/0
  auto=start
  aggressive=no
  forceencaps=no
  type=tunnel
  keyexchange=ikev2
  esp=aes128-sha256-ecp521!
  ike=aes256-sha512-ecp521!
</pre>


===Results===
----


== See also ==
[[File:Mbus data received v2.png|border|class=tlt-border]]


== External links ==
'''Note''': received data formating depends on the settings you apply under Data to Server and M-Bus configurations.

Latest revision as of 07:20, 25 October 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.

Adding M-Bus devices

The M-Bus Settings section is used to configure the general service functionality. To set up a new M-Bus instance, go to Services → M-Bus → Client. Add a new device to the configuration press button which is shown below.

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

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

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

  • 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:

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 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.

To start the scan click on button.

Found devices


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

You can either (1) M-Bus devices primary address or (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.

Data collecting groups


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

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. Depending on your needs you can select between 5 different data types: JSON, XML, ASCII, Hexadecimal and Binary.

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

Group values


To reach group values configuration press button:

There you can adjust additional settings:

  1. Enable: Enable/disable data group value.
  2. FCB toggle: FCB (Frame Count-Bit), one-bit counter for reliable server-client communication.
  3. Manufacturer information: Select to include manufacturer information in the payload.
  4. Selected parameters: Select to include the all parameters saved from device, or a custom subset of them. If the custom is selected you can specify frame, record numbers and also a paramater


Sending data to the server

The Data to Server feature provides you with the possibility to set up data senders that collect data from various sources and periodically send it to remote servers. This section will walk you through configuring the Data to Server to send M-Bus data to the desired HTTP or MQTT server.

Data to Server configuration


To set up Data to Server, navigate to Services → Data to Server. Enter desired name of the instnace and hit button which is shown below.

Data configuration


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

  1. Name: desired name of the instance
  2. Type: M-Bus data
  3. Format: custom or JSON depending on a need.


Once finished configuring Data configuration tab click on button.

Collection configuration


Once finished configuring Collection configuration tab click on button.

Server configuration


This section contains information on how to configure MQTT and HTTP servers information.

HTTP configuration


  1. Type: HTTP
  2. Server address: desired server address

Note: not specified fields are optional.

MQTT configuration


  1. Type: MQTT
  2. Server address: desired server address
  3. Topic: MQTT topic to be used for publishing the data.

Note: not specified fields are optional.

Once finished configuring Server configuration tab click on Savenapply button.png button.

Results


Note: received data formating depends on the settings you apply under Data to Server and M-Bus configurations.