Back-to-Home + Starlink + KNX

RouterOS
1

Hi everyone,

I want to check if someone’ve already faced issue with KNX connection trough its software on standard udp port 3671 by VPN though Back-to-Home and Starlink connection.
Trough VPN I can ping the device, can reach by WebGUI by HTTP, but with the software that use that port not. I have also another device, fire prevention system, that use instead TCP 7090 that I can’t reach it too, but I can ping it.
For testing purpose I also disable all firewall policy, but I’ve got the same result.
Anyone has facing this issue with something similar?

2

Hi Michael, in ETS you MUST select the "NAT" box in the tunnel configuration.

I typically use this configuration in my KNX training courses.

3

Hi Marco,

Thank you for your reply, so basically it’s something to do on ETS software and not related to Back-to-Home VPN and/or Starlink connection?

4

Hi everyone,

I re-write here because I’ve got also a problem with Back-to-Home on Starlink.
For no reason, after a bunch of weeks, I can’t connect to the router by Wireguard VPN remotelly but, if I try to connect to router by LAN, I can see that Back-To-Home for the Mikrotik is still up and running. This happened three times.
Did it happen to someone else with this mix of Back-to-Home and Starlink? I’ve got a lot of Mikrotik with Back-to-Home but this is the first time I find this kind of problem.