- tor-relays - lists.torproject.org

plans to require ContactInfo to be non-empty
by nusenu 11 Feb '19

11 Feb '19

Hi, due to some recent and ongoing events related to a malicious entity running tor relays I'll start to pursue an idea that I had for some time: require non-empty ContactInfo (non-empty does not mean valid email address) This is primarily a non-technical policy discussion which will take place on tor-dev@. If you want to help right away and currently don't make use of the ContactInfo, please set it. If you think such a change would negatively affect you please let me know (off-list is also fine if you prefer). thanks, nusenu -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

9 12

2 ip addresses at the same device, works except for the DirPort
by Toralf Förster 07 Feb '19

07 Feb '19

I ordered a 2nd ip address for my server and put them in the first order in my network configuration. I do wonder, why this adapted torrcconfiguration: $> cat /etc/tor/torrc # torrc at tor-relay # PIDFile /var/run/tor/tor.pid DataDirectory /var/lib/tor/data Nickname zwiebeltoralf OutboundBindAddress 5.9.158.75 DirPort 80 ORPort 443 DirPort [2a01:4f8:190:514a::2]:80 NoAdvertise ORPort [2a01:4f8:190:514a::2]:443 ControlPort 9051 Log warn file /tmp/warn.log #Log notice file /tmp/notice.log #Log info file /tmp/info.log ExitRelay 0 IPv6Exit 0 works at the first glance (about 6,000 connection) but still give after a while in the log: Feb 06 19:59:08.000 [notice] Tor 0.4.0.1-alpha opening log file. Feb 06 20:19:26.000 [warn] Your server (<xx>:80) has not managed to confirm that its DirPort is reachable. Relays do not publish descriptors until their ORPort and DirPort are reachable. Please check your firewalls, ports, address, /etc/hosts file, etc. (where <xx> is the new main ip address at my eth0 device) -- Toralf PGP C4EACDDE 0076E94E

2 2

Tor meetup @ Onionspace, Berlin
by Vasilis 03 Feb '19

03 Feb '19

Dear Tor friends and relay operators, Tomorrow (02.02.2019) a relay operators meetup will take place at Onionspace, Berlin. When: Saturday, February 2nd, 2019 Time: 16:00 / 4:00 PM Where: Gottschedstrasse 4, Entrance 4, 13357 Berlin (U Nauener Platz) Event link: https://blog.torproject.org/events/tor-meetup-berlin Hope to see many of you there! Cheers, ~Vasilis -- Fingerprint: 8FD5 CF5F 39FC 03EB B382 7470 5FBF 70B1 D126 0162 Pubkey: https://pgp.mit.edu/pks/lookup?op=get&search=0x5FBF70B1D1260162

3 2

note to Falback Directory operators: bandwidth wasting bot
by starlight.2018q2＠binnacle.cx 03 Feb '19

03 Feb '19

For the last year a bot of some kind has loaded Fallback Directory relays with excessive directory document requests. Some detail can be found in ticket #27921 at https://trac.torproject.org/projects/tor/ticket/27921. To determine if your relay is affected, look the relay up in https://metrics.torproject.org/rs.html, click the 6-Month history tab, and examine the graph for significantly higher "write bytes per second" relative to "read bytes per second". I find this annoying (since I pay for the wasted bandwidth) and came up with a one-line hack that mitigates the abuse without impairing the usefulness of the DIR service to normal relays and clients. If you compile your daemon from source and are interested contact me directly for the patch.

2 1

Re: [tor-relays] Tor RAM usage (DoS or memory leaks?) - Flood of circuits
by petrarca＠protonmail.ch 03 Feb '19

03 Feb '19

There is something really strange going on indeed. What I noticed is an increase of circuits and my device running out of memory until it stopped working so I had to reboot it on 31. Jan. Then again the memory usage increased until it leveled out at a rather unusual, high usage. The actual bandwidth usage is not unusual though (always around 2Mbps on my relay). Attached a screenshot of my memory usage the last few days (I hope attachments do work here; it's in fact Tor using that memory as could be checked with ps and htop). Heartbeat messages of the log are: Jan 31 10:57:56.000 [notice] Heartbeat: Tor's uptime is 6:00 hours, with 447 circuits open. I've sent 2.66 GB and received 2.65 GB. Jan 31 16:57:56.000 [notice] Heartbeat: Tor's uptime is 12:00 hours, with 19764 circuits open. I've sent 9.59 GB and received 9.54 GB. Jan 31 22:57:56.000 [notice] Heartbeat: Tor's uptime is 18:00 hours, with 54178 circuits open. I've sent 12.36 GB and received 12.30 GB. Feb 01 04:57:56.000 [notice] Heartbeat: Tor's uptime is 23:50 hours, with 79333 circuits open. I've sent 14.89 GB and received 14.81 GB. Feb 01 10:57:56.000 [notice] Heartbeat: Tor's uptime is 1 day 5:50 hours, with 110815 circuits open. I've sent 19.55 GB and received 19.45 GB. Feb 01 16:57:56.000 [notice] Heartbeat: Tor's uptime is 1 day 11:50 hours, with 141724 circuits open. I've sent 24.03 GB and received 23.90 GB. Feb 01 22:57:56.000 [notice] Heartbeat: Tor's uptime is 1 day 17:50 hours, with 12829 circuits open. I've sent 29.96 GB and received 29.75 GB. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Friday, 1. February 2019 23:50, Roman Mamedov <rm(a)romanrm.net> wrote: > Hello, > > There seems to be an issue with Tor's memory usage. > Earlier today, with Tor 3.5.7 and 1.5 GB of RAM running two Tor processes, the > machine got 430 MB into swap, slowing down to a crawl from iowait on accessing > the swapped out memory. Typically 1.5 GB is more than enough for these. "VIRT" > in top was ~1GB each, and "RES" was ~512MB each. Which is weird because that > doesn't add up to exhausting the 1.5 GB, and there are no other heavy > processes on the machine running. I rebooted it without further investigation. > > And right now on another machine running 2.9.16 I see: > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > 22432 debian-+ 30 10 5806816 5.157g 10464 R 39.5 33.1 39464:19 tor > > But not sure if it just accumulated 5.1GB of RAM slowly over time, or shot up > recently. > > Feb 01 17:00:49.000 [notice] Heartbeat: Tor's uptime is 82 days 23:59 hours, > with 70705 circuits open. I've sent 66622.45 GB and received 65906.91 GB. > Feb 01 17:00:49.000 [notice] Circuit handshake stats since last time: > 11361/11361 TAP, 239752/239752 NTor. > Feb 01 17:00:49.000 [notice] Since startup, we have initiated 0 v1 > connections, 0 v2 connections, 10 v3 connections, and 3385644 v4 connections; > and received 14 v1 connections, 78592 v2 connections, 822108 v3 connections, > and 8779474 v4 connections. > Feb 01 17:00:49.000 [notice] DoS mitigation since startup: 2899572 circuits > rejected, 121 marked addresses. 561 connections closed. 21956 single hop clients refused. > Feb 01 17:08:20.000 [warn] connection_edge_process_relay_cell (at origin) > failed. > > --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > With respect, > Roman > > tor-relays mailing list > tor-relays(a)lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

4 3

FOSDEM Relay Operator Meetup
by relaya relaya 02 Feb '19

02 Feb '19

Hello! I read there is a Relay Operator Meetup organized by Colin at. I'm surprised it has not been announced on this list yet. Where and when does it take place exactly? thank you!

2 3

AS: "I.C.S. Trabia-Network S.R.L."
by nusenu 02 Feb '19

02 Feb '19

Hello, if you are the operator of the relays listed bellow, please set MyFamily and contactInfo in your torrc to avoid getting rejected. ornetradar(a)riseup.net: > 2019-02-01 > > | Up | Ext | JoinTime | IP | CC | ORp | Dirp | Version | Contact | Nickname | eFamMembers | FP | > |------+-------+------------+-----------------+------+-------+--------+-----------+---------------------------+--------------+---------------+------------------------------------------| > | 1 | 1 | 13:41:51 | 178.175.132.211 | md | 9001 | 8080 | 0.3.5.7 | chatter | chatter | 1 | E0259C34CEDF2D7A15271336EF65E21171EDF0FE | > | 1 | 1 | 13:44:58 | 178.175.132.210 | md | 9001 | 8080 | 0.3.5.7 | rendon | rendon | 1 | 14678AB26ED87E843B232EAEDF2A7BB384652473 | > | 1 | 1 | 13:44:58 | 178.175.143.158 | md | 9001 | 8080 | 0.3.5.7 | lincoln | lincoln | 1 | 56F55271722E2F8FFC3A77CA3F7F955B703CB027 | > | 1 | 1 | 13:44:59 | 178.175.132.212 | md | 9001 | 8080 | 0.3.5.7 | dossier | dossier | 1 | 1B2E31990B0F0A51920F40D5AB7598D41B214A20 | > | 1 | 1 | 13:44:59 | 178.175.132.213 | md | 9001 | 8080 | 0.3.5.7 | lark | lark | 1 | 1C3EE6E25868F0A8B816B62D81534146F2616008 | > | 1 | 1 | 13:44:59 | 178.175.143.156 | md | 9001 | 8080 | 0.3.5.7 | cuban | cuban | 1 | 1F25B74EF811858112DE18220B456F3CF6EE642E | > | 1 | 1 | 13:44:59 | 178.175.143.157 | md | 9001 | 8080 | 0.3.5.7 | charly | charly | 1 | 3722EEBB445B4E91B1A10CED86CD2E32B3C92D41 | > | 1 | 1 | 13:44:59 | 178.175.132.209 | md | 9001 | 8080 | 0.3.5.7 | matador | matador | 1 | 3E48BE2E2AC257D20546B5547729F4A5096BE39F | > | 1 | 1 | 13:44:59 | 178.175.132.214 | md | 9001 | 8080 | 0.3.5.7 | azorian | azorian | 1 | 72193825EE4EE6F9EF3243D8A7B49DB9122ADF21 | > | 1 | 1 | 13:44:59 | 178.175.143.155 | md | 9001 | 8080 | 0.3.5.7 | contras | contras | 1 | A67EB8AA880ACC94B716E178576142CB25D63B8C | > > https://nusenu.github.io/OrNetRadar/2019/02/01/a1 -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

1 0

Re: [tor-relays] Circuit storms
by starlight.2018q2＠binnacle.cx 02 Feb '19

02 Feb '19

Jan 26 Heartbeat: circuits 6666 sent 103gb received 100gb Jan 26 Heartbeat: circuits 5672 sent 101gb received 98gb Jan 26 Heartbeat: circuits 6156 sent 106gb received 103gb Jan 26 Heartbeat: circuits 5902 sent 92gb received 90gb Jan 27 Heartbeat: circuits 6171 sent 80gb received 78gb Jan 27 Heartbeat: circuits 5920 sent 85gb received 82gb Jan 27 Heartbeat: circuits 4841 sent 82gb received 79gb Jan 27 Heartbeat: circuits 5718 sent 77gb received 71gb Jan 28 Heartbeat: circuits 5676 sent 86gb received 80gb Jan 28 Heartbeat: circuits 5157 sent 84gb received 81gb Jan 28 Heartbeat: circuits 7548 sent 105gb received 102gb Jan 28 Heartbeat: circuits 16448 sent 88gb received 84gb Jan 29 Heartbeat: circuits 31521 sent 107gb received 97gb Jan 29 Heartbeat: circuits 6255 sent 90gb received 86gb Jan 29 Heartbeat: circuits 14920 sent 91gb received 89gb Jan 29 Heartbeat: circuits 21502 sent 75gb received 72gb Jan 30 Heartbeat: circuits 37649 sent 80gb received 76gb Jan 30 Heartbeat: circuits 69831 sent 84gb received 81gb Jan 30 Heartbeat: circuits 16740 sent 102gb received 99gb Jan 30 Heartbeat: circuits 59552 sent 105gb received 101gb Jan 31 Heartbeat: circuits 73727 sent 88gb received 84gb Jan 31 Heartbeat: circuits 12156 sent 74gb received 71gb Jan 31 Heartbeat: circuits 63624 sent 81gb received 79gb Jan 31 Heartbeat: circuits 89129 sent 77gb received 72gb Feb 1 Heartbeat: circuits 98432 sent 105gb received 80gb Feb 1 Heartbeat: circuits 97975 sent 69gb received 66gb Feb 1 Heartbeat: circuits 27443 sent 94gb received 91gb

1 0

Tor RAM usage (DoS or memory leaks?)
by Roman Mamedov 01 Feb '19

01 Feb '19

Hello, There seems to be an issue with Tor's memory usage. Earlier today, with Tor 3.5.7 and 1.5 GB of RAM running two Tor processes, the machine got 430 MB into swap, slowing down to a crawl from iowait on accessing the swapped out memory. Typically 1.5 GB is more than enough for these. "VIRT" in top was ~1GB each, and "RES" was ~512MB each. Which is weird because that doesn't add up to exhausting the 1.5 GB, and there are no other heavy processes on the machine running. I rebooted it without further investigation. And right now on another machine running 2.9.16 I see: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 22432 debian-+ 30 10 5806816 5.157g 10464 R 39.5 33.1 39464:19 tor But not sure if it just accumulated 5.1GB of RAM slowly over time, or shot up recently. Feb 01 17:00:49.000 [notice] Heartbeat: Tor's uptime is 82 days 23:59 hours, with 70705 circuits open. I've sent 66622.45 GB and received 65906.91 GB. Feb 01 17:00:49.000 [notice] Circuit handshake stats since last time: 11361/11361 TAP, 239752/239752 NTor. Feb 01 17:00:49.000 [notice] Since startup, we have initiated 0 v1 connections, 0 v2 connections, 10 v3 connections, and 3385644 v4 connections; and received 14 v1 connections, 78592 v2 connections, 822108 v3 connections, and 8779474 v4 connections. Feb 01 17:00:49.000 [notice] DoS mitigation since startup: 2899572 circuits rejected, 121 marked addresses. 561 connections closed. 21956 single hop clients refused. Feb 01 17:08:20.000 [warn] connection_edge_process_relay_cell (at origin) failed. -- With respect, Roman

1 0

tor relay shutsdown
by Neelix 01 Feb '19

01 Feb '19

Hello, I have setup a tor exit but it seems like that is shutsdown after x hours. I can not find anything in the logs. Anyone knows how this might happen? Regards, Neelix fingerprint: 32A6 5D7A 955C 546C 0E9B F559 EB09 D028 36A3 79E

5 11