Mesh/Exit setup - Revision history

Jhpoelen at 20:27, 8 February 2018

2018-02-08T20:27:52Z

← Older revision		Revision as of 13:27, 8 February 2018
Line 1:		Line 1:
	An exit node is like a [[Mesh/Relay setup\|relay node]] but with a connection out to the Internet. Exit nodes are run by sudo mesh and have the sudo mesh organization listed as the whois abuse complaint contact. This ensures that legal inquires for Internet-bound traffic from the mesh are sent to sudo mesh so node-operators don't have to deal with e.g. DMCA complaints and other legal issues unless absolutely necessary. We encourage anyone and everyone to run relay nodes, but we do not expect anyone else to run public exit nodes. If you're still interested in running an exit node, come talk to us!		An exit node is like a [[Mesh/Relay setup\|relay node]] but with a connection out to the Internet. Exit nodes are run by sudo mesh and have the sudo mesh organization listed as the whois abuse complaint contact. This ensures that legal inquires for Internet-bound traffic from the mesh are sent to sudo mesh so node-operators don't have to deal with e.g. DMCA complaints and other legal issues unless absolutely necessary. We encourage anyone and everyone to run relay nodes, but we do not expect anyone else to run public exit nodes. If you're still interested in running an exit node, come talk to us!

			This page below is outdated and is kept for our communal scrapbook. Please use https://github.com/sudomesh/exitnode for a more up-to-date info.

			-----

	Exit nodes do everything relay nodes do and adds the following:		Exit nodes do everything relay nodes do and adds the following:

Maxb: /* NATed internet access */

2014-02-02T05:12:47Z

NATed internet access

← Older revision		Revision as of 22:12, 1 February 2014
Line 49:		Line 49:
	chmod 755 /etc/init.d/meshnat		chmod 755 /etc/init.d/meshnat

	Now modify the tunneldigger broker ~~session~~.up hook script to start the meshnat script. Change the section:		Now modify the tunneldigger broker/up_hook.sh hook script to start the meshnat script. Change the section:

	if [ `cat /sys/class/net/bat0/operstate` != "up" ]; then		if [ `cat /sys/class/net/bat0/operstate` != "up" ]; then

Juul: /* NATed internet access */

2013-12-27T06:12:31Z

NATed internet access

← Older revision		Revision as of 23:12, 26 December 2013
Line 21:		Line 21:
	case "$1" in		case "$1" in
	start)		start)
	echo "Starting mesh NAT"		if [ "`iptables -t nat -L\|grep MASQUERADE`" = '' ]; then
	echo 1 > /proc/sys/net/ipv4/ip_forward		echo "Starting mesh NAT"
	iptables -t nat -A POSTROUTING -o $PUBIF -j MASQUERADE		echo 1 > /proc/sys/net/ipv4/ip_forward
	iptables -A FORWARD -i $PUBIF -o $BATIF -m state --state RELATED,ESTABLISHED $		iptables -t nat -A POSTROUTING -o $PUBIF -j MASQUERADE
	iptables -A FORWARD -i $PUBIF -o $BATIF -j DROP		iptables -A FORWARD -i $PUBIF -o $BATIF -m state --state RELATED,ESTABLISHED -j ACCEPT
			iptables -A FORWARD -i $PUBIF -o $BATIF -j DROP
			else
			echo "Mesh NAT already started"
			fi
	;;		;;
	stop)		stop)
Line 38:		Line 42:
	;;		;;
	esac		esac

	</pre>		</pre>

Line 47:		Line 52:

	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

Line 53:		Line 58:

	if [ `cat /sys/class/net/bat0/operstate` != "up" ]; then		if [ `cat /sys/class/net/bat0/operstate` != "up" ]; then
	~~ifup~~ bat0 && /etc/init.d/meshnat start		ifconfig bat0 <exit_mesh_ip> netmask 255.0.0.0 up
			/etc/init.d/meshnat start
	fi		fi

			Where <exit_mesh_ip> is the assigned mesh IP address for your exit node. E.g: 10.42.0.1.

	Now NAT should be set up correctly.		Now NAT should be set up correctly.

Juul at 14:30, 24 December 2013

2013-12-24T14:30:51Z

@@ Line 11: / Line 11: @@
 = NATed internet access =
-  TODO
+Create the script /etc/init.d/meshnat containing the following:
 = Setting up DNS =
@@ Line 21: / Line 66: @@
   sudo aptitude install dnsmasq
-TODO complete this section
+Ensure that you have one or more domain name server IPs in /etc/resolv.conf
 = Fake captive portal =
 TODO write this section

Juul: Created page with "An exit node is like a relay node but with a connection out to the Internet. Exit nodes are run by sudo mesh and have the sudo mesh organization listed as..."

2013-12-24T13:46:19Z

Created page with "An exit node is like a relay node but with a connection out to the Internet. Exit nodes are run by sudo mesh and have the sudo mesh organization listed as..."

New page

An exit node is like a [[Mesh/Relay setup|relay node]] but with a connection out to the Internet. Exit nodes are run by sudo mesh and have the sudo mesh organization listed as the whois abuse complaint contact. This ensures that legal inquires for Internet-bound traffic from the mesh are sent to sudo mesh so node-operators don't have to deal with e.g. DMCA complaints and other legal issues unless absolutely necessary. We encourage anyone and everyone to run relay nodes, but we do not expect anyone else to run public exit nodes. If you're still interested in running an exit node, come talk to us!

Exit nodes do everything relay nodes do and adds the following:

*NATed internet access
*DNS server
*[[Mesh/Firmware/Splash_page|Fake captive portal]]

This guide builds on top of the [[Mesh/Relay setup|relay node guide]], so follow that first and them come back here!

= NATed internet access =

TODO

= Setting up DNS =

First, ensure that tunneldigger broker is not running on port 53 by removing port 53 from the "ports=" entry in /opt/tunneldigger/broker/l2tp_broker.cfg

Now, install dnsmasq:

sudo aptitude install dnsmasq

TODO complete this section

= Fake captive portal =

TODO write this section