81 lines
3.1 KiB
Text
81 lines
3.1 KiB
Text
|
## Stripped down configuration file for a tor relay mode
|
||
|
|
|
||
|
|
DataDirectory /var/lib/tor
|
||
|
|
PidFile /var/run/tor/tor.pid
|
||
|
|
RunAsDaemon 0
|
||
|
|
|
||
|
|
|
||
|
|
################ This section is just for relays #####################
|
||
|
|
#
|
||
|
|
## See https://www.torproject.org/docs/tor-doc-relay for details.
|
||
|
|
|
||
|
|
## Required: what port to advertise for incoming Tor connections.
|
||
|
|
ORPort 9001
|
||
|
|
|
||
|
|
## A handle for your relay, so people don't have to refer to it by key.
|
||
|
|
Nickname xxTOR_NICKxx
|
||
|
|
|
||
|
|
## Define these to limit how much relayed traffic you will allow. Your
|
||
|
|
## own traffic is still unthrottled. Note that RelayBandwidthRate must
|
||
|
|
## be at least 20 kilobytes per second.
|
||
|
|
## Note that units for these config options are bytes (per second), not
|
||
|
|
## bits (per second), and that prefixes are binary prefixes, i.e. 2^10,
|
||
|
|
## 2^20, etc.
|
||
|
|
#RelayBandwidthRate 100 KBytes # Throttle traffic to 100KB/s (800Kbps)
|
||
|
|
#RelayBandwidthBurst 200 KBytes # But allow bursts up to 200KB (1600Kb)
|
||
|
|
|
||
|
|
## Use these to restrict the maximum traffic per day, week, or month.
|
||
|
|
## Note that this threshold applies separately to sent and received bytes,
|
||
|
|
## not to their sum: setting "4 GB" may allow up to 8 GB total before
|
||
|
|
## hibernating.
|
||
|
|
##
|
||
|
|
## Set a maximum of 4 gigabytes each way per period.
|
||
|
|
#AccountingMax 4 GBytes
|
||
|
|
## Each period starts daily at midnight (AccountingMax is per day)
|
||
|
|
#AccountingStart day 00:00
|
||
|
|
## Each period starts on the 3rd of the month at 15:00 (AccountingMax
|
||
|
|
## is per month)
|
||
|
|
#AccountingStart month 3 15:00
|
||
|
|
|
||
|
|
## Administrative contact information for this relay or bridge. This line
|
||
|
|
## can be used to contact you if your relay or bridge is misconfigured or
|
||
|
|
## something else goes wrong. Note that we archive and publish all
|
||
|
|
## descriptors containing these lines and that Google indexes them, so
|
||
|
|
## spammers might also collect them. You may want to obscure the fact that
|
||
|
|
## it's an email address and/or generate a new address for this purpose.
|
||
|
|
#ContactInfo Random Person <nobody AT example dot com>
|
||
|
|
## You might also include your PGP or GPG fingerprint if you have one:
|
||
|
|
ContactInfo xxTOR_CONTACTxx
|
||
|
|
|
||
|
|
## Uncomment this to mirror directory information for others. Please do
|
||
|
|
## if you have enough bandwidth.
|
||
|
|
DirPort 9030
|
||
|
|
|
||
|
|
## Bridge relays (or "bridges") are Tor relays that aren't listed in the
|
||
|
|
## main directory. Since there is no complete public list of them, even an
|
||
|
|
## ISP that filters connections to all the known Tor relays probably
|
||
|
|
## won't be able to block all the bridges. Also, websites won't treat you
|
||
|
|
## differently because they won't know you're running Tor. If you can
|
||
|
|
## be a real relay, please do; but if not, be a bridge!
|
||
|
|
BridgeRelay xxTOR_BRIDGExx
|
||
|
|
## By default, Tor will advertise your bridge to users through various
|
||
|
|
## mechanisms like https://bridges.torproject.org/. If you want to run
|
||
|
|
## a private bridge, for example because you'll give out your bridge
|
||
|
|
## address manually to your friends, uncomment this line:
|
||
|
|
#PublishServerDescriptor 0
|
||
|
|
|
||
|
|
## We are just a relay, so no exits or SOCKS are allowed
|
||
|
|
ExitPolicy reject *:*
|
||
|
|
SocksPort 0
|
||
|
|
|
||
|
|
|
||
|
|
xxTOR_OPTION1xx
|
||
|
|
xxTOR_OPTION2xx
|
||
|
|
xxTOR_OPTION3xx
|
||
|
|
xxTOR_OPTION4xx
|
||
|
|
xxTOR_OPTION5xx
|
||
|
|
xxTOR_OPTION6xx
|
||
|
|
xxTOR_OPTION7xx
|
||
|
|
xxTOR_OPTION8xx
|
||
|
|
xxTOR_OPTION9xx
|