ok, maybe i haven't waited that long. I will put it back and come back to you in a couple of days. I must say I would be surprised it would take so long to check connectivity.
On Sat, Feb 23, 2019 at 4:02 PM Blicky tor@blicky.net wrote:
Hi,
For how long have you advertised the v6 address? My relays also received the UnreachableIpv6 flag shortly after I setup IPv6, but after 24 hours that automatically turned into ReachableIPv6. I'm guessing it takes some time for the measurements to take place and propagate.
I can reach your IPv6 address on that port, so the network configuration is fine, at least.
Regards,
Blicky.
On 2019-02-23, Charly Ghislain wrote:
Hi all,
My tor relay has got the UnreachableIpv6 flag set once i mentionned an OrPort with my ipv6 address.
From what i can tell, my server is reachable over ipv6, and can contact
the
directory authorities through ipv6 (following the instructions found
there:
https://trac.torproject.org/projects/tor/wiki/TorRelayGuide#Makesurerelaypor...
).
The node is behind an haproxy that relays ipv6 traffic to natted ipv4
(with
no logging for those concerned). It seems to work fine for web content
over
ipv6, and traffic on both ips (v4 and v6) goes through this channel.
I can successfully telnet my node ORPort using my v6 address. The ports have been defined this way in torrc: ORPort 0.0.0.0:9001 NoAdvertise ORPort 91.121.79.188:9001 NoListen ORPort [2001:41d0:1:84bc::1]:9001 NoListen
Is there a way to make a tor client connect to a specific relay to debug this kind of connectivity issues? Or any other mean?
In the meantime ive removed the advertized ip6.
Regards,
Charly
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays