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

recommended way to run 0.4.7 on armhf?
by ilf 25 Nov '23

25 Nov '23

What's the recommended way to run 0.4.7 on armhf? > The package repository [deb.torproject.org] does not offer 32-bit ARM > architecture (armhf) images (yet). https://support.torproject.org/apt/tor-deb-repo/ Debian has 0.4.7 in bullseye-backports. But Raspbian doesn't have bullseye-backports: http://raspbian.raspberrypi.org/raspbian/dists/ -- ilf If you upload your address book to "the cloud", I don't want to be in it.

3 6

PSA: Tor 0.4.5 reaches end of life (EOL) on 2023-02-15
by Georg Koppen 17 May '23

17 May '23

Hello! In case it affects you as you are still running your relay or bridge on Tor 0.4.5.x: the 0.4.5 series is going EOL on *2023-02-15* (roughly in 3 weeks from now). That's currently still 760 relays, which means roughly 7% of the advertised bandwidth of the network (and 387 bridges, which means roughly 9% of the advertised bridges bandwidth). Please make sure you have upgraded to the 0.4.7.x series by then. Supported releases in general can be found on the network team wiki.[1] Thanks, Georg [1] https://gitlab.torproject.org/tpo/core/team/-/wikis/NetworkTeam/CoreTorRele…

6 8

inet_csk_bind_conflict
by Christopher Sheats 20 Mar '23

20 Mar '23

Hello tor-relays, We are using Ubuntu server currently for our exit relays. Occasionally, exit throughput will drop from ~4Gbps down to ~200Mbps and the only observable data point that we have is a significant increase in inet_csk_bind_conflict, as seen via 'perf top', where it will hit 85% [kernel] utilization. A while back we thought we solved with with two /etc/sysctl.conf settings: net.ipv4.ip_local_port_range = 1024 65535 net.ipv4.tcp_tw_reuse = 1 However we are still experiencing this problem. Both of our (currently, two) relay servers suffer from the same problem, at the same time. They are AMD Epyc 7402P bare-metal servers each with 96GB RAM, each has 20 exit relays on them. This issue persists after upgrading to 0.4.7.11. Screenshots of perf top are shared here: https://digitalcourage.social/@EmeraldOnion/109440197076214023 Does anyone have experience troubleshooting and/or fixing this problem? Cheers, -- Christopher Sheats (yawnbox) Executive Director Emerald Onion Signal: +1 206.739.3390 Website: https://emeraldonion.org/ Mastodon: https://digitalcourage.social/@EmeraldOnion/

6 20

(Save the date) Tor Relay Operators Meetup - 2023-01-28 @ 19UTC
by gus 02 Feb '23

02 Feb '23

Dear relay operators, Save the date: our next Tor relay operator meetup will happen on January 28 at 19:00 UTC! We're drafting the agenda here: - pad: https://pad.riseup.net/p/tor-relay-op-meetup-j28-keep - onionsite: http://kfahv6wfkbezjyg4r6mlhpmieydbebr5vkok5r34ya464gqz6c44bnyd.onion/p/tor… Feel free to add topics and/or questions. Room Link - https://tor.meet.coop/gus-og0-x74-dzn cheers, Gus -- The Tor Project Community Team Lead

2 2

relayor v23.0.0 is released
by nusenu 27 Jan '23

27 Jan '23

Hi, relayor v23.0.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#main-benefits-for-a-tor-relay-ope… This release comes with some great new prometheus integration features (some labels that tor does not provide out of the box). I'll follow up with a post that gives a general introduction on how to use relayor's prometheus integration soon. Changelog: https://github.com/nusenu/ansible-relayor/releases/tag/v23.0.0 Note: If you used relayor's prometheus support in previous relayor releases, make sure to set the tor_prometheus_scrape_file variable after upgrading to v23.0.0 and before running ansible-playbook with v23.0.0 for the first time. See the README for an example value. kind regards, nusenu -- https://nusenu.github.io

1 0

Tor Relay Operators Meetup Jan 28
by George 27 Jan '23

27 Jan '23

Tomorrow is the next Tor relay operator meetup will happen on January 28 at 19:00 UTC! We're drafting the agenda here: - pad: https://pad.riseup.net/p/tor-relay-op-meetup-j28-keep - onionsite: http://kfahv6wfkbezjyg4r6mlhpmieydbebr5vkok5r34ya464gqz6c44bnyd.onion/p/tor… Feel free to add topics and/or questions. Room Link - https://tor.meet.coop/gus-og0-x74-dzn g

1 0

