Hello,
I’m trying to add a remote Device running to my Win10 Notebook.
- Remote Device:
- Syncthing v1.5.0
- Debian Linux (64 bit)
- Reachable via VPN, IP: 10.192.232.111
- listen address set to “default”, which includes “tcp://0.0.0.0:22000”
- Notebook:
- Syncthing v1.8.0
- Windows 10 (64 bit)
- I want the notebook to be as “quiet” as possible, therefore I disabled all the fancy functionality, i.e. NAT traversal, Global Discovery, Local Discovery, Relaying.
The Notebook is configured to try and connect to “tcp://10.192.232.111:22000” which is working fine from another Linux machine. The remote device is only reachable via a VPN connection and the routes are all configured correctly. I didn’t have to manually change any routes, but checked them using PowerShell’s Find-NetRoute. 10.192.232.111:22000 is reachable from the notebook, which I verified using telnet.
The Problem is: Syncthing is trying to connect to the remote machine using the wrong route/interface and therefore fails. The error message is:
[6BEVK] 2020/08/13 14:08:03.784082 service.go:889: DEBUG: dialing CNWM7SR tcp://10.192.232.111:22000 error: dial tcp 192.168.0.110:22000->10.192.232.111:22000: i/o timeout
[6BEVK] 2020/08/13 14:08:03.784082 service.go:920: DEBUG: failed to connect to CNWM7SR 10
It tries to connect from 192.168.0.110 which is its IP on my local network instead of going via the VPN-Interface.
Why is syncthing not using the Routes configured in Windows, or am I misunderstanding something here?
7 posts - 2 participants