- tor-relays - lists.torproject.org

Re: [tor-relays] tor-relays Digest, Vol 131, Issue 2
by Ali Druno 06 Dec '21

06 Dec '21

Hi! I've also noticed suddenly 3-5x more bridge users using the one I run with a concrete difference in Russian connections highly increased in number of unique users compared as the others countries which are looking stable. (Sorry for my bad English, I hope it was comprehensible enough) Have a nice week! Nils Le lun. 6 déc. 2021 à 13:00, <tor-relays-request(a)lists.torproject.org> a écrit : > Send tor-relays mailing list submissions to > tor-relays(a)lists.torproject.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > or, via email, send a message with subject or body 'help' to > tor-relays-request(a)lists.torproject.org > > You can reach the person managing the list at > tor-relays-owner(a)lists.torproject.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of tor-relays digest..." > > > Today's Topics: > > 1. Snowflake's package for FreeBSD available (Vin?cius Zavam) > 2. Is Tor Actually "Blocked" In Russia, or Are Some Users > Unblocked for now? (Neel Chauhan) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 5 Dec 2021 19:30:38 +0000 > From: Vin?cius Zavam <egypcio(a)googlemail.com> > To: undisclosed-recipients:; > Subject: [tor-relays] Snowflake's package for FreeBSD available > Message-ID: > < > CA+Kr6DNtCC6-iQ7Et71UyTkqArcB_ruO4CcY8nMUm278BJaeyg(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > ol?! :) > agora temos um pacote para instalar Snowflake em FreeBSD. aproveitem! > > tl;dr; we now have a package to install Snowflake on FreeBSD. enjoy! > > since the 14th of Nov 2021 we have a port that builds a Snowflake package > that can be installed on FreeBSD. it gives us all 3 different > features/functions that we can use Snowflake for: > > - client > - proxy > - server > > don't know Snowflake yet? > > - https://snowflake.torproject.org/ > - https://community.torproject.org/relay/setup/snowflake/ > - > > https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… > > if you are using the "latest" branch of pkg, try it out! the package is > called "snowflake-tor" > > # pkg update -f > # pkg install -U snowflake-tor > > wanna checkout the source of its port? > > - > > https://cgit.freebsd.org/ports/commit/?id=057c0c3c0645c0b237bb2a96dda440e04… > > did you know about the "Run a Bridge" campaign? > > - https://blog.torproject.org/run-a-bridge-campaign/ > > that's it! stay safe and have a great one > obrigado ]=) > > > -- > Vin?cius Zavam > keybase.io/egypcio >

1 0

Snowflake's package for FreeBSD available
by Vinícius Zavam 05 Dec '21

05 Dec '21

olá! :) agora temos um pacote para instalar Snowflake em FreeBSD. aproveitem! tl;dr; we now have a package to install Snowflake on FreeBSD. enjoy! since the 14th of Nov 2021 we have a port that builds a Snowflake package that can be installed on FreeBSD. it gives us all 3 different features/functions that we can use Snowflake for: - client - proxy - server don't know Snowflake yet? - https://snowflake.torproject.org/ - https://community.torproject.org/relay/setup/snowflake/ - https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… if you are using the "latest" branch of pkg, try it out! the package is called "snowflake-tor" # pkg update -f # pkg install -U snowflake-tor wanna checkout the source of its port? - https://cgit.freebsd.org/ports/commit/?id=057c0c3c0645c0b237bb2a96dda440e04… did you know about the "Run a Bridge" campaign? - https://blog.torproject.org/run-a-bridge-campaign/ that's it! stay safe and have a great one obrigado ]=) -- Vinícius Zavam keybase.io/egypcio

1 0

Recent rejection of relays
by Georg Koppen 02 Dec '21

02 Dec '21

Hello everyone! Some of you might have noticed that there is a visible drop of relays on our consensus-health website.[1] The reason for that is that we kicked roughly 600 non-exit relays out of the network yesterday. In fact, only a small fraction of them had the guard flag, so the vast majority were middle-only relays. We don't have any evidence that these relays were doing any attack, but there are attacks possible which relays could perform from the middle position. Therefore, we decided we'd remove those relays for our users' safety sake. While we were already tracking some of the relays for a while, a big chunk of them was also independently reported by a cypherpunk and nusenu helped analyzing the data. Thanks to both of them from our side. Foe what it is worth: a large part of those relays did not set any valid contact info and/or when we tried to contact some of the relays' operators the emails bounced. However, we sometimes need to have ways to reach relay operators, be it for debugging purposes or for helping them with relay misconfiguration. Thus, please set a valid contact info when running relays. Finally, anyone running relays: try to get connected to the community so we can build some trust among each other. That seems to be an essential part in our long-term strategy to fight bad relays trying to enter our network. Georg [1] https://consensus-health.torproject.org/graphs

