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.

VPN access to webinterface and programming interface
#1
Hi,

I'm having trouble accessing my webinterface through VPN set up by a client. Also having trouble accessing the programming interface via LM in ETS when connected to VPN.

The IT department at my client asked me what ports that needed to be opened up.
I said TPC 80 or 443 and UDP 3671.

Anything else that needs to be opened?
Reply
#2
Yes, it's TCP 80/443 for the web interface and UDP 3671 for KNX tunneling. Access to the KNX port is blocked from public IP ranges. In some rare cases internal networks are misconfigured to use public IP ranges. Private ranges are defined as follows:
10.0.0.0 – 10.255.255.255
172.16.0.0 – 172.31.255.255
192.168.0.0 – 192.168.255.255
Reply
#3
Hi, thanks for the reply.

That's strange, I've asked for 80 and 443 TCP and 3671 UDP. And the LM is on range 172.22.74.xxx. Are there any other issues that might stop my connection?
Reply
#4
Hello asgeirsb.
Are you Shute that you entered the correct subnet mask and gateway?
Reply
#5
When I think about it I am actually not sure I did. I need to contact IT again and ask them what is the correct subnet mask and gateway. I just assumed the standard 255.255.255.0 and 172.22.74.1 gateway
Reply
#6
Hi.
Have you find any solution on your issue?

I have a similar issue. Have a ISE Remote access on site at client and a openVPN setup that have work fine until last week when I tried, now suddely I cant fine the IP adress of the controller and even when I ad a fixed route to the local IP of the controler it cant connect.
Reply
#7
You sure the VPN is working, did he connect ?
Does the controller work locally at the moment?
or maybe you can try a ping or a scan to find all the IP addresses?
Reply
#8
(04.07.2022, 07:29)admin Wrote: Yes, it's TCP 80/443 for the web interface and UDP 3671 for KNX tunneling. Access to the KNX port is blocked from public IP ranges. In some rare cases internal networks are misconfigured to use public IP ranges. Private ranges are defined as follows:
10.0.0.0 – 10.255.255.255
172.16.0.0 – 172.31.255.255
192.168.0.0 – 192.168.255.255

Hello, and what can I do when I need to access locally to a " In some rare cases internal networks are misconfigured to use public IP ranges"  using the 3671 port?

A building: public range
B building: public range

VPN between them, I cannot access from one to another to change some values, because the given range it's some 10.x.x.x

Thanks for your help.
Reply


Forum Jump: