tor-webwml.git

1) ## translation metadata
2) # Revision: $Revision: 22144 $
3) # Translation-Priority: 2-medium
4) 
5) #include "head.wmi" TITLE="Tor Project: Relay Configuration Instructions" CHARSET="UTF-8"
6) <div id="content" class="clearfix">
7)   <div id="breadcrumbs">

8)     <a href="<page index>">Home &raquo; </a>

9)     <a href="<page docs/documentation>">Documentation &raquo; </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</h1>
15)     
16)     #<!-- BEGIN SIDEBAR -->
17)     #<div class="sidebar-left">
18)     #<h3>Config Steps</h3>
19)     #<ol>
20)     #<li><a href="<page docs/tor-doc-relay>#install">Download &amp; Install</a></li>
21)     #<li><a href="<page docs/tor-doc-relay>#setup">Configuration</a></li>
22)     #<li><a href="<page docs/tor-doc-relay>#check">Check &amp; Confirm</a></li>
23)     #<li><a href="<page docs/tor-doc-relay>#after">Final Steps</a></li>
24)     #</ol>
25)     #</div>
26)     #<!-- END SIDEBAR -->
27)     #
28)     <hr />
29)     
30)     <p>
31)     The Tor network relies on volunteers to donate bandwidth. The more
32)     people who run relays, the faster the Tor network will be. If you have
33)     at least 20 kilobytes/s each way, please help out Tor by configuring your
34)     Tor to be a relay too. We have many features that make Tor relays easy

35)     and convenient, including <a href="<wikifaq>#RelayFlexible">rate limiting

36)     for bandwidth, exit policies so you can limit your exposure to abuse
37)     complaints, and support for dynamic IP addresses</a>.
38)     </p>
39)     

40)     <p>You can run a Tor relay on <a href="<wikifaq>#RelayOS">pretty

41)     much any</a> operating system. Tor relays work best on Linux, OS X Tiger
42)     or later, FreeBSD 5.x+, NetBSD 5.x+, and Windows Server 2003 or later.
43)     </p>
44)     
45)     <hr />
46)     <a id="zero"></a>
47)     <a id="install"></a>
48)     <h2><a class="anchor" href="#install">Step One: Download and Install Tor</a></h2>
49)     <br />
50)     
51)     <p>Before you start, you need to make sure that Tor is up and running.
52)     </p>
53)     
54)     <p>Visit our <a href="<page download/easy-download>">download page</a> and
55)     install the "Installation Bundle" for your OS.
56)     </p>
57)     
58)     <p>If it's convenient, you might also want to use it as a client for a
59)     while to make sure it's actually working.</p>
60)     
61)     <hr />
62)     <a id="setup"></a>
63)     <h2><a class="anchor" href="#setup">Step Two: Set it up as a relay</a></h2>
64)     <br />
65)     <ol>
66)     <li>Verify that your clock and timezone are set
67)     correctly. If possible, synchronize your clock with public <a
68)     href="http://en.wikipedia.org/wiki/Network_Time_Protocol">time
69)     servers</a>.
70)     </li>
71)     
72)     <li><strong>Configuring Tor with the Vidalia Graphical Interface</strong>:
73)     <ol>
74)     
75)     <li>
76)     	<dt>Right click on the Vidalia icon in your task bar.  Choose <tt>Control Panel</tt>.</dt>
77)     	<dd><img alt="vidalia right click menu" src="../img/screenshot-win32-vidalia.png"></dd>
78)     </li>
79)     
80)     <li>Click <tt>Setup Relaying</tt>.</li>
81)     
82)     <li>

83)     	<dt>Choose <tt>Relay Traffic for the Tor network</tt> if you
84) want to be a public relay (recommended), or choose 		<tt>Help
85) censored users reach the Tor network</tt> if you want to be a <a

86) href="<wikifaq>#RelayOrBridge">bridge</a> for users in countries that censor their Internet.</dt>