10 16

Relays running an unsupported (EOL) Tor version
by Georg Koppen 01 Dec '21

01 Dec '21

Hello! Relays running unsupported Tor versions is a problem we have never really dealt with in a systematic way in the way. Some of you might recall that we (with the help of volunteers) tried back in 2019/2020 to get operators, running an unsupported Tor version, to upgrade[1] but then we dropped the ball. Alas. We just started that process again by contacting every relay operator running an outdated Tor version (any version not 0.3.5.x or 0.4.5.x or 0.4.6.x or 0.4.7.x) by email where possible. Additionally, we created a wiki page outlining the current process and things we still need to figure out.[2] On that page we plan to make statistics related to the EOL relay removal available as well, including the final list of relays we'll reject. Thus, stay tuned. Feedback, as always, is very much welcome! We plan to keep this topic on our radar this time while refining the process as we go. Meanwhile, if you are running a relay with an unsupported Tor version, please upgrade for the sake of our users' safety. If you need help, join us on #tor-relays or #tor-relays:matrix.org if you use Element. Thanks, Georg [1] https://blog.torproject.org/removing-end-life-relays-network [2] https://gitlab.torproject.org/tpo/network-health/team/-/wikis/Relay-EOL-pol…

2 4

Rerouting exit relays detected - EXNODE35037
by nusenu 24 Nov '21

24 Nov '21

BadExit: Rerouting exit relays detected (1) The following exit relays are routing their traffic back into the tor network: nickname: EXNODE35037 First seen: 2021-11-22 15:00:00 Consensus weight: 1 AS: ITL LLC OR IP address: 195.123.220.84 Exit addresses: 185.220.101.138 195.123.220.84 https://atlas.torproject.org/#details/E6FBCC437A708ADC396FDE12ACF7E333BEC02… -- https://nusenu.github.io

2 1

Mystery with Exitnode 4273E6D162ED2717A1CF4207A254004CD3F5307B (176.10.99.200)
by Tschador 23 Nov '21

23 Nov '21

Hi, in the last few days I noticed a curiosity with the Exitnode 4273E6D162ED2717A1CF4207A254004CD3F5307B: Every time I call 'https://www.startpage.com', the URL in the Browser changes to 'http://localhost/'. Other browser: same effect. Other sites - no problem. Other Exitnodes - no problem with 'https://www.startpage.com' and other sites. What's going on there …? Regards

2 2

Massive CPU load on high capacity guard node
by failing.flyaway443＠mailer.me 20 Nov '21

20 Nov '21

Hello Everybody, my relay is now almost two weeks old and has the following flags: Fast, Guard, Running, Stable, V2Dir, Valid. I lost the HSDir flag because I had to restart the Tor process, my downtime was just a few seconds, maybe that's why I kept the Guard flag. I was expecting a drop in traffic when I got the Guard flag (as mentioned in the FAQ), but the opposite happened. At the moment there are around 15000 active connections, over 11000 inbound and just 4000 outbound. I looked at the connections in Nyx, and it seems that my relay is indeed used as a Guard node (most of the IPs are "scrubbed" and the outgoing connections are to middle nodes). Before I got the Guard flag, I had around 5000 connections at the same time and was relaying traffic at peaks of 55MB/s. My server is connected to a Gigabit link. It's not a regular VPS, I have a dedicated CPU with two cores and dedicated 8GB RAM. Traffic is unlimited. The problem is that I'm now relaying traffic at ~25MB/s, and whenever there are spikes of over 30MB/s the CPU load on both cores (!) is very high. I'm still moving ~5TB per day, that's a lot, I know. But there would be even more possible with the internet connection of my server. My Server has two dedicated CPU cores of an AMD EPYC 7702, but unfortunately I only get the base frequency of 2GHz inside the VM, not the boost frequency of 3,35GHz (misleading information on the hoster's website). I could relay way more traffic if there wouldn't be this issue with the CPU load. This is the bottleneck, the 1Gbit link is guaranteed. I read in the FAQ that a modern CPU with hardware acceleration is able to relay traffic @~500Mbit in both directions. The EPYC 7702 supports AES-NI. I checked this, it is activated in my VM. I'm running Debian 11 Bullseye and tweaked the networking capabilities with some instructions I found from torservers.net (mnostly sysctl.conf tweaks) There is no additional software installed that uses lots of ressources, just a few tools. Here is a screenshot of Glances during a traffic peak (I set the Tor process to +10 on purpose): https://i.ibb.co/8brmZkf/glances.png The average CPU load is ~1.50, this is still ok for a dual core, but it should stay below 2.0 (at least it should not go above 2.0 for more than a few minutes). Does anyone here have an idea what I could do? Since the load on both cores is pretty high, I don't think it makes much sense to set up a second relay on the same server. Of course I could throttle the traffic, but is there anything else I can do? I rented this rather expensive server to help the Tor network with a really fast Guard node... Thank you everyone for your time and responses! Have a great weekend! Best Regards, Elias

