[tor-relays] Trying to set up a relay at home, but get no connections

r1610091651 r1610091651 at telenet.be
Mon Jun 11 19:34:55 UTC 2018


On Mon, 11 Jun 2018 at 20:30 Gunnar Wolf <gwolf at iiec.unam.mx> wrote:

> Graeme Neilson dijo [Sat, Jun 09, 2018 at 11:53:20AM +1200]:
> > See if you can route to all the authorities.
> > Tor requires that all relays are able to contact all directory
> authorities.
> >
> > In my case tcptraceroute would not get to all the authorities. For some
> > authorities my ISP was not routing to them.
>
> This seems to be the issue - I'm attaching a screenshot of «mtr»
> trying to reach all of the directory authorities from said server.
>
> So, it seems my ISP does not want us to run relays ☹ Can you think of
> any way my connection (oversized for my regular uses) can be put to
> use for Tor? I guess it would not work as a bridge either, would it?
> _______________________________________________
> tor-relays mailing list
> tor-relays at lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays


Hi

Traceroute requires support by all hops on the way, and that's not a given.
Try pinging the DA's instead or connecting to their tor ports.

Only Dizum doesn't respond to ping requests, but it has a "welcome" page on
80.

dannenberg dannenberg.torauth.de 193.23.244.244 80 443
tor26 86.59.21.38 86.59.21.38 80 443
longclaw 199.58.81.140 199.58.81.140 80 443
bastet 204.13.164.118 204.13.164.118 80 443
maatuska 171.25.193.9 171.25.193.9 443 80
moria1 128.31.0.34 128.31.0.34 9131 9101
dizum 194.109.206.212 194.109.206.212 80 443
gabelmoo 131.188.40.189 131.188.40.189 80 443
Faravahar 154.35.175.225 154.35.175.225 80 443

Regards
Seb
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20180611/ca068548/attachment.html>


More information about the tor-relays mailing list