tor-relays November 2021

tor-relays@lists.torproject.org

39 participants
34 discussions

Tor on cloud VPS
by potlatch 12 Nov '21

12 Nov '21

Hello All, My VPS host recently moved one of my Tor exits to cloud ops (I believe AWS). Since that time the instance will not function as an exit. Torcc and keys are as before. I was operating on Ubuntu 21.04 but reloaded to 20.04. Still the same. I messed with the netplan config to no avail. George brought this to my attention and suggested (and I agree) a DNS problem. I can't find where it's failing--to be honest I don't have much experience with cloud instances or netplan. I am of the opinion that there is a conflict between the cloud hosting and Tor. When I call Nyx I see the strange exit policy: reject [FC00:'string of zeros']/7:*, reject [FE80:'string of zeros off of Nyx page']. Other exits I operate are fine in the cloud. Thanks for any help you can provide. potlatch Sent with [ProtonMail](https://protonmail.com/) Secure Email.

2 1

Re: [tor-relays] Tor website
by failing.flyaway443＠mailer.me 11 Nov '21

11 Nov '21

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Sorry, it was not my intention to interfere. $man tor I forgot to mention, that works too of course. Or in this case $man torrc. I already run a relay myself, after several "failed" attempts on cheap VPS now on a root server with unlimited traffic and extremely fast connection. This one: https://metrics.torproject.org/rs.html#details/D1F7BEC34A66498FC565BC057632… I had to take the VPS' offline because they could not handle the traffic I would like to relay. Maybe I'll run a much smaller second relay, I'm still thinking about that. As I said, it was not my intention to provide links to outdated ressources. Won't happen again :) All the best... 95C6676453094B229C4EDB34ABA333DFF432E1DD -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEElcZnZFMJSyKcTts0q6Mz3/Qy4d0FAmGNCJkACgkQq6Mz3/Qy 4d1CLA//UtJzIdphbucuqAY5o4P3K+R4pgqooY9bgsOO9G/A1Ra+hVe2d7yBhESH FnoCsuIAKjBJRX30W8AQIh4R6amwhCLRgrdhacfHFtgjksxKavqXQ3bwS7RfnbZ5 R0V2QDSFyulhwsqIvqKF30WE/Ks3niimQS7nPHzgXRxrBV3yUW0ldw6/tNhS8G+T L6QB0/GuVnZlRat285Y2mx5wX8MAxqoowD3YFI8i1HGEf4IZayyXzQxZobaTlFN9 PcGrZUCgw26N6jDknlpc81ZbX1ZKeeFrcQunl3/LXxE225oASQBoasPmHbTpO2QO wOYbqCJ3eptPZq1e4jvzC0MnBG2nVFH7BcJ4/f7TbrvAhZqxEzvQqHNU/r7s/4Le YzJrEhadxUKESO5W7XGMQdaxlY670JolP1yRL7x3Ese8EgtugKM3BZXMr5w1EAby x6erAiuj+36GEuR8IiXB2bqHJ1GeQmXWOh0lSFdJri9SthF8KYC4jlEvHtvib0wJ NsdaBAEQ2DhgiDtCp9HNDAiDeHf6QanFt+1JGEuKno1HMYzky2rxmYonNcoxfXX0 KnqFKKxn7F78RpTXbioWB4/4MqMUZpV0SWl5LUS/v4zY4B26W9gxQ6/FPGq0a8zs Zeei9AK1gMg+NeFSajC1FSVDncbEEFYKqNryEGMPzrD2b5RVSms= =zzGy -----END PGP SIGNATURE-----

1 0

Tor website
by potlatch 11 Nov '21

11 Nov '21

Hello, Does the new Tor web configuration have an overall site map or index page? I can't find the old page with the manual for torrc. I've had trouble finding other information over the past few weeks as well. Thanks, potlatch Sent with ProtonMail Secure Email.

1 0

A Simple Web of Trust for Tor Relay Operator IDs
by nusenu 10 Nov '21

10 Nov '21

Hi, I wrote down a spec for a simple web of trust for relay operator IDs: https://gitlab.torproject.org/nusenu/torspec/-/blob/simple-wot-for-relay-op… This is related to: https://gitlab.torproject.org/tpo/network-health/metrics/relay-search/-/iss… https://lists.torproject.org/pipermail/tor-relays/2020-July/018656.html kind regards, nusenu -- https://nusenu.github.io

5 9

Crashed Relay
by sysmanager7 10 Nov '21

10 Nov '21

