tor-relays October 2021

tor-relays@lists.torproject.org

33 participants
22 discussions

Dropped off consensus (0.4.4.5)
by Felix 23 Oct '21

23 Oct '21

Hi everybody This is early. Yesterday I upgraded Ichotolot60 1AE039EE0B11DB79E4B4B29CBA9F752864A0259E from 4.2.7 to 4.4.5. Now I see in the consensus health: moria1 Fast Run Stab V2Dir Valid bw=566 tor26 Fast Guard Stab V2Dir Valid dizum Fast Guard Stab V2Dir Valid gabel. Fast Stab V2Dir Valid bw=1130 danne. Fast Guard Run Stab V2Dir Valid maatu. Fast Stab V2Dir Valid bw=1200 farav. Fast Guard Run Stab V2Dir Valid bw=2970 longc. Fast Stab V2Dir Valid bw=490 bastet Fast Guard Run Stab V2Dir Valid bw=3520 And _no_ Authority "owns" the relay. Old Apr 02 21:51:31.872 [notice] Tor 0.4.2.7 running on FreeBSD with Libevent 2.1.11-stable, OpenSSL LibreSSL 3.0.2, Zlib 1.2.11, Liblzma 5.2.4, and Libzstd 1.4.4. New Sep 18 21:00:22.384 [notice] Tor 0.4.4.5 running on FreeBSD with Libevent 2.1.12-stable, OpenSSL LibreSSL 3.2.1, Zlib 1.2.11, Liblzma 5.2.4, and Libzstd 1.4.5. (Yeah, some Lib stuff is new too, hehe) The "Guard !Run Stab" consensus looks quite interesting to me. How can it be? Other relays with that nice "Guard !Run Stab" dropped off consensus over night (or since days) and no authority "owns" them too: HORUS1 0.4.4.4-rc norisknofun 0.3.5.10 ULayerKiriakou 0.4.3.5 Stellvia 0.4.3.6 torexit42 (StaleDesc) 0.4.1.6 torpidsDEhetzner1 0.4.3.2-alpha (3 days) karen (StaleDesc) 0.4.2.7 Stephen304 0.4.2.7 (3 days) Rigel2020 (StaleDesc) 0.4.3.6 dgplug (FallbackDir, StaleDesc) 0.4.4.5 =?= May-be the operators updated and are now in the same floating position? May-be this is super normal and came to my attention by surprise? Anyways, I let everthing run for a day or so. Time can heal. -- Cheers, Felix

5 8

Tor Bridge Question
by Josh Lawson 19 Oct '21

19 Oct '21

I work for a bank and was informed that when I connect to my employer network, it shows I am coming from a Tor IP and sets off an alert that then leads to me being on a call with an investigative team for my employers. I was running a Tor relay, but had to shut it down because of these alerts. I am not thinking of running a bridge instead, but I have a question. Are the bridge IP addresses private enough to not likely trigger an alert by bank fraud detection software? Please let me know if I am not phrasing this well. I would like to donate some bandwidth and was thinking maybe running a bridge would be less likely to set off alerts.

3 2

Overloaded state indicator on relay-search
by Silvia/Hiro 19 Oct '21

19 Oct '21

Hello all, One of our goals with our current performance work is to reduce the overload of relays in the network. The implementation of proposal 328[1] a while back made different overload indicators available to relay operators and since a couple of weeks ago those can be tracked via Onionoo[2] as well. As we know that a lot of our relay operators use relay search to check for the health of their relays, we have launched a new feature there, too, to help them know when their relays are overloaded. When a relay is in the overloaded state we show an amber dot next to the relay nickname. Currently we are counting between 50 and 80 overloaded relays and between 10 and 20 overloaded bridges. The overloaded state is reached when one or many of the possible load metrics have been triggered. When this happens we show it for 72 hours after the relay has recovered [3]. Note, though, that not all of the exposed overload metrics are triggering the overload indicator on relay search yet. If you noticed your relay is overloaded, please check the following support article to find out how you can recover to a "normal" state: https://support.torproject.org/relay-operators/relay-bridge-overloaded/ Let us known how you find this new feature. Cheers, -hiro [1] https://gitweb.torproject.org/torspec.git/tree/proposals/328-relay-overload… [2] https://lists.torproject.org/pipermail/tor-project/2021-August/003168.html [3] https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n637

13 51

What is: Channel padding timeout scheduled
by Eddie 18 Oct '21

18 Oct '21

Noticed that one of my relays (OhNoAnotherRelay02) is showing as off-line. Looking at the logs, I see a bunch of these messages: Oct 18 08:39:16.000 [notice] Channel padding timeout scheduled 143041ms in the past. Oct 18 08:39:21.000 [notice] Channel padding timeout scheduled 156925ms in the past. Oct 18 08:39:24.000 [notice] Channel padding timeout scheduled 168712ms in the past. Oct 18 08:39:25.000 [notice] Channel padding timeout scheduled 166895ms in the past. . . . Oct 18 10:18:48.000 [notice] Channel padding timeout scheduled 194581ms in the past. Oct 18 10:35:22.000 [notice] Channel padding timeout scheduled 216311ms in the past. Oct 18 10:35:30.000 [notice] Channel padding timeout scheduled 224267ms in the past. What's the cause of this. I used this downtime as an excuse to do a bunch of upgrades and a re-boot. Cheers.

1 0

help with exit
by Bass Down Low 17 Oct '21

17 Oct '21

Hi all, I am somewhat new to the project and trying to run a couple exits to help out. I noticed my relay amazinglizard F80494CE5B2441B67431FFA9CCA571D26BC4F6D8 has bee up for 4 days and not turned into an exit yet. I noticed the overload flag is present, does this prefent my relay from becoming an exit? If not, I would appreciate any help you can give. thank you very much

2 1

Tor automatic restart
by Keifer Bly 11 Oct '21

11 Oct '21

7 8

Updating from Ubuntu 20.04 using apt-secure
by John Csuti 11 Oct '21

11 Oct '21

Hello all, I recently went to update and upgrade my system and found that the certificate for deb.torproject.org is expired and no longer trusted? Is anyone else having this issue and is there a way to fix this. I also added the repo to a fresh install of ubuntu 20.04 and got the same error. Error Err:5 https://deb.torproject.org/torproject.org focal Release Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate. Could not handshake: Error in the certificate verification. [IP: 95.216.163.36 443] Thanks, John Csuti +1 (216) 633-1279

2 2

Restarting Tor
by sysmanager7 10 Oct '21

10 Oct '21

Greetings All, I have three relays that are in need of an upgrade and reboot. What is the best way to restart these relays without loosing flags or time? Secondly how long can a relay be down before flags are dropped? Thank you for any help! Sysop Sent with [ProtonMail](https://protonmail.com/) Secure Email.

4 3

relayor v21.1.0 is released
by nusenu 10 Oct '21

10 Oct '21

Hi, relayor v21.1.0 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 Changes since relayor v21.0.1 https://github.com/nusenu/ansible-relayor/releases/tag/v21.1.0 - generate ContactInfo v2 proof files for easy publishing (if enabled) - update apt cache if it is older than one day before installing dependencies (patch by @tsekityam) #219 #220 - increase min. ansible version 2.9.13 -> 2.9.23 - increase min. tor version 0.3.5 -> 0.4.5 - Debian 11, FreeBSD 13 and OpenBSD 6.9 are supported kind regards, nusenu -- https://nusenu.github.io

1 0

Connection Reset and IO Timeout errors on 0.4.6.7 with libnss
by theintern 09 Oct '21

09 Oct '21

Has anyone else on this list had issues with compiled versions of 0.4.6.7 in which the --enable-libnss is enabled?

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-relays October 2021