Proposal: increase max number of relays per IP
by mail＠nothingtohide.nl 23 Jan '23

23 Jan '23

Hello! Running a high bandwidth Tor server requires a lot of IPv4 addresses, while IPv4 addresses are becoming quite scarce and very expensive. For this reason we started the process to get the current limit of two relays per IPv4 address increased to reduce the cost of running high bandwidth Tor servers. You can find our proposal on Tor's Gitlab: https://gitlab.torproject.org/tpo/core/tor/-/issues/40744. If you would like to support this proposal, let us know and we add your domain/nick to the issue :). This topic will also be on the agenda of the Tor Relay Operator Meetup on 2023-01-28 19:00 UTC: https://lists.torproject.org/pipermail/tor-relays/2023-January/020973.html. See you there! - https://applied-privacy.net/ https://artikel10.org/ https://nothingtohide.nl/

1 0

bridge going down
by Anonforpeace 21 Jan '23

21 Jan '23

Hello: I have recently built a Tor Bridge (nickname is h4ck3rspace) and when it first went up, it was up to about two weeks and then it went down. So I brought it up again and ever since, it routinely goes down every 1 to 3 nights, between 8p and 10p EST. I've never seen this type of behavior before. Is there a way to know why it keeps going down so often, and subsequently how to prevent it? My area doesn't suffer from power outages and each time I restart Tor I wait to make sure it says that it is visible externally and that it will be published. Any help is greatly appreciated. Thank you Sent with [Proton Mail](https://proton.me/) secure email.

1 0

backports obfs4proxy unsigned
by tor 14 Jan '23

14 Jan '23

the backport of obfs4proxy seems to be unsigned I needed to use: deb [trusted=yes] http://deb.debian.org/debian bullseye-backports main

2 1

obfs4proxy ubuntu jammy arm64
by tor 14 Jan '23

14 Jan '23

Hello I'm running ubuntu, jammy, arm64. When I run: machine@user_1:~$ sudo apt-get install obfs4proxy Reading package lists... Done Building dependency tree... Done Reading state information... Done obfs4proxy is already the newest version (0.0.13-1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Where do I get version 14? -m On Fri, Jan 13, 2023 at 7:00 AM <tor-relays-request(a)lists.torproject.org> wrote: > 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. obfs4proxy on arm64 (tor) > 2. Re: obfs4proxy on arm64 (meskio) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 12 Jan 2023 18:11:40 -0500 > From: tor <tor(a)kevinandmatt.com> > To: tor-relays(a)lists.torproject.org > Subject: [tor-relays] obfs4proxy on arm64 > Message-ID: > <CAE8TgqTFidzSHmS+u2h5OBfwaS2xaK_tqc3ddh6jcm4= > OdgRLA(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi > Where do I find the updated version of obfs4proxy for arm64? > -m > > On Wed, Jan 11, 2023 at 7:00 AM <tor-relays-request(a)lists.torproject.org> > wrote: > > > 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. Re: security update for obfs4proxy (meskio) > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Tue, 10 Jan 2023 19:51:49 +0100 > > From: meskio <meskio(a)torproject.org> > > To: tor-relays <tor-relays(a)lists.torproject.org> > > Subject: Re: [tor-relays] security update for obfs4proxy > > Message-ID: <167337670907.1540.14665065923373201554@localhost> > > Content-Type: text/plain; charset="utf-8" > > > > We have made public the details of the distinguishability bugs that were > > affecting obfs4: > > https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/91 > > > > > https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/obfs… > > > > Most bridges are already upgraded, thank you all bridge operators for the > > work > > here. > > > > Quoting meskio (2022-10-14 11:28:44) > > > Hello, > > > > > > The latest version of obfs4proxy (0.0.14) comes with an important > > security fix. > > > If you are running a obfs4 Tor bridge please upgrade as soon as > possible. > > > > > > If you use debian you can find the Debian package in stable-backports: > > > https://packages.debian.org/stable-backports/obfs4proxy > > > > > > If you use docker you'll find the latest version in docker hub: > > > https://hub.docker.com/r/thetorproject/obfs4-bridge/ > > > > > > Or you can find the source code in the upstream repository: > > > https://gitlab.com/yawning/obfs4 > > > > > > If you need help upgrading your relay, please use this mailing list or > > the Tor > > > Forum: > > > https://forum.torproject.net/c/support/relay-operator/17 > > > > > > We appreciate a lot your effort and time! > > > > > > Thank you > > > > -- > > meskio | https://meskio.net/ > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > > My contact info: https://meskio.net/crypto.txt > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > > Nos vamos a Croatan. > >

3 4