Skip to content

Commit

Permalink
Tweaks
Browse files Browse the repository at this point in the history
  • Loading branch information
neilalexander committed Sep 30, 2024
1 parent c4d8461 commit 051bd55
Showing 1 changed file with 3 additions and 1 deletion.
4 changes: 3 additions & 1 deletion advanced-peering.md
Original file line number Diff line number Diff line change
Expand Up @@ -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: [
Expand All @@ -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.

Expand Down

0 comments on commit 051bd55

Please sign in to comment.