Template:Networking rutos manual mbus: Difference between revisions

From Teltonika Networks Wiki
VisualWikitext
No edit summary
No edit summary
 
(11 intermediate revisions by 2 users not shown)
Line 14: Line 14:
This manual page provides an overview of the M-Bus functionality in {{{name}}} devices.
This manual page provides an overview of the M-Bus functionality in {{{name}}} devices.


==M-Bus Settings==
==Client==


The <b>M-Bus Settings</b> section is used to configure the general service functionality. The figure below is an example of the M-Bus Settings and the table below provides information on the fields contained in that section:
===Global settings===
----
Notice the Global section config. It is used to outright turn the service off or on if any active configurations are present.  


[[File:Networking_rutos_manual_mbus_mbus_settings_v1.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_mbus_client_global_settings_cogwheel.png|border|class=tlt-border]]
 
Clicking the Cog icon opens a modal window. The global configuration slider can be set and it's state saved.
 
[[File:Networking_rutos_manual_mbus_client_global_settings.png|border|class=tlt-border]]


<table class="nd-mantable">
<table class="nd-mantable">
Line 27: Line 33:
     </tr>
     </tr>
     <tr>
     <tr>
         <td>Enable</td>
         <td>Enabled</td>
         <td>off | on; default: <b>off</b></td>
         <td>on {{!}} off; default: <b>on</b></td>
         <td>Enables the service.</td>
        <td>Global enable switch for the whole M-Bus service.</td>
    </tr>
    <tr>
        <td>Timeout</td>
        <td>integer; default: <b>1</b></td>
         <td>Maximum amount of time to wait when receiving a response from the device (in seconds).</td>
    </tr>
</table>
 
===General settings===
----
 
The M-Bus device configuration section is used to configure the general service functionality. The figure below is an example of the M-Bus Settings and the table below provides information on the fields contained in that section:
 
[[File:Networking_rutos_manual_mbus_client_general_settings_v1.png|border|class=tlt-border]]
 
<table class="nd-mantable">
    <tr>
        <th>Field</th>
        <th>Value</th>
        <th>Description</th>
    </tr>
    <tr>
        <td>Status</td>
        <td>Inactive {{!}} Active</td>
        <td>Status of service, whether it is currently running. If it is active, it will also show how long it has been running.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>Baud rate</td>
         <td>Baud rate</td>
         <td>300 | 600 | 1200 | 2400 | 4800 | 9600 ; default: <b>2400</b></td>
         <td>300 {{!}} 600 {{!}} 1200 {{!}} 2400 {{!}} 4800 {{!}} 9600 ; default: <b>2400</b></td>
         <td>Specifies the M-Bus server network baud rate.</td>
         <td>Specifies the M-Bus server network baud rate.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>Database location</td>
         <td>Stop bits</td>
         <td>RAM memory | Flash memory; default: <b>RAM memory</b></td>
         <td>1 {{!}} 2; default: <b>1</b></td>
         <td>Specifies where the database will be stored..</td>
         <td>Select how many stop bits will be used to detect the end of character.</td>
    </tr>
        <tr>
        <td>Parity</td>
        <td>Even {{!}} Odd {{!}} None; default: <b>Even</b></td>
        <td>Select what kind of parity bit to use for error detection.</td>
     </tr>
     </tr>
</table>
</table>


==Records==
===Devices===
----


By default there are no <b>Records</b> instances created. To start configuring, add a new record using the <b>Add New Instance</b> section below.
To add new device to configuration press <b>Add</b> button which is shown below.


[[File:Networking_rutos_manual_mbus_records_add_new_instance_v1.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_mbus_client_devices_add.png|border|class=tlt-border]]
 
The Devices section is used to configure the general device instance. The figure below is an example of the M-Bus device and the table below provides information on the fields contained in that section:
 
[[File:Networking_rutos_manual_mbus_client_device_configuration.png|border|class=tlt-border]]
 
<table class="nd-mantable">
    <tr>
        <th>Field</th>
        <th>Value</th>
        <th>Description</th>
    </tr>
    <tr>
        <td>Name</td>
        <td>String; default: <b>Device 1</b></td>
        <td>Display name of device configuration.</td>
    </tr>
    <tr>
        <td>Address type</td>
        <td>Primary | Secondary ; default: <b>Primary</b></td>
        <td>Primary address which will be used when sending requests.</td>
    </tr>
    <tr>
        <td>Primary address</td>
        <td>integer [0..250]; default: <b>empty</b></td>
        <td>Primary address which will be used when sending requests.</td>
    </tr>
    <tr>
        <td>Secondary address</td>
        <td>string of 16 symbols; default: <b>empty</b></td>
        <td>A unique device identifier which commonly includes the serial number.</td>
    </tr>
</table>


===M-Bus Record===
===Data collecting groups===
----
----
The <b>M-Bus Record</b> section is used to configure the general record instance. The figure below is an example of the M-Bus Record and the table below provides information on the fields contained in that section:


[[File:Networking_rutos_manual_mbus_record_mbus_record_demo_v4.png|border|class=tlt-border]]
To reach data collecting groups configuration press <b>Edit</b> button as shown below.
 
[[File:Networking_rutos_manual_mbus_client_data_collecting_groups.png|border|class=tlt-border]]
 
Before saving, you can check if your configuration works accordingly by pressing the Test Configuration button. You should see the data in a pop-up field.
 
[[File:Networking_rutos_manual_mbus_client_data_collecting_groups_configuration.png|border|class=tlt-border]]


<table class="nd-mantable">
<table class="nd-mantable">
Line 62: Line 136:
     </tr>
     </tr>
     <tr>
     <tr>
         <td>Enable</td>
         <td>Enabled</td>
         <td>off | on; default: <b>off</b></td>
         <td>on {{!}} off; default: <b>off</b></td>
         <td>Enables the service.</td>
         <td>Button to enable/disable data collecting group.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>Name</td>
         <td>Period</td>
         <td>string; default: <b>none</b></td>
         <td>integer [0..86400]|; default: <b>60</b></td>
         <td>Name used for distinguishing purposes.</td>
         <td>Time duration between data retrievals (in seconds).</td>
    </tr>
    <tr>
        <td>Data type</td>
        <td>JSON {{!}} XML {{!}} ASCII {{!}} Hexadecimal {{!}} Binary {{!}} CSV; default: <b>JSON</b></td>
        <td>Data type to process the received data.</td>
    </tr>
    <tr>
        <td>Test</td>
        <td>Interactive button</td>
        <td>A unique device identifier which commonly includes the serial number.</td>
    </tr>
</table>
 
To reach group values configuration press <b>Edit</b> button as shown below.
 
[[File:Networking_rutos_manual_mbus_client_data_collecting_groups_value_edit.png|border|class=tlt-border]]
 
[[File:Networking_rutos_manual_mbus_client_data_collecting_groups_value_edit_configuration.png|border|class=tlt-border]]
 
<table class="nd-mantable">
    <tr>
        <th>Field</th>
        <th>Value</th>
        <th>Description</th>
    </tr>
    <tr>
        <td>Enabled</td>
        <td>on | off; default: <b>off</b></td>
        <td>Button to enable/disable data group value.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>Period</td>
         <td>FCB toggle</td>
         <td>integer [1..86400]; default: <b>60</b></td>
         <td>on | off; default: <b>off</b></td>
         <td>Specifies the period how often record data will be collected.</td>
         <td>FCB (Frame Count-Bit): One-bit counter for reliable server-client communication. Some devices may have different uses for it.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>String before data</td>
         <td>Manufacturer information</td>
         <td>string; default: <b>none</b></td>
         <td>on | off; default: <b>off</b></td>
         <td>String that will be appended before request data.</td>
         <td>Should manufacturer information be included in the payload.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>String between data</td>
         <td>Selected parameters</td>
         <td>string; default: <b>none</b></td>
         <td>All | Custom; default: <b>All</b></td>
         <td>String that will be appended between request data.</td>
         <td>Should all parameters be saved from device, or a custom subset of them.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>String after data</td>
         <td>Frame number</td>
         <td>string; default: <b>none</b></td>
         <td>integer [0..15]|; default: <b>60</b></td>
         <td>String that will be appended after request data.</td>
         <td>Frame number.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>Failure mode</td>
         <td>Record number</td>
         <td>Never | <span style="color: red;">Any requests failed</span> | <span style="color: red;">All requests failed</span>; default: <b>Never</b></td>
         <td>integer [0..63]|; default: <b>60</b></td>
         <td>Specifies when whole record is considered as failure.</td>
         <td>Record number.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td><span style="color: red;">Store a failure message</span></td>
         <td>Parameter</td>
         <td>off | on; default: <b>off</b></td>
         <td>id | frame | Function | StorageNumber | Tariff | Device | Unit | Value | Timestamp; default: <b>id</b></td>
         <td>Select whether to store a failure message in the database or do nothing on failure.</td>
         <td>Parameter.</td>
     </tr>
     </tr>
