From ec08881f5cd269c237fb83377173fa0b572862a7 Mon Sep 17 00:00:00 2001 From: emma peel Date: Thu, 12 Jul 2018 18:54:44 +0200 Subject: [PATCH] clean html tags from mdwn --- content/operators/operators-1/contents.lr | 48 ++++++++++++++++------- content/operators/operators-7/contents.lr | 1 + 2 files changed, 34 insertions(+), 15 deletions(-) diff --git a/content/operators/operators-1/contents.lr b/content/operators/operators-1/contents.lr index ca34d16e..3aa7ff7c 100644 --- a/content/operators/operators-1/contents.lr +++ b/content/operators/operators-1/contents.lr @@ -5,24 +5,42 @@ title: How do I run a middle or guard relay on Debian? seo_slug: how-do-i-run-a-middle-or-guard-relay --- description: -

For the most in-depth resource on running a relay, see the Tor Relay Guide.

  1. Run "apt-get install tor" (as root).
  2. Make sure your clock, date, and timezone are set correctly. Install the ntp or openntpd (or similar) package to keep it that way.
  3. Edit /etc/tor/torrc to look like the following: -
    ## The IP address or hostname for incoming connections (leave commented and Tor will guess)
-#Address noname.example.com
+For the most in-depth resource on running a relay, see the Tor Relay Guide.
 
-## Set the nickname of this relay
-Nickname ididnteditheconfig
 
-## Set your own contact info
-ContactInfo 0xFFFFFFFF Random Person 
+* Run "apt-get install tor" (as root).
+* Make sure your clock, date, and timezone are set correctly. Install the ntp or openntpd (or similar) package to keep it that way.
+* Edit /etc/tor/torrc to look like the following:
 
-## If you control multiple relays, include then in the family
-#MyFamily $keyid,$keyid,...
 
-ORPort 9001
-DirPort 9030
+    ## The IP address or hostname for incoming connections (leave commented and Tor will guess)
+    #Address noname.example.com
 
-## Set your bandwidth rate (leave commented and Tor will run without bandwidth caps)
-#RelayBandwidthRate 30 MBytes
-#RelayBandwidthBurst 100 MBytes
+    ## Set the nickname of this relay
+    Nickname ididnteditheconfig
 
-ExitPolicy reject *:*
  4. Run "service tor reload" (as root)
  5. After 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 /var/log/syslog such as "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 the IP and ports you specified in your torrc are correct, etc.

When it confirms 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 to see whether your relay has successfully registered in the network. If it hasn't, re-check firewalls, IP and ports again.

+ ## Set your own contact info + ContactInfo 0xFFFFFFFF Random Person + + ## 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 + + ExitPolicy reject *:* +* Run "service tor reload" (as root) +* After 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 /var/log/syslog such as "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 the IP and ports you specified in your torrc are correct, etc. + +When it confirms 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 to see whether your relay has successfully registered in the network. +If it hasn't, re-check firewalls, IP and ports again. diff --git a/content/operators/operators-7/contents.lr b/content/operators/operators-7/contents.lr index 416ade61..cf84fa11 100644 --- a/content/operators/operators-7/contents.lr +++ b/content/operators/operators-7/contents.lr @@ -8,6 +8,7 @@ description: No. If law enforcement becomes interested in traffic from your exit relay, it's possible that officers will seize your computer. For that reason, it's best not to run your exit relay in your home or using your home internet connection. + Instead, consider running your exit relay in a commercial facility that is supportive of Tor. Have a separate IP address for your exit relay, and don't route your own traffic through it. Of course, you should avoid keeping any sensitive or personal information on the computer hosting your exit relay.