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>Alas, since Vidalia (a graphical interface for Tor) is <a
41)     href="<page docs/faq>#WhereDidVidaliaGo">no longer included</a>

42)     in Tor Browser, there are currently no

43)     easy relay packages for Windows and OS X users. One option might be to run

44)     Debian in a VM, or use a different means of getting a Tor binary on

45)     your system (Expert Bundle, Homebrew, Macports). Please help make
46)     this process easier!

47)     </p>
48) 
49)     <hr>
50)     <a id="torrc"></a>

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

52)     <br />

53) 

54)     <p>

55)     Tor's

56)     configuration file is named 'torrc'. In the Tor Browser folder, it's

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

60) 
61)     <pre>
62)     ORPort 443
63)     Exitpolicy reject *:*

64)     Nickname ididntedittheconfig

65)     ContactInfo human@...
66)     </pre>
67) 

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

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

71)     this page</a>.</p>
72) 

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

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

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

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

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

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

81) 

82)     <hr>

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

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

85)     <br>

86) 

87)     <p>If you are using a firewall, open a hole in your firewall
88)     so incoming connections can reach the ports you configured
89)     (ORPort, plus DirPort if you enabled it). If you have a
90)     hardware firewall (Linksys box, cable modem, etc) you might find <a
91)     href="http://portforward.com/">portforward.com</a> useful. Also, make sure you
92)     allow all <em>outgoing</em> connections too, so your relay can reach the
93)     other Tor relays.
94)     </p>
95) 
96)     <p>Restart your relay. If it <a
97)     href="<page docs/faq>#Logs">logs
98)     any warnings</a>, address them.
99)     </p>
100) 

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

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

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

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

110) 

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

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

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

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

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

118) 

119)     <hr>

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

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

122)     <br>

123) 

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

127)     </p>
128) 

129)     <hr>

130) 

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

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

134)   </div>
135)   <!-- END MAINCOL -->
136)   <div id = "sidecol">
137) #include "side.wmi"
138) #include "info.wmi"
139)   </div>
140)   <!-- END SIDECOL -->
141) </div>
142) <!-- END CONTENT -->

143) #include <foot.wmi>