- tor-relays - lists.torproject.org

hourly CPU spike at <hour>:02
by Toralf Förster 17 Mar '18

17 Mar '18

caused by both of the 2 Tor exits here at a Linux server. I do wonder what both processes do exactly 2 minutaes past each hour for about half a minute? -- Toralf PGP C4EACDDE 0076E94E

2 2

new Tor exit
by Arisbe 16 Mar '18

16 Mar '18

Hello all, I rolled out a new Tor exit [0] this morning West Coast U.S. time. It's special to me because I've negotiated the trust of a host company in Albania. I was the first Tor relay in that country and now I'm the first exit relay there. This trust took me a year to establish. I run a number of relays-both exit and non-exit. I run a dozen bridges for people that need the ISP connectivity. I host classes in Southwest Washington State to teach ordinary people how to be safe while they're on the internet. I teach high-school pupils how to set up and operate Tor relays. Here is my problem: The aforementioned relay has been on for nearly 24-hours and not a single user has frequented my doorsteps. I have had seven of the nine authorities parked in this node for most of the time but no inbound connections (except for those referenced and two hackers) and no outbound or exit connections. There is nothing technically wrong with the installation so what gives. I this an issue of administrative paperwork? While I am very supportive of Tor, I am not with unlimited patience. I have a job, wife and kids and money pit house to maintain. Thanks for giving me a bit of advice to make this guy blossom. If I don't understand, I apologize to all. Arisbe [0] 516D1B9E22484202322828D8CAC30325030017E2

4 7

How helpful is it to run your own DNS server?
by torix＠protonmail.com 16 Mar '18

16 Mar '18

