- tor-relays - lists.torproject.org

M1 anyone?
by niftybunny 29 Dec '20

29 Dec '20

With one of my servers down and giving me brain cancer … anyone tried to run relays on the new M1 chip? Is it even officially supported right now? Anyone any idea how much it could push? cheers, nifty

2 1

SSH
by Андрей Гвоздев 29 Dec '20

29 Dec '20

Hello I'm running a TOR relay, every time I SSH to my server I see a message that there were thousands of failed login attempts Do you see this message too?

10 12

Bridge acting strange
by enrollado 29 Dec '20

29 Dec '20

I have noticed some bizarre behavior on one of my relays. I logged into the server hosting particlefive (bridge) on November 15 and noticed that the tor process had crashed (not a clean exit). I had accounting set up, so it had hibernated from 11/07 00:00 UTC to 11/07 00:44 UTC. After that, it appeared to be running normally, but it crashed sometime after 11/07 06:25 UTC. I don't have crash dumps enabled, so I don't have any information on the crash. I restarted it and it appeared to have been working normally. I checked on it again on the 16th and all was well. On December 2nd, it suddenly stopped receiving client connections. According to the metrics page, it hasn't passed any traffic since then, though the logs show 20 - 60 GB per heartbeat interval. The log rotation has gone strange as well. As of today: notices.log - 12/29 06:25 to 12/29 12:20 notices.log.1 - 12/28 06:25 to 12/29 06:20 notices.log.2 - 11/06 06:25 to 11/07 06:25 notices.log.3 - 12/26 06:25 to 12/27 06:25 notices.log.4 - 12/25 06:25 to 12/26 06:25 notices.log.5 - 12/23 06:25 to 12/24 06:25 So, the log from the day before the crash is still hanging around with no unusual activity shown, and I'm missing the log file for 12/24. At this point, it seems to be running normally, but it is not receiving any new connections. Yesterday, I changed the configuration from accounting to bandwidth limiting, so notices.log.1 has the hup I sent to reload the configuration. However, notices.log.3 also shows a hup signal at 06:25 UTC that I did not send. I should probably report this on the tor-dev list, but moderation on that list appears to be pretty slow, and this list is more active. I was wondering if anyone else has seen this kind of odd activity on a bridge before. My paranoia alarm is in yellow status, so I'm about to dump this relay, get a new IP, and start over. Any advice is appreciated. No me preguntas nada, no te digo una mentira. Enrollado Sent with ProtonMail Secure Email.

1 0

Tor Traffic De-prioritization Script
by tontu 29 Dec '20

29 Dec '20

Hello all, I recently acquired a server with "unlimited" (not unmetered) bandwidth on a non-Hetzner/OVH/Scaleway network, but the pipe is just 100mbit (and will be saturated at some points by personal traffic bursts). That being said, I expect the 100mbit pipe to be idle 90% of the time, so it doesn't seem ideal to just set a low BandwidthRate. The documentation [1] for relay bandwidth shaping options points to a script to de-prioritize Tor traffic to ensure that personal traffic takes precedence. However, the script no longer exists within Tor source code. [2] Is this script now deprecated? If not, where can I find it? If so, what alternative methods might exist to de-prioritize Tor traffic during bursts from personal traffic pipes on Linux or BSD systems? Thanks all! -- Links [1] https://support.torproject.org/operators/bandwidth-shaping/ [2] https://gitweb.torproject.org/tor.git/tree/contrib/operator-tools/linux-tor…

3 2

new installation of an established TOR relay
by RJ Hofmann 28 Dec '20

28 Dec '20

Hello there, caused by a temporary failure of the raspberry I had to completely renew installation of my TOR relay nicknamed mosaik. The new installtion is already up and running, but since I had no copies of keys and fingerprints the new relay is completely new in terms of consensus weight etc.. I wonder if it is helpful in any way to inform you about this change as to accelerate the relay’s „reputation“ to make it fully functional for the community on the fast track. Anyway the relay will work its way up to its former capabilities. The old relay named „mosaik“ (see screenshot) is no longer existing, the new one is now called „kitchenaid“ (see screenshot) and active at its former speed. with best wishes RJH ______________________________ ______________________________

3 2

Re: [tor-relays] new installation of an established TOR relay (RJ Hofmann)
by Wilton Gorske 28 Dec '20

28 Dec '20

Hey RJH, Yep. This has happened to me with my Raspberry Pi too (nickname: mutualaid). Be sure you make a copy somewhere safe of kitchenaid's keys found in /var/lib/tor/keys to pick up where you left off next time. Given the network's extra capacity, I doubt core developers and the community will focus on finding a way to fasttrack a relay's reputation, let alone backing up the private keys in a secure way. It's up to relay operators to create copies of their keys. Alternatively, you can also just do period backups of the entire SD card for the Raspberry Pi relay. Either way, thanks for running one. In solidarity, Wilton tor-relays-request(a)lists.torproject.org: > Message: 2 > Date: Sun, 27 Dec 2020 13:50:03 +0100 > From: RJ Hofmann<cepa(a)weltzustand.de> > To:tor-relays@lists.torproject.org > Subject: [tor-relays] new installation of an established TOR relay > Message-ID:<04381F44-8483-4ACE-8928-6E008FB885B5(a)weltzustand.de> > Content-Type: text/plain; charset="utf-8" > > Hello there, > > caused by a temporary failure of the raspberry I had to completely renew installation of my TOR relay nicknamed mosaik. > > The new installtion is already up and running, but since I had no copies of keys and fingerprints the new relay is completely new in terms of consensus weight etc.. > > I wonder if it is helpful in any way to inform you about this change as to accelerate the relay?s ?reputation? to make it fully functional for the community on the fast track. > > Anyway the relay will work its way up to its former capabilities. > > The old relay named ?mosaik? (see screenshot) is no longer existing, the new one is now called ?kitchenaid? (see screenshot) and active at its former speed. > > with best wishes > RJH > >

1 0

Re: [tor-relays] Help with new relay
by lists＠for-privacy.net 22 Dec '20

22 Dec '20

On 21.12.2020 08:31, Thomas wrote: > It works fine when I run it as sudo, but according to its output, it > "isn't a good idea, nor should it be necessary." So my first question > is: How do I go about getting Nyx to connect to Tor's control socket > as a standard, non-sudo process? That will be FAQ in this list ;-) You have to add yourself to the Tor user 'debian-tor' group. (_tor-00, _tor-01,... if you set up several instances. see below) adduser user_name group_name or usermod -aG user_name group_name usermod -aG debian-tor user > My second question revolves around running the Tor daemon as a > service. It seems as if, again, I need to run it as root to make it > work, otherwise it gives me permission denied errors. What I want is > to be able to run 2 consecutive nodes on different accounts; that way > I can be more safe and secure while running my relay. If that's able > to happen, how would I go about configuring my relay daemons to be > separate, i.e. where would I put my torrc? Create 2 or more Tor instances: ~$ apt install tor-instances installs a helper script on a Debian or Ubuntu system. On other distributions you have to do all of this by hand what this script does! ~$ systemctl stop tor ~$ tor-instance-create 00 ~$ tor-instance-create 01 ~$ ... ~$ systemctl enable tor@00 ~$ systemctl enable tor@01 ~$ ... ~$ systemctl mask tor@default ~$ nano /etc/tor/instances/00/torrc ~$ nano /etc/tor/instances/01/torrc ~$ ... ~$ systemctl start tor@00 ~$ systemctl start tor@01 ... To see if the tor daemon is running: systemctl status _tor@00 systemctl status _tor@01 or '~$ journalctl -xe' to see if everything is ok I wrote it a little more in detail in the PIVX forum. Ignore the PIVX stuff: https://forum.pivx.org/threads/howto-setup-masternode-or-staker-wallet-behi… -- ╰_╯ Ciao Marco! Debian GNU/Linux It's free software and it gives you freedom!

1 0

Re: [tor-relays] Question: RAM requirement for an exit relay
by BRBfGWMz 21 Dec '20

21 Dec '20

