Hi, I set up a Wireguard based VPN for a PLCnext controller (StarterKit AXC F 2152) and a development machine with PLCnext Engineer installed. I can reach the controller with SSH through the dev machine’s VPN network interface without issues PS C:\\\Users\\\User> ssh root@100.73.15.73 Last login: Thu May 13 00:00:33 2021 from 100.119.102.104 root@axcf2152:~# This indicates that routing is correct and the interface is fully functional. PLCnext Engineer can not use that VPN interface though. It is not available in PLCnext Engineer to scan for online controllers. Here is some more info about that VPN interface (sorry, partially in German): PS C:\\\Users\\\InitialUser> ipconfig.exe Windows-IP-Konfiguration Unbekannter Adapter Tailscale: Verbindungsspezifisches DNS-Suffix: IPv6-Adresse. . . . . . . . . . . : fd7a:115c:a1e0:ab12:xxxx:xxxx:xxxx:xxxx Verbindungslokale IPv6-Adresse . : fe80::xxxx:xxxx:xxxx:xxxx%57 IPv4-Adresse . . . . . . . . . . : 100.119.102.104 Subnetzmaske . . . . . . . . . . : 255.255.255.255 Standardgateway . . . . . . . . . : PS C:\\\Users\\\InitialUser> Any ideas how to make use of the VPN connection in PLCnext Engineer? Kind regards & thanks in advance!
Hello, maybe there are two different problem here: scannning for find controller use Layer2 traffic, that normally can’t go through a VPN Tunnel. But this don’t mean you can’t go online with a controller where the IP is already known in the project. Just be sure to increase your timeout in the project setting (Under Extra) to comply with normal VPN delay. Hope this can help! Davide
Thank you for clarifying on the controller scan functionality and why it won’t work with VPN tunnels. In fact, my ping from the development PC to the PLC thorough the tunnel interface is usually < 100ms. After setting the IP manually, I was able to connect PLCnext Engineer to the PLC.