Please setup a Tor relay


I took the EFF Tor challenge as a kick to setup a Tor relay on one of my servers.

Since the Tor developers do provide more up2date packages than my Debian distribution, I added their repository first:


# add the repository
echo "deb http://deb.torproject.org/torproject.org squeeze main" >> /etc/apt/sources.list
# import the key
gpg --keyserver keys.gnupg.net --recv 886DDD89
gpg --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | apt-key add -
# update
apt-get update
# install package to keep the Tor signing key up2date
apt-get install deb.torproject.org-keyring
# install Tor itself
apt-get install tor


Then a quick edit of the configuration file.
This is mine:


ORPort 9001
Address torrelay.beastiebytes.com
Nickname beastiebytesrelay
RelayBandwidthRate 100 KB  # Throttle traffic to 100KB/s (800Kbps)
RelayBandwidthBurst 200 KB # But allow bursts up to 200KB/s (1600Kbps)
AccountingMax 1 GB
AccountingStart day 00:00
ContactInfo 0x069DD13C Sven Tantau <sven@beastiebytes.com>
ExitPolicy reject *:* # no exits allowed

Make sure that the domain for the 'Address' resolves.
The 'ExitPolicy' line defines that there won't be any connections to the public internet.
btw: There is no need to put anything into ContactInfo. The 0x069DD13C is the ID of my gpg key in case you are wondering..


Last step is to restart the Tor service: 

/etc/init.d/tor restart

Take a look into the logfile at /var/log/tor
It should show you something like this: 

Your Tor server's identity key fingerprint is 'beastiebytesrelay D4B34BD14DCFA9EE95C92D0DCD2875F2B91FF96E'
...
Tor has successfully opened a circuit. Looks like client functionality is working.
...
Now checking whether ORPort 178.63.162.212:9001 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
...
Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
...
Performing bandwidth self-test...done.

After one or two hours, you should be able to find your relay at GLOBE. Just search for the Nickname or the fingerprint of your relay.
Here is mine: Details for beastiebytesrelay.



Do you have a better/nicer way? Does this make sense to you? Something missing? Something wrong?
Let me know via: semi analog pingback












Talk to me


IT-Dienstleistungen Sven Tantau
Drostestrasse 3
53819 Neunkirchen
Germany
 USt-Id-Nr.: DE203610693
web:

email: sven@beastiebytes.com
skype: sven2342
phone: +49 22 47 90 80 250
mobile/signal: +49 157 3131 4424
xing,

OTR-Fingerprint: 7849BD93B65F9E4BC1206B06C09B7445721063BC
GPG/PGP-Key: (pub 4096R/069DD13C 2014-02-13) local copy pgp.mit.edu
GPG/PGP-Key: fingerprint: 9BAD 94D3 9176 5BD1 F64F 542E 37E4 3542 069D D13C