Tinc - Revision history

imported>Aforemny: Add missing quotes around `address`'s value

2022-02-27T13:54:11Z

Add missing quotes around `address`'s value

← Older revision		Revision as of 13:54, 27 February 2022
Line 68:		Line 68:

	<syntaxHighlight lang=nix># for heinz		<syntaxHighlight lang=nix># for heinz
	networking.interfaces."tinc.${networkName}".ipv4.addresses = [ { address = 10.1.1.25; prefixLength = 24; } ];		networking.interfaces."tinc.${networkName}".ipv4.addresses = [ { address = "10.1.1.25"; prefixLength = 24; } ];
	</syntaxHighlight>		</syntaxHighlight>

imported>Chuangzhu: Fix systemd unit

2021-12-16T11:11:22Z

Fix systemd unit

← Older revision		Revision as of 11:11, 16 December 2021
Line 68:		Line 68:

	<syntaxHighlight lang=nix># for heinz		<syntaxHighlight lang=nix># for heinz
	networking.interfaces."tinc.~~private~~".ipv4.addresses = [ { address = 10.1.1.25; prefixLength = 24; } ];		networking.interfaces."tinc.${networkName}".ipv4.addresses = [ { address = 10.1.1.25; prefixLength = 24; } ];
	</syntaxHighlight>		</syntaxHighlight>

Line 74:		Line 74:
	The following snippet '''seems''' to fix that (until perhaps a more proper fix is upstreamed?):		The following snippet '''seems''' to fix that (until perhaps a more proper fix is upstreamed?):
	<syntaxHighlight lang=nix>		<syntaxHighlight lang=nix>
	systemd.services."network-addresses-tinc.${networkName}".~~before~~ = [ "tinc.${networkName}.service" ];		# Start the unit for adding addresses if Tinc is started
	systemd.services."network-~~link~~-tinc.${networkName}".~~before~~ = [ "tinc.${networkName}.~~service~~" ];		systemd.services."tinc.${networkName}".wants = [ "network-addresses-tinc.${networkName}.service" ];
			# Stop the unit for adding addresses if Tinc is stopped or restarted
			systemd.services."network-addresses-tinc.${networkName}".partOf = [ "tinc.${networkName}.service" ];
			# Start the unit for adding addresses after the Tinc device is added
			systemd.services."network-addresses-tinc.${networkName}".after = [ "sys-subsystem-net-devices-tinc.${networkName}.device" ];
	</syntaxHighlight>		</syntaxHighlight>
	Note 2019-12-28: another author found that those lines were counter-productive. Their system hung for 90 seconds on boot waiting for /sys/subsystem/net/devices/tinc.<tinc network name> to be available, and then after booting they had to manually do something to get tinc working. Removing those lines fixed both problems.

	=== tinc-up/tinc-down ===		=== tinc-up/tinc-down ===

imported>Chuangzhu: Update expression to configure interface address

2021-12-16T10:52:05Z

Update expression to configure interface address

← Older revision		Revision as of 10:52, 16 December 2021
Line 68:		Line 68:

	<syntaxHighlight lang=nix># for heinz		<syntaxHighlight lang=nix># for heinz
	networking.interfaces."tinc.private" = [ { address = 10.1.1.25; } ];		networking.interfaces."tinc.private".ipv4.addresses = [ { address = 10.1.1.25; prefixLength = 24; } ];
	</syntaxHighlight>		</syntaxHighlight>

imported>Joepie91: Fix formatting for tinc-up/tinc-down example

2020-05-30T15:03:01Z

Fix formatting for tinc-up/tinc-down example

← Older revision		Revision as of 15:03, 30 May 2020
Line 86:		Line 86:

	<syntaxHighlight lang=nix># for heinz		<syntaxHighlight lang=nix># for heinz
	environment.etc."tinc/private/tinc-up".source = pkgs.writeScript ~~"~~tinc-up-private'		environment.etc = {
	#!${pkgs.stdenv.shell}		"tinc/private/tinc-up".source = pkgs.writeScript "tinc-up-private" ''
	${pkgs.nettools}/bin/ifconfig $INTERFACE 10.1.1.25 netmask 255.255.255.0		#!${pkgs.stdenv.shell}
	'';		${pkgs.nettools}/bin/ifconfig $INTERFACE 10.1.1.25 netmask 255.255.255.0
	~~environment.etc.~~"tinc/private/tinc-down".source = pkgs.writeScript "tinc-down-private''		'';
	#!${pkgs.stdenv.shell}		"tinc/private/tinc-down".source = pkgs.writeScript "tinc-down-private" ''
	/run/wrappers/bin/sudo ${pkgs.nettools}/bin/ifconfig $INTERFACE down		#!${pkgs.stdenv.shell}
	'';</syntaxHighlight>		/run/wrappers/bin/sudo ${pkgs.nettools}/bin/ifconfig $INTERFACE down
			'';
			};</syntaxHighlight>
	For the <code>tinc-down</code> we need to use sudo, because the user <code>tinc.private</code> who starts the service is not able to tear down the interface.		For the <code>tinc-down</code> we need to use sudo, because the user <code>tinc.private</code> who starts the service is not able to tear down the interface.

imported>Makefu: pre -> syntaxHighlight

2019-12-29T13:35:46Z

pre -> syntaxHighlight

Show changes

imported>Falsifian: /* networking.interfaces */ Add my experience getting tinc working.

2019-12-29T05:14:33Z

networking.interfaces: Add my experience getting tinc working.

