This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
vpn-tinc [2022/02/11 00:24] – [Tinc Configuration] hogwild | vpn-tinc [2023/06/27 20:19] – [Hosts Tab] -explain Subnet purpose, condense hogwild | ||
---|---|---|---|
Line 5: | Line 5: | ||
The Tinc Daemon menu is divided into tabbed sections, including Tinc Configuration, | The Tinc Daemon menu is divided into tabbed sections, including Tinc Configuration, | ||
- | ===== Tinc Configuration | + | ===== Config Tab ===== |
{{: | {{: | ||
Line 11: | Line 11: | ||
\\ | \\ | ||
- | **Start with WAN:** Enabling this will cause the tinc daemon to start as part of the wanup (WAN interface initialization) process. | + | **Start with WAN:** Enabling this will cause the Tinc daemon to start as part of the wanup (WAN interface initialization) process. |
**Interface type:** TUN/TAP: Here, you specify the communication protocol used within your VPN. TUN is routed, and runs at the network (IP) layer. TAP is switched, and runs at the datalink layer. Generally, you should choose TUN. For more information on these protocols, see the " | **Interface type:** TUN/TAP: Here, you specify the communication protocol used within your VPN. TUN is routed, and runs at the network (IP) layer. TAP is switched, and runs at the datalink layer. Generally, you should choose TUN. For more information on these protocols, see the " | ||
Line 19: | Line 19: | ||
**Host Name:** This is the unique identifier of the OpenVPN device. This is NOT the same as the device' | **Host Name:** This is the unique identifier of the OpenVPN device. This is NOT the same as the device' | ||
- | **Poll interval: | + | **Poll interval: |
| | ||
Line 29: | Line 29: | ||
**Ed25519 Private Key: **In this field, enter your private Ed25519 encryption key. This key is needed for the encryption process. | **Ed25519 Private Key: **In this field, enter your private Ed25519 encryption key. This key is needed for the encryption process. | ||
- | **RSA Private Key * : **Here, enter your private RSA key. The RSA encryption | + | **RSA Private Key: * |
- | **Custom: **This field allows you to specify any custom | + | **Custom: **This field allows you to specify any custom |
- | ===== Hosts ===== | + | ===== Hosts Tab ===== |
- | Most of the hosts on your network should be defined on this page. Tinc doesn' | + | Most of the hosts on your network should be defined on this page. Tinc doesn' |
+ | |||
+ | However, you do need to define " | ||
\\ | \\ | ||
- | {{:pasted:20220204-091804.png}} | + | {{:pasted:20230111-110422.png?800}} |
\\ | \\ | ||
- | **ConnectTo: | + | **ConnectTo: |
- | **Name:** As on the Config tab, this is the unique | + | **Name: |
- | **Address: **This is used only when direct communication is possible | + | **Address: |
- | **Port: **An empty value configures the default setting (both TCP/UDP port 655). You might need to tweak this value if you include direclty windows | + | **Port: |
- | **Compression: | + | **Compression: |
- | **Subnet: | + | **Subnet: |
- | \\ | + | **Ed25519 Public Key: |
- | {{:pasted: | + | **RSA Public Key: * ** If you're using RSA encryption, you must define each host's public key here. RSA is optional in Tinc versions 1.0 and later. |
- | \\ | + | You must provide minimal information for every host defined before you can click OK and go to the next row. Clicking OK **does not** save settings. Only after you've defined all hosts, clicked " |
- | **Ed25519 Public Key:** This is where you enter your Ed25519 encryption Public Key. | + | **Custom:** In this field, |
- | **RSA Public Key *:** In case of RSA key you must define the public on on a host basis here. RSA is optional in tinc 1.0+ | + | For example, if a host communicates with with another subnet, you could add: |
- | For every host you define, you must provide the minimum info before being able to click OK and proceed to the next row. OK doesn' | + | // Subnet = 10.10.8.0/ |
- | **Custom:** In this field, you are free to define custom configuration settings for each host. For example, if a host is providing reachability to a second subnet you could add something like: //Subnet = 10.10.8.0/ | + | You must ensure these settings |
+ | |||
+ | \\ | ||