I was notified by Uptime Robot that relay 1 of 3 had been shut down. Unfortunately I found this out 12 hours after the fact. guard flag is lost. journalctl -u tor@default Nov 01 01:03:18 ubuntu-s-1vcpu-2gb-nyc1-01 Tor[328387]: I learned some more directory information, but not enough to build a circuit: We need more microdescrors: we have 6178/6618, and can only build 49% of likely paths. (We have 99% of guards bw, 50% of midpoint bw, and 98% of exit bw = 49% of path bw.) ptors: we have 6178/6618, and can only build 49% of likely paths. (We have 99% of guards bw, 50% of midpoint bw, and 98% of exit bw = 49% of path bw.) ived 4371.61 GB. I've received 7345604 connections on IPv4 and 0 on IPv6. I've made 677780 connections with IPv4 and 0 with IPv6. Nov 01 06:47:26 ubuntu-s-1vcpu-2gb-nyc1-01 Tor[328387]: Interrupt: we have stopped accepting new connections, and will shut down in 30 seconds. Interrupt aga> Nov 01 06:47:26 ubuntu-s-1vcpu-2gb-nyc1-01 Tor[328387]: Delaying directory fetches: We are hibernating or shutting down. Nov 01 06:47:56 ubuntu-s-1vcpu-2gb-nyc1-01 Tor[328387]: Clean shutdown finished. Exiting. Nov 01 06:48:04 ubuntu-s-1vcpu-2gb-nyc1-01 systemd[1]: tor(a)default.service: Succeeded. Nov 01 06:48:04 ubuntu-s-1vcpu-2gb-nyc1-01 systemd[1]: Stopped Anonymizing overlay network for TCP. This is NOT a first time for the above on this relay, more like a 7th or 8th. CPU usage according to NYX is 90/95%. That has been the last three weeks or so. Prior to that, average CPU usage was 30% or less. Current BW/Burst is 3/4 MBs on torrc and nyx. Prior was BW/Burst 4/5 *Me - retired fixed income. Average billing for 3 Digital Ocean Droplets was $40. budget is good with that. Octobers billing - $87.50 I used 10 gb instead of 6Gb. Essentially a $40 overage. It's almost as if, torrc and nyx are being ignored. Sent with [ProtonMail](https://protonmail.com/) Secure Email.

3 2

Re: [tor-relays] Hardware requirements for a fast Tor relay
by failing.flyaway443＠mailer.me 10 Nov '21

10 Nov '21

Hi Gary, thank you for your response. I think I just worry too much. I watched my relay all the time today, I had bandwidth usage of 30MB/s at times and HTOP showed me a Load average of 0.29/0.29/0.30. I know that this is totally fine for a dual core. The relay is up and running for 3 days and 8 hours now and I already moved ~700GB in each direction (upload/download). I was just concerned because the VPS started crashing after 2 weeks solid uptime, but I should have set stricter bandwith limits. You can't really compare a VM with a root server, I don't think this will happen again. It's ok for me to invest a little more and have a fast and stable relay this way. The traffic was capped with the VPS plan, this was obviously a big disadvantage, now I can use as much traffic as I want with a 2,5Gbit link (1Gbit guaranteed). For your info, the most important lines of my config: SocksPort 0 Log notice file /var/log... Log debug file /var/log... ORPort 443 RelayBandwithRate 1000Mbit RelayBandwithBurst 1000Mbit Exit policy reject *:* ContactInfo & Nickname set, of course... ;) Is there anything I should change? Thanks for your help! Best Regards...

2 1

Re: [tor-relays] Hardware requirements for a fast Tor relay
by failing.flyaway443＠mailer.me 10 Nov '21

