|
| 1 | +# $NetBSD: tinc.conf,v 1.1 2018/09/30 15:55:25 jperkin Exp $ |
| 2 | +# |
| 3 | +# tinc-vpn example configuration file. Please do NOT rely solely in the |
| 4 | +# information of this template, the information tinc.conf(5) manpage might |
| 5 | +# be more current. |
| 6 | +# |
| 7 | +# ------------------------------------------------------------------------------- |
| 8 | +# Name = name [required] |
| 9 | +# This is the name which identifies this tinc daemon. It must be unique |
| 10 | +# for the virtual private network this daemon will connect to. |
| 11 | +# We're using 'default' to match the instance name of the SMF service which |
| 12 | +# is created by default. |
| 13 | +# ------------------------------------------------------------------------------- |
| 14 | +Name = default |
| 15 | +# |
| 16 | +# |
| 17 | +# ------------------------------------------------------------------------------- |
| 18 | +# Mode = router | switch | hub (router) |
| 19 | +# This option selects the way packets are routed to other daemons. |
| 20 | +# |
| 21 | +# router In this mode Subnet variables in the host configuration files will |
| 22 | +# be used to form a routing table. Only unicast packets of routable |
| 23 | +# protocols (IPv4 and IPv6) are supported in this mode. |
| 24 | +# |
| 25 | +# This is the default mode, and unless you really know you need |
| 26 | +# another mode, don't change it. |
| 27 | +# |
| 28 | +# switch In this mode the MAC addresses of the packets on the VPN will be |
| 29 | +# used to dynamically create a routing table just like an Ethernet |
| 30 | +# switch does. Unicast, multicast and broadcast packets of every |
| 31 | +# protocol that runs over Ethernet are supported in this mode at the |
| 32 | +# cost of frequent broadcast ARP requests and routing table updates. |
| 33 | +# |
| 34 | +# This mode is primarily useful if you want to bridge Ethernet |
| 35 | +# segments. |
| 36 | +# |
| 37 | +# hub This mode is almost the same as the switch mode, but instead every |
| 38 | +# packet will be broadcast to the other daemons while no routing |
| 39 | +# table is managed. |
| 40 | +# ------------------------------------------------------------------------------- |
| 41 | +# Mode = router |
| 42 | +# |
| 43 | +# |
| 44 | +# ------------------------------------------------------------------------------- |
| 45 | +# ConnectTo = name |
| 46 | +# Specifies which other tinc daemon to connect to on startup. Multiple |
| 47 | +# ConnectTo variables may be specified, in which case outgoing connections |
| 48 | +# to each specified tinc daemon are made. The names should be known to this |
| 49 | +# tinc daemon (i.e., there should be a host configuration file for the name |
| 50 | +# on the ConnectTo line). |
| 51 | +# |
| 52 | +# If you don't specify a host with ConnectTo, tinc won't try to connect to |
| 53 | +# other daemons at all, and will instead just listen for incoming |
| 54 | +# connections. |
| 55 | +# ------------------------------------------------------------------------------- |
| 56 | +# ConnectTo = vpn1 |
| 57 | +# |
| 58 | +# |
| 59 | +# ------------------------------------------------------------------------------- |
| 60 | +# DeviceType = type (platform dependent) |
| 61 | +# The type of the virtual network device. Tinc will normally automatically |
| 62 | +# select the right type of tun/tap interface, and this option should not be |
| 63 | +# used. However, this option can be used to select one of the special |
| 64 | +# interface types, if support for them is compiled in. |
| 65 | +# ------------------------------------------------------------------------------- |
| 66 | +# DeviceType = tap |
0 commit comments