Tinc/2018-04-12 - Revision history

Admin: Admin moved page Tincd/2018-04-12 to Tinc/2018-04-12

2018-04-13T06:33:19Z

← Older revision	Revision as of 06:33, 13 April 2018
(No difference)

2018-04-13T06:33:05Z

← Older revision		Revision as of 06:33, 13 April 2018
Line 195:		Line 195:

	Fix this script: https://git.charlesreid1.com/dotfiles/debian/src/branch/master/dotfiles/scripts/tincd_install.sh		Fix this script: https://git.charlesreid1.com/dotfiles/debian/src/branch/master/dotfiles/scripts/tincd_install.sh


			[[Category:Tinc]]

2018-04-13T03:22:51Z

Step 0: Set Up Nodes

← Older revision		Revision as of 03:22, 13 April 2018
Line 27:		Line 27:
	Real solution: have a reserved private/public key pair, hard code public key.		Real solution: have a reserved private/public key pair, hard code public key.

			On AWS, also needed to open port 655 to the world for the security group.

	==Step 1: Prep Nodes==		==Step 1: Prep Nodes==

2018-04-13T03:22:14Z

Step 4: Give It A Whirl

← Older revision		Revision as of 03:22, 13 April 2018
Line 179:		Line 179:
	sudo tincd -n zombie --no-detach --debug=5		sudo tincd -n zombie --no-detach --debug=5
	</pre>		</pre>

			Now, open a separate window and log into machine 1. Ping the VPN IP address of machine 2 and machine 3 from machine 1:

			<pre>
			ping 10.6.0.2


			ping 10.6.0.3
			</pre>

			Both should be reachable, and you should see activity in the windows of both machines when the ping action occurs.

	=Next Steps=		=Next Steps=

	Fix this script: https://git.charlesreid1.com/dotfiles/debian/src/branch/master/dotfiles/scripts/tincd_install.sh		Fix this script: https://git.charlesreid1.com/dotfiles/debian/src/branch/master/dotfiles/scripts/tincd_install.sh

2018-04-13T03:18:27Z

Step 4: Give It A Whirl

← Older revision		Revision as of 03:18, 13 April 2018
Line 177:		Line 177:

	<pre>		<pre>
	sudo tincd -n zombie -D -d3		sudo tincd -n zombie --no-detach --debug=5
	</pre>		</pre>

2018-04-13T03:13:29Z

Create VPN Control Scripts

← Older revision		Revision as of 03:13, 13 April 2018
Line 166:		Line 166:
	</pre>		</pre>

			Make executable:

			<pre>
			sudo chmod +x /etc/tinc/$LABEL/tinc-{up,down}
			</pre>

	==Step 4: Give It A Whirl==		==Step 4: Give It A Whirl==

2018-04-13T03:11:49Z

Step 3: Set Up Tinc

← Older revision		Revision as of 03:11, 13 April 2018
Line 164:		Line 164:
	ip addr del 10.6.0.X dev $INTERFACE		ip addr del 10.6.0.X dev $INTERFACE
	ip link set $INTERFACE down		ip link set $INTERFACE down
			</pre>


			==Step 4: Give It A Whirl==

			From each machine, run tinc VPN in the foreground:

			<pre>
			sudo tincd -n zombie -D -d3
	</pre>		</pre>

2018-04-13T03:06:48Z

Aside: Setting Up Passwordless Scp

@@ Line 107: / Line 107: @@
 One of the things you'll need to do is copy the key files from each machine to each other machine.
 AWS uses private keys by default, which is a pain in the ass. But with the debian dotfiles and the cloud init script, each node already has a regular user and a private/public key pair for that user, so we're ready to go with passwordless access.
@@ Line 131: / Line 125: @@
 Now you can ssh from Machine A into Machine B.
 Copy the completed machine file to each other machine server:

2018-04-13T03:05:41Z

Create VPN Host Files

← Older revision		Revision as of 03:05, 13 April 2018
Line 107:		Line 107:

	One of the things you'll need to do is copy the key files from each machine to each other machine.		One of the things you'll need to do is copy the key files from each machine to each other machine.

			Before you do this, make sure everything in <code>hosts/</code> is owned by a regular user:

			<pre>
			sudo chown -R charles:charles /etc/tinc/$LABEL/hosts
			</pre>

	AWS uses private keys by default, which is a pain in the ass. But with the debian dotfiles and the cloud init script, each node already has a regular user and a private/public key pair for that user, so we're ready to go with passwordless access.		AWS uses private keys by default, which is a pain in the ass. But with the debian dotfiles and the cloud init script, each node already has a regular user and a private/public key pair for that user, so we're ready to go with passwordless access.

2018-04-13T03:04:43Z

Create VPN Control Scripts

← Older revision		Revision as of 03:04, 13 April 2018
Line 137:		Line 137:

	Create tinc-up script (modify the IP address):		Create tinc-up script (modify the IP address):

			<code>/etc/tinc/$LABEL/tinc-up</code>:

	<pre>		<pre>
	~~cat > /etc/tinc/$LABEL/tinc-up <<EOL~~
	#!/bin/sh		#!/bin/sh
	ip link set $INTERFACE up		ip link set $INTERFACE up
	ip addr add 10.6.0.X dev $INTERFACE		ip addr add 10.6.0.X dev $INTERFACE
	ip route add 10.6.0.0/24 dev $INTERFACE		ip route add 10.6.0.0/24 dev $INTERFACE
	~~EOL~~
	</pre>		</pre>

	Create tinc-down script:		Create tinc-down script:

			<code>/etc/tinc/$LABEL/tinc-down</code>

	<pre>		<pre>
	~~cat > /etc/tinc/$LABEL/tinc-down <<EOL~~
	#!/bin/sh		#!/bin/sh
	ip route del 10.6.0.0/24 dev $INTERFACE		ip route del 10.6.0.0/24 dev $INTERFACE