Olaf is right Get a $ 5 per month VPS On Wed, Dec 16, 2020 at 08:28 AM, Olaf Grimm <jeep665(a)posteo.de> wrote: > Hello Amadeus! > > When you talk about a RasPi, I assume you mean a home location. > Please read the recommendations. Never operate an Exit Relay at home! > It will be expensive if the wrong people knock on the door. > > By the way, for an Exit Relay the bandwidth should already be 10MBit/s > or better. > > Olaf > > Am 15.12.20 um 01:44 schrieb Amadeus Ramazotti: > > hey, > > partly related to original question: > > I'm planning to set up a new exit. My very first relay. I'm planning to > use a small SoC with 2GB ram. Something running on ARM like a raspberry pi. > > > > Is this feasible or even a good idea? > > > > Regards > > > > > > On 14 Dec 2020, at 15:10, torix(a)protonmail.com wrote: > > > > I have several 1 G RAM exits running unbound without a problem. They never > seem to hit swap, either. On FreeBSD: > > last pid: 83973; load averages: 0.86, 0.71, 0.62 up 130+15:44:28 16:02:04 > > 23 processes: 2 running, 21 sleeping > > CPU: 43.1% user, 0.0% nice, 2.7% system, 5.5% interrupt, 48.6% idle > > Mem: 101M Active, 734M Inact, 444M Wired, 151M Buf, 210M Free > > Swap: 512M Total, 512M Free > > > > Go for it, > > > > \--Torix > > > > > > Original Message > >> On Monday, December 14, 2020 1:11 PM, <lists(a)for-privacy.net> wrote: > >> > >>> On 14.12.2020 13:58, lists(a)for-privacy.net wrote: > >>> > >>> grep VmPeak/proc/$PID/status = 181836 kB > >> A non exit has less: > >> grep VmPeak/proc/$PID/status = 57336 kB > >> tor-proxy-02.for-privacy.net ^^ > >> > >> > \----------------------------------------------------------------------------------------------- > >> > >> p_o Ciao Marco! > >> > >> Debian GNU/Linux > >> > >> It's free software and it gives you freedom! > >> > >> tor-relays mailing list > >> tor-relays(a)lists.torproject.org > >> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > > > > _______________________________________________ > > tor-relays mailing list > > tor-relays(a)lists.torproject.org > > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > > _______________________________________________ > > tor-relays mailing list > > tor-relays(a)lists.torproject.org > > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > > > _______________________________________________ > tor-relays mailing list > tor-relays(a)lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > \-- Sent using MsgSafe.io's Free Plan Private, encrypted, online communication For everyone. https://www.msgsafe.io

4 4

Help with new relay
by Thomas 21 Dec '20

21 Dec '20

Hi all! I'm a fairly new relay operator and I have a few questions regarding some of the nitty-gritty setup on Debian. I've set it up a couple times before, but I can't seem to be able to run my relay as non-root. Every time I boot up Nyx without using sudo, it says We were unable to read tor's authentication cookie... Path: /run/tor/control.authcookie Issue: Authentication failed: unable to read '/run/tor/control.authcookie' ([Errno 13] Permission denied: '/run/tor/control.authcookie') It works fine when I run it as sudo, but according to its output, it "isn't a good idea, nor should it be necessary." So my first question is: How do I go about getting Nyx to connect to Tor's control socket as a standard, non-sudo process? My second question revolves around running the Tor daemon as a service. It seems as if, again, I need to run it as root to make it work, otherwise it gives me permission denied errors. What I want is to be able to run 2 consecutive nodes on different accounts; that way I can be more safe and secure while running my relay. If that's able to happen, how would I go about configuring my relay daemons to be separate, i.e. where would I put my torrc? Any help would be much appreciated. Thanks! Thomas

1 0

Well, that escalated quickly
by enrollado 17 Dec '20

17 Dec '20

Hello all. I started an exit relay on Saturday. Last night I took a look at the log and I saw something like 30 active circuits at the heartbeat and the relay had passed a few tens of megabytes. I just logged in and saw 8,000 active circuits at the heartbeat and > 2 GB passed. Is it normal for an exit relay to suddenly ramp up like that? Just curious. Sent with ProtonMail Secure Email.

4 3