X-Git-Url: https://www.tinc-vpn.org/git/browse?p=tinc;a=blobdiff_plain;f=doc%2Ftinc.texi;h=0697f103bedbbba1030079d33eaf6fb726e3152d;hp=b6d0c21626ee080049b9d3132379a261e1a0c254;hb=5a28aa7b8b0ab6237c2eab5f8b11253ea3ec5a05;hpb=46506b7aaf6c6a8a85561c38fdb9c95eae21aa75

diff --git a/doc/tinc.texi b/doc/tinc.texi
index b6d0c216..0697f103 100644
--- a/doc/tinc.texi
+++ b/doc/tinc.texi
@@ -923,6 +923,16 @@ Depending on the operating system and the type of device this may or may not act
 Under Windows, this variable is used to select which network interface will be used.
 If you specified a Device, this variable is almost always already correctly set.
 
+@cindex LocalDiscovery
+@item LocalDiscovery = <yes | no> (no) [experimental]
+When enabled, tinc will try to detect peers that are on the same local network.
+This will allow direct communication using LAN addresses, even if both peers are behind a NAT
+and they only ConnectTo a third node outside the NAT,
+which normally would prevent the peers from learning each other's LAN address.
+
+Currently, local discovery is implemented by sending broadcast packets to the LAN during path MTU discovery.
+This feature may not work in all possible situations.
+
 @cindex Mode
 @item Mode = <router|switch|hub> (router)
 This option selects the way packets are routed to other daemons.