</table>
</table>


===Request Configuration===
==Gateway==
===M-Bus device configuration===
----
----
In this section, you can configure requests from servers. By default there are no instances created. To add a new instance and start configuring press the <b>Add</b> button.


[[File:Networking_rutos_manual_mbus_record_request_configuration_v2.png|border|class=tlt-border]]
The M-Bus device configuration section is used to configure the general service functionality. The figure below is an example of the M-Bus Settings and the table below provides information on the fields contained in that section: 


====Request Configuration Edit====
[[File:Networking rutos manual mbus gateway mbus device configuration_v1.png|border|class=tlt-border]]
 
<table class="nd-mantable">
    <tr>
        <th>Field</th>
        <th>Value</th>
        <th>Description</th>
    </tr>
    <tr>
        <td>Enabled</td>
        <td>on {{!}} off; default: <b>off</b></td>
        <td>Button to enable/disable service.</td>
    </tr>
    <tr>
        <td>Baud rate</td>
        <td>300 {{!}} 600 {{!}} 1200 {{!}} 2400 {{!}} 4800 {{!}} 9600 ; default: <b>2400</b></td>
        <td>Specifies the M-Bus server network baud rate.</td>
    </tr>
    <tr>
        <td>Stop bits</td>
        <td>1 {{!}} 2; default: <b>1</b></td>
        <td>Select how many stop bits will be used to detect the end of character.</td>
    </tr>
    <tr>
        <td>Parity</td>
        <td>Even {{!}} Odd {{!}} None; default: <b>Even</b></td>
        <td>Select what kind of parity bit to use for error detection.</td>
    </tr>
</table>
 
===Configuration settings===
----
----
[[File:Networking rutos manual mbus record request configuration edit v4.png|border|class=tlt-border]]
 
This is just a simplified way of configuring Over IP settings and the table below provides information on the fields contained in that section: 
 
[[File:Networking_rutos_manual_mbus_gateway_configuration_settings_general.png|border|class=tlt-border]]


<table class="nd-mantable">
<table class="nd-mantable">
Line 120: Line 256:
     </tr>
     </tr>
     <tr>
     <tr>
         <td>Enable</td>
         <td>Mode</td>
         <td>off | on; default: <b>off</b></td>
         <td>Server {{!}} Client {{!}} Client+server {{!}} Bidirect(legacy mode, not recommended); default: <b>Server</b></td>
         <td>Enables request processing.</td>
         <td>
            <ul>
                <li>Server - launches service in server mode and listens on the selected port.</li>
                <li>Client - launches service in client mode, which connects to one or several servers with the selected addresses and ports.</li>
                <li>Client + server - launches service in server and client(s) mode simultaneously.</li>
                <li>Bidirect(legacy) - launches service in bidirect mode, which means that the service keeps changing between server and client modes. If server mode fails it switches to client mode and vice versa.</li>
            </ul>
      </td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>Server address</td>
         <td>Protocol</td>
         <td>int | hexstring; default: <b>none</b></td>
         <td>TCP {{!}} <span style="color:blue">UDP</span>; default: <b>TCP</b></td>
         <td>Address of the server to be inquired.</td>
         <td>Select which protocol to use for data transmission.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>Data type</td>
         <td>Listening port</td>
         <td>XML | HEX | BIN | JSON; default: <b>XML</b></td>
        <td>integer [1..65535]; default: <b>empty</b></td>
         <td>Data type to process the received data.</td>
        <td>Specify port number for server to listen.</td>
    </tr>
    <tr>
        <td>Predefined addresses</td>
        <td>ipv4 and port - integer [1..65535]; default: <b>none</b></td>
        <td>Set predefined IP and port for UDP connection (e.g., first field for address second for port).</td>
    </tr>