3 3

relayor v21.2.0-rc is released: prometheus exporter support
by nusenu 19 Nov '21

19 Nov '21

Hi, relayor v21.2.0-rc is released. relayor is an ansible role that helps you with running tor relays with minimal effort (automate everything). https://github.com/nusenu/ansible-relayor#main-benefits-for-a-tor-relay-ope… NOTE: This release contains a backwards incompatible change, if you upgrade from an older release please read the upgrade guide before upgrading. https://github.com/nusenu/ansible-relayor/wiki/Upgrade-Guide-from-version-2… This version of relayor uses MetricsPort (when enabled) via TCP on 127.0.0.1. This is less safe then using unix sockets because all processes on the system get access to tor's prometheus metrics since there is no authentication supported. When MetricsPort gets unix socket support, relayor will switch to that safer option. https://gitlab.torproject.org/tpo/core/tor/-/issues/40192 Changes since relayor v21.1.0: * major new features: * add support for tor's prometheus exporter (MetricsPort) * this is a relayor beta feature requiring tor >=0.4.7.2-alpha) #217 * generates prometheus scrape, nginx reverse and htpasswd config files on the control node for easy copy paste into your prometheus/nginx configuration * every tor instance gets an id label (IPv4_ORPort) * support arbitrary torrc options #192 * fix broken debian tag - reported by @jn9999 #224 * fix broken link - PR by @jn9999 #223 * README: * make clear that we do not remove previously managed tor instances on config change - reported by @tsekityam * update OfflineMasterKeys link * make apt update_cache configurable * drop support for Debian 9 * increase min. ansible version 2.9.23 -> 2.9.27 kind regards, nusenu -- https://nusenu.github.io

1 0

Help Censored Users, Run a Tor Bridge
by gus 18 Nov '21

18 Nov '21

Hi everyone, We're launching a campaign to get more obfs4 bridges and help censored Tor users. The campaign will run from November 17 to January 7, 2022. You can read all the details below, including our special reward kits for participants: https://blog.torproject.org/run-a-bridge-campaign/ Join us and help censored users! Gus -- The Tor Project Community Team Lead

1 0

Loss of Stable flag
by Arlen Yaroslav 16 Nov '21

16 Nov '21

Hello to all relay operators! My relay Deepsky (09A70E396DE93F54D4541BBB0EC8E2B23761F34F) has not been receiving the 'Stable' flag from the DA consensus. Up until recently (the past month or so) it had been assigned the full complement of flags. Nothing has been changed on the server and I am not aware of any issues. Would any of the directory authority operators be able to shed light on why some of the DAs are not assigning it the flag? Thanks!

3 3

Compression bomb from dizum
by Logforme 15 Nov '21

15 Nov '21

Got the following in my log today: Nov 06 18:19:01.000 [warn] Possible compression bomb; abandoning stream. Nov 06 18:19:01.000 [warn] Unable to decompress HTTP body (tried Zstandard compressed, on Directory connection (client reading) with 45.66.33.45:80). 45.66.33.45 is tor.dizum.com, a Tor directory authority. False positive or a problem generating directory info at dizum?

3 2

Questions about my tor node
by Bobby 15 Nov '21

15 Nov '21

Hello I'm running a tor node and I paid for a VPS for the express purposes of running that node. I have configured it to use almost all of the bandwidth of the VPS and then to allow bursts to use all of the bandwidth I have also set it to serve directory requests. The server also has 1GB of ram and 1 CPU core. Is this good enough to be helpful in the tor network?

