From 051bd551691b10d3220b980f2917429c2c51586e Mon Sep 17 00:00:00 2001 From: Neil Alexander Date: Mon, 30 Sep 2024 19:05:07 +0100 Subject: [PATCH] Tweaks --- advanced-peering.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/advanced-peering.md b/advanced-peering.md index 6389adf..a8126d3 100644 --- a/advanced-peering.md +++ b/advanced-peering.md @@ -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.