</table>
 
[[File:Networking_rutos_manual_mbus_gateway_configuration_settings_security.png|border|class=tlt-border]]
 
<table class="nd-mantable">
    <tr>
        <th>Field</th>
        <th>Value</th>
        <th>Description</th>
    </tr>
    <tr>
        <td>Use TLS/SSL</td>
        <td>on {{!}} off; default: <b>off</b></td>
        <td>Button to use TLS/SSL for connection.</td>
    </tr>
    <tr>
        <td>TLS version</td>
        <td>tlsv1.0 {{!}} tlsv1.1 {{!}} tlsv1.2 {{!}} tlsv1.3 {{!}} Support all ; default: <b>Support all</b></td>
        <td>Minimum TLS version allowed to be used.</td>
    </tr>
    <tr>
        <td>TLS type</td>
         <td>Certificate based {{!}} <span style="color: red">Pre-Shared-Key based</span>; default: <b>Certificate based</b></td>
        <td>Select the type of TLS encryption.</td>
    </tr>
    <tr>
        <td>Require certificate</td>
        <td>off {{!}} on; default: <b>on</b></td>
        <td>Demand certificate and key from peer and verify them against certificate authority.</td>
    </tr>
    <tr>
        <td><span style="color: red">Pre-Shared-Key</span></td>
        <td>hexadecimal string of symbols; default: <b>empty</b></td>
        <td>The pre-shared-key in hex format with no leading “0x”.</td>
    </tr>
    <tr>
        <td><span style="color: red">Identity</span></td>
        <td>string of symbols; default: <b>empty</b></td>
        <td>Specify the identity.</td>
    </tr>
    <tr>
        <td>Certificate files from device</td>
        <td>on {{!}} off; default: <b>off</b></td>
        <td>Choose this option if you want to select certificate files from device.</td>
    </tr>
    <tr>
        <td>Certificate file</td>
        <td></td>
        <td>.crt file; default: <b>none</b></td>
    </tr>
    <tr>
        <td>Key file</td>
        <td>.key file; default: <b>none</b></td>
        <td>Upload certificate file.</td>
    </tr>
</table>
 
[[File:Networking_rutos_manual_mbus_gateway_configuration_settings_advanced.png|border|class=tlt-border]]
 
<table class="nd-mantable">
    <tr>
        <th>Field</th>
        <th>Value</th>
        <th>Description</th>
    </tr>
    <tr>
        <td>Raw mode</td>
        <td>on {{!}} off; default: <b>on</b></td>
        <td>Enable to transmit all data transparently.</td>
    </tr>
    <tr>
        <td>Remove all zeros</td>
        <td>on {{!}} off; default: <b>off</b></td>
        <td>Remove all zero bytes from received data.</td>
    </tr>
    <tr>
        <td>Inactivity timeout</td>
        <td>integer [0..36000] ; default: <b>300</b></td>
         <td>Specifies period of time in seconds, where server connection must be inactive, to disconnect client. To disable timeout input 0.</td>
    </tr>
    <tr>
        <td>Serial timeout</td>
        <td>integer [0..1000] ; default: <b>empty</b></td>
        <td>Specifies the maximum milliseconds to wait for serial data.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>Error value</td>
         <td>Max clients</td>
         <td>string; default: <b>none</b></td>
         <td>integer [1..32] ; default: <b>4</b></td>
         <td>Changes request data to this value if request fails.</td>
         <td>Specify (1-32) how many clients are allowed to connect simultaneously.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>FCB toggle</td>
         <td>TCP echo</td>
         <td>off | on; default: <b>on</b></td>
         <td>on {{!}} off; default: <b>off</b></td>
         <td>FCB (Frame Count-Bit): One-bit counter for reliable server-client communication; some devices have special uses for it.</td>
         <td>Software TCP echo.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>Reset after read</td>
         <td>Close connections</td>
         <td>off | on; default: <b>off</b></td>
         <td>on {{!}} off; default: <b>off</b></td>
         <td>Resets the device after every read.</td>
         <td>Close TCP connections everytime data is sent or received (might result in serial data loss).</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>Test configuration</td>
         <td>Keep alive</td>
         <td>button; default: <b>-</b></td>
         <td>on {{!}} off; default: <b>off</b></td>
         <td>Tests the current configuration.</td>
         <td>Enable keep alive.</td>
     </tr>
     </tr>
