l2_vm
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
l2_vm [2022/10/21 07:40] – [Adding virtual cloud node] 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: | 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 | * 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 ===== | ===== Adding virtual cloud node ===== | ||
Line 40: | Line 40: | ||
You can connect your virtual node to real equipment with either ways: | You can connect your virtual node to real equipment with either ways: | ||
- | ***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** | ||
+ | ==== 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==== | ||
+ | In this scenario, you arrange your system like this: | ||
+ | {{ : | ||
- | ==== NAT with VPN connection ==== | + | Below is the example of NAT settings for Mikrotik router: |
+ | {{ : | ||
+ | |||
+ | And you also have to enable routing to the L2 node for your router: | ||
+ | |||
+ | {{ : | ||
===== Virtual node peculiarities ===== | ===== Virtual node peculiarities ===== |
l2_vm.txt · Last modified: 2023/10/04 13:29 by emozolyak