Tinc/NewNode - Revision history

Admin: /* Network Architecture/Configuration */

2018-04-12T11:57:48Z

Network Architecture/Configuration

← Older revision		Revision as of 11:57, 12 April 2018
Line 143:		Line 143:

	jupiter/cronus/maya = behind nat network		jupiter/cronus/maya = behind nat network




			==Old Example==

			Old example: three computers behind NAT network + firewall (jupiter/cronus/maya), one public computer on the public internet (rojo)

	The setup with Tinc when there are multiple nodes is as follows:		The setup with Tinc when there are multiple nodes is as follows:

Admin: /* Network Architecture/Configuration */

2018-04-12T11:56:34Z

Network Architecture/Configuration

← Older revision		Revision as of 11:56, 12 April 2018
Line 137:		Line 137:

	==Network Architecture/Configuration==		==Network Architecture/Configuration==

			krash = central public server

			blackbeard = secondary public server

			jupiter/cronus/maya = behind nat network

	The setup with Tinc when there are multiple nodes is as follows:		The setup with Tinc when there are multiple nodes is as follows:

Admin: /* Network Architecture/Configuration */

2018-01-22T02:30:03Z

Network Architecture/Configuration

← Older revision		Revision as of 02:30, 22 January 2018
Line 151:		Line 151:

	Maya and cronus will be set to connect to jupiter when tinc starts.		Maya and cronus will be set to connect to jupiter when tinc starts.

			[[Image:TincNetworkConfiguration.png\|500px]]

	'''tinc.conf on rojo:'''		'''tinc.conf on rojo:'''

Admin: /* Network Architecture/Configuration */

2018-01-22T02:18:55Z

Network Architecture/Configuration

← Older revision		Revision as of 02:18, 22 January 2018
Line 140:		Line 140:
	The setup with Tinc when there are multiple nodes is as follows:		The setup with Tinc when there are multiple nodes is as follows:

	jupiter = debian server, cronus = mac, maya = mac		rojo = debian server, jupiter = debian server, cronus = mac, maya = mac

	~~Jupiter~~ is ~~the "~~server~~" (spoke on~~ the ~~wheel). Tinc is a peer~~-~~to-peer VPN model, but we can still have everybody share a single connection to the most convenient nearest~~ server~~, which for cronus and maya is jupiter~~.		Rojo is a public server, so it serves as the furthest-upstream server.

	Jupiter ~~will not be set~~ to connect to ~~anyone~~, so ~~it will simply listen for incoming connections~~.		Jupiter, cronus, and maya are all on a private network behind a firewall, so they connect to each other and then one reaches out to connect to rojo. Tinc is a peer-to-peer VPN model, so that allows the flexible arrangement.

	~~Cronus~~ will ~~bet set to~~ connect to ~~Jupiter when Tinc starts~~.		Rojo will not connect to anyone, but will simply listen for incoming connections.

	Maya will be set to connect to ~~Jupiter~~ when ~~Tinc~~ starts.		Jupiter will be set to connect to rojo when tinc starts.

			Maya and cronus will be set to connect to jupiter when tinc starts.

			'''tinc.conf on rojo:'''

			<pre>
			$ cat tinc.conf
			Name = rojo
			AddressFamily = any
			Device = /dev/net/tun
			Mode = switch
			</pre>

	'''tinc.conf on jupiter:'''		'''tinc.conf on jupiter:'''
Line 158:		Line 170:
	Device = /dev/net/tun		Device = /dev/net/tun
	Mode = switch		Mode = switch
			ConnectTo = rojo
	</pre>		</pre>

Line 179:		Line 192:
	ConnectTo = jupiter		ConnectTo = jupiter
	</pre>		</pre>




	==Flags==		==Flags==

Admin: /* Setting Up New Mac Node */

2018-01-22T02:16:18Z

Setting Up New Mac Node

@@ Line 51: / Line 51: @@
 </pre>
-Edit the file cronus, and add it to the repository
+Edit the file cronus to add the IP and subnet for cronus:
 Pull the updated cronus machine file on other machines (e.g. jupiter)
 ==Network Architecture/Configuration==

Admin: /* Setting Up New Node */

2018-01-22T02:04:55Z

Setting Up New Node

← Older revision		Revision as of 02:04, 22 January 2018
Line 1:		Line 1:
	Procedure for adding a new node (Mac):		Procedure for adding a new node (Mac):

	==Setting Up New Node==		==Setting Up New Mac Node==

	Install:		Install:

Admin: /* Flags */

2018-01-22T00:57:22Z

Flags

← Older revision		Revision as of 00:57, 22 January 2018
Line 110:		Line 110:

	[[Category:Anonymous Browsing]]		[[Category:Anonymous Browsing]]

	~~{{OpenVPNFlag}}~~
	~~{{AnonymousBrowsingFlag}}~~

Admin: /* Network Architecture/Configuration */

2018-01-22T00:56:18Z

Network Architecture/Configuration

← Older revision		Revision as of 00:56, 22 January 2018
Line 98:		Line 98:
	ConnectTo = jupiter		ConnectTo = jupiter
	</pre>		</pre>




			==Flags==

			[[Category:VPN]]
			[[Category:Tinc]]
			[[Category:Networking]]
			[[Category:Linux]]

			[[Category:Anonymous Browsing]]

			{{OpenVPNFlag}}
			{{AnonymousBrowsingFlag}}

Admin at 00:55, 22 January 2018

2018-01-22T00:55:15Z

@@ Line 1: / Line 1: @@
 Procedure for adding a new node (Mac):
 Install:
@@ Line 34: / Line 36: @@
 #!/bin/sh
 ifconfig $INTERFACE down
 </pre>

Admin: Created page with "Procedure for adding a new node (Mac): Install:

 $ brew install tinc

Prep directory structure:

 mkdir -p /usr/local/etc/tinc/master/ cd /usr/local/etc/tin..."

2018-01-22T00:50:20Z

Created page with "Procedure for adding a new node (Mac): Install: <pre> $ brew install tinc </pre> Prep directory structure: <pre> mkdir -p /usr/local/etc/tinc/master/ cd /usr/local/etc/tin..."

New page

Procedure for adding a new node (Mac):

Install:

<pre>
$ brew install tinc
</pre>

Prep directory structure:

<pre>
mkdir -p /usr/local/etc/tinc/master/
cd /usr/local/etc/tinc/master/
</pre>

Edit tinc.conf:

<pre>
$ cat tinc.conf
Name = cronus
AddressFamily = any
Mode = switch
ConnectTo = jupiter
</pre>

Edit tinc-up and tinc-down:

<pre>
$ cat tinc-up
#!/bin/sh
ifconfig $INTERFACE 10.6.0.3 netmask 255.255.0.0

$ cat tinc-down
#!/bin/sh
ifconfig $INTERFACE down
</pre>