Re: [tor-relays] tor relay ipv6

["Matt Westfall" <mwestfall@xxxxxxxxxxx>]

I can traceroute to your ipv6 address:

traceroute to 2a03:e2c0:bc7::2 (2a03:e2c0:bc7::2), 30 hops max, 80 byte packets
 1  2001:559:800c:1900::5a01 (2001:559:800c:1900::5a01)  0.356 ms  0.345 ms  0.449 ms
 2  2001:558:180:1c::1 (2001:558:180:1c::1)  0.317 ms  0.435 ms  0.429 ms
 3  2001:558:180:36::1 (2001:558:180:36::1)  7.756 ms  7.763 ms  7.864 ms
 4  be-21508-cr02.ashburn.va.ibone.comcast.net (2001:558:0:f6cd::1)  10.873 ms * *
 5  * * *
 6  * * *
 7  * * *
 8  lo-0-v6.ear4.frankfurt1.level3.net (2001:1900:2::3:12b)  96.479 ms  96.505 ms  96.654 ms
 9  2001:1900:5:2:2::5be2 (2001:1900:5:2:2::5be2)  108.774 ms  108.757 ms  108.757 ms
10  rt.mr.msk.ru.retn.net (2a02:2d8::57f5:e005)  141.933 ms  142.148 ms  141.996 ms
11  gw-mediaserviceplus.retn.net (2a02:2d8:0:82a:232a::1)  136.907 ms  136.871 ms  136.670 ms
12  2a04:5200::5555 (2a04:5200::5555)  142.424 ms  141.550 ms  141.963 ms
13  2a03:e2c0:bc7::2 (2a03:e2c0:bc7::2)  140.933 ms  141.737 ms  141.245 ms

So perhaps your ISP is wonking with tor traffic as suggested.

Thanks,

Matt Westfall

President & CIO

ECAN Solutions, Inc.

Everything Computers and Networks

804.592.1672

------ Original Message ------

From: "teor" <teor@xxxxxxxxxx>

To: tor-relays@xxxxxxxxxxxxxxxxxxxx

Sent: 8/22/2019 7:23:03 AM

Subject: Re: [tor-relays] tor relay ipv6

Hi,

 

On 22 Aug 2019, at 20:00, Станислав <armik900@xxxxxxxxx> wrote:

 

22.08.2019, 06:57, "teor" <teor@xxxxxxxxxx>:

 

 

On 21 Aug 2019, at 23:38, armik900@xxxxxxxxx wrote:

 

hi.in relay stopped working ipv6.address is correct all pings, including tor to the servers, but relay does not work.before that it worked perfectly 2 months.

 

Please tell us your relay's fingerprint.

 

CE5ED345398CC02D573347C2F238F80B18E680EE.

 

 

Your relay's IPv6 address is not reachable from the directory authorities:

https://metrics.torproject.org/rs.html#details/CE5ED345398CC02D573347C2F238F80B18E680EE

 

All 6 directory authorities on IPv6 can't reach your relay on IPv6:

https://consensus-health.torproject.org/consensus-health-2019-08-22-10-00.html#CE5ED345398CC02D573347C2F238F80B18E680EE

 

But your relay is still reachable over IPv4 from the 3 directory authorities

that don't have IPv6.

 

Please copy and paste the notice-level logs that tor creates on startup,

from launch to the end of the ORPort and DirPort reachability checks.

 

And your relay is reachable over IPv6 on its ORPort and DirPort from at least

one relay in the tor network.

 

It looks like your torrc matches your local network config.

 

Please copy and paste your torrc, particularly the Address, ORPort, DirPort,

and OutboundBindAddress options.

 

Your torrc looks correct.

 

It can be hard to set up IPv6 for a relay, we're working on a grant to make

it easier.

 

Tor doesn't do IPv6 reachability checks yet, that's part of the grant.

 

The only issue I can see is that all 6 directory authorities on IPv6 can't

reach your relay on IPv6.

 

Has your provider stopped routing your IPv6 address to your relay?

Does your provider censor Tor over IPv6?

 

It looks like the problem is somewhere between your relay machine and

the IPv6 internet.

 

T

 

_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays