It could be that your provider has throttled you temporarily.

I don't think so, I get that message on a dedicated 10 GbE link with little to no use except for the exit relay on it.

Also, if his relay publishes it's descriptor, then why Metrics won't reflect that?

It should show it as online, as you don't need IPv6 to be reachable to get the online flag.

-GH

On Tuesday, October 1st, 2024 at 7:55 PM, boldsuck via tor-relays tor-relays@lists.torproject.org wrote:

On Tuesday, 1 October 2024 19:32 denny.obreham@a-n-o-n-y-m-e.net wrote:

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

That looks good :-)

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

It could be that your provider has throttled you temporarily.

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.

With some providers you get the IPv6 prefix too late¹ and systemd stops tor
because of errors. Unfortunately, I have one of those too.
After a reboot I have to log in and do:

systemctl list-units --failed
systemctl stop tor
systemctl reset-failed
systemctl start tor

That's one reason why I don't have an auto reboot after upgrade but would like
to receive an email from the system. <- @toralf ;-)

¹Even the sysctl settings don't help.
# Disable IPv6 autoconf and router advertising
net.ipv6.conf.all.autoconf=0
net.ipv6.conf.default.autoconf=0
net.ipv6.conf.all.accept_ra=0
net.ipv6.conf.default.accept_ra=0

# Do not accept DAD
net.ipv6.conf.all.accept_dad=0
net.ipv6.conf.default.accept_dad=0

# Disable DAD transmits
net.ipv6.conf.all.dad_transmits=0
net.ipv6.conf.default.dad_transmits=0

--
╰_╯ Ciao Marco!

Debian GNU/Linux

It's free software and it gives you freedom!_______________________________________________
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays