[tor-relays] Tor relay says it is reachable, but is not appearing on the network.

Thu May 23 23:19:49 UTC 2019

Hi all, so this is the tor log since the last restart. It includes the
relay fingerprint. The tor version is (0.2.9.16-1). When I tried updating
tor I got a message saying that was the newest version.
The relay has an assigned static ip and port which are both allowed by the
firewall. It seems strange that
Dmitrii Tcvetkov was able to reach the relay though teor cannot, also that
the relay says it is reachable and receiving traffic but not appearing in
the relay list. It seems like the relay
would not be able to start at all if Google was blocking it. Thanks very
much for the help.

May 21 20:01:30.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
May 21 20:01:32.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
May 21 20:01:32.000 [notice] Configured to measure statistics. Look for the
*-stats files that will first be written to the data directory in 24 hours
from now.
May 21 20:01:32.000 [warn] You are running Tor as root. You don't need to,
and you probably shouldn't.
May 21 20:01:33.000 [notice] Your Tor server's identity key fingerprint is
'torworld 3A4E582092E7C6B822EC01F4D76F680F6C65B0A2'
May 21 20:01:33.000 [notice] Bootstrapped 0%: Starting
May 21 20:03:53.000 [notice] Bootstrapped 80%: Connecting to the Tor network
May 21 20:03:54.000 [notice] Guessed our IP address as 104.154.93.253
(source: 128.31.0.34).
May 21 20:03:56.000 [notice] Bootstrapped 85%: Finishing handshake with
first hop
May 21 20:03:56.000 [notice] Bootstrapped 90%: Establishing a Tor circuit
May 21 20:03:58.000 [notice] Tor has successfully opened a circuit. Looks
like client functionality is working.
May 21 20:03:58.000 [notice] Bootstrapped 100%: Done
May 21 20:03:58.000 [notice] Now checking whether ORPort
104.154.93.253:65534 is reachable... (this may take up to 20 minutes --
lookfor log messages indicating success)
May 21 20:04:01.000 [notice] Self-testing indicates your ORPort is
reachable from the outside. Excellent.
May 21 20:05:08.000 [notice] Your network connection speed appears to have
changed. Resetting timeout to 60s after 18 timeouts and 156 buildtimes.
May 21 20:05:12.000 [notice] Performing bandwidth self-test...done.
May 22 02:03:53.000 [notice] Heartbeat: It seems like we are not in the
cached consensus.
May 22 02:03:53.000 [notice] Heartbeat: Tor's uptime is 5:59 hours, with 0
circuits open. I've sent 1.13 MB and received 8.70 MB.
May 22 02:03:53.000 [notice] Average packaged cell fullness: 100.000%. TLS
write overhead: 21%
May 22 02:03:53.000 [notice] Circuit handshake stats since last time: 0/0
TAP, 22/22 NTor.
May 22 02:03:53.000 [notice] Since startup, we have initiated 0 v1
connections, 0 v2 connections, 0 v3 connections, and 29 v4 connections; and
received 1 v1 connections, 0 v2 connections, 0 v3 connections, and 21 v4
connections.
May 22 02:03:53.000 [notice] DoS mitigation since startup: 0 circuits
rejected, 0 marked addresses. 0 connections closed. 0 single hop clients
refused.
May 22 08:03:53.000 [notice] Heartbeat: It seems like we are not in the
cached consensus.
May 22 08:03:53.000 [notice] Heartbeat: Tor's uptime is 11:59 hours, with 0
circuits open. I've sent 1.29 MB and received 16.06 MB.
May 22 08:03:53.000 [notice] Average packaged cell fullness: 100.000%. TLS
write overhead: 21%
May 22 08:03:53.000 [notice] Circuit handshake stats since last time: 0/0
TAP, 0/0 NTor.
May 22 08:03:53.000 [notice] Since startup, we have initiated 0 v1
connections, 0 v2 connections, 0 v3 connections, and 29 v4 connections; and
received 1 v1 connections, 0 v2 connections, 0 v3 connections, and 21 v4
connections.
May 22 08:03:53.000 [notice] DoS mitigation since startup: 0 circuits
rejected, 0 marked addresses. 0 connections closed. 0 single hop clients
refused.
May 22 14:03:53.000 [notice] Heartbeat: It seems like we are not in the
cached consensus.
May 22 14:03:53.000 [notice] Heartbeat: Tor's uptime is 17:59 hours, with 0
circuits open. I've sent 1.44 MB and received 22.35 MB.
May 22 14:03:53.000 [notice] Average packaged cell fullness: 100.000%. TLS
write overhead: 21%
May 22 14:03:53.000 [notice] Circuit handshake stats since last time: 0/0
TAP, 0/0 NTor.
May 22 14:03:53.000 [notice] Since startup, we have initiated 0 v1
connections, 0 v2 connections, 0 v3 connections, and 29 v4 connections; and
received 1 v1 connections, 0 v2 connections, 0 v3 connections, and 21 v4
connections.
May 22 14:03:53.000 [notice] DoS mitigation since startup: 0 circuits
rejected, 0 marked addresses. 0 connections closed. 0 single hop clients
refused.
May 22 20:03:53.000 [notice] Heartbeat: It seems like we are not in the
cached consensus.
May 22 20:03:53.000 [notice] Heartbeat: Tor's uptime is 23:59 hours, with 0
circuits open. I've sent 1.58 MB and received 29.42 MB.
May 22 20:03:53.000 [notice] Average packaged cell fullness: 100.000%. TLS
write overhead: 21%
May 22 20:03:53.000 [notice] Circuit handshake stats since last time: 0/0
TAP, 0/0 NTor.
May 22 20:03:53.000 [notice] Since startup, we have initiated 0 v1
connections, 0 v2 connections, 0 v3 connections, and 29 v4 connections; and
received 1 v1 connections, 0 v2 connections, 0 v3 connections, and 21 v4
connections.
May 22 20:03:53.000 [notice] DoS mitigation since startup: 0 circuits
rejected, 0 marked addresses. 0 connections closed. 0 single hop clients
refused.
May 23 02:03:53.000 [notice] Heartbeat: It seems like we are not in the
cached consensus.
May 23 02:03:53.000 [notice] Heartbeat: Tor's uptime is 1 day 5:59 hours,
with 0 circuits open. I've sent 1.72 MB and received 36.42 MB.
May 23 02:03:53.000 [notice] Average packaged cell fullness: 100.000%. TLS
write overhead: 21%
May 23 02:03:53.000 [notice] Circuit handshake stats since last time: 0/0
TAP, 0/0 NTor.
May 23 02:03:53.000 [notice] Since startup, we have initiated 0 v1
connections, 0 v2 connections, 0 v3 connections, and 29 v4 connections; and
received 1 v1 connections, 0 v2 connections, 0 v3 connections, and 21 v4
connections.
May 23 02:03:53.000 [notice] DoS mitigation since startup: 0 circuits
rejected, 0 marked addresses. 0 connections closed. 0 single hop clients
refused.
May 23 08:03:53.000 [notice] Heartbeat: It seems like we are not in the
cached consensus.
May 23 08:03:53.000 [notice] Heartbeat: Tor's uptime is 1 day 11:59 hours,
with 0 circuits open. I've sent 1.82 MB and received 42.16MB.
May 23 08:03:53.000 [notice] Average packaged cell fullness: 100.000%. TLS
write overhead: 21%
May 23 08:03:53.000 [notice] Circuit handshake stats since last time: 0/0
TAP, 0/0 NTor.
May 23 08:03:53.000 [notice] Since startup, we have initiated 0 v1
connections, 0 v2 connections, 0 v3 connections, and 29 v4 connections; and
received 1 v1 connections, 0 v2 connections, 0 v3 connections, and 21 v4
connections.
May 23 08:03:53.000 [notice] DoS mitigation since startup: 0 circuits
rejected, 0 marked addresses. 0 connections closed. 0 single hop clients
refused.
May 23 14:03:53.000 [notice] Heartbeat: It seems like we are not in the
cached consensus.
May 23 14:03:53.000 [notice] Heartbeat: Tor's uptime is 1 day 17:59 hours,
with 0 circuits open. I've sent 1.96 MB and received 48.91MB.
May 23 14:03:53.000 [notice] Average packaged cell fullness: 100.000%. TLS
write overhead: 21%
May 23 14:03:53.000 [notice] Circuit handshake stats since last time: 0/0
TAP, 0/0 NTor.
May 23 14:03:53.000 [notice] Since startup, we have initiated 0 v1
connections, 0 v2 connections, 0 v3 connections, and 29 v4 connections; and
received 1 v1 connections, 0 v2 connections, 0 v3 connections, and 21 v4
connections.
May 23 14:03:53.000 [notice] DoS mitigation since startup: 0 circuits
rejected, 0 marked addresses. 0 connections closed. 0 single hop clients
refused.
May 23 20:03:53.000 [notice] Heartbeat: It seems like we are not in the
cached consensus.
May 23 20:03:53.000 [notice] Heartbeat: Tor's uptime is 1 day 23:59 hours,
with 0 circuits open. I've sent 2.07 MB and received 54.87MB.
May 23 20:03:53.000 [notice] Average packaged cell fullness: 100.000%. TLS
write overhead: 21%
May 23 20:03:53.000 [notice] Circuit handshake stats since last time: 0/0
TAP, 0/0 NTor.
May 23 20:03:53.000 [notice] Since startup, we have initiated 0 v1
connections, 0 v2 connections, 0 v3 connections, and 29 v4 connections; and
received 1 v1 connections, 0 v2 connections, 0 v3 connections, and 21 v4
connections.
May 23 20:03:53.000 [notice] DoS mitigation since startup: 0 circuits
rejected, 0 marked addresses. 0 connections closed. 0 single hop clients
refused.
--Keifer

