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.

Issues with KNX/IP and BACnet/IP when using 170.x.x.x network range
#1
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.
Reply
#2
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.
------------------------------
Ctrl+F5
Reply


Forum Jump: