5
0
mirror of https://github.com/cwinfo/yggdrasil-public-peers.git synced 2024-12-26 05:25:45 +00:00
yggdrasil-public-peers/README.md

61 lines
2.1 KiB
Markdown
Raw Normal View History

2018-03-11 20:08:02 +00:00
# Public Peers
2019-03-25 18:04:52 +00:00
This repository contains peering information for publicly accessible nodes on
2020-06-13 18:43:41 +00:00
the Yggdrasil network.
Note that not all peers in this repository are guaranteed to be online - check
the [Public Peers](https://publicpeers.neilalexander.dev/) page instead to find
peers that are online now.
2018-03-11 20:08:02 +00:00
2019-03-25 18:04:52 +00:00
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`:
```
2024-02-18 10:25:07 +00:00
Peers: [
2019-03-25 18:04:52 +00:00
tcp://a.b.c.d:e
2024-02-18 10:25:07 +00:00
tls://d.c.b.a:e
2019-03-25 18:04:52 +00:00
tcp://[a:b:c::d]:e
2024-02-18 10:25:07 +00:00
tls://[d:c:b::a]:e
2019-03-25 18:04:52 +00:00
]
```
### How do I pick peers?
2020-06-13 18:43:41 +00:00
If you are new to the network then take a look at the [Public Peers](https://publicpeers.neilalexander.dev/)
page to find public peers that are online.
2019-03-25 18:04:52 +00:00
Always try to pick peers that are as close to you geographically as possible, as
this will keep the latency of the network down.
2024-02-18 10:25:07 +00:00
If you are using a home connection, then you should avoid peering with any nodes
2019-03-25 18:04:52 +00:00
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.
2019-10-31 10:34:46 +00:00
2024-02-18 10:25:07 +00:00
### Peering reference
URI format: `[protocol]://[host]:[port]?[options]`
2019-10-31 10:34:46 +00:00
2024-02-18 10:25:07 +00:00
**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]`
2024-08-16 08:40:47 +00:00
- WebSocket (v0.5.7+): `ws://`
- WebSocket over HTTPS (v0.5.7+): `wss://`
2019-10-31 10:34:46 +00:00
2024-02-18 10:25:07 +00:00
Yggdrasil supports basic authentication for SOCKS5 using credentials in the URI like this:
2019-10-31 10:34:46 +00:00
2024-02-18 10:25:07 +00:00
`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)