Re: [tor-relays] My Tor exit node not visible

[trinity Pointard <trinity.pointard@xxxxxxxxx>]

Hi,

By looking at the descriptor of your relay, I found it tries to bind
[::2]:9001. If I'm not mistaken this IPv6 address is in a reserved,
unroutable range. That is probably why authorities supporting IPv6
can't reach your server and vote it not running. You should make sure
your configuration does not contain `ORPort [::2]:9001` or something
similar.

Regards,

Trinity Pointard


Le mar. 20 oct. 2020 à 14:34, netaudit <netaudit@xxxxxxxxxxxxxx> a écrit :
>
> Hi thank you for your reply
>
> As per your suggestion I checked it on the link you provided.
> I can see my exit relay here:
> https://consensus-health.torproject.org/consensus-health.html
> Its cyrexlinuz EEDDDD9C (the exit one) and its on the list and it looks okay to me.
>
> I am hosting 2 node relays with nickname cyrexlinuz. One of them is exit relay other one is middle relay. Middle relay Im not experiencing any problems with it so far. The exit relay has this fingerprint EEDDDD9C8D0CE02449BA17DF99E0285CACA467B5
>
>
> But when I check this link for my exit node:
> https://metrics.torproject.org/rs.html#details/EEDDDD9C8D0CE02449BA17DF99E0285CACA467B5
>
>
> Its not there for some reason.
> I don't know. I also checked the exit relay logs for IPv6 configuration and it didn't log anything about IPv6.
>
> Thank you
>
>
> Sent with ProtonMail Secure Email.
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Monday, October 19, 2020 4:57 AM, Roger Dingledine <arma@xxxxxxxxxxxxxx> wrote:
>
> > On Sun, Oct 18, 2020 at 01:44:31PM +0000, netaudit wrote:
> >
> > > I've set up a new Tor exit node around 15 hours ago but despite it had been such a time and my exit is visible from outside world I still get little to no traffic at all. I also cannot see my servers IP on bulk tor exit node list.
> >
> > relay-search (atlas.torproject.org) is a better way to search Tor
> > relays than the bulk exit node list.
> >
> > But that said, if it has published its relay descriptor, but it isn't
> > getting enough "Running" votes to make it into the consensus, it won't
> > be on atlas.
> >
> > In that case, you can look it up by putting the identity fingerprint
> > onto the form at the bottom of
> > https://consensus-health.torproject.org/#relayinfo
> >
> > My guess is that it's the same situation as the person asking this
> > question a few days ago -- it has an IPv6 address listed, but that IPv6
> > address is not reachable, so the relay isn't getting enough "Running"
> > votes to get listed.
> >
> > Hope this helps!
> > --Roger
> >
> > tor-relays mailing list
> > tor-relays@xxxxxxxxxxxxxxxxxxxx
> > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
>
> _______________________________________________
> tor-relays mailing list
> tor-relays@xxxxxxxxxxxxxxxxxxxx
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays