Differences

This shows you the differences between two versions of the page.

--- l2_vm [2022/10/21 07:17] – [Virtual node peculiarities] emozolyak
+++ l2_vm [2022/10/24 10:09] – [TCP/IP based protocols using NAT technique] emozolyak
@@ Line 6: / Line 6: @@
 In this scenario, your WebHMI image is running on a cloud virtualization platform. You can connect to real world devices via two ways:
   * connecting the devices to the Level2 IoT with MQTT protocol
-  * use Level2 VPN and virtual IP feature
+  * use Level2 VPN and NAT method
 ===== Adding virtual cloud node =====
@@ Line 29: / Line 29: @@
 Then a progress window will come:
-{{ :level2:cloud_vm:create_vm_message.gif |}}
+{{ :level2:cloud_vm:create_vm_message.gif?600 |}}
 and final message:
-{{ :level2:cloud_vm:success_creation_popup.png?nolink |}}
+{{ :level2:cloud_vm:success_creation_popup.png?nolink&600 |}}
 Virtual nodes are basically the same as for hw WebHMI or Virtual Box image except for minor details (like VPN + HTTP proxy service control, which are enabled by default for that kind of nodes). Further node configuration is only performed on the Level2.
@@ Line 40: / Line 40: @@
 You can connect your virtual node to real equipment with either ways:
-  *MQTT protocol
-  *TCP/IP based protocols using NAT technique
-==== Using MQTT protocol ====
+==== MQTT protocol ====
+Please refer to the [[connect_iot_device_to_l2 | article]] on connecting MQTT devices to Level2
+==== TCP/IP based protocols using NAT technique====
-==== NAT with VPN connection ====
+In this scenario, you arrange your system like this:
+{{ :level2:cloud_vm:vpn_for_virtual_node.png?direct&400 |}}
+Below is the example of NAT settings for Mikrotik router:
+{{ :level2:cloud_vm:mikrotik-nat-for-cloud-final.png?direct&600 |}}
+And you also have to enable routing to the L2 node for your router:
+{{ :level2:cloud_vm:route-to-mikrotik-for-prox-mox.png?direct&600 |}}
 ===== Virtual node peculiarities =====