streamlined relay instructi...
Roger Dingledine authored 11 years ago
|
1) ## translation metadata
2) # Revision: $Revision$
3) # Translation-Priority: 2-medium
4)
5) #include "head.wmi" TITLE="Tor Project: Relay Configuration Instructions on Debian/Ubuntu" CHARSET="UTF-8"
6) <div id="content" class="clearfix">
7) <div id="breadcrumbs">
8) <a href="<page index>">Home » </a>
9) <a href="<page docs/documentation>">Documentation » </a>
10) <a href="<page docs/tor-doc-relay>">Configure Tor Relay</a>
11) </div>
12) <div id="maincol">
13)
14) <h1>Configuring a Tor relay on Debian/Ubuntu</h1>
15)
16) <hr>
17)
18) <p>
19) The Tor network relies on volunteers to donate bandwidth. The more
20) people who run relays, the faster the Tor network will be. If you have
21) at least 50 kilobytes/s each way, please help out Tor by configuring your
22) Tor to be a relay too.
23) </p>
24)
25) <hr>
26) <a id="zero"></a>
27) <a id="install"></a>
28) <h2><a class="anchor" href="#install">Step One: Download and Install Tor</a></h2>
29) <br>
30)
31) <p>If you're on Debian, you can just "apt-get install tor".</p>
32)
33) <p><b>Do not use the packages in Ubuntu's universe.</b> If you're
34) on Ubuntu or if you want to track newer Tor packages, follow the
35) <a href="<page docs/debian>#ubuntu">Tor on Ubuntu or Debian</a>
36) instructions to use our repository.
37) </p>
38)
|
|
streamlined relay instructi...
Roger Dingledine authored 11 years ago
|
42) <hr>
43) <a id="setup"></a>
44) <h2><a class="anchor" href="#setup">Step Two: Set it up as a relay</a></h2>
45)
46) <p>
47) 1. Make sure your clock, date, and timezone are set correctly. Install
48) the ntp or openntpd (or similar) package to keep it that way.
49) </p>
50)
51) <p>
52) 2. Edit the bottom part of <a href="<page
53) docs/faq>#torrc">/etc/tor/torrc</a>. Define an ORPort. Note
54) that public relays default to being <a href="<page
55) docs/faq>#ExitPolicies">exit relays</a> — either change your
56) ExitPolicy line or read our <a
57) href="https://trac.torproject.org/projects/tor/wiki/doc/TorExitGuidelines">guidelines
58) for exit relay operators</a>. Be sure to set your ContactInfo line
59) so we can contact you if you need to upgrade or something goes wrong.
60) </p>
61)
62) <p>
63) 3. If you are using a firewall, open a hole in your firewall
64) so incoming connections can reach the ports you configured
65) (ORPort, plus DirPort if you enabled it). If you have a
66) hardware firewall (Linksys box, cablemodem, etc) you might like <a
67) href="http://portforward.com/">portforward.com</a>. Also, make sure you
68) allow all <em>outgoing</em> connections too, so your relay can reach the
69) other Tor relays.
70) </p>
71)
72) <p>
73) 4. Restart your relay: "service tor reload" (as root).
74) </p>
75)
76) <hr>
77) <a id="check"></a>
78) <h2><a class="anchor" href="#check">Step Three: Make sure it is working</a></h2>
79) <br>
80)
81) <p>Once your relay connects to the network, it will
82) try to determine whether the ports you configured are reachable from
83) the outside. This step is usually fast, but it may take a few minutes.
84) Look for a <a href="<page docs/faq>#Logs">log entry</a> in your
85) /var/log/tor/log like
86) <tt>Self-testing indicates your ORPort is reachable from the outside. Excellent.</tt>
87) If you don't see this message, it means that your relay is not reachable
88) from the outside — you should re-check your firewalls, check that it's
89) testing the IP and port you think it should be testing, etc.
90) </p>
91)
92) <p>When it decides that it's reachable, it will upload a "server
|
|
remove typos near relay-sea...
Roger Dingledine authored 11 years ago
|
93) descriptor" to the directory authorities, to let clients know
94) what address, ports, keys, etc your relay is using. After a few
95) hours (to give it enough time to propagate), you can <a
|
streamlined relay instructi...