Zerotier - IP Interface and ETS Downloading

[savaskorkmaz]

Hello,
We previously succeeded with this type of connection via ZeroTier using an IP router, but this time we were not successful when using an IP interface. Our goal is to send programs to KNX devices through LM via ZeroTier. On site, the LM connection is through an IP interface.
We connected to the Logic Machine via ZeroTier. We opened ETS, entered the Logic Machine IP address and port number in the bus section, and when we pressed the test button, we saw the "OK" message. However, we couldn’t download the program from ETS.
I shared the following as image files:

• LM KNX settings
  
• ZeroTier connection settings
  
• ETS connection settings
  
• IP interface configuration in ETS
  

What could be the issue?

[Daniel]

Only IP routers will work.

[savaskorkmaz]

Hi We changed to IP Router and worked but i have also another question about ip tunneling and Pass ind. telegrams via IP Routing , Accept IP Tunneling connections settings.
We have 1 LM5 with 2025 fw. 1 Ip Router ( Not IP interface )

If we choose Mode IP Routing and select OK to Pass ind. telegrams via IP Routing , Accept IP Tunneling connections then we can download to KNX devices through Logic Machine with ETS.
If we choose Mode IP Tunnelling and select OK to Pass ind. telegrams via IP Routing , Accept IP Tunneling connections then we can't download to KNX devices through Logic Machine with ETS.

My question is what is the meaning of Pass ind. telegrams via IP Routing and Accept IP Tunneling connections in tunneling mode ? How we can use these settings in tunneling mode ?

[Daniel]

As the description says, this works over routing and not tunneling. Accept Tunneling is simply when you want to connect from ETS to LM as this is done via tunneling. The modes defines how LM is connecting to KNX. If you select tunneling then there is no routing and no download via routing.

[savaskorkmaz]

Hi,
If "Pass ind. telegrams via IP Routing" and "Accept IP Tunneling connections" is not working in IP Tunneling mode, can you remove this options in menu when we select ip tunneling ?
It's confusing.
Regards

[PolymorphedCust]

We have an installation with several lines, right now, with LM on each line. We're now told we CANNOT use multicast on the network. We can do the logic on each individual line in the corresponding LM, but the global functions AND visualisation gotta be on another platform. We were thinking of using a NETx software, and by doing this we were thinking of using IP tunnelling on each LM, to communicate between devices. My questions are therefore:
- By enabling IP Tunnelling, the LM can control the logic on the line and make the connection to the NETx server?
- By using NETx as the IP Tunnel, will we still be able to download to the KNX components on the line?

Thanks a lot

[admin]

LM can either connect to a local TP line or connect to IP tunneling interface but not both at the same time. How many objects in total do you have in this installation? Depending on the size you can use one central LM for visualization and run MQTT broker on it. Then use MQTT cloud app for local object exchange: https://forum.logicmachine.net/showthread.php?tid=5878

[PolymorphedCust]

If that is the case, then I really do not understand what the use case is for IP Tunnelling?
Components I've seen with IP Tunnelling makes the network device tunnel into the connected TP line. Furthermore, these components have several Tunnelling IP Connection, but I can only find one on the LM?

[Daniel]

It is true that tunneling mode has very limited functionality, we didn't remove it purely for backward compatibility. If you want to connect to LM then multiple tunnels are available. Multi LM communication was designed via multicast as normal IP router would do. As admin described above there are other ways to make LM to LM connection. MQTT is just one of them but it is the simplest and the fastest.