Hello.
Georg Koppen wrote:
But it seems a majority of directory authorities can't talk to it. If
you look at https://consensus-health.torproject.org/ and enter your
fingerprint at the bottom then you can see what each authority thinks
of your relay. Only 3/9 deem it to be running at this point.
Well that's odd. The relay is in India. Is there a possibility that it
is being blocked by them? Is that a known issue in India? I seem to be
unable to reach to moria1, gabelmoo, dannenberg, maatuska, longclaw, or
bastet, either with ICMP or HTTP.
According to traceroute, it manages four hops out of thirty:
1. _gateway (160.250.225.1)
2. 85.209.161.0 (85.209.161.0)
3. 180.150.241.241 (180.150.241.241)
4. 14.143.30.73.static-delhi.vsnl.net.in (14.143.30.73)
After that, the trail is lost. This is the same for all of the affected
authorities. I haven't noticed any other connectivity issues.
I will try contacting my hosting provider and requesting that they get
these IPs unblocked and, if they are unable to (they may very well not
be in charge of the blocks), move me to a new location.
Marco Moock wrote:
On which ports is it listening?
Only 160.250.225.3:9001. All others are blocked with nftables. Only the
ICMP messages echo-request, destination-unreachable, time-exceeded, and
parameter-problem are accepted. This configuration is used on all of my
relays, and the rest have no reachability issues.
Can you seen incoming traffic and are the TCP handshakes successful?
I can see incoming traffic from other relays, at least enough for it to
be used as a client. It's also successfully being used as an onion
service as an alternative to simply running SSH on a non-default port.
Of course, this is expected if the only blocked IPs are a few of the
authorities while some other authorities are reachable.
Regards,
forest
···
_______________________________________________
tor-relays mailing list -- tor-relays@lists.torproject.org
To unsubscribe send an email to tor-relays-leave@lists.torproject.org