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

Tweaks

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

4
advanced-peering.md
View File

@ -36,7 +36,7 @@ Note that the `priority` field only influences traffic between two peerings to t
### Prioritised multicast interfaces
If like above you have multiple network interfaces but are using multicast peers, but want to prefer one network interface over the other, you can specify the `Priority` for a given multicast interface.
Lower numbers are better. In this example, peerings that are automatically discovered and established over `eth0` will be preferred over `eth1`:
Lower numbers are better. In this example, peerings that are automatically discovered and established over `eth0` will be preferred over peerings to the same node made over `eth1`:
```
MulticastInterfaces: [
@ -55,6 +55,8 @@ MulticastInterfaces: [
]
```
Note that the `priority` field only influences traffic between two peerings to the same node. It does not affect routing decisions across different nodes and cannot be used, for example, to avoid sending traffic to one remote peer over another.
### 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.