5
0
mirror of https://github.com/cwinfo/yggdrasil-public-peers.git synced 2024-06-15 00:35:46 +00:00
Public peers in the Yggdrasil network
Go to file
Christer Warén 7b13f2c6f0
CWINFO Peers - fi1.servers.devices.cwinfo.net (#532)
New IPv6 address for fi1.servers.devices.cwinfo.net
2024-04-19 14:54:15 +01:00
africa Clean up African peers (#435) 2022-12-25 16:08:29 +00:00
asia Added Brazil and Hong Kong node (#529) 2024-04-19 12:54:28 +01:00
australia Australia Peer (#531) 2024-04-19 14:27:35 +01:00
europe CWINFO Peers - fi1.servers.devices.cwinfo.net (#532) 2024-04-19 14:54:15 +01:00
mena Update saudi-arabia.md (#510) 2023-11-11 22:02:22 +00:00
north-america Prune dead peers (#530) 2024-04-19 12:54:09 +01:00
other other/{i2p,tor}.md: remove PPFI peer (#488) 2023-09-30 15:44:06 +01:00
south-america Added Brazil and Hong Kong node (#529) 2024-04-19 12:54:28 +01:00
README.md Add peering reference (#523) 2024-02-18 10:25:07 +00:00

Public Peers

This repository contains peering information for publicly accessible nodes on the Yggdrasil network.

Note that not all peers in this repository are guaranteed to be online - check the Public Peers page instead to find peers that are online now.

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
  tls://d.c.b.a:e
  tcp://[a:b:c::d]:e
  tls://[d:c:b::a]:e
]

How do I pick peers?

If you are new to the network then take a look at the Public Peers page to find public peers that are online.

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.

Peering reference

URI format: [protocol]://[host]:[port]?[options]

Available protocols:

  • Cleartext TCP: tcp://
  • TLS: tls://
  • TCP over SOCKS5: socks://[proxyhost]:[proxyport]/[host]:[port]
  • UNIX sockets: unix://
  • QUIC (v0.5.0+): quic://
  • TLS over SOCKS5 (v0.5.2+): sockstls://[proxyhost]:[proxyport]/[host]:[port]

Yggdrasil supports basic authentication for SOCKS5 using credentials in the URI like this:

socks://[username]:[password]@[proxyhost]:[proxyport]/[host]:[port]

Query options:

  • Public-key authentication: ?key=[publickey] (can have multiple values)
  • Custom SNI (for TLS/QUIC): ?sni=[domain] (default is host if it's domain)
  • Same-peer link priority: ?priority=[integer] (default is 0, maximum 254 for lowest priority)
  • Password authentication (v0.5.0+): ?password=[string] (length up to 64 characters)
  • Maximum back-off time (v0.5.5+): ?maxbackoff=[seconds] (supports duration values like 5m, 1h etc)