[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-relays] New to Tor Relay, using Rasberry Pi3. Grateful for Help



Good evening, thanks for taking the time to help me.

I am fairly new to Pi, Linux/Raspbian, and TOR.  But I believe in what TOR stands for so I wanted to do something with the Pi I had sitting around.

i have a clean install of Rasbian on my Pi3.
I followed an Instructables guide to get most all of my settings for installing Tor
All my Apt-gets update and upgrades are current.
I am running Tor ver 0.2.9.15  (I need to figure out how to painlessless update that)  Apparantely that is the latest version in the sources file.  

Below is my sources file content:

deb http://raspbian.raspberrypi.org/raspbian/ stretch main contrib non-free rpi
# Uncomment line below then 'apt-get update' to enable 'apt-get source'
deb-src http://raspbian.raspberrypi.org/raspbian/ stretch main contrib non-free rpi
#deb http://deb.torproject.org/torproject.org Rasbian main 

Here is my log file contents:


Oct 25 21:23:04.000 [notice] Tor 0.2.9.15 (git-2dc1a1a2abab5403) opening new log
 file.
Oct 25 21:23:04.579 [notice] Tor 0.2.9.15 (git-2dc1a1a2abab5403) running on Linu
x with Libevent 2.0.21-stable, OpenSSL 1.1.0f and Zlib 1.2.8.
Oct 25 21:23:04.579 [notice] Tor can't help you if you use it wrong! Learn how t
o be safe at https://www.torproject.org/download/download#warning
Oct 25 21:23:04.579 [notice] Read configuration file "/usr/share/tor/tor-service
-defaults-torrc".
Oct 25 21:23:04.579 [notice] Read configuration file "/etc/tor/torrc".
Oct 25 21:23:04.593 [notice] Opening Socks listener on 127.0.0.1:9050
Oct 25 21:23:04.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Oct 25 21:23:05.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Oct 25 21:23:06.000 [notice] Bootstrapped 0%: Starting
Oct 25 21:23:06.000 [notice] Signaled readiness to systemd
Oct 25 21:23:07.000 [notice] Opening Socks listener on /var/run/tor/socks
Oct 25 21:23:07.000 [notice] Opening Control listener on /var/run/tor/control
Oct 25 21:23:07.000 [notice] Bootstrapped 5%: Connecting to directory server
Oct 25 21:23:07.000 [notice] Bootstrapped 10%: Finishing handshake with director
y server
Oct 25 21:23:09.000 [notice] Bootstrapped 15%: Establishing an encrypted directo
ry connection
Oct 25 21:23:09.000 [notice] Bootstrapped 20%: Asking for networkstatus consensu
s
Oct 25 21:23:09.000 [notice] Bootstrapped 25%: Loading networkstatus consensus
Oct 25 21:23:20.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
Oct 25 21:23:20.000 [notice] Bootstrapped 40%: Loading authority key certs
Oct 25 21:23:21.000 [notice] Bootstrapped 45%: Asking for relay descriptors
Oct 25 21:23:21.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/6404, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of exit bw = 0% of path bw.)
Oct 25 21:23:23.000 [notice] Bootstrapped 50%: Loading relay descriptors
Oct 25 21:23:23.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/6404, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of exit bw = 0% of path bw.)
Oct 25 21:23:25.000 [notice] Bootstrapped 56%: Loading relay descriptors
Oct 25 21:23:25.000 [notice] Bootstrapped 65%: Loading relay descriptors
Oct 25 21:23:25.000 [notice] Bootstrapped 71%: Loading relay descriptors
Oct 25 21:23:25.000 [notice] Bootstrapped 78%: Loading relay descriptors
Oct 25 21:23:26.000 [notice] Bootstrapped 80%: Connecting to the Tor network
Oct 25 21:23:26.000 [notice] Bootstrapped 90%: Establishing a Tor circuit
Oct 25 21:23:27.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Oct 25 21:23:27.000 [notice] Bootstrapped 100%: Done
Oct 25 21:58:10.000 [notice] Interrupt: exiting cleanly.
(END)

My torrc file is as follows...sorry there are lots of things commented out...I started with a template and just added a few lines as recommended by the Instructables.

