Hey,
for future reference, might be an libressl issue, see "[tor-relays] Dropped off
consensus (0.4.4.5) - reason is Libressl 3.2.1"
thread:
https://lists.torproject.org/pipermail/tor-relays/2020-September/018916.html
Will continue there.
On 29.07.20 05:30, Sebastian Hahn wrote:
> Hi there,
Hi there,
> On 28. Jul 2020, at 22:33, Fran wrote:
>
> thanks @Torix for the IPv6 suggestion, all auth were reachable via v6, but
> for testing I turned of IPv6 in the tor config - no change.
I can indeed ping both of your IPv4 and IPv6 from gabelmoo right now,
but this is potentially a
Hey,
thanks @Torix for the IPv6 suggestion, all auth were reachable via v6, but for
testing I turned of IPv6 in the tor config - no change.
So today I found some time for a deeper investigation.
Let's have a look at the latest votes of some auths:
moria1:
> r systemli
Dear Fran,
I now see no entry at all to your relay in the tor metrics. Am I correct in
saying that you are running ipv6 as well as 4? I have had problems with a
host's ipv6 connectivity and discovered somewhere in the docs a ping6 test of
all the bwauths you might try:
ing6 -c2
>> the machine has it's own global unicast ipv4 and ipv6 addresses.
I don't know for sure, but possibly that's causing the issue? I do know tor
uses one IP address for relays, so if it is detecting several different IPS
that may be confusing it.
It's only a thought.
--Keifer
On Tue, Jul 21,
It is worth noting, tor conscious does not immediately update. It can take
40 minutes up to about 3 hours for an operating status update to appear in
the conscious based on my experience from the bridge and middle relay I run.
>> Your relay has a very large number of connections to other relays.
Hello,
I'm taking care of a server of a friend who's on holiday. The server is up and
running but not part of the consensus.
As beeing instructed I updated to the lastest OpenBSD snapshot when I saw that
a new tor release is available (Tor 0.4.3.5 on OpenBSD).
Excerpts from the log:
Jul 13
