j3d1/tinc
1
0
Fork 0
Code Issues 1 Pull requests Releases Wiki Activity

Use a different UDP discovery interval if the tunnel is established.

Browse source 
This introduces a new configuration option,
UDPDiscoveryKeepaliveInterval, which is used as the UDP discovery
interval once the UDP tunnel is established. The pre-existing option,
UDPDiscoveryInterval, is therefore only used before UDP connectivity
is established.

The defaults are set so that tinc sends UDP pings more aggressively
if the tunnel is not established yet. This is appropriate since the
size of probes in that scenario is very small (16 bytes).
This commit is contained in:
Etienne Dechamps 2015-01-03 10:05:57 +00:00
parent 06345f89b9
commit 07108117ce
7 changed files with 21 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

9
doc/tinc.texi
View file

@ -1239,9 +1239,14 @@ using TCP while it determines if a node is reachable over UDP. If it is disabled
tinc always assumes a node is reachable over UDP.
Note that tinc will never use UDP with nodes that have TCPOnly enabled.
@cindex UDPDiscoveryKeepaliveInterval
@item UDPDiscoveryKeepaliveInterval = <seconds> (9)
The minimum amount of time between sending UDP ping datagrams to check UDP connectivity once it has been established.
Note that these pings are large, since they are used to verify link MTU as well.
@cindex UDPDiscoveryInterval
@item UDPDiscoveryInterval = <seconds> (9)
The minimum amount of time between sending UDP ping datagrams to test UDP connectivity.
@item UDPDiscoveryInterval = <seconds> (2)
The minimum amount of time between sending UDP ping datagrams to try to establish UDP connectivity.
@cindex UDPDiscoveryTimeout
@item UDPDiscoveryTimeout = <seconds> (30)