--- title: "Data Diode | Examples | N3uron KB V.1.20" 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: 2021-12-16T09:45:24Z published: 2021-12-16T09:45:24Z canonical: "docs.n3uron.com/data-diode-examples" --- > ## 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 DataDiode In this example, the **DataDiode** 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/10-Creating-new-module-instances.png) Figure 10: Creating new module instances - **Step 2:** Configure the **Logger** and **API** for the **DataDiode** 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/11-Creating-a-new-Sender.png) Figure 11: Creating a new Sender - **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/12-Sender-configuration.png) Figure 12: Sender configuration Configuring the receiving node: - **Step 5:** Add a new module in the “Modules” section, give it a name, and select “DataDiode” in the “Module type” field. ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/13-Creating-new-module-instances-2.png) Figure 13: Creating new module instances - **Step 6:** Configure the Logger and **API** for the **DataDiode** 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/14-Creating-a-new-Receiver.png) Figure 14: Creating a new Receiver - **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/15-Receiver-configuration.png) Figure 15: Receiver configuration - **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/16-Creating-a-new-Tag.png) Figure 16: Creating a new Tag - **Step 10:** Configure the **Tag** (Type, Source, etc.) and save the changes. ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/17-Tag-configuration.png) Figure 17: Tag configuration Result:![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/18-Tag-status-in-the-sending-node.png) Figure 18: Tag status in the sending node. ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/19-Tag-status-in-the-receiving-node.png)Figure 19: Tag status in the receiving node.