---
title: "Data Diode | Examples | N3uron KB V1.22"
slug: "data-diode-examples"
description: "Data Diode is a N3uron module designed to provide a cybersecurity solution that ensures information can only travel in one direction. Data Diode…"
updated: 2025-12-23T11:40:18Z
published: 2025-12-23T11:40:43Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.n3uron.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Example

## Sending data from one N3uron node to another via the Data Diode

In this example, the **Data Diode**module has been used to send data, in a unidirectional way, from a sending **N3uron**node to a receiving **N3uron**node.

Configuring the sending node:

- **Step 1:** Add a new module in the “Modules” section, name it, and select “DataDiode” in the “Module type” field.

![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/Figure%2010-%20Creating%20new%20module%20instances(2).png)

- **Step 2:** Configure the **Logger**and **API**for the **Data Diode**module. In this example, the default configuration settings have been left unedited, since (in most cases) this a valid configuration option.

- **Step 3:** Add a new Sender within the “Model” section and choose a name for it.

![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/Figure%2011-%20Creating%20a%20new%20sender(1).png)

- **Step 4:** Configure the **Sender**(Host, UDP port, etc.) and save the changes. In this example, data is sent without encryption to another **N3uron**node with the following IP address: 10.101.3.31.

![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/Figure%2012-%20Sender%20configuration(1).png)

Configuring the receiving node:

- **Step 5:** Add a new module in the “Modules” section, give it a name, and select “DataDiode” in the “<meta charset="utf-8">M<meta charset="utf-8"><meta charset="utf-8">odule type” field.

![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/Figure%2013-%20Creating%20new%20module%20instances(1).png)

- **Step 6:** Configure the Logger and **API**for the **Data Diode**module. In this example, the default configuration settings have been left unedited, since (in most cases) this is a valid configuration option.

- **Step 7:** Add a new Receiver in the “Mode” section and choose a name for it.

![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/Figure%2014-%20Creating%20a%20new%20receiver.png)

- **Step 8:** Configure the **Receiver**(Host, UDP port, etc.) and save the changes. In this example, the **Source IP addresse****s** field is left empty in order to allow all IP addresses for incoming datagrams. However, specifying the **Source IP address** is recommended, as this adds an extra layer of security.

![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/Figure%2015-%20Receiver%20configuration(1).png)

- **Step 9:** Add a new **Tag**within the **Model**and choose a name for it. In this example, since the target tag path (located in the sending node) is “frequency_VAL”, the tag (located in the receiving node) has been named with the same path “frequency_VAL” in order to obtain the same value.

![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/Figure%2016-%20Creating%20a%20new%20tag(1).png)

- **Step 10:** Configure the **Tag**(Type, Source, etc.) and save the changes.

![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/Figure%2017-%20Tag%20configuration(1).png)

Result:

![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/Figure%2018-%20Tag%20status%20in%20the%20sending%20node(2).png)

![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/Figure%2019-%20Tag%20status%20in%20the%20receiving%20node(2).png)