January 2024 - tor-relays - lists.torproject.org

Recent Tor versions not reloading config on / ignoring HUP kill signal.
by George Hartley 10 Aug '24

10 Aug '24

Hi, I think this started with release 0.4.8.10, but both of my Tor relays no longer reload their config when doing for example: - systemctl reload tor@exit Here is the relevant part of the unit file: > [Unit]Description=Anonymizing overlay network for TCP > After=syslog.target network.target nss-lookup.target > > [Service] > Type=notify > NotifyAccess=all > ExecStartPre=/usr/bin/tor -f /etc/tor/torrc_%i --verify-config > ExecStart=/usr/bin/tor -f /etc/tor/torrc_%i > ExecReload=/bin/kill -HUP ${MAINPID} > KillSignal=SIGINT > TimeoutSec=75 > Restart=on-failure > WatchdogSec=1m > LimitNOFILE=32768 Checking with: - journalctl -u tor@exit Just tells me that systemd attempted and successfully executed the specified reload command, but the actual line from the Tor instance stating that the config has been reloaded is missing. Is anyone else experiencing this? Regards, George

2 2

Worse throughput with 0.4.8.x, on a slow CPU
by Roman Mamedov 04 Mar '24

04 Mar '24

Hello, Ater upgrading from Tor 0.4.7.13 to 0.4.8.9, I get a much worse bandwidth numbers. The CPU is Atom C2338 with two cores at 1.75 Ghz. Multiple Tor instances are running to take advantage of both cores. On the older version it gets about 80+80 Mbit total in+out. On the new one the average is at most 45+45 Mbit. There are frequent periods where the bandwidth drops to 5-10 Mbit for 3-5 seconds, while all Tor processes continue to use 100% of both CPUs, then gradually climbs back up. Does anyone notice anything similar? Here's how it looks for a few days on 0.4.8 then a roll-back: ------------------------+-------------+-------------+--------------- today 461.94 GiB | 470.84 GiB | 932.78 GiB | 153.98 Mbit/s ######################################## 12/12/23 462.81 GiB | 475.67 GiB | 938.48 GiB | 91.12 Mbit/s ####################### 12/11/23 434.72 GiB | 443.08 GiB | 877.80 GiB | 85.23 Mbit/s ###################### 12/10/23 446.13 GiB | 459.56 GiB | 905.70 GiB | 87.93 Mbit/s ####################### 12/09/23 464.79 GiB | 473.17 GiB | 937.96 GiB | 91.07 Mbit/s ####################### 12/08/23 454.67 GiB | 463.48 GiB | 918.16 GiB | 89.14 Mbit/s ####################### 12/07/23 463.82 GiB | 472.84 GiB | 936.65 GiB | 90.94 Mbit/s ####################### 12/06/23 670.01 GiB | 680.55 GiB | 1.32 TiB | 131.13 Mbit/s ################################## 12/05/23 808.50 GiB | 817.32 GiB | 1.59 TiB | 157.85 Mbit/s ######################################### 12/04/23 854.09 GiB | 866.43 GiB | 1.68 TiB | 167.05 Mbit/s ########################################### 12/03/23 782.20 GiB | 799.00 GiB | 1.54 TiB | 153.52 Mbit/s ######################################## 12/02/23 805.18 GiB | 817.91 GiB | 1.59 TiB | 157.59 Mbit/s ######################################### 12/01/23 733.80 GiB | 745.35 GiB | 1.44 TiB | 143.61 Mbit/s ##################################### 11/30/23 742.48 GiB | 756.56 GiB | 1.46 TiB | 145.54 Mbit/s ##################################### 11/29/23 657.90 GiB | 673.66 GiB | 1.30 TiB | 129.28 Mbit/s ################################# In general, are there any tweaks to reduce relay CPU usage on a slow processor? I did seemingly most of what is possible, ethtool, iptables, sysctl, etc. How long before the Rust-based Tor will be ready for use on relays? -- With respect, Roman

4 5

Next Tor Relay Operator Meetup - 2024-01-27 @ 19:00 UTC
by gus 12 Feb '24

12 Feb '24

