It's surprising that you're running into CPU issues. It's typically RAM that is
exhausted first.
I have 5 x Dual Core 256MB Tor Relay Nodes loadbalanced as a Single Middle
Relay that never have CPU issues. It's always a matter of running out of RAM
for me. The loadbalanced Tor Relay maintai
Hello everyone!
Some of you might have noticed that there is a visible drop of relays on
our consensus-health website.[1] The reason for that is that we kicked
roughly 600 non-exit relays out of the network yesterday. In fact, only
a small fraction of them had the guard flag, so the vast major
Anders Trier Olesen:
The Tor relay guide should recommend running your recursive resolver
(unbound) on a different IP than your exit:
https://community.torproject.org/relay/setup/exit/
yes, that is a good idea, here is a PR for it:
https://github.com/torproject/community/pull/169/files
--
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 throt
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
Hello all,
I would have to agree on this it appears that the DNS failure timeout is
too low. I have more then enough bandwidth to host tor exit nodes, and
my own unbound full recursive relay and yet i still get the timeout
message 1-1.5%. Sometimes even weird amounts such as 40-50%.
I have be
