tor-relays October 2022

tor-relays@lists.torproject.org

33 participants
25 discussions

Your computer is too slow to handle this many circuit creation requests
by teamcat＠genocide.fun 07 Oct '22

07 Oct '22

Hello, After setting up a relay, I noticed that my log file was full of "Your computer is too slow to handle this many circuit creation requests" messages. This seems odd to me, as htop reports that my CPU and memory usage is nowhere near full. I'm running on two cores and 8 GB of RAM, and it's averaging about 40% usage on both cores and 2 GB of RAM usage. I've used the tor-ddos iptables rules that were suggested in a previous message thread, but it doesn't seem to have done anything to address the problem. (https://github.com/Enkidu-6/tor-ddos). I've also configured /etc/sysctl.conf to support a traffic flow as outlined in the github repo. Here is the link to the metrics page for my relay. https://metrics.torproject.org/rs.html#details/74181AB4D1A7D403ED9F190FAC92… Is this something that I should be concerned about, and work to mitigate? I am able to migrate my relay to much more powerful hardware, but obviously that would incur additional cost, so if there is some way to fully utilize my existing hardware I would prefer that. Regards, Evan

1 0

(FYI) Rejecting outdated snowflake proxies
by gus 06 Oct '22

06 Oct '22

Hello everyone, As part of scaling snowflake bridge and adding distributed snowflake server support[1], this week the Anti-censorship Team started to reject *outdated* snowflake proxies that can't support this feature (distributed server support). This will result in a loss of 30% of unrestricted NAT proxies. Read below the instructions how to check your snowflake proxy version: - WebExtension: 0.6.2. - Docker: To check the version: $ docker run thetorproject/snowflake-proxy -v should include "-allowed-relay-hostname-pattern" in the output. To update: $ docker pull thetorproject/snowflake-proxy - Standalone with Go Toolchain: To check the version: $ proxy -v should include "-allowed-relay-hostname-pattern" in the output. To update: $ go install git.torproject.org/pluggable-transports/snowflake.git/v2/proxy@latest If you need help, please check this Forum post: https://forum.torproject.net/t/please-update-your-snowflake-proxy-to-help-u… Thank you! gus [1] https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… -- The Tor Project Community Team Lead

2 1

Consensus weight tanking
by Me 06 Oct '22

06 Oct '22

Good day, Not sure if this would be the proper avenue to pursue this. I operate a couple of middle relays from my home server. All seemed well until this morning. Three days ago one was promoted to guard status while the other lags behind. This morning I check the Tor metrics page and the consensus weight graphs on both relays have bottomed out. The other metrics do not have appeared to have remained normal for daily operations. Any suggestions or input are greatly appreciated

2 1

Moving middle relays to bridges?
by Isaac Grover, Aileron I.T. 05 Oct '22

05 Oct '22

Good morning, According to tor metrics, there have been nearly three times the number of relays as bridges over the last three months so I would like to move my handful of middle relays to bridges. They will keep their same IP address. Is there a best practice with regards to doing this so the directories don't get confused? Make your day great, Isaac Grover

3 2

Thoughts about potentially abusive config option for exit nodes
by abuse-node49＠posteo.de 03 Oct '22

03 Oct '22

I did not manage to find anywhere on the new website the current config options of the torrc. So I ask the question here, although it may be already outdated. This is the third time I have had contact with the police about Exits Relays. That's why it occurred to me that someone might be acting targeted, because I run more than one node. Looking for configurations that allow dedicated IP addresses, I found the torrc-config option 'StrictNodes 1' in conjunction with 'ExitNodes [IP/Nickname/Key]' on the web. There were also hints that something had been changed before, but I tried it on a local installation. The goal was to use a specific exit address. StrictNodes 1 ExitNodes [MY_EXIT_NODE_IP] First I had a typo and the Tor service did not start. After the correction it worked and I got into the network. The conclusion remained that Tor accepts these configuration lines. The problem with this is, should this config line really allow a dedicated exit as the sole exit point into the network, the operator of that exit could be targeted and harmed with illegal traffic. In Metrics it is easy to show whole Tor families that always belong to a single operator. It would be nice if the developers remove the possibility to specify a dedicated IP address/nickname/key, if not already done. The config option 'Exitnodes {COUNTRY_CODE}' should remain though. Kind regards, Olaf

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-relays October 2022