+- LogicMachine Forum (https://forum.logicmachine.net)
+-- Forum: LogicMachine eco-system (https://forum.logicmachine.net/forumdisplay.php?fid=1)
+--- Forum: Gateway (https://forum.logicmachine.net/forumdisplay.php?fid=10)
+--- Thread: Issues with KNX/IP and BACnet/IP when using 170.x.x.x network range (/showthread.php?tid=6356)
Issues with KNX/IP and BACnet/IP when using 170.x.x.x network range - Alberto.ricof - 18.03.2026
Hi,
I'm facing a strange issue with a LogicMachine in a project.
Current setup:
LAN network configured as: 170.25.18.x
Web access to the LM works fine
The issue:
ETS cannot connect (error reading device description on port 3671, ping works)
KNXnet/IP tunneling is not working
BACnet/IP export is also not working
However:
Web server works normally
IP connectivity is OK (ping works)
What I have already tried:
Reboot LogicMachine
Reboot router
Factory reset of the LogicMachine (no change in behavior)
Configured ETS interface properly
My question is:
* Could using a public IP range like 170.x.x.x cause issues with KNX/IP (UDP/multicast) and BACnet/IP?
* Could the LogicMachine or router handle this differently compared to private networks (192.168.x.x / 10.x.x.x)?
Has anyone experienced something similar?
Thanks.
RE: Issues with KNX/IP and BACnet/IP when using 170.x.x.x network range - Daniel - 18.03.2026
Yes LM is blocking KNX IP and BAcnet from public IPs due to security as they have zero protections, anyone can access your site and do anything.