87)     <dd><img alt="vidalia basic settings" src="../img/screenshot-win32-configure-relay-1.png"></dd>
88)     </li>
89)     
90)     <li>Enter a nickname for your relay, and enter contact information in
91)     case we need to contact you about problems.</li>
92)     
93)     <li>Leave <tt>Attempt to automatically configure port forwarding</tt> clicked.
94)     Push the <tt>Test</tt> button to see if it works.  If it does work, great.
95)     If not, see number 3 below.</li>
96)     
97)     <li><dt>Choose the <tt>Bandwidth Limits</tt> tab.  Select how much bandwidth you want to provide for Tor users like yourself.</dt>
98)     <dd><img alt="vidalia bandwidth limits" src="../img/screenshot-win32-configure-relay-2.png"></dd>
99)     </li> 
100)     
101)     <li><dt>Choose the <tt>Exit Policies</tt> tab.  If you want to allow others
102)     to use your relay for these services, don't change anything.  Un-check

103)     the services you don't want to allow people to <a href="<wikifaq>#ExitPolicies">reach from your relay</a>.  If you want to be a non-exit relay, un-check all services.</dt>

104)     <dd><img alt="vidalia exit policies" src="../img/screenshot-win32-configure-relay-3.png"></dd>
105)     </li>
106)     
107)     <li>Click the <tt>Ok</tt> button.  See Step Three below for confirmation
108)     that the relay is working correctly.</li>
109)     </ol>
110)     
111)     <br />
112)     <strong>Manual Configuration</strong>:
113)     <ul>

114)     <li>Edit the bottom part of <a href="<wikifaq>#torrc">your torrc file</a>. If you want to be a public relay (recommended),
115)     make sure to define ORPort and <a href="<wikifaq>#ExitPolicies">look at ExitPolicy</a>; otherwise
116)     if you want to be a <a href="<wikifaq>#RelayOrBridge">bridge</a>

117)     for users in countries that censor their Internet,
118)     just use <a href="<page docs/bridges>#RunningABridge">these lines</a>.
119)     </li>
120)     
121)     </ul></li>
122)     
123)     <li>If you are using a firewall, open a hole in your firewall
124)     so incoming connections can reach the ports you configured
125)     (ORPort, plus DirPort if you enabled it). If you have a
126)     hardware firewall (Linksys box, cablemodem, etc) you might like <a
127)     href="http://portforward.com/">portforward.com</a>. Also, make sure you
128)     allow all <em>outgoing</em> connections too, so your relay can reach the
129)     other Tor relays.
130)     </li>
131)     
132)     <li>Restart your relay. If it <a

133)     href="<wikifaq>#Logs">logs

134)     any warnings</a>, address them.
135)     </li>
136)     
137)     <li>Subscribe to the <a
138)     href="http://archives.seul.org/or/announce/">or-announce</a>
139)     mailing list. It is very low volume, and it will keep you informed
140)     of new stable releases. You might also consider subscribing to <a
141)     href="<page docs/documentation>#MailingLists">the higher-volume Tor lists</a>
142)     too.
143)     </li>
144)     
145)     </ol>
146)     
147)     <hr />
148)     <a id="check"></a>
149)     <h2><a class="anchor" href="#check">Step Three: Make sure it is working</a></h2>
150)     <br />
151)     
152)     <p>As soon as your relay manages to connect to the network, it will
153)     try to determine whether the ports you configured are reachable from
154)     the outside. This step is usually fast, but may take up to 20
155)     minutes. Look for a

156)     <a href="<wikifaq>#Logs">log

157)     entry</a> like
158)     <tt>Self-testing indicates your ORPort is reachable from the outside. Excellent.</tt>
159)     If you don't see this message, it means that your relay is not reachable
160)     from the outside &mdash; you should re-check your firewalls, check that it's
161)     testing the IP and port you think it should be testing, etc.
162)     </p>
163)     
164)     <p>When it decides that it's reachable, it will upload a "server
165)     descriptor" to the directories, to let clients know
166)     what address, ports, keys, etc your relay is using. You can <a
167)     href="http://194.109.206.212/tor/status-vote/current/consensus">load one of
168)     the network statuses manually</a> and
169)     look through it to find the nickname you configured, to make sure it's
170)     there. You may need to wait up to one hour to give enough time for it to
171)     make a fresh directory.</p>
172)     
173)     <hr />
174)     <a id="after"></a>
175)     <h2><a class="anchor" href="#after">Step Four: Once it is working</a></h2>
176)     <br />
177)     
178)     <p>
179)     We recommend the following steps as well:
180)     </p>
181)     
182)     <p>
183)     6. Read

