Policy
Tune connection buffers and timing limits.
Updated
Policy is the Settings page for connection resource and timing limits. These are advanced controls. Change one slider at a time and return to defaults when the problem is not clearly improved. The Settings row summary calls out changed BufferSize, Handshake, and ConnIdle values; the close-timeout sliders stay on the page.
Policy sliders
Buffer Size
The internal buffer size of each connection. Larger values can improve throughput and increase memory use.
BufferSize
Slider from 0 to 10, displayed as Disabled, 1, 2, 4, 8, 16, 32, 64, 128, 256, or 512 KB. Disabled means Tunna does not set an extra buffer size. Default is 128 KB.
Connection setup and idle time
These timers decide how patient Tunna should be before treating a connection as failed or idle.
Handshake
3 to 60 seconds. This is the setup time limit before the connection is considered failed. Default is 5 seconds.
ConnIdle
0 to 600 seconds in 10-second steps. Lower values conserve resources; higher values help intermittent traffic. Default is 10 seconds.
Close timing
These sliders control how long one side remains after the other side has closed.
Upstream Close Timeout
0 to 300 seconds. Default is 5 seconds.
Downstream Close Timeout
0 to 300 seconds. Default is 2 seconds.
Policy saves when you leave
There is no Save button. Tunna keeps the current slider values when you leave the Policy screen and applies the changed policy to later connection behavior.
Practical policy uses
Diagnose slow setup
Raise Handshake only when a known-good node needs more time to complete setup on a slow network.
Good fit Logs or repeated tests show setup timing out before the server responds.
Not ideal The node fields, transport, or security settings are still uncertain.
Reduce idle resource use
Lower ConnIdle when many short-lived connections are staying open longer than needed.
Good fit You want unused connections to close sooner.
Not ideal Interactive apps need quiet gaps without reconnecting.
Keep defaults for normal use
Leave BufferSize and close timeouts alone unless support or a provider points to a specific transport behavior.
Good fit The tunnel is stable and you are not chasing a measured problem.
Not ideal You are changing several advanced settings at once.