Next: tinc examples, Previous: tinc environment variables, Up: Controlling tinc [Contents][Index]
Create initial configuration files and RSA and Ed25519 key pairs with default length. If no name for this node is given, it will be asked for.
Print the current value of configuration variable variable. If more than one variable with the same name exists, the value of each of them will be printed on a separate line.
Set configuration variable variable to the given value. All previously existing configuration variables with the same name are removed. To set a variable for a specific host, use the notation host.variable.
As above, but without removing any previously existing configuration variables. If the variable already exists with the given value, nothing happens.
Remove configuration variables with the same name and value. If no value is given, all configuration variables with the same name will be removed.
Start an editor for the given configuration file. You do not need to specify the full path to the file.
Export the host configuration file of the local node to standard output.
Export all host configuration files to standard output.
Import host configuration file(s) generated by the tinc export command from standard input. Already existing host configuration files are not overwritten unless the option –force is used.
The same as export followed by import.
The same as export-all followed by import.
Prepares an invitation for a new node with the given name, and prints a short invitation URL that can be used with the join command.
Join an existing VPN using an invitation URL created using the invite command. If no URL is given, it will be read from standard input.
Start tincd, optionally with the given extra options.
Stop tincd.
Restart tincd, optionally with the given extra options.
Partially rereads configuration files. Connections to hosts whose host config files are removed are closed. New outgoing connections specified in tinc.conf will be made.
Shows the PID of the currently running tincd.
Generate both RSA and Ed25519 key pairs (see below) and exit. tinc will ask where you want to store the files, but will default to the configuration directory (you can use the -c or -n option).
Generate public/private Ed25519 key pair and exit.
Generate public/private RSA key pair and exit. If bits is omitted, the default length will be 2048 bits. When saving keys to existing files, tinc will not delete the old keys; you have to remove them manually.
Dump a list of all known nodes in the VPN. If the reachable keyword is used, only lists reachable nodes.
Dump a list of all known connections in the VPN.
Dump a list of all known subnets in the VPN.
Dump a list of all meta connections with ourself.
Dump a graph of the VPN in dotty format. Nodes are colored according to their reachability: red nodes are unreachable, orange nodes are indirectly reachable, green nodes are directly reachable. Black nodes are either directly or indirectly reachable, but direct reachability has not been tried yet.
Dump a list of outstanding invitations. The filename of the invitation, as well as the name of the node that is being invited is shown for each invitation.
Show information about a particular node, subnet or address. If an address is given, any matching subnet will be shown.
Purges all information remembered about unreachable nodes.
Sets debug level to level.
Capture log messages from a running tinc daemon. An optional debug level can be given that will be applied only for log messages sent to tinc.
Forces tinc to try to connect to all uplinks immediately. Usually tinc attempts to do this itself, but increases the time it waits between the attempts each time it failed, and if tinc didn’t succeed to connect to an uplink the first time after it started, it defaults to the maximum time of 15 minutes.
Closes the meta connection with the given node.
If tinc is compiled with libcurses support, this will display live traffic statistics for all the known nodes, similar to the UNIX top command. See below for more information.
Dump VPN traffic going through the local tinc node in pcap-savefile format to standard output, from where it can be redirected to a file or piped through a program that can parse it directly, such as tcpdump.
If netname is given, switch to that network. Otherwise, display a list of all networks for which configuration files exist.
This will check the configuration files for possible problems, such as unsafe file permissions, missing executable bit on script, unknown and obsolete configuration variables, wrong public and/or private keys, and so on.
When problems are found, this will be printed on a line with WARNING or ERROR in front of it. Most problems must be corrected by the user itself, however in some cases (like file permissions and missing public keys), tinc will ask if it should fix the problem.
Sign a file with the local node’s private key. If no filename is given, the file is read from standard input. The signed file is written to standard output.
Check the signature of a file against a node’s public key. The name of the node must be given, or can be ‘.’ to check against the local node’s public key, or ‘*’ to allow a signature from any node whose public key is known. If no filename is given, the file is read from standard input. If the verification is successful, a copy of the input with the signature removed is written to standard output, and the exit code will be zero. If the verification failed, nothing will be written to standard output, and the exit code will be non-zero.
Next: tinc examples, Previous: tinc environment variables, Up: Controlling tinc [Contents][Index]