Hello.
Tor at 1AEO wrote:
Currently, looks like two main issues and a minor third issue for
forest18
Right now the biggest issue is that, although they unblocked the IPs not
too long ago, they've been re-blocked and they are now "looking into the
issue". Hopefully they will unblock them again.
2) Fast flag: The speed is also very slow, shown by very low bandwidth
scanner results from the 6 bandwidth directory authorities (Consensus
Weight from Authorities, i.e. "Cons Wt" in source below).
I'm having that problem with many of my relays. The relay's CPU and port
are absolutely capable of handling a sustained 100 Mbps. From what I
understand, the problem is that the bandwidth authorities are mostly
concentrated in the Americas and western Europe, so they mistake high
latency for poor bandwidth capacity. I don't know how to fix that. I
assume running multiple relays on the same VPS would help, although that
seems to me like a crappy hack to patch up a real problem.
Meanwhile, of the 33 VPSes I have, each of the 3 in the Netherlands that
I bought on a Black Friday sale simply because they were cheap pass more
traffic than all my non-US, non-EU servers combined, despite scoring a
bit low on speedtests. It would be nice if authorities simply increased
the consensus weight of distant servers proportional to their distance.
It's a bit discouraging to run a relay in South Africa for months and
have it pass 0.4 MiB/s when a server in Europe for a fraction of the
price and a slower network port and CPU passes 12 MiB/s after just a few
weeks.
3) Uptime: Relay reports and operator directly controls, also shows
low, ~2 days.
I brought all my servers down for a few hours recently. That could be
the reason for that.
···
_______________________________________________
tor-relays mailing list -- tor-relays@lists.torproject.org
To unsubscribe send an email to tor-relays-leave@lists.torproject.org