Hi all,
I have been operating the relays
- Bazinga B198C0B4B8C551F174FBB841A172616E3DB3124D
- JPsi2 F6EC46933CE8D4FAD5CCDAA8B1C5A377685FC521
for about 10 years.
The hosting provider stops providing their current service and their
successor services are not Tor-friendly anymore.
Hence, these
On Sun, 28 Aug 2022 13:46:00 +0200
Ole Rydahl via tor-relays wrote:
> Since 2014 I have run a non-exit relay at my premises. However ultimo
> July the system load increased abruptly. Idle-cpu -typically 60-70% -
> dropped to 30%, _and_ with frequent drops to 0!
>
> I reduced the max bandwidth
Hi all,
In the effort of deploying obfs4 bridges for the community we are sharing our
Ansible role that allowed us to deploy multiple nodes:
https://github.com/NewNewYorkBridges/ansible-tor-bridge
For now it is only available on Debian but we will make it available for other
distributions.
Elias via tor-relays wrote:
> This is actually not a "real" root server, it's a KVM server (of
> course). The CPU is an AMD EPYC 7702 with 2 dedicated cores per
> server@3,35GHz.
Since this is virtualization, make sure that features such as AES
acceleration are active.
The number of cores is
> I have three relays running Hardened BSD hosted at Frantech. They do
> not offer support for setting up IPv6.
By Frantech do you mean buyvm.net ?
If it works the same way as buyvm, your VM should have a single public
IPv6 address. You can request a /48 or /56 prefix to be routed to that
public
