Before my last restart 6 hours ago you get a series of messages like these:

```

Since startup we initiated 0 and received 0 v1 connections; initiated 0 and received 0 v2 connections; initiated 0 and received 81 v3 connections; initiated 0 and received 341 v4 connections; initiated 38535 and received 87986 v5 connections.

Heartbeat: DoS mitigation since startup: 0 circuits killed with too many cells, 0 circuits rejected, 0 marked addresses, 0 marked addresses for max queue, 0 same address concurrent connections rejected, 0 connections rejected, 0 single hop clients refused, 0 INTRODUCE2 rejected.

Heartbeat: It seems like we are not in the cached consensus.

Heartbeat: Tor's uptime is 2 days 18:00 hours, with 185 circuits open. I've sent 41.52 GB and received 55.06 GB. I've received 105529 connections on IPv4 and 0 on IPv6. I've made 46384 connections with IPv4 and 0 with IPv6.

While not bootstrapping, fetched this many bytes: 53988798 (server descriptor fetch); 11748 (server descriptor upload); 3201890 (consensus network-status fetch); 548826 (microdescriptor fetch)

Circuit handshake stats since last time: 0/0 TAP, 2/2 NTor.

```

After my last restart I have:

```

Read configuration file "/usr/share/tor/tor-service-defaults-torrc".

Read configuration file "/etc/tor/torrc".

Based on detected system memory, MaxMemInQueues is set to 4440 MB. You can override this by setting MaxMemInQueues by hand.

Opening Control listener on 127.0.0.1:9051

Opened Control listener connection (ready) on 127.0.0.1:9051

Opening OR listener on 156.67.111.146:443

Opened OR listener connection (ready) on 156.67.111.146:443

[...]

Bootstrapped 5% (conn): Connecting to a relay

Opening Control listener on /run/tor/control

Opened Control listener connection (ready) on /run/tor/control

Self-testing indicates your ORPort 156.67.111.146:443 is reachable from the outside. Excellent. Publishing server descriptor.

Bootstrapped 10% (conn_done): Connected to a relay

Bootstrapped 14% (handshake): Handshaking with a relay

Bootstrapped 15% (handshake_done): Handshake with a relay done

Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits

Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits

Bootstrapped 95% (circuit_create): Establishing a Tor circuit

Bootstrapped 100% (done): Done

Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 1000 buildtimes.

Performing bandwidth self-test...done.

```

I can confirm that the IPv6 address is not reachable for an unknown reason. The IPv6 address and flag have been removed from the torrc file to correct the problem and don't appear in the log at restart, as shown above. IPv6 should be completely ignored by the DirAuth.

Denny

On 2024-10-01 08:06, George Hartley via tor-relays wrote:

Hi, looks like the DirAuth's think that your relay is unreachable, and so your descriptor isn't published, so your flags are not updated, this would explain the lack of change in flags.

Port 443 on 156.67.111.146 is open for me, can't test IPv6 as I have disabled it through my modem and kernel command line.

Can you attach your tor log file?

You can also adjust the log verbosity of certain "domains" within Tor like so:

[1]https://2019.www.torproject.org/docs/tor-manual.html.en#Log

Please let us know what you find.

Thanks,

George

On Tuesday, October 1st, 2024 at 1:40 PM, denny.obreham@a-n-o-n-y-m-e.net denny.obreham@a-n-o-n-y-m-e.net wrote:

My exit relay which has been running for months without a problem has not been in the cached consensus for days now. https://consensus-health.torproject.org/consensus-health.html?#7BDDE 0E7607A5F49578768F44CD721793FA2D7AE

After investigating, I thought the reason was that the IPv6 wasn't reachable anymore. It happened once before with another relay. Seems to be a problem with my ISP. Anyway, I just remove the ORPort IPv6 address and IPv6Exit flag from the torrc file and everything should return to normal. It has been days and it doesn't. Reloaded and restarted more than once since then.

What I don't understand is that the OR IPv6 address and the ReachableIPv6 flag are still listed in the metrics. h ttps://metrics.torproject.org/rs.html#details/7BDDE0E7607A5F49578768 F44CD721793FA2D7AE

Any help would be appreciated.

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