[tor-commits] r26882: {website} Add a FAQ entry about outgoing filters for Tor relays (website/trunk/docs/en)

[Lunar]

Author: lunar
Date: 2014-07-22 09:26:34 +0000 (Tue, 22 Jul 2014)
New Revision: 26882

Modified:
   website/trunk/docs/en/faq.wml
Log:
Add a FAQ entry about outgoing filters for Tor relays


Modified: website/trunk/docs/en/faq.wml
===================================================================
--- website/trunk/docs/en/faq.wml	2014-07-22 06:35:49 UTC (rev 26881)
+++ website/trunk/docs/en/faq.wml	2014-07-22 09:26:34 UTC (rev 26882)
@@ -198,6 +198,7 @@
     account?</a></li>
     <li><a href="#WrongIP">My relay is picking the wrong IP address.</a></li>
     <li><a href="#BehindANAT">I'm behind a NAT/Firewall</a></li>
+    <li><a href="#OutgoingFirewall">How should I configure my outgoing filters?</a></li>
     <li><a href="#RelayMemory">Why is my Tor relay using so much memory?
     </a></li>
     <li><a href="#BetterAnonymity">Do I get better anonymity if I run a relay?
@@ -2332,6 +2333,28 @@
 
     <hr>
 
+    <a id="OutgoingFirewall"></a>
+    <h3><a class="anchor" href="#BandwidthShaping">How should I configure
+    my outgoing filters?</a></h3>
+
+    <p>
+    Tor design assumes that any relay can reach every other relays. So
+    all <em>outgoing</em> connections must be allowed.
+    </p>
+    <p>
+    Tor is promoting free network access without interference.
+    Exit nodes must not attempt to filter any traffic coming from the
+    Tor network. Selecting outgoing traffic is likely to forfeit the
+    protections usually given to <em>common carriers</em> in many
+    jurisdictions.
+    </p>
+    <p>
+    Exit nodes which filter traffic will get the <a
+    href="#WhatIsTheBadExitFlag">BadExit</a> flag once detected.
+    </p>
+
+    <hr>
+
     <a id="BandwidthShaping"></a>
     <h3><a class="anchor" href="#BandwidthShaping">What bandwidth shaping
     options are available to Tor relays?</a></h3>