- tor-relays - lists.torproject.org

3 questions
by niftybunny 29 Aug '19

29 Aug '19

Hi there, 1. anyone with any new news about the Darknet law in Germany or where you could ask for information? 2. Whats up with Torflow, still linked from Tor Atlas. As far as I can see it was last updated over 3,5 years ago? 3. So what happened to the new measurement? I can see a big spike https://metrics.torproject.org/bandwidth.html <https://metrics.torproject.org/bandwidth.html> and now its back to normal? Same with a lot of my relays, traffic doubled/tripled and now its the same or worse. niftybunny

2 2

Why is my Tor bridge relay not getting any traffic?
by Hikari 29 Aug '19

29 Aug '19

Hello everybody! I used to run a Tor bridge on Windows at home, where I have a 300/150 Mbps ISP. This Windows has memory leak and crashes after some hours, ad I believe that was making my bridge never get traffic. A few weeks ago I moved it to a Ubuntu server, also at home. I use uptimerobot.com to monitor if its port is reachable from outside and healthchecks.io to monitor if traffic entering from its local SOCKS port is reaching check.torproject.org. It's always up and reachable. But nyx reports it's rarely getting any traffic, and its bandwidth never surpasses 1KB/s. Its log heartbeat reports very little download and upload and always claims to has seen 0 unique clients. But how come, if my healthchecks.io monitor's curl call uses it every few minutes? metrics.torproject.org reports correct dates and uptime. Advertised Bandwidth is 58KB/s, way above what nyx reports. Flags are Fast, Running, V2Dir, Valid. What might be wrong? Or is it normal for a Tor bridge relay be this idle? This is my torrc removing identifiable data. |## Configuration file for a typical Tor user ## Last updated 9 October 2013 for Tor 0.2.5.2-alpha. ## (may or may not work for much older or much newer versions of Tor.) ## A handle for your relay, so people don't have to refer to it by key. Nickname MyNick ContactInfo mycontact ## Entry policies to allow/deny SOCKS requests based on IP address. SocksPort 9031 #SocksPort ::9031 #SocksPort 0.0.0.0:80 #SOCKSPolicy accept 192.168.* ## Send all messages of level 'notice' or higher to /var/log/tor/notices.log Log notice file /var/log/tor/notices.log ## Send every possible message to /var/log/tor/debug.log #Log debug file /var/log/tor/debug.log ## Use the system log instead of Tor's logfiles #Log notice syslog ## Uncomment this to start the process in the background... or use RunAsDaemon 1 ## The directory for keeping all the keys/etc. By default, we store ## things in $HOME/.tor on Unix, and in Application Data\tor on Windows. DataDirectory /var/lib/tor ## The port on which Tor will listen for local connections from Tor ## controller applications, as documented in control-spec.txt. ControlPort 9051 ## If you enable the controlport, be sure to enable one of these ## authentication methods, to prevent attackers from accessing it. CookieAuthentication 1 ################ This section is just for relays ##################### # ## See https://www.torproject.org/docs/tor-doc-relay for details. ## The IP address or full DNS name for incoming connections to your ## relay. Leave commented out and Tor will guess. Address hikari.mydomain.com ## Required: what port to advertise for incoming Tor connections. ORPort 80 ## Uncomment this to mirror directory information for others. Please do ## if you have enough bandwidth. DirPort 9030 # what port to advertise for directory connections ServerTransportPlugin obfs3,obfs4 exec /usr/bin/obfs4proxy #ExtORPort 0.0.0.0:8000 ExtORPort 9041 ## Uncomment to return an arbitrary blob of html on your DirPort. Now you ## can explain what Tor is if anybody wonders why your IP address is ## contacting them. See contrib/tor-exit-notice.html in Tor's source ## distribution for a sample. #DirPortFrontPage /etc/tor/tor-exit-notice.html ExitPolicy reject *:* # don't run as an exit node BridgeRelay 1 # bridge PublishServerDescriptor 1 # published on bridge directory DB BridgeRecordUsageByCountry 1 # it's nice to see the country codes of users you are assisting #BandwidthRate 512000 #RelayBandwidthBurst 512000 #RelayBandwidthRate 512000 CellStatistics 1 PaddingStatistics 1 DirReqStatistics 1 EntryStatistics 1 ExitPortStatistics 1 ConnDirectionStatistics 1 HiddenServiceStatistics 1 ExtraInfoStatistics 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) AvoidDiskWrites 0|

6 9

attack on my Finland exit/backup directory [9B31F1F1C1554F9FFB3455911F82E818EF7C7883]
by potlatch 28 Aug '19

28 Aug '19

I still haven't been able to rid myself of the Iranian servers revealed on the NYX connections page. I don't know their purpose but they slow the relay by about 85%. I have dropped them in the iptable input chain, restarted the VPS, but they show up after a day or two in spite. Today there were 121 of them with a large range of IPs. There have been as many as 1400 in a single day. None have identifiable hashed fingerprints. I've enclosed a couple attachments of my input table (partial) and the NYX connection page (also partial). Can anyone enlighten me regarding this situation? I will probably dump the exit relay if I can't fix this intrusion. Thanks people!! -potlatch Sent with [ProtonMail](https://protonmail.com) Secure Email.

2 1

Re: [tor-relays] Why is my Tor bridge relay not getting any traffic?
by Hikari 28 Aug '19

28 Aug '19

Thanks. It's been a few weeks I moved my relay to Ubuntu. I changed my Nickname and ContactInfo when I did that, so my fingerprint is new. Why is it on email bucket? Am I able to move it to bridges.torproject.org? On 27/08/2019 08:14 PM, Philipp Winter wrote: > On Tue, Aug 27, 2019 at 03:03:37PM -0300, Hikari wrote: >> Hello. Here's my fingerprint ------------ > > Your bridge is in the email bucket. It may not be requested as often as > over moat, but give it some time and you'll eventually see users. > > Cheers, > Philipp >

1 0

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 23 Aug '19

23 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 21 Aug '19

21 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