[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-relays] Re: Relay forest18 is still not on the consensus

To: tor-relays@xxxxxxxxxxxxxxxxxxxx
Subject: [tor-relays] Re: Relay forest18 is still not on the consensus
From: forest-relay-contact--- via tor-relays <tor-relays@xxxxxxxxxxxxxxxxxxxx>
Date: Fri, 12 Dec 2025 07:51:40 -0000
In-reply-to: <20251212074855.2b0e505f@ryz.dorfdsl.de>
List-id: "support and questions about running Tor relays (exit, non-exit, bridge)" <tor-relays.lists.torproject.org>
References: <20251212074855.2b0e505f@ryz.dorfdsl.de>
Reply-to: forest-relay-contact@xxxxxxxxxxxxx
User-agent: HyperKitty on https://lists.torproject.org/

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hello.

Marco Moock wrote:
> So please investigate what is going on, e.g. using traceroute on the
> TCP port of the authority.

> First investigate the issue.

I have already determined the cause of the issue, as I described in an
earlier message. The connection to several authorities is being dropped
right after it reaches 14.143.30.73.static-delhi.vsnl.net.in, according
to a traceroute (ICMP, TCP, and UDP) of all the affected authorities.

It is unlikely to be an innocent routing issue, as only the authorities
are blocked. For example, moria1 on 128.31.0.39 cannot be routed, but
128.31.0.38, which is on the same /24 on AS3, has no issues.

I am currently waiting for the hosting provider to reply back to me.

Regards,
forest
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEvLrj6cuOL+I/KdxYBh18rEKN1gsFAmk7yYkACgkQBh18rEKN
1gu2EhAAnzZmBFeqjYcoH/1RmeH3AQ7V/7Rki3Ge78T0UnRK33i1HoXr5N8shwmI
MVvrXFiC8Q2Djs6SIEiW0TDDukfmvv/kcwrjGtgpUnCp4/teVUU8wvCv3NbE6eIG
D4OpqrGaXaR7nqzqP5pHMxNJ//+b+HQk97MIMdo4Tqh4p2kFHL8whwLVNllzWP7y
5E+ryrUeGnARguwrBNtKIu+M3lP8tJd14ihWt70r0oBlkMuWt4zSlsvq5PlSfFBH
Uw6ZForsJuO7IhLfApr7xKpIBOlglPNb8WBQ+E5SUZehpBEPoJatX5d1XUJe4aGS
96t8sfaanBuSduHYVsQXzWyASatYfOEWms5NANOc54QphkVztHH+FDbpVeQzxO9l
l9cfGhzPWOrA7U4bmj+BaqfH+NchH/yre81+goPMN5c4PbQgeSZAzNrE5SCgGYQE
2nwaABM8n5tQF4mcl+Z97S1STHZOIaCx8cOkyrZ4in3dUDuYI9XQw7enIoo0dBMa
c3PYfUfkoO3agEK37TFhu+prMiHfh3r6eYW7SykBERdg1hMgLAg6XXaQwVfftDQA
fxQcHs31rjBu1d49fGR1jnq6Oc2GgHEQ8GeMbHfKXjUNaJAb37HVioCV6SttXxiM
0s3oDzifwcig854MyZke9DL5mWw+GsnFwqjGptCxOoIg1rL2cRk=
=HS5h
-----END PGP SIGNATURE-----
_______________________________________________
tor-relays mailing list -- tor-relays@xxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to tor-relays-leave@xxxxxxxxxxxxxxxxxxxx

Follow-Ups:
- [tor-relays] Re: Relay forest18 is still not on the consensus
  - From: forest-relay-contact--- via tor-relays

References:
- [tor-relays] Re: Relay forest18 is still not on the consensus
  - From: Marco Moock via tor-relays

Prev by Author: [tor-relays] Re: Relay forest18 is still not on the consensus
Next by Author: [tor-relays] Re: Relay forest18 is still not on the consensus
Previous by thread: [tor-relays] Re: Relay forest18 is still not on the consensus
Next by thread: [tor-relays] Re: Relay forest18 is still not on the consensus
Index(es):
- Author
- Thread