Mesh/Relay setup - Revision history

Jhpoelen at 20:26, 8 February 2018

2018-02-08T20:26:56Z

← Older revision		Revision as of 13:26, 8 February 2018
Line 1:		Line 1:
			This page is outdated and is kept for our communal scrapbook. Please use https://github.com/sudomesh/exitnode for a more up-to-date info.

	Relay nodes are Internet connected hosts that allow mesh nodes to talk to each other using batman-adv over the Internet. Mesh nodes connect to relay nodes using a type of layer 2 tunnel called [http://en.wikipedia.org/wiki/L2TP L2TP]. The software used to establish these tunnels is called [https://github.com/wlanslovenija/tunneldigger tunneldigger] and was developed by [https://dev.wlan-si.net/ wlan slovenija]. A relay node is usually a VPS or a dedicated server with a good amount of available bandwidth and cpu.		Relay nodes are Internet connected hosts that allow mesh nodes to talk to each other using batman-adv over the Internet. Mesh nodes connect to relay nodes using a type of layer 2 tunnel called [http://en.wikipedia.org/wiki/L2TP L2TP]. The software used to establish these tunnels is called [https://github.com/wlanslovenija/tunneldigger tunneldigger] and was developed by [https://dev.wlan-si.net/ wlan slovenija]. A relay node is usually a VPS or a dedicated server with a good amount of available bandwidth and cpu.

Juul: /* batman-adv */

2014-01-11T01:06:24Z

batman-adv

← Older revision		Revision as of 18:06, 10 January 2014
Line 108:		Line 108:
	Set a static IP for the bat0 interface by adding the following to /etc/network/interfaces:		Set a static IP for the bat0 interface by adding the following to /etc/network/interfaces:

	iface bat0 inet static		iface bat0 inet static
	address 10.42.254.254		address 10.42.254.254
	netmask 255.0.0.0		netmask 255.0.0.0

Juul: /* Configure the broker */

2013-12-27T06:14:13Z

Configure the broker

← Older revision		Revision as of 23:14, 26 December 2013
Line 215:		Line 215:

	if [ `cat /sys/class/net/bat0/operstate` != "up" ]; then		if [ `cat /sys/class/net/bat0/operstate` != "up" ]; then
	~~ifup~~ bat0		ifconfig bat0 <relay_mesh_ip> netmask 255.0.0.0 up
	fi		fi
	</pre>		</pre>

			Where <relay_mesh_ip> is your assigned mesh ip address (or 10.42.254.254 for testing).

	Now you're ready to run the broker.		Now you're ready to run the broker.

Juul: /* Configure the broker */

2013-12-24T14:19:29Z

Configure the broker

← Older revision		Revision as of 07:19, 24 December 2013
Line 215:		Line 215:

	if [ `cat /sys/class/net/bat0/operstate` != "up" ]; then		if [ `cat /sys/class/net/bat0/operstate` != "up" ]; then
	~~ifconfig bat0 down &&~~ ifup bat0		ifup bat0
	fi		fi
	</pre>		</pre>

Juul: /* Configure the broker */

2013-12-24T13:53:51Z

Configure the broker

← Older revision		Revision as of 06:53, 24 December 2013
Line 214:		Line 214:
	batctl if add $INTERFACE		batctl if add $INTERFACE

	if [ `cat /sys/class/net/bat0/operstate` != "~~down~~" ]; then		if [ `cat /sys/class/net/bat0/operstate` != "up" ]; then
	ifup bat0		ifconfig bat0 down && ifup bat0
	fi		fi
	</pre>		</pre>

Juul: /* Configure the broker */

2013-12-24T13:47:29Z

Configure the broker

← Older revision		Revision as of 06:47, 24 December 2013
Line 206:		Line 206:
	Edit up_hook.sh to contain the following:		Edit up_hook.sh to contain the following:

	#!/bin/sh		<pre>
			#!/bin/sh
	INTERFACE="$3"
			INTERFACE="$3"
	ifconfig $INTERFACE up
	batctl if add $INTERFACE		ifconfig $INTERFACE up
	ifup bat0		batctl if add $INTERFACE

			if [ `cat /sys/class/net/bat0/operstate` != "down" ]; then
			ifup bat0
			fi
			</pre>

	Now you're ready to run the broker.		Now you're ready to run the broker.

Juul at 12:58, 24 December 2013

2013-12-24T12:58:55Z

@@ Line 3: / Line 3: @@
 L2TP tunnels are unencrypted. They are used primarily because they are layer 2 (so they can be used for batman-adv) and are part of the Linux kernel. They code does not take up much space on the space-limited mesh nodes and does not use much cpu.
-A relay node needs two pieces of software configured:
+Configuring a relay node involves the following steps:
-# B.A.T.M.A.N. Advanced
+# Ensure that you have a compatible operating system
-# Tunneldigger Broker
+# Get a static IP assigned from sudo mesh (or use the test IP)
 = Operating system =
@@ Line 74: / Line 76: @@
 == Other distros ==
-You are on your own, but if you figure out how to get batman-adv and tunneldigger working on a different distro, then please edit this wiki!
+You are on your own, but if you figure out how to get batman-adv and tunneldigger working on a different distro, then please edit this wiki.
 = batman-adv =
@@ Line 91: / Line 105: @@
   sudo aptitude install batctl
 = Tunneldigger broker =
@@ Line 165: / Line 187: @@
 Open l2tp_broker.cfg.
-You will want to change the "address=" line to your public IP address, and "interface=" to your public ethernet interface.
+You will want to change the "address=" line to your public IP address, and "interface=" to your public ethernet interface. E.g:
 == Run the broker ==
@@ Line 177: / Line 226: @@
 == Test the broker ==
-To test the broker you need to install tunneldigger client on a different system. Ensure you have the L2TP modules loaded on your client system.
+To test the broker you need to install batman-adv and tunneldigger client on a different system. Ensure you have the L2TP modules installed and loaded on your client system. And ensure you have the batctl package installed and the batman_adv module loaded.
 Install tunneldigger client requirements on you client system:
@@ Line 212: / Line 261: @@
 This doesn't harm anything, but if you want to fix the behavior, look in traffic_control.py in the reset function.
 == Configure the broker to auto-start ==
@@ Line 229: / Line 313: @@
 Reboot your system and verify that tunneldigger starts correctly.
 = Securing your system =
 Now that you're running a piece of the mesh infrastructure, you may want to ensure that your server stays reasonably secure. We recommend that you set up automatic security updates as described in [[Mesh/Server_security]] this guide.

Juul: /* Configure the broker to auto-start */

2013-12-24T07:37:32Z

Configure the broker to auto-start

← Older revision		Revision as of 00:37, 24 December 2013
Line 214:		Line 214:

	== Configure the broker to auto-start ==		== Configure the broker to auto-start ==

			To configure the broker to start on boot, download the init script and place it in /etc/init.d:

			cd
			wget https://github.com/sudomesh/tunneldigger/raw/master/broker/scripts/tunneldigger-broker.init.d_alt
			sudo mv tunneldigger-broker.init.d_alt /etc/init.d/tunneldigger
			sudo chmod 755 /etc/init.d/tunneldigger

			Edit the script to ensure that the BROKER_DIR is set to the directory where tunneldigger broker resides on your system.

			Now configure the script to start and stop when your system boots up and shuts down:

			sudo update-rc.d tunneldigger defaults

			Reboot your system and verify that tunneldigger starts correctly.

	= Telling the sudo mesh organization about your relay node =		= Telling the sudo mesh organization about your relay node =

Juul at 06:30, 24 December 2013

2013-12-24T06:30:09Z

← Older revision		Revision as of 23:30, 23 December 2013
Line 7:		Line 7:
	# B.A.T.M.A.N. Advanced		# B.A.T.M.A.N. Advanced
	# Tunneldigger Broker		# Tunneldigger Broker


	= Operating system =		= Operating system =

Juul at 06:29, 24 December 2013

2013-12-24T06:29:47Z

← Older revision		Revision as of 23:29, 23 December 2013
Line 215:		Line 215:

	== Configure the broker to auto-start ==		== Configure the broker to auto-start ==

			= Telling the sudo mesh organization about your relay node =

			If you want others to use your relay node, you should contact the sudo mesh group, either at info@sudomesh.org or by showing up to a weekly meeting or hacknight!

			= Securing your system =

			Now that you're running a piece of the mesh infrastructure, you may want to ensure that your server stays reasonably secure. We recommend that you set up automatic security updates as described in [[Mesh/Server_security]] this guide.