184)     <a href="<wiki>TheOnionRouter/OperationalSecurity">about operational security</a>

185)     to get ideas how you can increase the security of your relay.
186)     </p>
187)     
188)     <p>
189)     7. If you want to run more than one relay that's great, but please set <a

190)     href="<wikifaq>#MultipleRelays">the

191)     MyFamily option</a> in all your relays' configuration files.
192)     </p>
193)     
194)     <p>
195)     8. Decide about rate limiting. Cable modem, DSL, and other users
196)     who have asymmetric bandwidth (e.g. more down than up) should
197)     rate limit to their slower bandwidth, to avoid congestion. See the <a

198)     href="<wikifaq>#LimitBandwidth">rate

199)     limiting FAQ entry</a> for details.
200)     </p>
201)     
202)     <p>
203)     9. Back up your Tor relay's private key (stored in "keys/secret_id_key"
204)     in your DataDirectory). This is your relay's "identity," and
205)     you need to keep it safe so nobody can read the traffic that goes
206)     through your relay. This is the critical file to keep if you need to <a

207)     href="<wikifaq>#UpgradeRelay">move

208)     or restore your Tor relay</a> if something goes wrong.
209)     </p>
210)     
211)     <p>
212)     
213)     10. If you control the name servers for your domain, consider setting your
214)     reverse DNS hostname to 'anonymous-relay', 'proxy' or 'tor-proxy', so when
215)     other people see the address in their web logs, they will more quickly
216)     understand what's going on. Adding the <a
217)     href="<gitblob>contrib/tor-exit-notice.html">Tor
218)     exit notice</a> on a vhost for this name can go a long way to deterring abuse
219)     complaints to you and your ISP if you are running an exit node.
220)     
221)     </p>
222)     
223)     <p>
224)     11. If your computer isn't running a webserver, please consider
225)     changing your ORPort to 443 and your DirPort to 80. Many Tor
226)     users are stuck behind firewalls that only let them browse the
227)     web, and this change will let them reach your Tor relay. Win32
228)     relays can simply change their ORPort and DirPort directly
229)     in their torrc and restart Tor. OS X or Unix relays can't bind
230)     directly to these ports (since they don't run as root), so they will
231)     need to set up some sort of <a

232)     href="<wikifaq>#ServerForFirewalledClients">

233)     port forwarding</a> so connections can reach their Tor relay. If you are
234)     using ports 80 and 443 already but still want to help out, other useful
235)     ports are 22, 110, and 143.
236)     </p>
237)     
238)     <p>
239)     12. If your Tor relay provides other services on the same IP address
240)     &mdash; such as a public webserver &mdash; make sure that connections to the
241)     webserver are allowed from the local host too. You need to allow these
242)     connections because Tor clients will detect that your Tor relay is the <a

243)     href="<wikifaq>#ExitEavesdroppers">safest

244)     way to reach that webserver</a>, and always build a circuit that ends
245)     at your relay. If you don't want to allow the connections, you must
246)     explicitly reject them in your exit policy.
247)     </p>
248)     
249)     <p>
250)     13. (Unix only). Make a separate user to run the relay. If you
251)     installed the OS X package or the deb or the rpm, this is already
252)     done. Otherwise, you can do it by hand. (The Tor relay doesn't need to
253)     be run as root, so it's good practice to not run it as root. Running
254)     as a 'tor' user avoids issues with identd and other services that
255)     detect user name. If you're the paranoid sort, feel free to <a

256)     href="<wiki>TheOnionRouter/TorInChroot">put Tor