syncthing/cmd/relaysrv
Audrius Butkevicius a51b948f45 Update README.md
2015-09-21 22:53:29 +01:00
..
client Connected clients should know their own latency 2015-09-20 13:40:24 +02:00
protocol Use a single socket for relaying 2015-09-02 21:35:52 +01:00
testutil Add a test method, fix nil pointer panic 2015-09-06 18:35:38 +01:00
LICENSE Initial commit 2015-06-24 00:34:16 +01:00
listener.go Merge pull request #5 from syncthing/info 2015-09-14 16:20:08 +02:00
main.go Always print URI 2015-09-21 22:15:29 +01:00
pool.go A bit more verbose 2015-09-21 22:33:29 +01:00
README.md Update README.md 2015-09-21 22:53:29 +01:00
session.go Drop all sessions when we realize a node has gone away 2015-09-11 22:29:50 +01:00
status.go Drop all sessions when we realize a node has gone away 2015-09-11 22:29:50 +01:00
utils.go Progress 2015-06-28 19:57:13 +01:00

relaysrv

Latest Build

This is the relay server for the syncthing project.

To get it, run go get github.com/syncthing/relaysrv or download the latest build from the build server.

Warnings - Read or regret

By default, all relay servers will join the default public relay pool, which means that the relay server will be availble for public use, and will consume your bandwidth helping others to connect.

If you wish to disable this behaviour, please specify -pool="" argument.

Please note that relaysrv is only usable by syncthing version v0.12 and onwards.

To run relaysrv you need to have port 22067 available to the internet, which means you might need to allow it through your firewall if you have a public IP, or setup a port-forwarding (22067 to 22067) if you are behind a router.

Running for public use

Make sure you have a public IP with port 22067 open, or make sure you have port-forwarding (22067 to 22067) if you are behind a router.

Run the relaysrv with no arguments (or -debug if you want more output), and that should be enough for the server to join the public relay pool. You should see a message saying:

2015/09/21 22:45:46 pool.go:60: Joined https://relays.syncthing.net rejoining in 48m0s

See relaysrv -help for other options, such as rate limits, timeout intervals, etc.

Running for private use

Once you've started the relaysrv, it will generate a key pair and print an URI:

relay://:22067/?id=EZQOIDM-6DDD4ZI-DJ65NSM-4OQWRAT-EIKSMJO-OZ552BO-WQZEGYY-STS5RQM&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070

This URI contains partial address of the relay server, as well as it's options which in the future may be taken into account when choosing the best suitable relay out of multiple available.

Because -listen option was not used, the relaysrv does not know it's external IP, therefore you should replace the host part of the URI with your public IP address on which the relaysrv will be available:

relay://123.123.123.123:22067/?id=EZQOIDM-6DDD4ZI-DJ65NSM-4OQWRAT-EIKSMJO-OZ552BO-WQZEGYY-STS5RQM&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070

If you do not care about certificate pinning (improved security) or do not care about passing verbose settings to the clients, you can shorten the URL to just the host part:

relay://123.123.123.123:22067

This URL can then be used in syncthing as one of the relay servers.

See relaysrv -help for other options, such as rate limits, timeout intervals, etc.