05.04.2024, 12:49 (This post was last modified: 05.04.2024, 12:51 by joaodaniel.pereira.)
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 ?
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
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!
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.
(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.