handshakes
None of the handshakes settings are reloadable. Changing one takes effect after Nebula restarts, and a reload that
changes one reports that a restart is required.
handshakes.try_interval
Default: 100msHandshakes are sent to all known addresses at each interval with a linear backoff, waiting try_interval after the 1st
attempt, 2 * try_interval after the 2nd, etc, until the handshake is older than timeout.
handshakes.retries
Default: 10A 100ms interval with the default 10 retries will give a handshake 5.5 seconds to resolve before timing out.
handshakes.trigger_buffer
Default: 64trigger_buffer is the size of the buffer channel for quickly sending handshakes after receiving the response for
lighthouse queries.
handshakes.query_buffer
Default: 1024query_buffer is the size of the buffer channel for queries to the lighthouses. Starting a handshake never waits on a
full buffer: the lighthouse query is dropped instead and counted in the lighthouse.query.dropped metric. The handshake
still proceeds with any addresses already known. Raise this on hosts that start many tunnels at once.
handshakes:
try_interval: 100ms
retries: 10
trigger_buffer: 64
query_buffer: 1024