Changes between Version 72 and Version 73 of TorRelayGuide


Ignore:
Timestamp:
Dec 18, 2017, 8:49:06 PM (11 months ago)
Author:
alison
Comment:

minor edits

Legend:

Unmodified
Added
Removed
Modified
  • TorRelayGuide

    v72 v73  
    66This guide includes the best practices that are essential for healthy Tor relays. We've included technical steps, legal considerations, and information about running relays with others. It's organized into three parts:
    77
    8 * Part one: Deciding to run a relay [[OperatorsTips#Partone:decidingtorunarelay]]
    9 * Part two: Technical setup [[OperatorsTips#Parttwo:technicalsetup]]
    10 * Part three: Legal info, social info, and more resources [[OperatorsTips#Partthree:legalinfosocialinfoandmoreresources]]
     8* Part one: Deciding to run a relay: [[OperatorsTips#Partone:decidingtorunarelay]]
     9* Part two: Technical setup: [[OperatorsTips#Parttwo:technicalsetup]]
     10* Part three: Legal info, social info, and more resources: [[OperatorsTips#Partthree:legalinfosocialinfoandmoreresources]]
    1111
    1212For the tl;dr version of this guide, read only part two.
     
    3131Guard and middle relays usually do not receive abuse complaints. All relays will be listed in the public list of Tor relays, so may be blocked by certain services that don't understand how Tor works. If you are running a relay from home and have one static IP, you may want to consider running a bridge instead so that your non-Tor traffic doesn't get blocked as though it's coming from Tor. If you have a dynamic IP address or multiple static IPs, this isn't as much of an issue.
    3232
    33 A non-exit Tor relay requires minimal maintenance efforts and bandwidth usage can be highly customized in Tors' configuration (will be covered in more detail later in this guide). The so called "exit policy" of the relay decides if it is a relay allowing clients to exit or not. A non-exit relay does not allow exiting in its exit policy.
     33A non-exit Tor relay requires minimal maintenance efforts and bandwidth usage can be highly customized in the tor configuration (will be covered in more detail later in this guide). The so called "exit policy" of the relay decides if it is a relay allowing clients to exit or not. A non-exit relay does not allow exiting in its exit policy.
    3434
    3535==== Exit relay ====
     
    430430* [Automatic configuration script: ​https://github.com/coldhakca/tor-relay-bootstrap Please add more documentation on this]
    431431* add IPtables rules
     432* add https://trac.torproject.org/projects/tor/wiki/OperatorsTips/DebianUbuntuUpdates
    432433* change 10MBit/s to "recommended" bandwidth and set a "required" bandwidth lower (2Mbit/s?)
    433434* add OS comparison table