From 37f45918da5413c65c79ac9af938d3f552406d55 Mon Sep 17 00:00:00 2001
From: "Tristan B. Velloza Kildaire" <deavmi@redxen.eu>
Date: Wed, 21 Dec 2022 13:56:42 +0200
Subject: [PATCH] Tunneling

- Added `float yes` to peer configuration
---
 docs/tunneling/fastd.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/docs/tunneling/fastd.md b/docs/tunneling/fastd.md
index b2d0a51..8d1956c 100644
--- a/docs/tunneling/fastd.md
+++ b/docs/tunneling/fastd.md
@@ -47,6 +47,7 @@ peer "<peerName>"
     remote <type> "<ip>" port <port>;
     key "<peer's public key>";
     interface "<interface>";
+	float yes;
 }
 
 ```
@@ -94,6 +95,9 @@ Now we need to fill in the peer details of the node you are connecting to:
 5. `"<peer's public key>"`
 	* Set this to your peer's public key
 
+> The `float yes` is to allow the peer with the provided public key to connect to you using a source address **other** than the one specified (as fastd does authenticate against that). [Read more](https://fastd.readthedocs.io/en/stable/manual/config.html#main-configuration).
+
+
 The last thing to configure now is to rise the interface up when fastd starts (as it normally doesn't rise it for you), all occurences of `<interfaceName>` here should match the one in the `interface <interfaceName>;` declaration as shown earlier.
 
 ### Starting and maintaining the daemon