</table>
</table>


====Test Configuration====
===IP filter===
----
----
Before saving, you can check if your configuration works accordingly by pressing the <b>Test Configuration</b> button. You should see the data in a field below:


[[File:Networking_rutos_manual_mbus_record_request_configuration_edit_test_configuration_v1.png|border|class=tlt-border]]
The IP Filter section is used for configuring which network is allowed to communicate with the device. You may add a new instance by selecting the Interface and pressing Add.
 
[[File:Networking_rutos_manual_mbus_gateway_ip_filter.png|border|class=tlt-border]]
 
<table class="nd-mantable">
    <tr>
        <th>Field</th>
        <th>Value</th>
        <th>Description</th>
    </tr>
    <tr>
        <td>Allow IP</td>
        <td>IPv4 and IPv6 addresses with or without mask prefix are accepted. E.g 192.168.1.0/24.</td>
        <td>Allow IP connecting to server, write 0.0.0.0/0 for allowing all</td>
    </tr>
</table>


[[Category:{{{name}}} Services section]]
[[Category:{{{name}}} Services section]]

Latest revision as of 10:17, 8 October 2024

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

Summary

The M-Bus (Meter Bus) is a cost-effective fieldbus communication protocol for transmitting energy consumption data. A central client – in this case {{{name}}} – communicates via a two-wire bus (up to max. 250 servers per segment) with bus devices (e.g., heat meter, water meter, electric meter, gas meter).

This manual page provides an overview of the M-Bus functionality in {{{name}}} devices.

Client

Global settings

Notice the Global section config. It is used to outright turn the service off or on if any active configurations are present.

Clicking the Cog icon opens a modal window. The global configuration slider can be set and it's state saved.

Field Value Description
Enabled on | off; default: on Global enable switch for the whole M-Bus service.
Timeout integer; default: 1 Maximum amount of time to wait when receiving a response from the device (in seconds).

General settings

The M-Bus device configuration section is used to configure the general service functionality. The figure below is an example of the M-Bus Settings and the table below provides information on the fields contained in that section:

Field Value Description
Status Inactive | Active Status of service, whether it is currently running. If it is active, it will also show how long it has been running.
Baud rate 300 | 600 | 1200 | 2400 | 4800 | 9600 ; default: 2400 Specifies the M-Bus server network baud rate.
Stop bits 1 | 2; default: 1 Select how many stop bits will be used to detect the end of character.
Parity Even | Odd | None; default: Even Select what kind of parity bit to use for error detection.

Devices

To add new device to configuration press Add button which is shown below.

The Devices section is used to configure the general device instance. The figure below is an example of the M-Bus device and the table below provides information on the fields contained in that section:

Field Value Description
Name String; default: Device 1 Display name of device configuration.
Address type Primary | Secondary ; default: Primary Primary address which will be used when sending requests.
Primary address integer [0..250]; default: empty Primary address which will be used when sending requests.
Secondary address string of 16 symbols; default: empty A unique device identifier which commonly includes the serial number.

Data collecting groups

To reach data collecting groups configuration press Edit button as shown below.

Before saving, you can check if your configuration works accordingly by pressing the Test Configuration button. You should see the data in a pop-up field.

Field Value Description
Enabled on | off; default: off Button to enable/disable data collecting group.
Period integer [0..86400]|; default: 60 Time duration between data retrievals (in seconds).
Data type JSON | XML | ASCII | Hexadecimal | Binary | CSV; default: JSON Data type to process the received data.
Test Interactive button A unique device identifier which commonly includes the serial number.

To reach group values configuration press Edit button as shown below.

