cwinfo/yggdrasil-network.github.io
5
0
Fork 0
mirror of https://github.com/cwinfo/yggdrasil-network.github.io.git synced 2025-02-28 21:01:33 +00:00
Code Releases Activity

Tweaks

Browse Source
This commit is contained in:
Neil Alexander 2024-09-30 19:02:38 +01:00
parent 52f4344411
commit c4d8461f28
No known key found for this signature in database
GPG Key ID: A02A2019A2BB0944
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
advanced-peering.md
View File

@ -5,7 +5,7 @@ tags: dontlink
# Advanced Peerings
This document contains information on more advanced peering setups.
### Multi-homed machine
### Multi-homed outbound peerings
On a machine that has multiple network interfaces, where more than one interface can be used to reach a given peer (or the Internet), the `InterfacePeers` option can be used instead of the `Peers` option to create peerings over specific interfaces.
It is possible to connect to the **same peer multiple times** using different interfaces, creating a highly-available peering configuration:
@ -55,7 +55,7 @@ MulticastInterfaces: [
]
```
### Multiple Tor circuits
### Multiple outbound Tor circuits
Peering over Tor is possible using the SOCKS proxy support, although it is typically discouraged as Tor peerings are often slow and fragile. Most notably, Tor circuits can be broken at any time, taking down your Yggdrasil peering connection with it.
To mitigate this, enable the `IsolateSOCKSAuth ` option in Tor and then establish **multiple connections to the same peer** using different SOCKS usernames and passwords. The usernames and passwords can be anything, but these unique pairs will force Tor to use a separate circuit for each peering connection, providing redundancy against one of those circuits breaking: