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 250 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 — 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 might be to run
51)     Debian in a VM, or use a different means of getting a Tor binary on
52)     your system (Homebrew, Macports). Please help make this process
53)     easier!

54)     </p>
55) 

56)     <hr>
57)     <a id="setup"></a>
58)     <h2><a class="anchor" href="#setup">Configure Tor with the Vidalia Graphical Interface</a></h2>
59)     <br>
60) 
61)     <p>Please note that this graphical approach is only for
62)     Windows users (and very dedicated OS X users): most fast Tor
63)     relays are run on Debian or Ubuntu using the <a href="<page
64)     docs/tor-relay-debian>">system Tor package</a>, and we encourage
65)     you to go that route too.
66)     </p>
67) 

68)     <p>

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

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

72)     servers</a>.
73)     </p>

74) 
75)     <ol type=1>

76) 
77) 

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

80) 

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

82) 

83)     <li>

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

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

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 "Attempt to automatically configure port forwarding" ticked.
94)     Push the "Test" button to see if it works. If it does work, great.
95)     If not, see the section on reachability below.</li>

96) 

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

99) 

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

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

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

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

106) 

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

108) 

109)     </ol>
110) 
111)     <hr>
112)     <a id="torrc"></a>

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

114)     <br />

115) 

116)     <p>

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

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

122) 
123)     <pre>
124)     ORPort 443
125)     Exitpolicy reject *:*

126)     Nickname ididntedittheconfig

127)     ContactInfo human@...
128)     </pre>
129) 

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

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

133)     this page</a>.</p>
134) 

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

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

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

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

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

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

143) 

144)     <hr>

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

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

147)     <br>

148) 

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

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

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

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

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

172) 

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

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

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

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

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

180) 

181)     <hr>

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

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

184)     <br>

185) 

186)     <p>To learn more about the proper care and feeding for your relay,
187)     see the advice on the <a href=<page docs/tor-relay-debian>#after>Tor
188)     relay on Debian/Ubuntu</a> page.

189)     </p>
190) 

191)     <hr>

192) 

193)     <p>If you have suggestions for improving this document, please <a

194)     href="<page about/contact>">send them to us</a>. Thanks
195)     for helping to make the Tor network grow!</p>

196)   </div>
197)   <!-- END MAINCOL -->
198)   <div id = "sidecol">
199) #include "side.wmi"
200) #include "info.wmi"
201)   </div>
202)   <!-- END SIDECOL -->
203) </div>
204) <!-- END CONTENT -->

205) #include <foot.wmi>