Jake Visser wrote:
Thanks Roger - that was a palm facing moment for me... I thought I had all the ND issues with IPv6 fixed, but apparently not... those 4 were not accessible externally on V6.
I just corrected and will see if they start registering 😊
Thanks for running relays! Well, it happens. Wasn't your fault entirely, Tor currently doesn't have an IPv6 discovery and reach-ability testing mechanism, but hopefully will have soon.
To make it even worse, Tor allows you to specify an advertised IPv6 address even if you have no IPv6 listening socket on the host running the Tor instance:
https://trac.torproject.org/projects/tor/ticket/29570
Some think this is not a bug, and it should stay like this. I think it only makes such accidental configurations or mistakes harder to track down by operators.
Thanks again,
Jake
-----Original Message----- From: tor-relays tor-relays-bounces@lists.torproject.org On Behalf Of Roger Dingledine Sent: Thursday, April 18, 2019 11:11 AM To: tor-relays@lists.torproject.org Subject: Re: [tor-relays] Debugging relays not showing online
On Thu, Apr 18, 2019 at 05:52:48PM +0000, Jake Visser wrote:
I am looking for some help in debugging a strange one.... EO runs ~30ish relays in our /24; but we currently have 4 relays that don't want to play nice and are reporting offline (although look to be online).
The effected relay IPs are:
23.129.64.157 23.129.64.164 23.129.64.170 23.129.64.174
Whenever I see strange issues like this, my first thought is whether the relay advertises an IPv6 address, yet it's unreachable there.
Tor is pretty good at self-testing its IPv4 addresses, but it just trusts you that your IPv6 address works.
And then only some of the directory authorities have IPv6 support, but these days it's a majority of them, so you won't get the Running flag (i.e. won't be in the consensus) if your advertised IPv6 address doesn't work.
Finally -- this is very good! It was about time.