add the "why is it easy to be a relay" to the faq
Roger Dingledine commited on 2009-06-24 05:17:10
Zeige 1 geänderte Dateien mit 51 Einfügungen und 0 Löschungen.
- en/faq.wml 704708b35..884b958e8
| ... | ... |
@@ -48,6 +48,7 @@ have a virus or spyware?</a></li> |
| 48 | 48 |
|
| 49 | 49 |
<p>Running a Tor relay:</p> |
| 50 | 50 |
<ul> |
| 51 |
+<li><a href="#RelayFlexible">How stable does my relay need to be?</a></li> |
|
| 51 | 52 |
<li><a href="#WhyNotNamed">Why is my Tor relay not named?</a></li> |
| 52 | 53 |
</ul> |
| 53 | 54 |
|
| ... | ... |
@@ -680,6 +681,56 @@ Please contact us if you know any others. |
| 680 | 681 |
|
| 681 | 682 |
<hr /> |
| 682 | 683 |
|
| 684 |
+<a id="RelayFlexible"></a> |
|
| 685 |
+<h3><a class="anchor" href="#RelayFlexible">How stable does my relay |
|
| 686 |
+need to be?</a></h3> |
|
| 687 |
+ |
|
| 688 |
+<p> |
|
| 689 |
+We aim to make setting up a Tor relay easy and convenient: |
|
| 690 |
+</p> |
|
| 691 |
+ |
|
| 692 |
+<ul> |
|
| 693 |
+<li>Tor has built-in support for <a |
|
| 694 |
+href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#LimitBandwidth"> |
|
| 695 |
+rate |
|
| 696 |
+limiting</a>. Further, if you have a fast link |
|
| 697 |
+but want to limit the number of bytes per day |
|
| 698 |
+(or week or month) that you donate, check out the <a |
|
| 699 |
+href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#Hibernation">hib |
|
| 700 |
+ernation |
|
| 701 |
+feature</a>. |
|
| 702 |
+</li> |
|
| 703 |
+<li>Each Tor relay has an <a |
|
| 704 |
+href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RunARelayBut">ex |
|
| 705 |
+it |
|
| 706 |
+policy</a> that specifies what sort of outbound connections are allowed |
|
| 707 |
+or refused from that relay. If you are uncomfortable allowing people |
|
| 708 |
+to exit from your relay, you can set it up to only allow connections |
|
| 709 |
+to other Tor relays. |
|
| 710 |
+</li> |
|
| 711 |
+<li>It's fine if the relay goes offline sometimes. The directories |
|
| 712 |
+notice this quickly and stop advertising the relay. Just try to make |
|
| 713 |
+sure it's not too often, since connections using the relay when it |
|
| 714 |
+disconnects will break. |
|
| 715 |
+</li> |
|
| 716 |
+<li>We can handle relays with dynamic IPs just fine — simply |
|
| 717 |
+leave the Address config option blank, and Tor will try to guess. |
|
| 718 |
+</li> |
|
| 719 |
+<li>If your relay is behind a NAT and it doesn't know its public |
|
| 720 |
+IP (e.g. it has an IP of 192.168.x.y), you'll need to set up port |
|
| 721 |
+forwarding. Forwarding TCP connections is system dependent but <a |
|
| 722 |
+href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ServerForFirewal |
|
| 723 |
+ledClients">this |
|
| 724 |
+FAQ entry</a> offers some examples on how to do this. |
|
| 725 |
+</li> |
|
| 726 |
+<li>Your relay will passively estimate and advertise its recent |
|
| 727 |
+bandwidth capacity, so high-bandwidth relays will attract more users than |
|
| 728 |
+low-bandwidth ones. Therefore having low-bandwidth relays is useful too. |
|
| 729 |
+</li> |
|
| 730 |
+</ul> |
|
| 731 |
+ |
|
| 732 |
+<hr /> |
|
| 733 |
+ |
|
| 683 | 734 |
<a id="WhyNotNamed"></a> |
| 684 | 735 |
<h3><a class="anchor" href="#WhyNotNamed">Why is my Tor relay not named?</a></h3> |
| 685 | 736 |
|
| 686 | 737 |