tor-relays March 2018

tor-relays@lists.torproject.org

65 participants
63 discussions

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

Relay operators meetup @ CSOA Forte Prenestino, Rome, Italy
by Vasilis 13 Mar '18

13 Mar '18

Dear relay operators and *Tor people, A number of people will participate this Thursday Thursday 15/03/18, 18:30 @ CSOA Forte Prenestino in Rome, Italy [1]. Hope to see many of you there. [1] https://blog.torproject.org/events/relay-operators-meetup-csoa-forte-prenes… Cheers, ~Vasilis -- Fingerprint: 8FD5 CF5F 39FC 03EB B382 7470 5FBF 70B1 D126 0162 Pubkey: https://pgp.mit.edu/pks/lookup?op=get&search=0x5FBF70B1D1260162

1 0

Experimental DoS mitigation is in tor master
by Roger Dingledine 11 Mar '18

11 Mar '18

Hi folks, Thanks for your patience with the relay overload issues. We've merged https://bugs.torproject.org/24902 into tor git master. We'll be putting out an 0.3.3.2-alpha release in not too long for wider testing, and eventually backporting it all the way back to 0.2.9, but if you're the sort who enjoys running code from git, now is a great time to try it and let us know of problems and/or successes. Here's the changelog stanza: o Major features: - Give relays some defenses against the recent network overload. We start with three defenses (default parameters in parentheses). First: if a single client address makes too many connections (>100), hang up on further connections. Second: if a single client address makes circuits too quickly (more than 3 per second, with an allowed burst of 90) while also having too many connections open (3), refuse new create cells for the next while (1-2 hours). Third: if a client asks to establish a rendezvous point to you directly, ignore the request. These defenses can be manually controlled by new torrc options, but relays will also take guidance from consensus parameters, so there's no need to configure anything manually. Implements ticket 24902. To repeat that last part: there are a bunch of torrc options you can use to tweak stuff, but you can leave it all at the defaults and it will read its instructions out of the consensus parameters: https://consensus-health.torproject.org/#consensusparams Woo, --Roger

12 22

2 entries in tor relay search
by peter.zehetner＠liwest.at 11 Mar '18

11 Mar '18

OK, thank you. Then I let it as it is. Peter The "UbuntuCoreNNN" one is "tor-middle-relay" snap. You can remove it if you are managing your own tor. Incidentally, tor-middle-relay snap is being updated right now to v0.3.1.10. You need not do anything. Updates are automatic. On Sat, Mar 10, 2018 at 11:45 PM, <peter.zehetner(a)liwest.at mailto:peter.zehetner@liwest.at > wrote: > > I've installed tor and the relay via ubuntu-software. > > Did you install a Snap package of "tor-middle-relay"? > > > > On Mar 10, 2018 23:38, <peter.zehetner(a)liwest.at mailto:peter.zehetner@liwest.at > wrote: > > > > > > Hello! > > > > Can anybody explain this: > > > > Peter > > > > > > _______________________________________________ > > tor-relays mailing list > > tor-relays(a)lists.torproject.org mailto:tor-relays@lists.torproject.org > > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > > > > > > > > > > _______________________________________________ > tor-relays mailing list > tor-relays(a)lists.torproject.org mailto:tor-relays@lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > > > _______________________________________________ > tor-relays mailing list > tor-relays(a)lists.torproject.org mailto:tor-relays@lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > > -- Chad Miller http://chad.org gpg:a806deac30420066 _______________________________________________ tor-relays mailing list tor-relays(a)lists.torproject.org mailto:tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-relays March 2018