Browse code

Add a FAQ entry about outgoing filters for Tor relays

Lunar authored on22/07/2014 11:26:34
Showing1 changed files
... ...
@@ -198,6 +198,7 @@ relay.</a></li>
198 198
     account?</a></li>
199 199
     <li><a href="#WrongIP">My relay is picking the wrong IP address.</a></li>
200 200
     <li><a href="#BehindANAT">I'm behind a NAT/Firewall</a></li>
201
+    <li><a href="#OutgoingFirewall">How should I configure my outgoing filters?</a></li>
201 202
     <li><a href="#RelayMemory">Why is my Tor relay using so much memory?
202 203
     </a></li>
203 204
     <li><a href="#BetterAnonymity">Do I get better anonymity if I run a relay?
... ...
@@ -2332,6 +2333,28 @@ too.
2332 2333
 
2333 2334
     <hr>
2334 2335
 
2336
+    <a id="OutgoingFirewall"></a>
2337
+    <h3><a class="anchor" href="#BandwidthShaping">How should I configure
2338
+    my outgoing filters?</a></h3>
2339
+
2340
+    <p>
2341
+    Tor design assumes that any relay can reach every other relays. So
2342
+    all <em>outgoing</em> connections must be allowed.
2343
+    </p>
2344
+    <p>
2345
+    Tor is promoting free network access without interference.
2346
+    Exit nodes must not attempt to filter any traffic coming from the
2347
+    Tor network. Selecting outgoing traffic is likely to forfeit the
2348
+    protections usually given to <em>common carriers</em> in many
2349
+    jurisdictions.
2350
+    </p>
2351
+    <p>
2352
+    Exit nodes which filter traffic will get the <a
2353
+    href="#WhatIsTheBadExitFlag">BadExit</a> flag once detected.
2354
+    </p>
2355
+
2356
+    <hr>
2357
+
2335 2358
     <a id="BandwidthShaping"></a>
2336 2359
     <h3><a class="anchor" href="#BandwidthShaping">What bandwidth shaping
2337 2360
     options are available to Tor relays?</a></h3>