Mesh/Exit setup

Revision as of 05:46, 24 December 2013 by Juul (talk | contribs) (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...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

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 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:

This guide builds on top of the 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