l2_vm
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
l2_vm [2022/10/21 07:37] – [Connecting virtual cloud node to your hardware] emozolyak | l2_vm [2023/10/04 13:26] – [Virtual node peculiarities] 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 29: | Line 29: | ||
Then a progress window will come: | Then a progress window will come: | ||
- | {{ : | + | {{ : |
and final message: | and final message: | ||
- | {{ : | + | {{ : |
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. | 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: | 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** | ||
- | ==== 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: |
+ | {{ : | ||
+ | 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 ===== | ||
Line 53: | Line 61: | ||
Please note, that the virtual node will be created with the " | Please note, that the virtual node will be created with the " | ||
+ | <WRAP center round important 60%> | ||
+ | Please note that licensed cloud image will be stopped after account balance becomes zero, then after 2 weeks of stopped state this image will be deleted. | ||
+ | </ | ||
l2_vm.txt · Last modified: 2023/10/04 13:29 by emozolyak