VPN with Tinc - Revision history

320x200 at 23:26, 8 January 2022

2022-01-08T23:26:03Z

← Older revision		Revision as of 23:26, 8 January 2022
Line 147:		Line 147:
	In router mode tinc runs as a Layer 3 network, while switch allows tinc to run as a Layer 2 network. By default Tinc runs in router mode and it will be fine for most of the things you may need. However, sometimes an application going through tinc may need Layer 2 to work properly, for instance some automagical network/peer discovery making use of Layer 2 broadcasts. If you need to switch to switch (haha...) then add the following in the <code>tinc.conf</code> of '''all the nodes''':		In router mode tinc runs as a Layer 3 network, while switch allows tinc to run as a Layer 2 network. By default Tinc runs in router mode and it will be fine for most of the things you may need. However, sometimes an application going through tinc may need Layer 2 to work properly, for instance some automagical network/peer discovery making use of Layer 2 broadcasts. If you need to switch to switch (haha...) then add the following in the <code>tinc.conf</code> of '''all the nodes''':
	Mode = switch		Mode = switch

			=== Conflict with OpenVPN on Windows ===
			Tinc's TAP driver and OpenVPN's own TAP driver seem to confuse each other. There must be a way to make them live in harmony? As a workaround, it's possible to disable OpenVPN Tinc driver so that when Tinc is launched it properly uses its interface and not the one from OpenVPN.
			netsh interface set interface "Connexion au réseau local" disable

	== Further readings and more cool stuff ==		== Further readings and more cool stuff ==
	* https://pzwiki.wdka.nl/mediadesign/Tinc		* https://pzwiki.wdka.nl/mediadesign/Tinc
	* https://www.tinc-vpn.org/documentation-1.1		* https://www.tinc-vpn.org/documentation-1.1

	~~== Conflict with OpenVPN on Windows ==~~
	Tinc's TAP driver and OpenVPN's own TAP driver seem to confuse each other. There must be a way to make them live in harmony? As a workaround, it's possible to disable OpenVPN Tinc driver so that when Tinc is launched it properly uses its interface and not the one from OpenVPN.
	~~netsh interface set interface "Connexion au réseau local" disable~~



	[[Category: VPN]]		[[Category: VPN]]

320x200: /* Further readings and more cool stuff */

2022-01-08T23:25:19Z

320x200: /* FreeBSD and GNU/Linux */

2021-06-11T16:27:52Z

FreeBSD and GNU/Linux

← Older revision		Revision as of 16:27, 11 June 2021
Line 47:		Line 47:
	=== FreeBSD and GNU/Linux ===		=== FreeBSD and GNU/Linux ===
	* Generate invite '''on the server'''		* Generate invite '''on the server'''
	tinc -b beernet invite ${CLIENT_NAME}		tinc -n beernet invite ${CLIENT_NAME}
	* This will give you ${URL}		* This will give you ${URL}
	* '''On the BSD/Linux client'''		* '''On the BSD/Linux client'''
	tinc~~.exe~~ -n beernet join ${URL}		tinc -n beernet join ${URL}
	tinc~~.exe~~ -n beernet add subnet 10.10.10.2		tinc -n beernet add subnet 10.10.10.2
	* edit <code>/usr/local/etc/tinc/beernet/tinc-up</code>, so that your network interface is brought up correctly, for instance with:		* edit <code>/usr/local/etc/tinc/beernet/tinc-up</code>, so that your network interface is brought up correctly, for instance with:
	ifconfig $INTERFACE 10.10.10.2 netmask 255.255.255.0 # leave $INTERFACE as it is and remove the echo line		ifconfig $INTERFACE 10.10.10.2 netmask 255.255.255.0 # leave $INTERFACE as it is and remove the echo line

320x200: /* Windows */

2021-06-11T16:27:34Z

Windows

← Older revision		Revision as of 16:27, 11 June 2021
Line 61:		Line 61:
	=== Windows ===		=== Windows ===
	* Generate invite '''on the server'''		* Generate invite '''on the server'''
	tinc -b beernet invite ${CLIENT_NAME}		tinc -n beernet invite ${CLIENT_NAME}
	* This will give you ${URL}		* This will give you ${URL}
	* '''On the windows client machine''', open a terminal, locate the Tinc install folder and:		* '''On the windows client machine''', open a terminal, locate the Tinc install folder and:

320x200: /* iptables */

2021-06-11T16:16:58Z

iptables

← Older revision		Revision as of 16:16, 11 June 2021
Line 82:		Line 82:
	=== Firewall ===		=== Firewall ===
	==== iptables ====		==== iptables ====
	<~~code~~>		<pre>
	# Allow Tinc VPN connections without port restrictions		# Allow Tinc VPN connections without port restrictions
	-A INPUT -i tun+ -j ACCEPT		-A INPUT -i tun+ -j ACCEPT
Line 96:		Line 96:
	-A OUTPUT -p udp --sport 655 -j ACCEPT		-A OUTPUT -p udp --sport 655 -j ACCEPT
	-A OUTPUT -p udp --dport 655 -j ACCEPT		-A OUTPUT -p udp --dport 655 -j ACCEPT
	</~~code~~>		</pre>

	=== GNU/Linux with new net interface tool ===		=== GNU/Linux with new net interface tool ===