← Older revision		Revision as of 05:14, 29 December 2019
Line 77:		Line 77:
	systemd.services."network-link-tinc.${networkName}".before = [ "tinc.${networkName}.service" ];		systemd.services."network-link-tinc.${networkName}".before = [ "tinc.${networkName}.service" ];
	</pre>		</pre>
			Note 2019-12-28: another author found that those lines were counter-productive. Their system hung for 90 seconds on boot waiting for /sys/subsystem/net/devices/tinc.<tinc network name> to be available, and then after booting they had to manually do something to get tinc working. Removing those lines fixed both problems.

	=== tinc-up/tinc-down ===		=== tinc-up/tinc-down ===

imported>V3vAP at 15:11, 26 October 2018

2018-10-26T15:11:06Z

← Older revision		Revision as of 15:11, 26 October 2018
Line 63:		Line 63:

	=== networking.interfaces ===		=== networking.interfaces ===
			NOTE: There are changes proposed to nix configuration, for using networkd based configuration instead of the current fragile scripted configuration, that will hopefully make the following section obsolete.

	The simplest way is to use the networking module. But it has some minor flaws on package updates.		The simplest way is to use the networking module. But it has some minor flaws on package updates.

imported>V3vAP: Possible fix for bad tinc restarts when using networking.interfaces

2018-10-22T03:35:17Z

Possible fix for bad tinc restarts when using networking.interfaces

← Older revision		Revision as of 03:35, 22 October 2018
Line 68:		Line 68:
	<pre># for heinz		<pre># for heinz
	networking.interfaces."tinc.private" = [ { address = 10.1.1.25; } ];		networking.interfaces."tinc.private" = [ { address = 10.1.1.25; } ];
			</pre>

			Another author has experienced problems with the network failing to restart when using the above to configure interfaces.
			The following snippet '''seems''' to fix that (until perhaps a more proper fix is upstreamed?):
			<pre>
			systemd.services."network-addresses-tinc.${networkName}".before = [ "tinc.${networkName}.service" ];
			systemd.services."network-link-tinc.${networkName}".before = [ "tinc.${networkName}.service" ];
	</pre>		</pre>
	=== tinc-up/tinc-down ===		=== tinc-up/tinc-down ===

imported>V3vAP: Spelling

2018-07-03T07:08:22Z

Spelling

← Older revision		Revision as of 07:08, 3 July 2018
Line 7:		Line 7:
	The following tutorial will setup a very simple scenario, where you create a tinc vpn between two computers in the same network. In this scenario <code>heinz</code> will connect to <code>peter</code>. But this will make <code>heinz</code> also visible to <code>peter</code>.		The following tutorial will setup a very simple scenario, where you create a tinc vpn between two computers in the same network. In this scenario <code>heinz</code> will connect to <code>peter</code>. But this will make <code>heinz</code> also visible to <code>peter</code>.

	It can easily be [https://www.tinc-vpn.org/examples/ improved to a setup with ~~muliple~~ computers] involved.		It can easily be [https://www.tinc-vpn.org/examples/ improved to a setup with multiple computers] involved.

	== Overview ==		== Overview ==
Line 22:		Line 22:
	== Generate keys ==		== Generate keys ==

	Tinc clients need to verify ~~themself~~ to each other, which is done by keys. There are multiple ways to generate your keys. Here is one.		Tinc clients need to verify themselves to each other, which is done by keys. There are multiple ways to generate your keys. Here is one.

	<pre>nix-shell -p tinc_pre --run "tinc generate-keys 4096"</pre>		<pre>nix-shell -p tinc_pre --run "tinc generate-keys 4096"</pre>
Line 43:		Line 43:
	Also the host files need to contain the public keys for this host.		Also the host files need to contain the public keys for this host.

	So lets create the two hostfiles. ~~Asuming~~ we have generated keys for the 2 machines and they are stored in the folders <code>heinz</code> and <code>peter</code>.		So lets create the two hostfiles. Assuming we have generated keys for the 2 machines and they are stored in the folders <code>heinz</code> and <code>peter</code>.

	<pre>cat >hosts_heinz <<EOF		<pre>cat >hosts_heinz <<EOF
Line 60:		Line 60:
	== Setup interface ==		== Setup interface ==

	We have to configure the tinc ~~tunel~~ interface.		We have to configure the tinc tunnel interface.

	=== networking.interfaces ===		=== networking.interfaces ===

	The simplest way is to use the ~~networing~~ module. But it has some minor flaws on package updates.		The simplest way is to use the networking module. But it has some minor flaws on package updates.

	<pre># for heinz		<pre># for heinz

imported>V3vAP: Spelling

2018-07-03T07:05:40Z

Spelling

← Older revision		Revision as of 07:05, 3 July 2018
Line 32:		Line 32:
	* <code>/etc/tinc/ed25519_key.pub</code>		* <code>/etc/tinc/ed25519_key.pub</code>

	== ~~Creatie~~ host files ==		== Create host files ==

	The hostfile can have a lot of parameters ([https://www.tinc-vpn.org/documentation/Host-configuration-variables.html here is an overview]).		The hostfile can have a lot of parameters ([https://www.tinc-vpn.org/documentation/Host-configuration-variables.html here is an overview]).
Line 64:		Line 64:
	=== networking.interfaces ===		=== networking.interfaces ===

	The simplest way is to us the networing module. But it has some minor flaws on package updates.		The simplest way is to use the networing module. But it has some minor flaws on package updates.

	<pre># for heinz		<pre># for heinz