<html><head></head><body><div>Good evening, thanks for taking the time to help me.</div><div><br></div><div>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.</div><div><br></div><div>i have a clean install of Rasbian on my Pi3.</div><div>I followed an Instructables guide to get most all of my settings for installing Tor</div><div>All my Apt-gets update and upgrades are current.</div><div>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. </div><div><br></div><div>Below is my sources file content:</div><div><br></div><div><span><div>deb http://raspbian.raspberrypi.org/raspbian/ stretch main contrib non-free rpi</div><div># Uncomment line below then 'apt-get update' to enable 'apt-get source'</div><div>deb-src http://raspbian.raspberrypi.org/raspbian/ stretch main contrib non-free rpi</div><div>#deb http://deb.torproject.org/torproject.org Rasbian main </div><div><br></div></span></div><div>Here is my log file contents:<br></div><div><br></div><div><span></span><span></span><span><div><br></div><div>Oct 25 21:23:04.000 [notice] Tor 0.2.9.15 (git-2dc1a1a2abab5403) opening new log</div><div> file.</div><div>Oct 25 21:23:04.579 [notice] Tor 0.2.9.15 (git-2dc1a1a2abab5403) running on Linu</div><div>x with Libevent 2.0.21-stable, OpenSSL 1.1.0f and Zlib 1.2.8.</div><div>Oct 25 21:23:04.579 [notice] Tor can't help you if you use it wrong! Learn how t</div><div>o be safe at https://www.torproject.org/download/download#warning</div><div>Oct 25 21:23:04.579 [notice] Read configuration file "/usr/share/tor/tor-service</div><div>-defaults-torrc".</div><div>Oct 25 21:23:04.579 [notice] Read configuration file "/etc/tor/torrc".</div><div>Oct 25 21:23:04.593 [notice] Opening Socks listener on 127.0.0.1:9050</div><div>Oct 25 21:23:04.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.</div><div>Oct 25 21:23:05.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.</div><div>Oct 25 21:23:06.000 [notice] Bootstrapped 0%: Starting</div><div>Oct 25 21:23:06.000 [notice] Signaled readiness to systemd</div><div>Oct 25 21:23:07.000 [notice] Opening Socks listener on /var/run/tor/socks</div><div>Oct 25 21:23:07.000 [notice] Opening Control listener on /var/run/tor/control</div><div>Oct 25 21:23:07.000 [notice] Bootstrapped 5%: Connecting to directory server</div><div>Oct 25 21:23:07.000 [notice] Bootstrapped 10%: Finishing handshake with director</div><div>y server</div><div>Oct 25 21:23:09.000 [notice] Bootstrapped 15%: Establishing an encrypted directo</div><div>ry connection</div><div>Oct 25 21:23:09.000 [notice] Bootstrapped 20%: Asking for networkstatus consensu</div><div>s</div><div><span><div>Oct 25 21:23:09.000 [notice] Bootstrapped 25%: Loading networkstatus consensus</div><div>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.</div><div>Oct 25 21:23:20.000 [notice] Bootstrapped 40%: Loading authority key certs</div><div>Oct 25 21:23:21.000 [notice] Bootstrapped 45%: Asking for relay descriptors</div><div>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.)</div><div>Oct 25 21:23:23.000 [notice] Bootstrapped 50%: Loading relay descriptors</div><div>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.)</div><div>Oct 25 21:23:25.000 [notice] Bootstrapped 56%: Loading relay descriptors</div><div>Oct 25 21:23:25.000 [notice] Bootstrapped 65%: Loading relay descriptors</div><div>Oct 25 21:23:25.000 [notice] Bootstrapped 71%: Loading relay descriptors</div><div>Oct 25 21:23:25.000 [notice] Bootstrapped 78%: Loading relay descriptors</div><div>Oct 25 21:23:26.000 [notice] Bootstrapped 80%: Connecting to the Tor network</div><div>Oct 25 21:23:26.000 [notice] Bootstrapped 90%: Establishing a Tor circuit</div><div>Oct 25 21:23:27.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.</div><div>Oct 25 21:23:27.000 [notice] Bootstrapped 100%: Done</div><div>Oct 25 21:58:10.000 [notice] Interrupt: exiting cleanly.</div><div>(END)</div><div><br></div><div>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.</div><div><br></div><div><span><div>## Configuration file for a typical Tor user</div><div>## Last updated 22 September 2015 for Tor 0.2.7.3-alpha.</div><div>## (may or may not work for much older or much newer versions of Tor.)</div><div>##</div><div>## Lines that begin with "## " try to explain what's going on. Lines</div><div>## that begin with just "#" are disabled commands: you can enable them</div><div>## by removing the "#" symbol.</div><div>##</div><div>## See 'man tor', or https://www.torproject.org/docs/tor-manual.html,</div><div>## for more options you can use in this file.</div><div>##</div><div>## Tor will look for this file in various places based on your platform:</div><div>## https://www.torproject.org/docs/faq#torrc</div><div><br></div><div>SocksPort 0</div><div>Log notice file /var/log/tor/notices.log</div><div>RunAsDaemon 1</div><div>ORPORT 9001</div><div>DirPort 9030</div><div>ExitPolicy reject *.*</div><div>Nickname Lebowski1</div><div>RelayBandwidthRate 200 KB</div><div>RelayBandwidthBurst 400KB</div><div><br></div><div><br></div><div>## Tor opens a SOCKS proxy on port 9050 by default -- even if you don't</div><div>## configure one below. Set "SOCKSPort 0" if you plan to run Tor only</div><div>## as a relay, and not make any local application connections yourself.</div><div>#SOCKSPort 9050 # Default: Bind to localhost:9050 for local connections.</div><div>#SOCKSPort 192.168.0.1:9100 # Bind to this address:port too.</div><div><br></div><div>## Entry policies to allow/deny SOCKS requests based on IP address.</div><div>## First entry that matches wins. If no SOCKSPolicy is set, we accept</div><div>## all (and only) requests that reach a SOCKSPort. Untrusted users who</div><div>## can access your SOCKSPort may be able to learn about the connections</div><div>## you make.</div><div>#SOCKSPolicy accept 192.168.0.0/16</div><div>#SOCKSPolicy accept6 FC00::/7</div><div>#SOCKSPolicy reject *</div><div><br></div></span><span><div>## Logs go to stdout at level "notice" unless redirected by something</div><div>## else, like one of the below lines. You can have as many Log lines as</div><div>## you want.</div><div>##</div><div>## We advise using "notice" in most cases, since anything more verbose</div><div>## may provide sensitive information to an attacker who obtains the logs.</div><div>##</div><div>## Send all messages of level 'notice' or higher to /var/log/tor/notices.log</div><div>#Log notice file /var/log/tor/notices.log</div><div>## Send every possible message to /var/log/tor/debug.log</div><div>#Log debug file /var/log/tor/debug.log</div><div>## Use the system log instead of Tor's logfiles</div><div>#Log notice syslog</div><div>## To send all messages to stderr:</div><div>#Log debug stderr</div><div><br></div><div>## Uncomment this to start the process in the background... or use</div><div>## --runasdaemon 1 on the command line. This is ignored on Windows;</div><div>## see the FAQ entry if you want Tor to run as an NT service.</div><div>#RunAsDaemon 1</div><div><br></div></span><span></span><span></span><span></span><span><div>## The directory for keeping all the keys/etc. By default, we store</div><div>## things in $HOME/.tor on Unix, and in Application Data\tor on Windows.</div><div>#DataDirectory /var/lib/tor</div><div><br></div><div>## The port on which Tor will listen for local connections from Tor</div><div>## controller applications, as documented in control-spec.txt.</div><div>#ControlPort 9051</div><div>## If you enable the controlport, be sure to enable one of these</div><div>## authentication methods, to prevent attackers from accessing it.</div><div>#HashedControlPassword 16:872860B76453A77D60CA2BB8C1A7042072093276A3D701AD684053EC4C</div><div>#CookieAuthentication 1</div><div><br></div><div>############### This section is just for location-hidden services ###</div><div><br></div><div>## Once you have configured a hidden service, you can look at the</div><div>## contents of the file ".../hidden_service/hostname" for the address</div><div>##</div></span><span><div>## HiddenServicePort x y:z says to redirect requests on port x to the</div><div>## address y:z.</div><div><br></div><div>#HiddenServiceDir /var/lib/tor/hidden_service/</div><div>#HiddenServicePort 80 127.0.0.1:80</div><div><br></div><div>#HiddenServiceDir /var/lib/tor/other_hidden_service/</div><div>#HiddenServicePort 80 127.0.0.1:80</div><div>#HiddenServicePort 22 127.0.0.1:22</div><div><br></div><div>################ This section is just for relays #####################</div><div>#</div><div>## See https://www.torproject.org/docs/tor-doc-relay for details.</div><div><br></div><div>## Required: what port to advertise for incoming Tor connections.</div><div>#ORPort 9001</div><div>## If you want to listen on a port other than the one advertised in</div><div>## ORPort (e.g. to advertise 443 but bind to 9090), you can do it as</div><div>## follows. You'll need to do ipchains or other port forwarding</div><div>## yourself to make this work.</div><div>#ORPort 443 NoListen</div><div>#ORPort 127.0.0.1:9090 NoAdvertise</div></span><span><div>## The IP address or full DNS name for incoming connections to your</div><div>## relay. Leave commented out and Tor will guess.</div><div>#Address noname.example.com</div><div><br></div><div>## If you have multiple network interfaces, you can specify one for</div><div>## outgoing traffic to use.</div><div># OutboundBindAddress 10.0.0.5</div><div><br></div><div>## A handle for your relay, so people don't have to refer to it by key.</div><div>## Nicknames must be between 1 and 19 characters inclusive, and must</div><div>## contain only the characters [a-zA-Z0-9].</div><div>#Nickname ididnteditheconfig</div><div><br></div><div>## Define these to limit how much relayed traffic you will allow. Your</div><div>## own traffic is still unthrottled. Note that RelayBandwidthRate must</div><div>## be at least 75 kilobytes per second.</div><div>## Note that units for these config options are bytes (per second), not</div><div>## bits (per second), and that prefixes are binary prefixes, i.e. 2^10,</div><div>## 2^20, etc.</div><div>#RelayBandwidthRate 100 KBytes # Throttle traffic to 100KB/s (800Kbps)</div><div>#RelayBandwidthBurst 200 KBytes # But allow bursts up to 200KB (1600Kb)</div></span><span><div><br></div><div>Plus a bunch of other stuff that is commented out.</div><div><br></div><div>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.</div><div><br></div><div>Best regards,</div><div><br></div><div>Judge</div><div><br></div><div><br></div><div><br></div></span></div><div><br></div><div><br></div></span></div></span></div><div class="ydpf0b3dbyahoo-style-wrap" style="font-family: Helvetica Neue, Helvetica, Arial, sans-serif; font-size: 13px;"></div></body></html>