This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm that you accept these cookies being set.

LM - "IP Tunneling" "IP Routing" and "Multicast IP"
#1
Hi,

I'm trying to understand the concept of "IP Tunneling" "IP Routing" and "Multicast IP" for LM

If I have 2 devices on the same VLAN imagine: 192.168.28.01 and  192.168.28.02:
     the device *.01 mode: TP-UART,  knx: 15.15.1 and multicast 224.0.23.12     and 
     the device *.02 mode: IP-Tunneling : router: 192.168.28.01 (device 01), knx: 15.15.2 and multicast 224.0.23.12

Whit this I can send KNX frames from one to other with success and it's possible to update remote values... but
ETS return error programing device 01: "FAILED TO CONNECT TO 1.1.1"  .. if I remove the power of device 02, the programming is updated with success! 

If I have a company with multiple VLANs, it's possible to connect all the to appear on ETS , to program devices from 1 vlan to others ? 

Thanks.
Reply
#2
The Mode defines how LM is connecting to KNX. If you select tunneling it means this LM is connected via another interface to TP and the locally connected TP is ignored.
TP-uart is a default mode with the TP and routing enabled. Routing mode is then just routing enabled but TP disabled.

Use TP-uart mode on all and in ETS you may need to use NAT if going from another Vlan

You can also use Zerotier and do it via cloud.
------------------------------
Ctrl+F5
Reply
#3
(05.04.2024, 12:49)joaodaniel.pereira Wrote: Hi,

I'm trying to understand the concept of "IP Tunneling" "IP Routing" and "Multicast IP" for LM

If I have 2 devices on the same VLAN imagine: 192.168.28.01 and  192.168.28.02:
     the device *.01 mode: TP-UART,  knx: 15.15.1 and multicast 224.0.23.12     and 
     the device *.02 mode: IP-Tunneling : router: 192.168.28.01 (device 01), knx: 15.15.2 and multicast 224.0.23.12

Whit this I can send KNX frames from one to other with success and it's possible to update remote values... but
ETS return error programing device 01: "FAILED TO CONNECT TO 1.1.1"  .. if I remove the power of device 02, the programming is updated with success! 

If I have a company with multiple VLANs, it's possible to connect all the to appear on ETS , to program devices from 1 vlan to others ? 

Thanks.

(05.04.2024, 12:56)Daniel Wrote: The Mode defines how LM is connecting to KNX. If you select tunneling it means this LM is connected via another interface to TP and the locally connected TP is ignored.
TP-uart is a default mode with the TP and routing enabled. Routing mode is then just routing enabled but TP disabled.

Use TP-uart mode on all and in ETS you may need to use NAT if going from another Vlan

You can also use Zerotier and do it via cloud.

ok, this is my original configuration, maybe between vlans port 3671 is blocked on the firewall!
Reply
#4
Hii,

when trying to trigger light from knx via ip tunneling(logic machine) then its showing Failed to read devce description from 172.168.150.125, but ping succeeded.
Could you pls Suggest us solution.
 

Pls find attached Screenshot for our work

Attached Files Thumbnail(s)
   
Reply
#5
See this: https://forum.logicmachine.net/showthread.php?tid=4757
Reply
#6
Hii ,

Now we have new IP range Still Program is not downloading or Triggering from ETS.

here I have attached screenshots of our work.

Attached Files Thumbnail(s)
           
Reply
#7
Change LM address to 1.1.255 and see again.
Is it just with this device or any?
------------------------------
Ctrl+F5
Reply
#8
(20.08.2024, 08:59)Daniel Wrote: Change LM address to 1.1.255 and see again. 
Is it just with this device or any?


Still it is not able to download after changed.
Reply
#9
Is it just with this device or any?
------------------------------
Ctrl+F5
Reply
#10
(20.08.2024, 10:18)Daniel Wrote: Is it just with this device or any?

its is happening with Every Device .
Reply
#11
Is LM overloaded? What is the KNX status?
Try rebooting LM and restart ETS.
------------------------------
Ctrl+F5
Reply
#12
(20.08.2024, 10:26)Daniel Wrote: Is LM overloaded? What is the KNX status?
Try rebooting LM and restart ETS.

There are 61 pages in LM. ETS Showing Failed to connect indivisual Address like 1.1.213.
still  not downloading after restart both.

one more think I observed that knx Light is Triggering from Knx via LM. But not Downloading.
Reply
#13
Go to LogicMAchine and check what you see in bottom right corner where CPU/IO, Memory and KNX is.
------------------------------
Ctrl+F5
Reply
#14
(20.08.2024, 10:40)Daniel Wrote: Go to LogicMAchine and check what you see in bottom right corner where CPU/IO, Memory and KNX is.

Here Is Sceeenshot.

Attached Files Thumbnail(s)
   
Reply
#15
OK this looks good.
In KNX connection, IP > Local filter, did you enable Apply filter to tunneling? It should be disabled.
------------------------------
Ctrl+F5
Reply
#16
(20.08.2024, 10:54)Daniel Wrote: OK this looks good.
In KNX connection, IP > Local filter, did you enable Apply filter to tunneling?  It should be disabled.

Attached Files Thumbnail(s)
   
Reply
#17
What firmware do you use? it is not the latest.
------------------------------
Ctrl+F5
Reply
#18
Try change the ETS setting in project details (i) -> details -> Check "Use a low bus communication speed"
Reply


Forum Jump: