- tor-relays - lists.torproject.org

Improving throughput on weak CPU?
by Jochen 27 Aug '19

27 Aug '19

Hi there, I'm the operator of the following two exit nodes: https://metrics.torproject.org/rs.html#search/family:94C268630BEDCB64E7F888… My CPU is an Intel C2750 (8 cores total), which supports hardware accelerated AES yet a single process still maxes out at only ~150mbit/s. To get the most out of the machine and my single IPv4 address, I simply ran another relay which works fine, and now I'm averaging at around ~315mbit/s. Is there anything else I can tweak to improve throughput without having to order more IP addresses? I'm running Arch with stock 5.2.9 linux kernel. That being said, true multi threading would be much appreciated and would help people like me a lot :-) Regards, Jochen

4 4

AvoidDiskWrites
by [REDACTED] 25 Aug '19

25 Aug '19

Hi Torproject, i think about enabling AvoidDiskWrites 1 on all my relays and not only on my Pi because the prices for the VPS are anyway cheap as f*ck so i think saving the provider a few disk writes is a nice deal. In the manual it is described as: *AvoidDiskWrites* *0*|*1* If non-zero, try to write to disk less frequently than we would otherwise. This is useful when running on flash memory or other media that support only a limited number of writes. (Default: 0) ... which is not a very informative description on how it changes the behavior of Tor. I didnt found any more explanation about it. I would like to understand what Tor is NOT writing to disk anymore if set to 1 or what Tor IS writing to disk if set to 0 and if changing that have any effect for Tor users. As a relay operator i couldnt really see any difference enabled or not. Kind regards

3 2

tor relay ipv6
by armik900＠gmail.com 22 Aug '19

22 Aug '19

hi.in relay stopped working ipv6.address is correct all pings, including tor to the servers, but relay does not work.before that it worked perfectly 2 months.

6 12

Tor Relay - RelayBandwidthRate vs. RelayBandwidthBurst
by petrarca＠protonmail.ch 22 Aug '19

22 Aug '19

I'm struggling a bit with the two config options for RelayBandwidthRate and RelayBandwidthBurst - what I currently have in my torrc config file is: > ... > RelayBandwidthRate 8 Mbit > RelayBandwidthBurst 12 Mbit > ... My assumption was that on average the Relay would consume 8 Mbps max. but over a shorter period of time also up to 12 Mbps in case needed. What I see (historical monitor data at 10 s intervals for the past 6 months) is that the bandwidth usage never exceeds 8 Mbps. I can also see the consumption to be levelled out at 8 Mbps for minutes or hours so it looks like there would be a need for more bandwidth. My question: why can't I see the bandwidth usage going above 8 Mbps and making use of the allowed burst? Btw, I'm typically using the latest stable tor, currently the relay is on 0.4.0.5. Any comment welcome!

2 2

Very high CPU Load and low Traffic since Sunday
by Tim Niemeyer 20 Aug '19

20 Aug '19

Hello I've noticed a reduction in tor traffic about 50% since Sunday. The cpu load stayed almost same. The amount of TCP Sessions increased from ~34k to ~65k. Also the abuse rated about network scans got increased since Sunday. Does anyone knows what's there going on? My guess is that since Sunday anyone uses Tor for extended network scans, which results in a very high packet rate. Personally I've no problem with some network scans, but this is a bit annoying and I asked myself if this is still a scan or more a DOS. https://metrics.torproject.org/rs.html#search/family:719FD0FA327F3CCBCDA0D4… Kind regards Tim

7 7

Emerald Onion's new relays
by Christopher Sheats 20 Aug '19

20 Aug '19

Hello, Beginning this Wednesday, 2019-Apr-03, Emerald Onion will be starting 40 new uncapped and unfiltered exit relays using HardenedBSD in Seattle. We will turn on 10 new relays per day and be monitoring performance. In tandem, we will be publishing our updated edge routing and Tor relay configurations on our Github. We'll also publish an updated transparency report (spoiler: zero new requests). This work is part of our efforts to saturate our new unmetered 10Gbps transit link in the Westin data center. There we peer with the Seattle Internet Exchange with a separate 10Gbps connection. We'll be using our existing IP scopes: 2620:18C::/36 23.129.64.0/24 We are in the process of creating an RPKI ROA for our prefixes, and we are still rebuilding our DNS resolver (thanks nusenu for the feedback). These things will be completed before we turn on the new relays. If you donated to Emerald Onion (a 501(c)(3)) nonprofit), thank you! We'll be naming the relays accordingly. We will still accept new donations for relay naming rights-- email me directly for more information. Lastly, and If you're unaware, I spoke about our work at DEFCON 26: https://www.youtube.com/watch?v=cs6a1i4Owic Cheers, -- Christopher Sheats Executive Director for Emerald Onion Email: yawnbox(a)emeraldonion.org Office (& Signal): +1-206-739-3390 Website: https://emeraldonion.org/

12 20

Tor Activities - CCCamp 2019
by gus 19 Aug '19

19 Aug '19

Dear relay operators, The Chaos Communication Camp is an international, five-day open-air event for hackers and associated life-forms. It provides a relaxed atmosphere for free exchange of technical, social, and political ideas. == Tor Activities == * 2019/08/21 18:00 - Tor Relay Operator Meetup, about:freedom Village If you're a Tor user, operate a Tor relay, want to operate a Tor relay, or simply have questions, come and join us in this session with Q&A about the tor network and Tor Project. * 2019/08/22 12:30 - OONI: Measuring internet censorship around the world, about:freedom Village * 2019/08/22 13:30 - 14:55 - Tor Project: running Tor trainings with human rights defenders in Global South, about:freedom Village * 2019/08/23 14:00 - Updates from the Onion - The Road to Mobile Tor and Improved Censorship Circumvention, Room Curie == During all camp == Visit the Tor Project booth and the OONI booth in the about:freedom Village. https://blog.torproject.org/events/cccamp-germany

1 0

Attack on Tor exit and back-up directory server
by potlatch 19 Aug '19

19 Aug '19

Hello All, I commented and questioned earlier about significant slowing of one of my Finnish exit relays [1] and potential DoS attack. I took the server off line and did the best job I could hardening it. The host does not have DoS protection and uses Xen OpenVZ as his VPS manager. I was getting "nf_contract: table full, dropping packet." errors by the 1000s. That's fixed and I'm back on the Tor net now. One question remains: At any time I look there are 20-150 Iranian IP addresses trying to access the Tor server. Their IP range is from 5.113.x.x to 5.126.x.x. None have hashed fingerprints. Is it okay to let these guys go? Can they harm or slow Tor? Should I ban them? I'd like to learn from this. -potlatch Sent with [ProtonMail](https://protonmail.com) Secure Email.

2 1

removal from the Fallback Directory list
by contact-tor-turing＠g0b.eu 19 Aug '19

19 Aug '19

hello, I managed until now the relay tor-turing - 8456DFA94161CDD99E480C2A2992C366C6564410 - ip 62.210.254.132 for four years and it was in the list of Fallback Directory. However he did not answer for 2 weeks, the support of my hosting provider told me that the motherboard is out of order and data are irrecoverable, so it should remove it from the list of Fallback Directory. thank you.

2 1

Fwd: Emerald Onion's new relays
by teor 19 Aug '19

19 Aug '19

Hi, We didn't clear the moderation queue last week, and this message was dropped from the queue. We'll make sure someone is looking at the queue every 1-3 days in future. T Begin forwarded message: >> On Mon, Aug 12, 2019 at 09:02:58PM +0200, lists(a)for-privacy.net wrote: >>> On 12.08.2019 02:46, Christopher Sheats wrote: >>> >>> It is discouraging to see so many small and large network operators >>> not using IPv6. Why is this such a problem? Tor Project, please >>> increase your #IPv6 awareness/outreach similar to how ARIN and the >>> other RIRs try very hard to do. >>> >> +1 >> >> Twitter :-( Wish you're on Mastodon, too. > > EO's Shawn Webb is on Mastodon: @lattera@bsd.network > > Thanks, > > -- > Shawn Webb > Cofounder / Security Engineer > HardenedBSD > > Tor-ified Signal: +1 443-546-8752 > Tor+XMPP+OTR: lattera(a)is.a.hacker.sx > GPG Key ID: 0xFF2E67A277F8E1FA > GPG Key Fingerprint: D206 BB45 15E0 9C49 0CF9 3633 C85B 0AF8 AB23 0FB2

1 0