tor-webwml.git

1) ## translation metadata

2) # Revision: $Revision$

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)     <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)     <p>You can run a Tor relay on pretty much any operating system. Tor relays
26)     work best on Linux, OS X Tiger or later, FreeBSD 5.x+, NetBSD 5.x+, and
27)     Windows Server 2003 or later.

28)     </p>

29) 

30)     <p>

31)     An easy way to get started is with Vidalia, a graphical interface for
32)     Tor. Vidalia is not included in the standard Tor Browser Bundle, although it

33)     <a href="<page docs/faq>#WhereDidVidaliaGo">once was</a>.

34)     <p>
35) 

36)     <p>The Vidalia Bridge Bundle, the Vidalia Relay Bundle
37)     and the Vidalia Exit Bundle are available on the

38)     <a href="<page download/download>">download

39)     page</a>. These bundles are only available for Windows. They come
40)     preconfigured to run Tor as a bridge, a non-exit relay, or an exit relay.

41)     </p>
42) 
43)     <p>

44)     Vidalia is also available as a standalone package from <a
45)     href="https://people.torproject.org/~erinn/vidalia-standalone-bundles/">this
46)     directory</a>. To use the Vidalia standalone, you will first need to <a

47)     href="<page projects/torbrowser>">download the Tor Browser Bundle</a>
48)     or the <a href="<page download/download>">Tor Expert Bundle</a>.

49)     Unpack the Vidalia package into your Tor Browser folder. This will allow
50)     Vidalia to control and configure the Tor Browser Bundle's Tor client. If
51)     you use the Expert Bundle, which contains Tor only and no browser, you'll

52)     need to inform Vidalia of your Tor's location.

53)     </p>
54) 
55)     <p>

56)     Make sure your Tor works by using Tor as a client (surf with the Tor

57)     Browser, for example). Verify that your clock and timezone are set
58)     correctly. If possible, synchronize your clock with public <a
59)     href="http://en.wikipedia.org/wiki/Network_Time_Protocol">time
60)     servers</a>.</p>
61) 

62)     <hr>

63)     <a id="setup"></a>

64)     <h2><a class="anchor" href="#setup">Configure Tor with the Vidalia Graphical Interface</a></h2>

65)     <br>

66)     <ol type=1>

67) 
68) 

69) <li>Right click on the Vidalia icon in your task bar.  Choose Control Panel.</li><br />
70)     	<img alt="Vidalia right click menu" src="$(IMGROOT)/screenshot-win32-vidalia.png" />

71) 

72)     <li>Click "Setup Relaying".</li>

73) 

74)     <li>

75)     Choose "Relay Traffic for the Tor network" if you
76) want to be a public relay (recommended), or choose "Help
77) censored users reach the Tor network" if you want to be a <a

78) href="<page docs/faq>#RelayOrBridge">non-public bridge</a>.</li><br />
79)     <img alt="Vidalia basic settings" src="$(IMGROOT)/screenshot-win32-configure-relay-1.png" />

80) 

81)     <li>Enter a nickname for your relay, and enter contact information in
82)     case we need to contact you about problems.</li>

83) 

84)     <li>Leave "Attempt to automatically configure port forwarding" ticked.
85)     Push the "Test" button to see if it works. If it does work, great.
86)     If not, see the section on reachability below.</li>

87) 

88)     <li>Choose the "Bandwidth Limits" tab.  Select how much bandwidth you want to provide for Tor users like yourself.</li><br />
89)     <img alt="Vidalia bandwidth limits" src="$(IMGROOT)/screenshot-win32-configure-relay-2.png" />

90) 

91)     <li>Select the "Exit Policies" tab.  If you want to allow others

92)     to use your relay for these services, don't change anything.  Un-check

93)     the services you don't want to allow people to <a href="<page
94)     docs/faq>#ExitPolicies">reach from your relay</a>.  If you want to

95)     be a non-exit relay, un-check all services.</li><br />
96)     <img alt="Vidalia exit policies" src="$(IMGROOT)/screenshot-win32-configure-relay-3.png" />

97) 

98)     <li>Click "Ok".</li>

99) 

100)     </ol>
101) 
102)     <hr>
103)     <a id="torrc"></a>

104)     <h2><a class="anchor" href="#torrc">Configure Tor by editing the torrc file</a></h2>

105)     <br />

106) 

107)     <p>

108)     You can set up a relay without using Vidalia if you wish. Tor's
109)     configuration file is named 'torrc'. In the Tor Browser folder, it's

110)     located at</p>
111)     <pre>Data\Tor\torrc</pre>
112)     <p>Open the file with a text editor and add the following lines:</p>

113) 
114)     <pre>
115)     ORPort 443
116)     Exitpolicy reject *:*

117)     Nickname ididntedittheconfig

118)     ContactInfo human@...
119)     </pre>
120) 

121)     <p>If you want to be a bridge, read about the BridgeRelay and
122)     ServerTransportPlugin values <a

123)     href="<page projects/obfsproxy-instructions>#instructions">on

124)     this page</a>.</p>
125) 

126)     <p>Tor will use all your bandwidth if you don't set limits for it. Some
127)     options are described in <a href="<page docs/faq>#LimitTotalBandwidth">these</a>

128)     <a href="<page docs/faq>#BandwidthShaping">FAQ entries</a>.</p>
129) 

130)     <p>See the <a href="https://gitweb.torproject.org/tor.git/blob/HEAD:/src/config/torrc.sample.in">sample
131)     torrc file</a> and the <a

132)     href="<page docs/tor-manual>">man

133)     page</a> for other Tor options you may want to set.</p>

134) 

135)     <hr>

136)     <a id="check"></a>

137)     <h2><a class="anchor" href="#check">Make sure your relay is reachable</a></h2>

138)     <br>

139) 

140)     <p>If you are using a firewall, open a hole in your firewall
141)     so incoming connections can reach the ports you configured
142)     (ORPort, plus DirPort if you enabled it). If you have a
143)     hardware firewall (Linksys box, cable modem, etc) you might find <a
144)     href="http://portforward.com/">portforward.com</a> useful. Also, make sure you
145)     allow all <em>outgoing</em> connections too, so your relay can reach the
146)     other Tor relays.
147)     </p>
148) 
149)     <p>Restart your relay. If it <a
150)     href="<page docs/faq>#Logs">logs
151)     any warnings</a>, address them.
152)     </p>
153) 

154)     <p>As soon as your relay manages to connect to the network, it will
155)     try to determine whether the ports you configured are reachable from
156)     the outside. This step is usually fast, but may take up to 20

157)     minutes. Look for a <a href="<page docs/faq>#Logs">log entry</a> like

158)     <pre>Self-testing indicates your ORPort is reachable from the outside. Excellent.</pre>

159)     If you don't see this message, it means that your relay is not reachable
160)     from the outside — 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 your relay has decided 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 search <a

167)     href="https://atlas.torproject.org/">Atlas</a> or <a
168)     href="https://globe.torproject.org/">Globe</a> for
169)     the nickname you configured, to make sure it's there. You may need to wait

170)     up to one hour for the directories to publish the new server information.</p>

171) 

172)     <hr>

173)     <a id="after"></a>

174)     <h2><a class="anchor" href="#after">Once your relay is working</a></h2>

175)     <br>

176) 

177)     <p>Subscribe to the <a
178)     href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-announce">tor-announce</a>
179)     mailing list. It is very low volume, and it will keep you informed
180)     of new stable releases.</p>

181) 
182)     <p>As a relay operator, you should consider subscribing to the

183)     <a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays">
184)     tor-relays mailing list</a>. You might find <a

185)     href="<page docs/documentation>#MailingLists">other higher-volume

186)     Tor lists</a> of interest to you as well.

187)     </p>
188) 
189)     <p><a href="https://weather.torproject.org/">Tor Weather</a> provides
190)     an email notification service to any users who want to monitor the
191)     status of a Tor node. Upon subscribing, you can specify what types of
192)     alerts you would like to receive. The main purpose of Tor Weather is
193)     to notify node operators via email if their node is down for longer
194)     than a specified period, but other notification types are available.
195)     </p>
196) 

197)     <p>Read

198)     <a href="<wiki>doc/OperationalSecurity">about operational security</a>

199)     to get ideas how you can increase the security of your relay.

200)     </p>

201) 

202)     <p>

203)     If you control the name servers for your domain, consider setting your

204)     reverse DNS hostname to 'anonymous-relay', 'proxy' or 'tor-proxy', so when
205)     other people see the address in their web logs, they will more quickly
206)     understand what's going on. Adding the <a
207)     href="<gitblob>contrib/tor-exit-notice.html">Tor
208)     exit notice</a> on a vhost for this name can go a long way to deterring abuse
209)     complaints to you and your ISP if you are running an exit node.

210)     </p>

211) 

212)     <p>
213)     When you change your Tor configuration, remember to verify that your

214)     relay still works correctly after the change.
215)     If you have problems or questions, see

216)     the <a href="<page docs/documentation>#Support">Support</a> section or

217)     <a href="<page about/contact>">contact us</a>. Thanks

218)     for helping to make the Tor network grow!
219)     </p>

220) 

221) 

222)     <hr>

223) 

224)     <p>If you have suggestions for improving this document, please <a
225)     href="<page about/contact>">send them to us</a>. Thanks!</p>
226)   </div>
227)   <!-- END MAINCOL -->
228)   <div id = "sidecol">
229) #include "side.wmi"
230) #include "info.wmi"
231)   </div>
232)   <!-- END SIDECOL -->
233) </div>
234) <!-- END CONTENT -->

235) #include <foot.wmi>