Field Value Description
Enabled on | off; default: off Button to enable/disable data group value.
FCB toggle on | off; default: off FCB (Frame Count-Bit): One-bit counter for reliable server-client communication. Some devices may have different uses for it.
Manufacturer information on | off; default: off Should manufacturer information be included in the payload.
Selected parameters All | Custom; default: All Should all parameters be saved from device, or a custom subset of them.
Frame number integer [0..15]|; default: 60 Frame number.
Record number integer [0..63]|; default: 60 Record number.
Parameter id | frame | Function | StorageNumber | Tariff | Device | Unit | Value | Timestamp; default: id Parameter.

Gateway

M-Bus device configuration

The M-Bus device configuration section is used to configure the general service functionality. The figure below is an example of the M-Bus Settings and the table below provides information on the fields contained in that section:

Field Value Description
Enabled on | off; default: off Button to enable/disable service.
Baud rate 300 | 600 | 1200 | 2400 | 4800 | 9600 ; default: 2400 Specifies the M-Bus server network baud rate.
Stop bits 1 | 2; default: 1 Select how many stop bits will be used to detect the end of character.
Parity Even | Odd | None; default: Even Select what kind of parity bit to use for error detection.

Configuration settings

This is just a simplified way of configuring Over IP settings and the table below provides information on the fields contained in that section:

Field Value Description
Mode Server | Client | Client+server | Bidirect(legacy mode, not recommended); default: Server
  • Server - launches service in server mode and listens on the selected port.
  • Client - launches service in client mode, which connects to one or several servers with the selected addresses and ports.
  • Client + server - launches service in server and client(s) mode simultaneously.
  • Bidirect(legacy) - launches service in bidirect mode, which means that the service keeps changing between server and client modes. If server mode fails it switches to client mode and vice versa.
Protocol TCP | UDP; default: TCP Select which protocol to use for data transmission.
Listening port integer [1..65535]; default: empty Specify port number for server to listen.
Predefined addresses ipv4 and port - integer [1..65535]; default: none Set predefined IP and port for UDP connection (e.g., first field for address second for port).

Field Value Description
Use TLS/SSL on | off; default: off Button to use TLS/SSL for connection.
TLS version tlsv1.0 | tlsv1.1 | tlsv1.2 | tlsv1.3 | Support all ; default: Support all Minimum TLS version allowed to be used.
TLS type Certificate based | Pre-Shared-Key based; default: Certificate based Select the type of TLS encryption.
Require certificate off | on; default: on Demand certificate and key from peer and verify them against certificate authority.
Pre-Shared-Key hexadecimal string of symbols; default: empty The pre-shared-key in hex format with no leading “0x”.
Identity string of symbols; default: empty Specify the identity.
Certificate files from device on | off; default: off Choose this option if you want to select certificate files from device.
Certificate file .crt file; default: none
Key file .key file; default: none Upload certificate file.

Field Value Description
Raw mode on | off; default: on Enable to transmit all data transparently.
Remove all zeros on | off; default: off Remove all zero bytes from received data.
Inactivity timeout integer [0..36000] ; default: 300 Specifies period of time in seconds, where server connection must be inactive, to disconnect client. To disable timeout input 0.
Serial timeout integer [0..1000] ; default: empty Specifies the maximum milliseconds to wait for serial data.
Max clients integer [1..32] ; default: 4 Specify (1-32) how many clients are allowed to connect simultaneously.
TCP echo on | off; default: off Software TCP echo.
Close connections on | off; default: off Close TCP connections everytime data is sent or received (might result in serial data loss).
Keep alive on | off; default: off Enable keep alive.

IP filter

The IP Filter section is used for configuring which network is allowed to communicate with the device. You may add a new instance by selecting the Interface and pressing Add.

Field Value Description
Allow IP IPv4 and IPv6 addresses with or without mask prefix are accepted. E.g 192.168.1.0/24. Allow IP connecting to server, write 0.0.0.0/0 for allowing all

[[Category:{{{name}}} Services section]]

Retrieved from "https://wiki.teltonika-networks.com/index.php?title=Template:Networking_rutos_manual_mbus&oldid=133856"