4 3

Re: [tor-relays] Hardware requirements for a fast Tor relay
by failing.flyaway443＠mailer.me 13 Nov '21

13 Nov '21

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 >Since this is virtualization, make sure that features such as AES >acceleration are active. Yes, I have tested that. Is active. >The number of cores is not really relevant since Tor is not >multi-threaded. The EPYC 7702 can boost up to 3.35 GHz, check that it >reaches that under load. It actually reaches the frequency under load. Unfortunately, the one core is now fully under load. My Relay moved 5TB today, with an average bandwidth of 500Mbit. The average load according to HTOP is now just over 1.0, which is fine for a dual core. However, one core is loaded to 100%. So far, there are no error messages and I achieve a stable 40MB/s with peaks of up to 50MB/s. But my Relay is only a few days old. Advertised Bandwith is currently at just over 30 MiB, but that will change soon. I'm afraid the CPU won't do much more, but with 500Mbit/s I'm among the fastest Relays at this hoster. Directly on page 1. Let's see if I can tune a bit, otherwise I'll just let it run as long as no errors appear. >Also since you have 2 cores, you can run two instances of Tor. Yes, I know. However, the DirAuths then have more work to do because they have to add another Relay to the Consensus. Everything has advantages and disadvantages. Let's see what I do. >> I chose this server because the bandwith is unmetered and it's a >> guaranteed 1GHz link. >I assume you mean 1 Gbit/s. Yes, that was a typo. By the way, can someone explain to me how to reply directly to a reply in a thread without my reply just appearing at the bottom? I'm new to this list and haven't quite figured it out yet. I hope you understand what I mean - I want my replies to be indented correctly. Thanks! Have a great weekend, everyone! -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEElcZnZFMJSyKcTts0q6Mz3/Qy4d0FAmGO/j0ACgkQq6Mz3/Qy 4d395A/+NDRe7IhCbsmgWCUM2Li1XnoN4g3Z091T+U1QPQg7kCvibXXeiHhgs/jP und/63N7FM3OmHi/WUPerK4qfk5lssRU0OPvyAApIzruCTBDj2TuCdpagsfNRQCU QFE162q/cUvwRDyoNHVXxhSk8Bvtwj6Mxw4oE5p6yJFvBgSjT7uHGZgAgHobs/QH zgCKsoEI3H0Wj8kYtxfP9xlhDe1XNidaGIXe5axFlcraw2/f7LXhG7BPJ2XaQHsp CCPFOoLt3Ggpl3AFyIT/UYJ+2e/y+RJXSy71ptew0Xl3MQXv8j5avpo1zmDFXYqV 4SYbjzqmn/5t/O5QPprTBDVr2+SgkjNoFJWFTFK5R7jjqqGvs9fzbAXV6XGOKBeC F6aRs/caQiJ57gAJmYdUW9dQubeIulR0yUlQlwXWWdAPEduLP3B8MxDtEuFOYHWL h+C3I1tlPp+DFE3hfPARW1hX8DGBtA8pH6MKwn6onJh65mWv6f7pmU8LQHbuPPmw w7o7qZHuXxhFSoxPRklISr0BjcLG94DHGWlD2UMyxpU/m3745+JGHhqlTJX+/aeN HHWJ9FN1beI4YHfeUHBgicEx8pywtHK/l6vi5v9rrzko7nbYwG4SayrsgrpXqz6F ifqCNzouxpjVs7MvuTDPIC62mNLED7Zop3tsMwdnyRZJc8Lm3Uo= =Gm4l -----END PGP SIGNATURE-----

1 0

Question about IPv6
by xplato 12 Nov '21

12 Nov '21