## Configuration file for a typical Tor user
## Last updated 22 September 2015 for Tor 0.2.7.3-alpha.
## (may or may not work for much older or much newer versions of Tor.)
##
## Lines that begin with "## " try to explain what's going on. Lines
## that begin with just "#" are disabled commands: you can enable them
## by removing the "#" symbol.
##
## See 'man tor', or https://www.torproject.org/docs/tor-manual.html,
## for more options you can use in this file.
##
## Tor will look for this file in various places based on your platform:
## https://www.torproject.org/docs/faq#torrc

SocksPort 0
Log notice file /var/log/tor/notices.log
RunAsDaemon 1
ORPORT 9001
DirPort 9030
ExitPolicy reject *.*
Nickname Lebowski1
RelayBandwidthRate 200 KB
RelayBandwidthBurst 400KB


## Tor opens a SOCKS proxy on port 9050 by default -- even if you don't
## configure one below. Set "SOCKSPort 0" if you plan to run Tor only
## as a relay, and not make any local application connections yourself.
#SOCKSPort 9050 # Default: Bind to localhost:9050 for local connections.
#SOCKSPort 192.168.0.1:9100 # Bind to this address:port too.

## Entry policies to allow/deny SOCKS requests based on IP address.
## First entry that matches wins. If no SOCKSPolicy is set, we accept
## all (and only) requests that reach a SOCKSPort. Untrusted users who
## can access your SOCKSPort may be able to learn about the connections
## you make.
#SOCKSPolicy accept 192.168.0.0/16
#SOCKSPolicy accept6 FC00::/7
#SOCKSPolicy reject *

## Logs go to stdout at level "notice" unless redirected by something
## else, like one of the below lines. You can have as many Log lines as
## you want.
##
## We advise using "notice" in most cases, since anything more verbose
## may provide sensitive information to an attacker who obtains the logs.
##
## Send all messages of level 'notice' or higher to /var/log/tor/notices.log
#Log notice file /var/log/tor/notices.log
## Send every possible message to /var/log/tor/debug.log
#Log debug file /var/log/tor/debug.log
## Use the system log instead of Tor's logfiles
#Log notice syslog
## To send all messages to stderr:
#Log debug stderr

## Uncomment this to start the process in the background... or use
## --runasdaemon 1 on the command line. This is ignored on Windows;
## see the FAQ entry if you want Tor to run as an NT service.
#RunAsDaemon 1

## The directory for keeping all the keys/etc. By default, we store
## things in $HOME/.tor on Unix, and in Application Data\tor on Windows.
#DataDirectory /var/lib/tor

## The port on which Tor will listen for local connections from Tor
## controller applications, as documented in control-spec.txt.
#ControlPort 9051
## If you enable the controlport, be sure to enable one of these
## authentication methods, to prevent attackers from accessing it.
#HashedControlPassword 16:872860B76453A77D60CA2BB8C1A7042072093276A3D701AD684053EC4C
#CookieAuthentication 1

############### This section is just for location-hidden services ###

## Once you have configured a hidden service, you can look at the
## contents of the file ".../hidden_service/hostname" for the address
##
## HiddenServicePort x y:z says to redirect requests on port x to the
## address y:z.

#HiddenServiceDir /var/lib/tor/hidden_service/
#HiddenServicePort 80 127.0.0.1:80

#HiddenServiceDir /var/lib/tor/other_hidden_service/
#HiddenServicePort 80 127.0.0.1:80
#HiddenServicePort 22 127.0.0.1:22

################ 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
## If you want to listen on a port other than the one advertised in
## ORPort (e.g. to advertise 443 but bind to 9090), you can do it as
## follows.  You'll need to do ipchains or other port forwarding
## yourself to make this work.
#ORPort 443 NoListen
#ORPort 127.0.0.1:9090 NoAdvertise
## The IP address or full DNS name for incoming connections to your
## relay. Leave commented out and Tor will guess.
#Address noname.example.com

## If you have multiple network interfaces, you can specify one for
## outgoing traffic to use.
# OutboundBindAddress 10.0.0.5

## A handle for your relay, so people don't have to refer to it by key.
## Nicknames must be between 1 and 19 characters inclusive, and must
## contain only the characters [a-zA-Z0-9].
#Nickname ididnteditheconfig

## Define these to limit how much relayed traffic you will allow. Your
## own traffic is still unthrottled. Note that RelayBandwidthRate must
## be at least 75 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)

Plus a bunch of other stuff that is commented out.

Appreciate any help.  And by the way, i did go back and look through the archives over the last several months and didn't find a solution.

Best regards,

Judge





_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays