`
- **but** our local clients should still be able to use their 1/10 GigE connections by connecting directly to each other if possible
And right now it looks like as if all clients always connect to each other via relay (the address is `relay-client`). Your remarks suggests that I can tell clients to listen on relays **and** their local interface? I think that would solve my problem. How do I do that?
---
### Author:  [@AudriusButkevicius](https://forum.syncthing.net/u/AudriusButkevicius)
#### Post date: [January 27, 2019, 12:39pm UTC](https://forum.syncthing.net/t/prefer-direct-connection-over-configured-relay/12777/4 "2019-01-27T12:39:52Z")
> [@octomike](#):
>
> **but** our local clients should still be able to use their 1/10 GigE connections by connecting directly to each other if possible
No, because all clients are listening on the relay and relay only, because you removed `default` where default translats to `tcp://0.0.0.0:22000 dynamic+relay://relays.syncthing.net/endpoint`.
You probably want `tcp://0.0.0.0:22000 relay://yourrelay`
---
### Author:  [@octomike](https://forum.syncthing.net/u/octomike)
#### Post date: [January 27, 2019, 12:46pm UTC](https://forum.syncthing.net/t/prefer-direct-connection-over-configured-relay/12777/5 "2019-01-27T12:46:15Z")
That makes total sense 🙂
I’ll experiment a little with `default relay://` and `tcp:// relay://` to see if everything checks out. Thank you so much.
---
### Author:  [@AudriusButkevicius](https://forum.syncthing.net/u/AudriusButkevicius)
#### Post date: [January 27, 2019, 12:59pm UTC](https://forum.syncthing.net/t/prefer-direct-connection-over-configured-relay/12777/6 "2019-01-27T12:59:56Z")
default + relay will result in connecting to two relays plus listen locally
---
### Author:  [@octomike](https://forum.syncthing.net/u/octomike)
#### Post date: [January 27, 2019, 1:01pm UTC](https://forum.syncthing.net/t/prefer-direct-connection-over-configured-relay/12777/7 "2019-01-27T13:01:38Z")
And then it’s round robin with these two relays? I’m a little reluctant to use hard coded ports in the default setting to be honest.
---
### Author:  [@AudriusButkevicius](https://forum.syncthing.net/u/AudriusButkevicius)
#### Post date: [January 27, 2019, 1:02pm UTC](https://forum.syncthing.net/t/prefer-direct-connection-over-configured-relay/12777/8 "2019-01-27T13:02:28Z")
I think the order of which relay will be used is undefined, probably the one it can connect to faster.
---
### Author:  [@Nummer378](https://forum.syncthing.net/u/Nummer378)
#### Post date: [January 27, 2019, 1:35pm UTC](https://forum.syncthing.net/t/prefer-direct-connection-over-configured-relay/12777/9 "2019-01-27T13:35:32Z")
My own configuration is this: relay://\, tcp://:22000. This is basically the same thing as the default config, just with a fixed relay instead of a “random” one.
This configuration enables direct connections over internet and relay connections. If local discovery is enabled, local connections are also possible. Syncthing will always prefer the direct connections, sometimes it connects first over relay and half a second later the log reads something like “replaced connection X with Y” when it switches to a direct connection instead of the relay.
tcp://:22000 makes Syncthing listen on both IPv4 and IPv6 on port 22000. From my knowledge, this is effectively the default behavior, syncthing will by default always bind to 22000 for the server-socket. If you want to randomize this, try if port 0 works.
PS: If you haven’t already, have a look at this: [https://docs.syncthing.net/users/config.html#listen-addresses](https://docs.syncthing.net/users/config.html#listen-addresses)
---
### Author:  [@system](https://forum.syncthing.net/u/system)
#### Post date: [February 26, 2019, 1:49pm UTC](https://forum.syncthing.net/t/prefer-direct-connection-over-configured-relay/12777/10 "2019-02-26T13:49:22Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.