On Thu, May 23, 2019 at 2:09 PM teor <teor at riseup.net> wrote:

> Hi,
>
> On 23 May 2019, at 18:41, Dmitrii Tcvetkov <demfloro at demfloro.ru> wrote:
>
> On Tue, 21 May 2019 23:36:28 -0700
> Keifer Bly <keifer.bly at gmail.com> wrote:
>
> Hi, so the relay in question does indeed have a reserved Static IP
>
> (104.154.93.253), and the traffic is allowed by the firewall, but the
>
> relay is still not appearing in the consensus. The port it's running
>
> on is 65534. This is starting to seem odd.....any thoughts are
>
> appreciated. Thanks. --Keifer
>
>
>
> Indeed, I don't have any problem connecting to your relay with openssl
> from multiple locations (at least Russia, Netherlands and Germany):
>
>
> $ openssl s_client -connect 104.154.93.253:65534
> <snip>
> Certificate chain
> ...
>
>
> I can't find a relay called "torworld" or at "104.154.93.253" on the tor
> network:
> * using consensus health, which shows relays with votes:
>   https://consensus-health.torproject.org/
>   * or relay search, which shows relays in the consensus:
>   https://metrics.torproject.org/rs.html#search/104.154.93.253
>
> Please copy and paste the latest logs from your relay the last time you
> started
> it up. We need to see logs that cover your relay's:
> * tor version,
> * role (relay or bridge),
> * nickname,
> * fingerprint,
> * IPv4 address,
> * reachability self-test, and
> * descriptor posts to authorities.
>
> We might need info-level logs to see some of these things.
>
> Do you know if Google supports tor relays?
> They could be blocking some connections.
>
> T
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20190523/b7a4e04c/attachment-0001.html>