320x200: /* PRO tips */

2021-06-11T16:16:37Z

PRO tips

@@ Line 80: / Line 80: @@
 == PRO tips ==
 === GNU/Linux with new net interface tool ===
 <code>ifconfig</code> will be likely deprecated or even removed on some recent GNU/Linux distros, so the proper way to configure <code>tinc-up</code> and on such machines is as follow:

320x200: /* PRO tips */

2021-02-18T23:52:26Z

PRO tips

← Older revision		Revision as of 23:52, 18 February 2021
Line 125:		Line 125:
	sudo systemctl start tinc@lurknet		sudo systemctl start tinc@lurknet
	sudo systemctl stop tinc@lurknet		sudo systemctl stop tinc@lurknet

			=== Switch vs Router mode ===
			In router mode tinc runs as a Layer 3 network, while switch allows tinc to run as a Layer 2 network. By default Tinc runs in router mode and it will be fine for most of the things you may need. However, sometimes an application going through tinc may need Layer 2 to work properly, for instance some automagical network/peer discovery making use of Layer 2 broadcasts. If you need to switch to switch (haha...) then add the following in the <code>tinc.conf</code> of '''all the nodes''':
			Mode = switch

	== Further readings and more cool stuff ==		== Further readings and more cool stuff ==

320x200: /* Windows */

2021-02-18T23:38:49Z

Windows

← Older revision		Revision as of 23:38, 18 February 2021
Line 25:		Line 25:
	=== Windows ===		=== Windows ===
	* Install tinc 1.1 pre win binaries from upstream at https://tinc-vpn.org/download/		* Install tinc 1.1 pre win binaries from upstream at https://tinc-vpn.org/download/

			=== MacOs ===
			'''FIXME'''

	== Setup Server(s) ==		== Setup Server(s) ==

320x200: /* MacOs */

2021-02-18T23:38:40Z

MacOs

← Older revision		Revision as of 23:38, 18 February 2021
Line 22:		Line 22:
	* If needed, make a directory for pidfile and socket		* If needed, make a directory for pidfile and socket
	sudo mkdir -p /usr/local/var/run/		sudo mkdir -p /usr/local/var/run/

	~~=== MacOs ===~~
	~~'''FIXME'''~~

	=== Windows ===		=== Windows ===

320x200 at 23:38, 18 February 2021

2021-02-18T23:38:20Z

@@ Line 22: / Line 22: @@
 * If needed, make a directory for pidfile and socket
   sudo mkdir -p /usr/local/var/run/
 === MacOs ===
@@ Line 100: / Line 44: @@
   tincd -n beernet -D -d3
-== Setup Client ==
+== Setup Client(s) ==
-=== FreeBSD ===
+=== FreeBSD and GNU/Linux ===
-=== GNU/Linux ===
+* Generate invite '''on the server'''
-=== MacOs ===
+ tinc -b beernet invite ${CLIENT_NAME}
 === Windows ===
-* Generate invite on the server
+* Generate invite '''on the server'''
   tinc -b beernet invite ${CLIENT_NAME}
 * This will give you ${URL}
-* On the windows client
+* '''On the windows client machine''', open a terminal, locate the Tinc install folder and:
   tinc.exe -n beernet join ${URL}
-  tinc.exe -n beernet add subnet 10.10.10.2
+  tinc.exe -n beernet add subnet 10.10.10.3
 * got to <code>C:\Program Files\tinc\tap-win64</code>
 * run <code>addtap.bat</code>. Click yes to install the driver.
@@ Line 118: / Line 73: @@
   netsh interface set interface name = "${NAME}" newname = "tinc"
 * give it the same IP as tinc client config
-  netsh interface ip set address "tinc" static 10.10.10.2 255.255.255.0.
+  netsh interface ip set address "tinc" static 10.10.10.3 255.255.255.0.
 == PRO tips ==
@@ Line 127: / Line 86: @@
 === Set up systemd services ===
 * <code>/lib/systemd/system/tinc.service</code>
   [Unit]
@@ Line 167: / Line 125: @@
   sudo systemctl start tinc@lurknet
   sudo systemctl stop tinc@lurknet
 [[Category: VPN]]

← Older revision		Revision as of 23:25, 8 January 2022
Line 151:		Line 151:
	* https://pzwiki.wdka.nl/mediadesign/Tinc		* https://pzwiki.wdka.nl/mediadesign/Tinc
	* https://www.tinc-vpn.org/documentation-1.1		* https://www.tinc-vpn.org/documentation-1.1

			== Conflict with OpenVPN on Windows ==
			Tinc's TAP driver and OpenVPN's own TAP driver seem to confuse each other. There must be a way to make them live in harmony? As a workaround, it's possible to disable OpenVPN Tinc driver so that when Tinc is launched it properly uses its interface and not the one from OpenVPN.
			netsh interface set interface "Connexion au réseau local" disable



	[[Category: VPN]]		[[Category: VPN]]