Greetings, I have three relays running Hardened BSD hosted at Frantech. They do not offer support for setting up IPv6. I am not sure how to accomplish this and wondered if anyone would have insight into setting this up? I have not found much in the way of instruction. A resource that provides instructions would be much appreciated. Kindly, Dan Sent with [ProtonMail](https://protonmail.com) Secure Email.

4 3

Re: [tor-relays] Tor website
by failing.flyaway443＠mailer.me 12 Nov '21

12 Nov '21

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi potlatch, is this what you are looking for? https://gitweb.torproject.org/tor.git/tree/src/config/torrc.sample.in https://2019.www.torproject.org/docs/tor-manual.html.en Both links can be found at the bottom of this site: https://support.torproject.org/tbb/tbb-editing-torrc/ I hope this helps... Best regards... 95C6676453094B229C4EDB34ABA333DFF432E1DD -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEElcZnZFMJSyKcTts0q6Mz3/Qy4d0FAmGM5nsACgkQq6Mz3/Qy 4d2QihAAhFAVPRFMdYVokJoRw6kck2kVWO9tJ5/O716UZcCPozHP/ht+RO8GUu5t xF0B3U3tFLtOscnLV8TvhQN0Ngr86IYR3+tD0wxcaiZPj55mD2SMjouxiWdjXHYK fhoGUlw3vM53CeL1QsoCoDcKQHCVMfJZ8NhSA/ME4H9SQl7kkwswmnwwOyOFJ7Wc OM6xTwKddreqkUwWOyCPzaVOj12SjE3gT4LqQjTDYds0c2GWdU4RZUlIFVPA64BD j+p6WJg5wwkgfHA8SNZfAmPg8DYzz+vqbGghnOQbBychugek+bfB4HRn3RgCcxFB s7D50M8jixAOVQDokb7br+xIzN/BxGUfZPD5zgQirjQ/Q2fPx/Xr8EFeYjBlsptI 3k/wqubPGlQpYJkZqrRGQLNVPnQTAwuyWREB/+f6kheoI4Lj84981cRP1XEMh3YB a/L+t84mJaIM8RGi1YoDbhj6Ljmnr57UdOJqev+RnfZjHyxTt1xN6RdsLZxghV8R 9u0MMVNtzhIRci66XUHsREhbm6EzfB/8e1PaX+/TVaX4W/3zprFU9OSoPiBXNYg8 wLeTt3PKFt8bZ6+kmfaM6fDWMiISH5DAGjOtgPU5yoaNlcob2V09DZnWBjE2REPz pebl2NgQad99LK5La5pKkZAawuF/knxfivC0GEj8+0mEAzdPzpk= =tcbs -----END PGP SIGNATURE-----

3 3

Re: [tor-relays] Hardware requirements for a fast Tor relay
by failing.flyaway443＠mailer.me 12 Nov '21

12 Nov '21

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Thank you for your suggestions, Gary. This is actually not a "real" root server, it's a KVM server (of course). The CPU is an AMD EPYC 7702 with 2 dedicated cores per server@3,35GHz. I chose this server because the bandwith is unmetered and it's a guaranteed 1GHz link. I don't think I will ever be able to relay 125MB/s, but I will try my best. If I can only reach ~50MB/s before the CPU starts to grumble I will set up a second Tor process and a second relay. I tuned my relay a bit today, using some of the tips from this conversation: https://lists.torproject.org/pipermail/tor-relays/2010-August/000164.html It's not really up to date, but still useful to some extent. Unfortunately I had to restart the Tor process, but my relay was already measured a few times and reaches spikes of 30MB/s. CPU usage is no issue at all yet, there is room for more. I can wait before I get the guard flag, this is not a race... Thanks again for your help. All the best. PGP-Fingerorint: 95C6676453094B229C4EDB34ABA333DFF432E1DD -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEElcZnZFMJSyKcTts0q6Mz3/Qy4d0FAmGMbCAACgkQq6Mz3/Qy 4d2bpBAAmQIQ6wvjeBhdL4DxPdL9qlxIqbjPMxpPQWWCqSa3x/t+V3mcEzl/Srz7 5hUVwmYwMprtVA9Zf/MDPCElqbs5MpDrHkJE/rGhfEc6ld/Xu62LLVS7US+/ocTb RCLW1WG8pAQymR9avbyDqTqqTBOinIGlxwmCLXAldEllsxfVnKd4nFzxxEv/Ms/4 JrWvnOjJde46CCFchmjEfUGWVgquU9lsjpHbqVz/+ErUKVAd57BmPNpteiXed8xi RuM6BqB5/blL+CmdVISprisaIPIhqlCW5UEkuNPm5ijlrKrBYTSn4/b8HnMdg5UE ynAkzR5dkxyYee+uI84mgIfFNUzaVBpBq2W5obPqGiocoWQKgT70zVPxzLuguyoG U/Mzxikq4K86aorimSad207BEIVkey76s6jqqgKKI7UoTIYUTmc1xsA1tcgi44Me MelT5gEZ/fcesfPpYB/gkIyOIE+ADuCfnvOqDWAOvfnX9q6U9ek8+aHYSXGIdf9M oKjAKkO8Y/BWBsEHlnyBIrfE48/WtSNlQRj9oKSzyFtQs8wDhgoe3mgcvyHnPTOu Tq7UJUGV3L1LHOW6iEZTMKUsD9t1/NpGLpnTgTXne6bYzyJYL4D5w6IX30EaeaPw 387TB7cTj8Vaaw2bTiM7NlfAEdWqxt2v0qcgzFtTSIhnHLGtnQo= =tlZd -----END PGP SIGNATURE-----

2 1

Tor on cloud VPS
by potlatch 12 Nov '21

12 Nov '21

Hello All, My VPS host recently moved one of my Tor exits to cloud ops (I believe AWS). Since that time the instance will not function as an exit. Torcc and keys are as before. I was operating on Ubuntu 21.04 but reloaded to 20.04. Still the same. I messed with the netplan config to no avail. George brought this to my attention and suggested (and I agree) a DNS problem. I can't find where it's failing--to be honest I don't have much experience with cloud instances or netplan. I am of the opinion that there is a conflict between the cloud hosting and Tor. When I call Nyx I see the strange exit policy: reject [FC00:'string of zeros']/7:*, reject [FE80:'string of zeros off of Nyx page']. Other exits I operate are fine in the cloud. Thanks for any help you can provide. potlatch Sent with [ProtonMail](https://protonmail.com/) Secure Email.

2 1

Re: [tor-relays] Tor website
by failing.flyaway443＠mailer.me 11 Nov '21

11 Nov '21

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Sorry, it was not my intention to interfere. $man tor I forgot to mention, that works too of course. Or in this case $man torrc. I already run a relay myself, after several "failed" attempts on cheap VPS now on a root server with unlimited traffic and extremely fast connection. This one: https://metrics.torproject.org/rs.html#details/D1F7BEC34A66498FC565BC057632… I had to take the VPS' offline because they could not handle the traffic I would like to relay. Maybe I'll run a much smaller second relay, I'm still thinking about that. As I said, it was not my intention to provide links to outdated ressources. Won't happen again :) All the best... 95C6676453094B229C4EDB34ABA333DFF432E1DD -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEElcZnZFMJSyKcTts0q6Mz3/Qy4d0FAmGNCJkACgkQq6Mz3/Qy 4d1CLA//UtJzIdphbucuqAY5o4P3K+R4pgqooY9bgsOO9G/A1Ra+hVe2d7yBhESH FnoCsuIAKjBJRX30W8AQIh4R6amwhCLRgrdhacfHFtgjksxKavqXQ3bwS7RfnbZ5 R0V2QDSFyulhwsqIvqKF30WE/Ks3niimQS7nPHzgXRxrBV3yUW0ldw6/tNhS8G+T L6QB0/GuVnZlRat285Y2mx5wX8MAxqoowD3YFI8i1HGEf4IZayyXzQxZobaTlFN9 PcGrZUCgw26N6jDknlpc81ZbX1ZKeeFrcQunl3/LXxE225oASQBoasPmHbTpO2QO wOYbqCJ3eptPZq1e4jvzC0MnBG2nVFH7BcJ4/f7TbrvAhZqxEzvQqHNU/r7s/4Le YzJrEhadxUKESO5W7XGMQdaxlY670JolP1yRL7x3Ese8EgtugKM3BZXMr5w1EAby x6erAiuj+36GEuR8IiXB2bqHJ1GeQmXWOh0lSFdJri9SthF8KYC4jlEvHtvib0wJ NsdaBAEQ2DhgiDtCp9HNDAiDeHf6QanFt+1JGEuKno1HMYzky2rxmYonNcoxfXX0 KnqFKKxn7F78RpTXbioWB4/4MqMUZpV0SWl5LUS/v4zY4B26W9gxQ6/FPGq0a8zs Zeei9AK1gMg+NeFSajC1FSVDncbEEFYKqNryEGMPzrD2b5RVSms= =zzGy -----END PGP SIGNATURE-----

1 0

Tor website
by potlatch 11 Nov '21

11 Nov '21

Hello, Does the new Tor web configuration have an overall site map or index page? I can't find the old page with the manual for torrc. I've had trouble finding other information over the past few weeks as well. Thanks, potlatch Sent with ProtonMail Secure Email.

1 0

A Simple Web of Trust for Tor Relay Operator IDs
by nusenu 10 Nov '21

10 Nov '21

Hi, I wrote down a spec for a simple web of trust for relay operator IDs: https://gitlab.torproject.org/nusenu/torspec/-/blob/simple-wot-for-relay-op… This is related to: https://gitlab.torproject.org/tpo/network-health/metrics/relay-search/-/iss… https://lists.torproject.org/pipermail/tor-relays/2020-July/018656.html kind regards, nusenu -- https://nusenu.github.io

5 9

Crashed Relay
by sysmanager7 10 Nov '21

10 Nov '21

I was notified by Uptime Robot that relay 1 of 3 had been shut down. Unfortunately I found this out 12 hours after the fact. guard flag is lost. journalctl -u tor@default Nov 01 01:03:18 ubuntu-s-1vcpu-2gb-nyc1-01 Tor[328387]: I learned some more directory information, but not enough to build a circuit: We need more microdescrors: we have 6178/6618, and can only build 49% of likely paths. (We have 99% of guards bw, 50% of midpoint bw, and 98% of exit bw = 49% of path bw.) ptors: we have 6178/6618, and can only build 49% of likely paths. (We have 99% of guards bw, 50% of midpoint bw, and 98% of exit bw = 49% of path bw.) ived 4371.61 GB. I've received 7345604 connections on IPv4 and 0 on IPv6. I've made 677780 connections with IPv4 and 0 with IPv6. Nov 01 06:47:26 ubuntu-s-1vcpu-2gb-nyc1-01 Tor[328387]: Interrupt: we have stopped accepting new connections, and will shut down in 30 seconds. Interrupt aga> Nov 01 06:47:26 ubuntu-s-1vcpu-2gb-nyc1-01 Tor[328387]: Delaying directory fetches: We are hibernating or shutting down. Nov 01 06:47:56 ubuntu-s-1vcpu-2gb-nyc1-01 Tor[328387]: Clean shutdown finished. Exiting. Nov 01 06:48:04 ubuntu-s-1vcpu-2gb-nyc1-01 systemd[1]: tor(a)default.service: Succeeded. Nov 01 06:48:04 ubuntu-s-1vcpu-2gb-nyc1-01 systemd[1]: Stopped Anonymizing overlay network for TCP. This is NOT a first time for the above on this relay, more like a 7th or 8th. CPU usage according to NYX is 90/95%. That has been the last three weeks or so. Prior to that, average CPU usage was 30% or less. Current BW/Burst is 3/4 MBs on torrc and nyx. Prior was BW/Burst 4/5 *Me - retired fixed income. Average billing for 3 Digital Ocean Droplets was $40. budget is good with that. Octobers billing - $87.50 I used 10 gb instead of 6Gb. Essentially a $40 overage. It's almost as if, torrc and nyx are being ignored. Sent with [ProtonMail](https://protonmail.com/) Secure Email.

3 2

Re: [tor-relays] Hardware requirements for a fast Tor relay
by failing.flyaway443＠mailer.me 10 Nov '21

10 Nov '21

Hi Gary, thank you for your response. I think I just worry too much. I watched my relay all the time today, I had bandwidth usage of 30MB/s at times and HTOP showed me a Load average of 0.29/0.29/0.30. I know that this is totally fine for a dual core. The relay is up and running for 3 days and 8 hours now and I already moved ~700GB in each direction (upload/download). I was just concerned because the VPS started crashing after 2 weeks solid uptime, but I should have set stricter bandwith limits. You can't really compare a VM with a root server, I don't think this will happen again. It's ok for me to invest a little more and have a fast and stable relay this way. The traffic was capped with the VPS plan, this was obviously a big disadvantage, now I can use as much traffic as I want with a 2,5Gbit link (1Gbit guaranteed). For your info, the most important lines of my config: SocksPort 0 Log notice file /var/log... Log debug file /var/log... ORPort 443 RelayBandwithRate 1000Mbit RelayBandwithBurst 1000Mbit Exit policy reject *:* ContactInfo & Nickname set, of course... ;) Is there anything I should change? Thanks for your help! Best Regards...

2 1

Re: [tor-relays] Hardware requirements for a fast Tor relay
by failing.flyaway443＠mailer.me 10 Nov '21

10 Nov '21

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 I'm sorry that I now spam the mailing list, but I made a mistake. I'm of course NOT logging at debug level, it's just one logfile (notices.log). I logged debug when I was running the relay on the VPS because I wanted to know why it crashed all the time, but all that happened was that my 20TB SSD was maxed out within two hours and I had to reboot to get rid of the old logfiles. My bad, please don't think I write a debug log, that's completely pointless. Why would I. I rented a pretty expensive root server because I think Tor is really important and I want to relay as much traffic as possible, not to log debug messages. This was obviously not correct, but the rest of my torrc looks as described above. By the way, my relay has now around 4000 incoming and 4000 outgoing connections and a throughput of almost 1TB/day, and the load averages are still below .40. Everything looks good. :) Have a nice day, everyone! -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEElcZnZFMJSyKcTts0q6Mz3/Qy4d0FAmGLxa0ACgkQq6Mz3/Qy 4d1vJhAArWytI9hG6iGIvVzUP6lOgLMCEVfn4KBiFzq0iGqr2ex+utWIt8gek3SX Bm9McRbicgDUSzbnrHJrPzKxrpYvvtABbApyDZDSOEwgSXeaUcE2J8jhk20fOA6u tLFf7S+ON88KW8HkwNIkqSFmRifp3dZEBOapFZnBfgREwu19qxg1iyYZfJHDIMd6 4vWzI5oo2D1iFTyCDZllduqEURZNgZRfwtNk8ydfOje9X0QMkHgzy4fECCNgcYdY to+1BbYxY2lT34+1aLoRnnyA2yLykYI2ivRNx+IyD9X/QCKq+3sV+xjRvyOH39r7 Tmvg8NTNuZCiEwi9JCIJlRynrFk3HgUTbCT87iK8PGMTG6TimnBvFKUfKQMwIicD 1YrLQ30hSjTnetRbyLT0B7gd+h+CkDg6ssi0j6eKV0urP6PTipnr19OJeBZ3kZbw j+a3qipxy3mNIp9dW9d+ZBzhV+jtrDUMKUpjqHUkUEEdNH060TSMyYMBwCf7/dgH Ft8FWgTcLtX9dohx/CAHfQ+8rsa/wYEuLnXgc3AXibof9VZaTMKz5iDkhUwOnCoA 0528RNKLH+Rf4CoMOCycjqW0k1svPX9oAXoOgX0GQz/1DnocA4DEs+wVPJmr6dR+ mcHwDiKlOd5ksARl+fivmHurUE+ULzhI8l+Cdhr+Wi7NzVzuZ5U= =s8hY -----END PGP SIGNATURE-----

1 0

Re: [tor-relays] Hardware requirements for a fast Tor relay
by failing.flyaway443＠mailer.me 09 Nov '21

09 Nov '21

I just read this research paper, maybe it's worth thinking about some kind of implementation of this approach some time in the future. It's an interesting read anyway. uwspace.uwaterloo.ca/bitstream/handle/10012/16108/Engler_Steven.pdf Regards

1 0

Hardware requirements for a fast Tor relay
by failing.flyaway443＠mailer.me 09 Nov '21

09 Nov '21

Hi everyone, about two weeks ago, I signed up for a VPS with a cloud provider and set up a Tor relay. I installed Debian 11 Bullseye, secured it, and then set up Tor 0.4.6.8 and started the relay. The VPS had the following specs: 1vCore, 2GB RAM, 40TB traffic per month on a 1Gbit/s link. I throttled the traffic accordingly so that the monthly limit of 40TB would not be exceeded. Nevertheless, the CPU load was extreme, the server was running at full capacity and crashed several times. Since I want to help the Tor network with a fast relay I now signed up for a root server which has the following specs: Dual core CPU, 8GB ECC RAM, 2,5Gbit link, 1Gbit guaranteed, unlimited traffic. I set this thing up with Debian 11 Bullseye again and Tor 0.4.6.8. Since my bandwith gets throttled when I use more than a certain amount of traffic/month and at the same time (!) on average more than a certain amount of bandwith for more than one hour, I set the MaxBandwith to 1000Mbit/sec (equals 125MB/sec). This relay is up and running for a few days now, and I already have around 4000 incoming and outgoing connections. My bandwith is not fully used yet, but sometimes I see spikes of 20MB/s. What concerns me is that the CPU load again is sometimes 40-50% on both cores, even though this relay is not fully used yet. Can somebody tell me if it is even possible to run such a fast relay on this hardware? Should I set a more restrictive bandwith throttle myself, or go for a quad core CPU? I don't think I will ever run out of RAM this time, since I have 8GB. Thank you for your advice! All the best!

2 1