10 Nov '21

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 I'm sorry that I now spam the mailing list, but I made a mistake. I'm of course NOT logging at debug level, it's just one logfile (notices.log). I logged debug when I was running the relay on the VPS because I wanted to know why it crashed all the time, but all that happened was that my 20TB SSD was maxed out within two hours and I had to reboot to get rid of the old logfiles. My bad, please don't think I write a debug log, that's completely pointless. Why would I. I rented a pretty expensive root server because I think Tor is really important and I want to relay as much traffic as possible, not to log debug messages. This was obviously not correct, but the rest of my torrc looks as described above. By the way, my relay has now around 4000 incoming and 4000 outgoing connections and a throughput of almost 1TB/day, and the load averages are still below .40. Everything looks good. :) Have a nice day, everyone! -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEElcZnZFMJSyKcTts0q6Mz3/Qy4d0FAmGLxa0ACgkQq6Mz3/Qy 4d1vJhAArWytI9hG6iGIvVzUP6lOgLMCEVfn4KBiFzq0iGqr2ex+utWIt8gek3SX Bm9McRbicgDUSzbnrHJrPzKxrpYvvtABbApyDZDSOEwgSXeaUcE2J8jhk20fOA6u tLFf7S+ON88KW8HkwNIkqSFmRifp3dZEBOapFZnBfgREwu19qxg1iyYZfJHDIMd6 4vWzI5oo2D1iFTyCDZllduqEURZNgZRfwtNk8ydfOje9X0QMkHgzy4fECCNgcYdY to+1BbYxY2lT34+1aLoRnnyA2yLykYI2ivRNx+IyD9X/QCKq+3sV+xjRvyOH39r7 Tmvg8NTNuZCiEwi9JCIJlRynrFk3HgUTbCT87iK8PGMTG6TimnBvFKUfKQMwIicD 1YrLQ30hSjTnetRbyLT0B7gd+h+CkDg6ssi0j6eKV0urP6PTipnr19OJeBZ3kZbw j+a3qipxy3mNIp9dW9d+ZBzhV+jtrDUMKUpjqHUkUEEdNH060TSMyYMBwCf7/dgH Ft8FWgTcLtX9dohx/CAHfQ+8rsa/wYEuLnXgc3AXibof9VZaTMKz5iDkhUwOnCoA 0528RNKLH+Rf4CoMOCycjqW0k1svPX9oAXoOgX0GQz/1DnocA4DEs+wVPJmr6dR+ mcHwDiKlOd5ksARl+fivmHurUE+ULzhI8l+Cdhr+Wi7NzVzuZ5U= =s8hY -----END PGP SIGNATURE-----

1 0

Re: [tor-relays] Hardware requirements for a fast Tor relay
by failing.flyaway443＠mailer.me 09 Nov '21

09 Nov '21

I just read this research paper, maybe it's worth thinking about some kind of implementation of this approach some time in the future. It's an interesting read anyway. uwspace.uwaterloo.ca/bitstream/handle/10012/16108/Engler_Steven.pdf Regards

1 0

Hardware requirements for a fast Tor relay
by failing.flyaway443＠mailer.me 09 Nov '21

09 Nov '21

Hi everyone, about two weeks ago, I signed up for a VPS with a cloud provider and set up a Tor relay. I installed Debian 11 Bullseye, secured it, and then set up Tor 0.4.6.8 and started the relay. The VPS had the following specs: 1vCore, 2GB RAM, 40TB traffic per month on a 1Gbit/s link. I throttled the traffic accordingly so that the monthly limit of 40TB would not be exceeded. Nevertheless, the CPU load was extreme, the server was running at full capacity and crashed several times. Since I want to help the Tor network with a fast relay I now signed up for a root server which has the following specs: Dual core CPU, 8GB ECC RAM, 2,5Gbit link, 1Gbit guaranteed, unlimited traffic. I set this thing up with Debian 11 Bullseye again and Tor 0.4.6.8. Since my bandwith gets throttled when I use more than a certain amount of traffic/month and at the same time (!) on average more than a certain amount of bandwith for more than one hour, I set the MaxBandwith to 1000Mbit/sec (equals 125MB/sec). This relay is up and running for a few days now, and I already have around 4000 incoming and outgoing connections. My bandwith is not fully used yet, but sometimes I see spikes of 20MB/s. What concerns me is that the CPU load again is sometimes 40-50% on both cores, even though this relay is not fully used yet. Can somebody tell me if it is even possible to run such a fast relay on this hardware? Should I set a more restrictive bandwith throttle myself, or go for a quad core CPU? I don't think I will ever run out of RAM this time, since I have 8GB. Thank you for your advice! All the best!

2 1

metrics: add `IPv6 Exit Address` in addition to `Exit Address`
by s7r 09 Nov '21

09 Nov '21

Hello, Currently we have Exit Address for relays that use a different IPv4 address for `Exit` connections vs their ORPort IPv4 address. Similarly, one relay *could* listen on a certain IPv6 address ORPort but use a different IPv6 address for v6 exiting. Wouldn't it be useful to add this data too? This would tell us how many relays use one static IPv6 address for ORPort connections and temporary IPv6 addresses for exiting (using IPv6 privacy extensions). By looking at https://metrics.torproject.org/relays-ipv6.html one could assume that almost 50% of the IPv6 enabled relays (IPv6 ORPort) are exits.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-relays November 2021