[tor-commits] [support-portal/master] Add initial answer for running exits

[colin@xxxxxxxxxxxxxx]

commit 0226b2df5a4443a0b01f57939c284a962c19dbe3
Author: Colin Childs <colin@xxxxxxxxxxxxxx>
Date:   Wed May 17 02:01:38 2017 -0500

    Add initial answer for running exits
---
 plain/operator.txt | 30 ++++++++++++++++++++++++++++++
 1 file changed, 30 insertions(+)

diff --git a/plain/operator.txt b/plain/operator.txt
index 901c778..fb18606 100644
--- a/plain/operator.txt
+++ b/plain/operator.txt
@@ -33,6 +33,36 @@ When it decides that it's reachable, it will upload a "server descriptor" to the
 
 Q. How do I run an exit relay on Debian?
 A.
+1. Review our Exit relay guidelines at https://trac.torproject.org/projects/tor/wiki/doc/TorExitGuidelines
+2. If you're on Debian, start with "apt-get install tor" (as root).
+3. Make sure your clock, date, and timezone are set correctly. Intall the ntp or openntpd (or similar) package to keep it that way.
+4. Edit /etc/torrc to look like the following:
+'''
+## The IP address or hostname for incoming connections (leave commented and Tor will guess)
+#Address noname.example.com
+
+## Set the nickname of this relay
+Nickname ididnteditheconfig
+
+## Set your own contact info
+ContactInfo 0xFFFFFFFF Random Person <nobody AT example dot com>
+
+## If you control multiple relays, include then in the family
+#MyFamily $keyid,$keyid,...
+
+ORPort 9001
+DirPort 9030
+
+## Set your bandwidth rate (leave commented and Tor will run without bandwidth caps)
+#RelayBandwidthRate 30 MBytes
+#RelayBandwidthBurst 100 MBytes
+'''
+5. Run "service tor reload" (as root)
+6. Once your relay connects to the network, it will try to determine whether the ports you configured are reachable from the outside. This step is usually fast, but it may take a few minutes. Look for a log entry in your /var/log/tor/log like Self-testing indicates your ORPort is reachable from the outside. Excellent. If you don't see this message, it means that your relay is not reachable from the outside you should re-check your firewalls, check that it's testing the IP and port you think it should be testing, etc.
+
+When it decides that it's reachable, it will upload a "server descriptor" to the directory authorities, to let clients know what address, ports, keys, etc your relay is using. After a few hours (to give it enough time to propagate), you can query Atlas[https://atlas.torproject.org] to see whether your relay has successfully registered in the network.
+
+7. Consider if you'd like to switch to the [Reduced exit policy] (link to policy page)
 
 Q. How do I run a bridge?
 A.

_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits