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 100 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)     The best approach for most users is to <a href="<page
32)     docs/tor-relay-debian>">run your relay on Debian or Ubuntu</a> using
33)     the system Tor package &mdash the deb takes care of running Tor as a
34)     separate user, making sure it has enough file descriptors available,
35)     starting it at boot, and so on. Tor relays also run nicely on other
36)     Linux flavors, and on FreeBSD and NetBSD for those who are comfortable
37)     with those operating systems.
38)     </p>

39) 

40)     <p>Windows users can use the Vidalia Bridge Bundle, the Vidalia Relay
41)     Bundle and the Vidalia Exit Bundle, which come preconfigured to run
42)     Tor as a bridge, a non-exit relay, or an exit relay. Get them from
43)     the <a href="<page download/download>">download page</a>, and use
44)     the graphical instructions below for help setting them up.

45)     </p>
46) 

47)     <p>Alas, since Vidalia (a graphical interface for Tor) is <a
48)     href="<page docs/faq>#WhereDidVidaliaGo">no longer included</a>
49)     in the standard Tor Browser Bundle, there are currently no
50)     easy relay packages for OS X users. One option is to run
51)     Debian in a VM; another option is to install TBB and then a
52)     standalone Vidalia bundle on top of it; and a third option is to <a
53)     href="https://lists.torproject.org/pipermail/tor-relays/2014-June/004650.html">use
54)     Homebrew</a>. Please help make this process easier!

55)     </p>
56) 
57)     <p>

58)     Before you start, verify that your clock and timezone are set

59)     correctly. If possible, synchronize your clock with public <a
60)     href="http://en.wikipedia.org/wiki/Network_Time_Protocol">time

61)     servers</a>.
62)     </p>

63) 

64)     <hr>

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

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

67)     <br>

68)     <ol type=1>

69) 
70) 

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

73) 

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

75) 

76)     <li>

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

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

82) 

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

85) 

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

89) 

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

92) 

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

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

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

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

99) 

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

101) 

102)     </ol>
103) 
104)     <hr>
105)     <a id="torrc"></a>

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

107)     <br />

108) 

109)     <p>

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

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

115) 
116)     <pre>
117)     ORPort 443
118)     Exitpolicy reject *:*

119)     Nickname ididntedittheconfig

120)     ContactInfo human@...
121)     </pre>
122) 

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

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

126)     this page</a>.</p>
127) 

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

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

132)     <p>See the <a href="https://gitweb.torproject.org/tor.git/blob_plain/HEAD:/src/config/torrc.sample.in">sample

133)     torrc file</a> and the <a

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

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

136) 

137)     <hr>

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

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

140)     <br>

141) 

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

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

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

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

161)     If you don't see this message, it means that your relay is not reachable
162)     from the outside — you should re-check your firewalls, check that it's
163)     testing the IP and port you think it should be testing, etc.
164)     </p>

165) 

166)     <p>When your relay has decided that it's reachable, it will upload a "server

167)     descriptor" to the directories, to let clients know

168)     what address, ports, keys, etc your relay is using. You can search <a

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

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

173) 

174)     <hr>

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

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

177)     <br>

178) 

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

183) 
184)     <p>As a relay operator, you should consider subscribing to the

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

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

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

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

199)     <p>Read

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

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

202)     </p>

203) 

204)     <p>

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

206)     reverse DNS hostname to 'anonymous-relay', 'proxy' or 'tor-proxy', so when
207)     other people see the address in their web logs, they will more quickly
208)     understand what's going on. Adding the <a

209)     href="<gitblob>contrib/operator-tools/tor-exit-notice.html">Tor

210)     exit notice</a> on a vhost for this name can go a long way to deterring abuse
211)     complaints to you and your ISP if you are running an exit node.

212)     </p>

213) 

214)     <p>
215)     When you change your Tor configuration, remember to verify that your

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

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

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

220)     for helping to make the Tor network grow!
221)     </p>

222) 

223) 

224)     <hr>

225) 

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

237) #include <foot.wmi>