Dear Tor relay operators and volunteers, Save the date: the next Tor Relay Operator Meetup will happen on Saturday, January 27 at 19 UTC! We're still working on the agenda for this meetup, however feel free to add your topics directly to the ticket or just reply to the mailing list: https://gitlab.torproject.org/tpo/community/relays/-/issues/84 Where: Room link: https://tor.meet.coop/gus-og0-x74-dzn When: January 27, 19:00 UTC Tor Code of Conduct: https://community.torproject.org/policies/code_of_conduct/ Registration No need for a registration or anything else, just use the room-linkabove. We will open the room 10 minutes before so you can test your mic setup. Please share with your friends, social media and other mailing lists! cheers, Gus -- The Tor Project Community Team Lead

2 3

Relay in AT marked as DE in metrics
by Carlo P. 04 Feb '24

04 Feb '24

Hello, I have a relay on 152.53.17.183 / 2a0a:4cc0:1:1333::beef which is listed as "German" in metrics.torproject.org, but actually it is in Austria (see e.g. whatismyip.com) Is this the right place to request a fix ? Thanks, C. -- Sent with https://mailfence.com Secure and private email

3 3

Relay first seen reset on Tor metrics
by Zachary 30 Jan '24

30 Jan '24

The "first seen" date on my relay A00E3AAF5A24DC69740FA7A3A1C4A0ECB7972722 Got reset today while I was at work. It's not a problem and I don't particularly care, but is there anything that would cause this? IP hasn't changed, Tor version hasn't changed, etc. Thanks, Zachary

2 1

Setting up HTML page for exit relay
by templeos＠skiff.com 29 Jan '24

29 Jan '24

If I want to serve an HTML page for my exit node do I need Apache2/nginx or can I just modify my torrc?

3 2

tor relayS! stuck at 100% bootstrapped - not kickstarting 8B6A6D02A80A7CBB1ED0630150D8D9F9F7D471AF
by eff_03675549＠posteo.se 29 Jan '24

29 Jan '24

Hi. I am trying several Singapoor relays stuck at 100% bootstrapped without any coming speed evaluation nor id key attributions, 8B6A6D02A80A7CBB1ED0630150D8D9F9F7D471AF one middle/guard out of 4/5 came out witn keys an shows in relay search still without any speed attribution now over 48 hours, the others (guards, exit) are tusk at 100% bootstrapped. all in singapoor. Your kind evaluation please. an.

1 0

What a mess with the database of 'metrics.torproject.org'!
by Tschador 24 Jan '24

24 Jan '24

Example: Fingerprint: 9D5A7A81BC6194555CE751F75FB196E4A3982CC5 This relay appears to be less than 2 weeks old. Uptime 43 days 13 hours 30 minutes and 17 seconds First Seen 2024-01-10 16:00:00 (14 days 2 hours 32 minutes and 41 seconds) Last Restarted 2023-12-12 05:02:24 When will it be fixed? Regards

1 0

Why is Cloudflare displayed when I do a speed test?
by templeos＠skiff.com 19 Jan '24

19 Jan '24

A blog post I discovered brought up that when they perform a speed test through Tor browser, Cloudflare is quite frequently displayed as the local host. I had the same result. Is there a reason for this, like perhaps the exit relay is proxied through Cloudflare? You can easily replicate this yourself by going to speedtest.net in Tor Browser.

1 0

A new kind of attack?
by Chris Enkidu-6 19 Jan '24

19 Jan '24

I've noticed a new kind of possible attack on some of my relays, as early as Dec.23 which causes huge spikes of outbound traffic that eventually maxes out RAM and crashes Tor. The newest one today lasted for 5 hours switching between two of the three relays on the same IP. During the attack, Tor becomes so busy processing the traffic that it becomes unresponsive to new connections for minutes at a time and effectively becomes a zombie exclusively processing the attacker's traffic until it eventually crashes and restarts. The interesting part is that when Tor restarts, it doesn't start from scratch building new circuits but it starts right from where it left out and keeps processing the previous connections. I have tried shutting down Tor for over 5 minutes and within one minute of restart, The RAM maxes out and the outbound traffic reaches the previous heights. This has been happening, not to all relays but to a select group of relays at a time and unless you're monitoring your Tor port from outside, you may not notice it's unresponsive. Another way to see if it's happening to you too is to check your monthly history on the metrics page and look for spikes of written bytes or sudden decrease of read bytes where you see a big gap between the two. I have included charts and excerpts from the log in my post in Tor forum at below link: https://forum.torproject.org/t/new-kind-of-attack/11122 I'd appreciate your insights and comments. Thank you.

6 5