Dear All, I have seen mentions on this list of people using pi-hole and unbound DNS servers in their setups, and I wondered if others had considered opinions as to the usefulness of doing this. Pi-hole's biggest feature seems to be their filter lists to block extra/evil DNS queries, while Unbound seems to feature caching and validating functions. I would think that a DNS cache that kept queries for a long time would certainly keep most of your queries out of an ISP's DNS logs. Or are there DNS providers that are relatively immune to their logs being requited by others? TIA, --Torix Sent with [ProtonMail](https://protonmail.com) Secure Email.

3 2

Tor program
by Arisbe 16 Mar '18

16 Mar '18

Hello People, Does anyone have a graphic or verbal discussion about the Tor network that they would share? I want to give a talk at the public library about the uses, advantage and how-to's of Tor. I want to get my facts correct before I commit to this task. Thanks

5 5

"Received http status code 404 ("Consensus is too old")" keeps popping up in my logs
by nottryingtobelame＠protonmail.com 16 Mar '18

16 Mar '18

I'm just wondering if there is anything I can do to resolve this. The relay is running ntpd and consistently keeps the right time, and I'm not getting this from any other server (it's the same IP address every time). Is this of concern or should I just ignore it? Will it hinder the relay's performance when I'm getting this error? Apologies for all the questions; I'm new to the mailing list. Sent with ProtonMail Secure Email.

2 1

DoS statistics from EA4366BCDCA6167B8CFF70E41D8CD1EE9968E445
by robink 16 Mar '18

16 Mar '18

Running tor 0.3.3.3 Mar 15 19:00:44.000 [warn] Tried to establish rendezvous on non-OR circuit with purpose Acting as rendezvous (pending)Mar 15 19:00:48.000 [warn] Tried to establish rendezvous on non-OR circuit with purpose Acting as rendezvous (pending)Mar 15 19:01:17.000 [warn] Tried to establish rendezvous on non-OR circuit with purpose Acting as rendezvous (pending)Mar 15 19:03:01.000 [warn] Tried to establish rendezvous on non-OR circuit with purpose Acting as rendezvous (pending)Mar 15 19:03:52.000 [warn] eventdns: All nameservers have failed Mar 15 19:03:52.000 [notice] eventdns: Nameserver 8.8.4.4:53 is back upMar 15 19:04:01.000 [warn] eventdns: All nameservers have failed Mar 15 19:04:01.000 [notice] eventdns: Nameserver 8.8.8.8:53 is back upMar 15 19:04:08.000 [warn] eventdns: All nameservers have failed Mar 15 19:04:09.000 [notice] eventdns: Nameserver 8.8.8.8:53 is back upMar 15 19:04:10.000 [warn] eventdns: All nameservers have failed Mar 15 19:04:10.000 [notice] eventdns: Nameserver 8.8.4.4:53 is back upMar 15 19:04:16.000 [warn] eventdns: All nameservers have failed Mar 15 19:04:16.000 [notice] eventdns: Nameserver 8.8.8.8:53 is back upMar 15 19:04:35.000 [warn] eventdns: All nameservers have failed Mar 15 19:04:35.000 [notice] eventdns: Nameserver 8.8.8.8:53 is back upMar 15 19:04:49.000 [warn] Tried to establish rendezvous on non-OR circuit with purpose Acting as rendezvous (pending)Mar 15 19:05:16.000 [warn] Tried to establish rendezvous on non-OR circuit with purpose Acting as rendezvous (pending)Mar 15 19:06:05.000 [warn] Tried to establish rendezvous on non-OR circuit with purpose Acting as rendezvous (pending)Mar 15 19:06:11.000 [warn] Tried to establish rendezvous on non-OR circuit with purpose Acting as rendezvous (pending)Mar 15 19:07:06.000 [warn] Tried to establish rendezvous on non-OR circuit with purpose Acting as rendezvous (pending)Mar 15 19:07:34.000 [warn] Tried to establish rendezvous on non-OR circuit with purpose Acting as rendezvous (pending)Mar 15 19:07:47.000 [warn] Tried to establish rendezvous on non-OR circuit with purpose Acting as rendezvous (pending)Mar 15 19:07:56.000 [warn] Tried to establish rendezvous on non-OR circuit with purpose Acting as rendezvous (pending)Mar 15 19:08:04.000 [warn] Tried to establish rendezvous on non-OR circuit with purpose Acting as rendezvous (pending)Mar 15 19:08:12.000 [warn] eventdns: All nameservers have failed Mar 15 19:08:12.000 [notice] eventdns: Nameserver 8.8.4.4:53 is back upMar 15 19:09:05.000 [warn] Tried to establish rendezvous on non-OR circuit with purpose Acting as rendezvous (pending)Mar 15 19:09:15.000 [warn] Tried to establish rendezvous on non-OR circuit with purpose Acting as rendezvous (pending)Mar 15 19:10:21.000 [warn] Tried to establish rendezvous on non-OR circuit with purpose Acting as rendezvous (pending)Mar 15 19:10:59.000 [warn] Tried to establish rendezvous on non-OR circuit with purpose Acting as rendezvous (pending)Mar 15 19:11:16.000 [warn] Tried to establish rendezvous on non-OR circuit with purpose Acting as rendezvous (pending)Mar 15 19:11:42.000 [warn] Tried to establish rendezvous on non-OR circuit with purpose Acting as rendezvous (pending)Mar 15 19:12:31.000 [warn] Tried to establish rendezvous on non-OR circuit with purpose Acting as rendezvous (pending)Mar 15 19:13:03.000 [warn] Tried to establish rendezvous on non-OR circuit with purpose Acting as rendezvous (pending)Mar 15 19:13:24.000 [warn] Tried to establish rendezvous on non-OR circuit with purpose Acting as rendezvous (pending)Mar 15 19:13:30.000 [notice] Heartbeat: Tor's uptime is 5 days 17:59 hours, with 2819 circuits open. I've sent 621.50 GB and received 636.02 GB.Mar 15 19:13:30.000 [notice] Circuit handshake stats since last time: 19393/19393 TAP, 119870/119870 NTor.Mar 15 19:13:30.000 [notice] Since startup, we have initiated 0 v1 connections, 0 v2 connections, 0 v3 connections, and 110064 v4 connections; and received 35 v1 connections, 187 v2 connections, 949 v3 connections, and 621316 v4 connections. Mar 15 19:13:30.000 [notice] DoS mitigation since startup: 0 circuits rejected, 0 marked addresses. 0 connections closed. 64 single hop clients refused.Mar 15 19:13:44.000 [warn] Tried to establish rendezvous on non-OR circuit with purpose Acting as rendezvous (pending)Mar 15 19:14:02.000 [warn] Tried to establish rendezvous on non-OR circuit with purpose Acting as rendezvous (pending)Mar 15 19:14:21.000 [warn] Tried to establish rendezvous on non-OR circuit with purpose Acting as rendezvous (pending)Mar 15 19:15:29.000 [warn] eventdns: All nameservers have failed Mar 15 19:15:30.000 [notice] eventdns: Nameserver 8.8.8.8:53 is back upMar 15 19:15:37.000 [warn] eventdns: All nameservers have failed Mar 15 19:15:37.000 [notice] eventdns: Nameserver 8.8.4.4:53 is back up Best regards, Robin

4 4

middle relay connexions dropped in half
by torix＠protonmail.com 15 Mar '18

15 Mar '18

Dear All, On March 5 I changed to the newest version 3.2.10 on a middle relay I run. I went away for a few days, checked today, and found that my traffic is down, and my connexions, which were around 2,000 since December, are now about 1,000. Consensus weight is still the same (about 450) as it has been before. And my throughput is down from 35G/day, hitting that max most days to about 23-26G/day. Don't know if this is because it is a better Tor and is filtering out extra crap now or not, but just thought I'd mention it, as the Tor version is the only thing that changed.\ --Torix Sent with [ProtonMail](https://protonmail.com) Secure Email.

5 8

ISP Nat
by Paul Templeton 14 Mar '18

14 Mar '18

Hi All, I have an ISP who has started NATting inbound traffic and has screwed DNS resolution. Is there a way to bind DNS requests to use a specific IP address (Have multiple) that is not affected with this NATting problem. Paul 609662E824251C283164243846C035C803940378

3 7

Best tor version
by Даннил Николаев 14 Mar '18

14 Mar '18

What is best to run on relay? Version 0.2 or 0.3?

3 2

Relay node requirements
by sqrrm 13 Mar '18

13 Mar '18

The distributed bitcoin exchange Bisq is reliant on Tor as a communication layer and as such dependent on its stability. To support the network we're looking at incentivizing contributors to run their own Tor relay nodes. For this we need some recommendations on what setup is needed as a minimum to be actually useful for the network. I've run a relay node on a dedicated server which seems to be quite a bit of overkill, preferably it would run on as cheap a vps as possible. I've been checking on metrics.torproject.org on stats for my own node, is that the best way to monitor the nodes? If this doesn't seem worthwhile pursuing, please let me know why and I'll stop. Cheers sqrrm

3 2