Add documentation about using system-assigned ports.
authorEtienne Dechamps <etienne@edechamps.fr>
Sun, 6 Jul 2014 10:34:57 +0000 (11:34 +0100)
committerGuus Sliepen <guus@tinc-vpn.org>
Sat, 12 Jul 2014 20:13:43 +0000 (22:13 +0200)
commit7bf61575fe1009ecb93b3f6b8f5145525874e470
tree02f4785ecf527647e1c1a62468bb7d18ffa1996a
parent5ffdff685a0e7d25f7c016f3a6cd89bb82fed71c
Add documentation about using system-assigned ports.

There are two caveats to be aware of which are documented in this
commit:

 - Because the system will likely assign different ports when binding
   several times to different address families, it is recommended to
   only use a single address family, otherwise other nodes will only
   get one port among the several that were assigned, possibly breaking
   communication.

 - AutoConnect won't work in this scenario, because it relies on the UDP
   port being the same as the TCP port, which is not the case when using
   system-assigned ports.
doc/tinc.conf.5.in