April 2020 - network-health - lists.torproject.org

No network health meeting today 27 April 2020
by Georg Koppen 27 Apr '20

27 Apr '20

Hi! Sorry for the late reply but we won't have a network health meeting this week. I am aiming to do a sync on Monday, May 4 2020 again at our usual time (1800 UTC). Georg

1 0

Status update for our bad relay processes
by Georg Koppen 08 Apr '20

08 Apr '20

Hi! I just sent a status update about our bad relays work to tor-relays[1]. It's focused on relay operators which is why I chose that list but, in case you are not reading it, I thought sending at least a note to this list as well as that mail essentially concerns network health questions (too). Georg [1] https://lists.torproject.org/pipermail/tor-relays/2020-April/018356.html

1 0

Next weekly meeting 20 April 2020
by Georg Koppen 08 Apr '20

08 Apr '20

Hello! I forgot to talk about it in our weekly sync earlier this week but as next Monday is a public holiday in a bunch of jurisdictions (Easter Monday) we'll skip that meeting. The next one will be held on 20 April same time, same place. See you there, Georg

1 0

Upgrade your 'tarragon' Tor relay?
by Roger Dingledine 06 Apr '20

06 Apr '20

Hi William, You are running a Tor relay, which is great: http://rougmnvswfsmd4dq.onion/rs.html#details/1D4AB6248E3D7DF9C4FBE40DCFAA3… First: that Tor version is obsolete, and because of old bugs, we will soon cut relays running those versions out of the network. Please consider upgrading! Second: let us know if there is any way to help you bump up the bandwidth that you are allocating to the Tor relay. :) You can find Tor packages for your distro / OS here: https://trac.torproject.org/projects/tor/wiki/TorRelayGuide#Platformspecifi… Ideally you will switch to keeping up with our stable releases, but if you need a stable that is especially stable, the Tor 0.3.5 branch will be maintained until Feb 2022: https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTor… and you can see the lifetimes of other Tor versions on that table too. Let us know if we can do anything to make the process easier. And lastly, I am cc'ing the new network health mailing list (which has public archives), to help us stay synced: https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkHealthTeam Thanks! --Roger

3 2

Re: [network-health] [tor-relays] Low bandwidth
by teor 01 Apr '20

01 Apr '20

Hi, I'm cc'ing the network health team, so they are aware of this issue. >>> On 30 Mar 2020, at 23:00, ha3ks ha3ks(a)protonmail.com wrote: >>> my relay dropped nearly all it’s bandwidth about a month ago, checking over it I can see 3 of the dir auths have given it a low consensus weighting, would that cause low bandwidth numbers? >>> I checked my ufw in Ubuntu and it’s allowing 443 and 80. >> >> Date: Tue, 31 Mar 2020 09:44:41 +1000 >> From: teor teor(a)riseup.net >> >> I have seen similar reports from a few other relay operators. >> >> What is your relay fingerprint? >> >> Have you followed the troubleshooting instructions here: >> https://trac.torproject.org/projects/tor/wiki/doc/MyRelayIsSlow > > On 31 Mar 2020, at 20:46, ha3ks <ha3ks(a)protonmail.com> wrote: > > The fingerprint is - 6E1DA4C0B0C05FB721B42329C47A20DA22908AEB > > I have followed some of this yes, though its a little over my head I have opened a ticket in sbws to follow up this issue: sbws measures some relays 100x lower than Torflow https://trac.torproject.org/projects/tor/ticket/33775 It could be related to these other issues: sbws does not detect changes in descriptor bandwidth values https://trac.torproject.org/projects/tor/ticket/30733 sbws bandwidth scans should require a minimum exit bandwidth https://trac.torproject.org/projects/tor/ticket/33009 T

2 2