Hi Judge
Am 26.10.2018 um 14:38 schrieb Judd Briggs:
Good evening, thanks for taking the time to help me.
...
Best regards, Judge
But I believe in what TOR stands for so I wanted to do something with the Pi I had sitting around.
Welcome.
The posting is hard to read so I reformated it. It looks like a valid Tor client log. Not a relay.
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 Linux 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 to 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 directory server Oct 25 21:23:09.000 [notice] Bootstrapped 15%: Establishing an encrypted directory connection Oct 25 21:23:09.000 [notice] Bootstrapped 20%: Asking for networkstatus consensus 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.
The torrc shows 'ORPORT' instead of 'ORPort'. I remember some issues with case sensitive torrc entries. Can you try 'ORPort' ?
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
-> ORPort 9001
PS: *Lebowski1* how cool!