[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
If everything else is done, you can start tinc by typing the following command:
tincd -n netname |
Tinc will detach from the terminal and continue to run in the background like a good daemon. If there are any problems however you can try to increase the debug level and look in the syslog to find out what the problems are.
5.1 Runtime options | ||
5.2 Signals | ||
5.3 Debug levels | ||
5.4 Solving problems | ||
5.5 Error messages | ||
5.6 Sending bug reports |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Besides the settings in the configuration file, tinc also accepts some command line options.
Read configuration options from the directory path. The default is ‘/etc/tinc/netname/’.
Don't fork and detach. This will also disable the automatic restart mechanism for fatal errors.
Set debug level to level. The higher the debug level, the more gets logged. Everything goes via syslog.
Attempt to kill a running tincd (optionally with the specified signal instead of SIGTERM) and exit. Use it in conjunction with the -n option to make sure you kill the right tinc daemon. Under native Windows the optional argument is ignored, the service will always be stopped and removed.
Use configuration for net netname. See section Multiple networks.
Generate public/private keypair of bits length. If bits is not specified, 1024 is the default. 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 in combination with -K). After that, tinc will quit.
Lock tinc into main memory. This will prevent sensitive data like shared private keys to be written to the system swap files/partitions.
Write log entries to a file instead of to the system logging facility. If file is omitted, the default is ‘/var/log/tinc.netname.log’.
Write PID to file instead of ‘/var/run/tinc.netname.pid’.
Disables encryption and authentication. Only useful for debugging.
Display a short reminder of these runtime options and terminate.
Output version information and exit.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
You can also send the following signals to a running tincd process:
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.
Partially rereads configuration files. Connections to hosts whose host config file are removed are closed. New outgoing connections specified in ‘tinc.conf’ will be made.
Temporarily increases debug level to 5. Send this signal again to revert to the original level.
Dumps the connection list to syslog.
Dumps virtual network device statistics, all known nodes, edges and subnets to syslog.
Purges all information remembered about unreachable nodes.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The tinc daemon can send a lot of messages to the syslog. The higher the debug level, the more messages it will log. Each level inherits all messages of the previous level:
This will log a message indicating tinc has started along with a version number. It will also log any serious error.
This will log all connections that are made with other tinc daemons.
This will log status and error messages from scripts and other tinc daemons.
This will log all requests that are exchanged with other tinc daemons. These include authentication, key exchange and connection list updates.
This will log a copy of everything received on the meta socket.
This will log all network traffic over the virtual private network.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
If tinc starts without problems, but if the VPN doesn't work, you will have to find the cause of the problem. The first thing to do is to start tinc with a high debug level in the foreground, so you can directly see everything tinc logs:
tincd -n netname -d5 -D |
If tinc does not log any error messages, then you might want to check the following things:
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
What follows is a list of the most common error messages you might find in the logs. Some of them will only be visible if the debug level is high enough.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
If you really can't find the cause of a problem, or if you suspect tinc is not working right, you can send us a bugreport, see Contact information. Be sure to include the following information in your bugreport:
[ << ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This document was generated by root on November, 5 2007 using texi2html 1.78.