Public peers in the Yggdrasil network
Go to file
Neil Alexander a074fad045
Merge pull request #151 from jcgruenhage/patch-4
removed jcgruenhage's ovh vps
2020-03-18 11:29:30 +00:00
asia cleanups (pagination, spaces, newlines) 2020-03-09 01:58:34 +03:00
europe removed jcgruenhage's ovh vps 2020-03-18 12:01:29 +01:00
north-america Merge pull request #148 from wfleurant/patch-3 2020-03-11 18:35:19 +00:00
oceania cleanups (pagination, spaces, newlines) 2020-03-09 01:58:34 +03:00
other add s2.i2pd.xyz node (fr, i2p) 2020-03-09 01:57:02 +03:00
south-america cleanups (pagination, spaces, newlines) 2020-03-09 01:58:34 +03:00
README.md Update README.md 2019-10-31 10:34:46 +00:00

Public Peers

This repository contains peering information for publicly accessible nodes on the Yggdrasil network. If you are new to the network then this is a good place to start in order to get connected.

In most cases, public peers should be accessible by adding the string provided for each peer to the Peers: [] section of your yggdrasil.conf configuration file.

Example in yggdrasil.conf:

Peers:
[
  tcp://a.b.c.d:e
  tcp://d.c.b.a:e
  tcp://[a:b:c::d]:e
  tcp://[d:c:b::a]:e
]

How do I pick peers?

Always try to pick peers that are as close to you geographically as possible, as this will keep the latency of the network down.

If you are using a home connection then you should avoid peering with any nodes that are far away, as you may end up carrying traffic for the rest of the network.

For normal usage, you probably only need 2 or 3 peers.

TLS peers

As of Yggdrasil v0.3.11, peering connections over TLS are now possible. This hides the peering connection inside a regular TLS session, which can help in some cases where firewalls or deep packet inspection may identify or block regular Yggdrasil peering traffic.

TLS public peers are identified by the prefix tls:// instead of tcp://.

Note that, due to the additional layer of encryption, performance via TLS peers may be slightly worse than via regular tcp:// peers.