the machine has it's own global unicast ipv4 and ipv6 addresses.
I don't know for sure, but possibly that's causing the issue? I do know tor uses one IP address for relays, so if it is detecting several different IPS that may be confusing it.
It's only a thought. --Keifer
On Tue, Jul 21, 2020 at 7:46 AM Fran fatal@mailbox.org wrote:
Hey,
the problem persists. upgraded to several new daily snapshots of openbsd in between, no success.
On 20.07.20 08:30, Keifer Bly wrote:
It is worth noting, tor conscious does not immediately update. It can
take 40 minutes up to about 3 hours for an operating status update to appear in the conscious based on my experience from the
bridge and middle relay I run.
the relay had been up for > 17 hours (see log excerpt)
Your relay has a very large number of connections to other relays. Is
your outbound address the same as your relay address? Found 9 connections to 6 relays. Found 4
What do you mean No FW on the machine?
no firewall
You need to configure port forwarding on the network for the specific
machine / ip address the relay is running on, for both inbound and outbound traffic.
the machine has it's own global unicast ipv4 and ipv6 addresses.
best
fran
On Sat, Jul 18, 2020 at 9:40 PM Fran <fatal@mailbox.org <mailto:
fatal@mailbox.org>> wrote:
Hello, I'm taking care of a server of a friend who's on holiday. The serveris up and running but not part of the consensus.
As beeing instructed I updated to the lastest OpenBSD snapshot whenI saw that a new tor release is available (Tor 0.4.3.5 on OpenBSD).
Excerpts from the log: Jul 13 20:04:02.000 [notice] Self-testing indicates your DirPort isreachable from the outside. Excellent.
Jul 13 20:05:02.000 [notice] Self-testing indicates your ORPort isreachable from the outside. Excellent. Publishing server descriptor.
Jul 13 20:05:35.000 [notice] Performing bandwidth self-test...done. Jul 14 02:04:01.000 [notice] Heartbeat: It seems like we are not inthe cached consensus.
Jul 14 02:04:01.000 [notice] Heartbeat: Tor's uptime is 6:00 hours,with 0 circuits open. I've sent 2.04 MB and received 6.25 MB.
Jul 14 02:04:01.000 [notice] Average packaged cell fullness:12.450%. TLS write overhead: 33%
Jul 14 02:04:01.000 [notice] Circuit handshake stats since lasttime: 0/0 TAP, 5/5 NTor.
Jul 14 02:04:01.000 [notice] Since startup we initiated 0 andreceived 157 v1 connections; initiated 0 and received 0 v2 connections; initiated 0 and received 0 v3 connections; initiated 0 and
received 5 v4 connections; initiated 48 and received 124 v5connections.
Jul 14 02:04:01.000 [notice] DoS mitigation since startup: 0circuits killed with too many cells. 0 circuits rejected, 0 marked addresses. 0 connections closed. 0 single hop clients refused. 0
INTRODUCE2 rejected. Jul 14 06:04:02.000 [notice] Your relay has a very large number ofconnections to other relays. Is your outbound address the same as your relay address? Found 9 connections to 6 relays. Found 4
current canonical connections, in 0 of which we were a non-canonicalpeer. 3 relays had more than 1 connection, 0 had more than 2, and 0 had more than 4 connections.
Jul 14 08:04:01.000 [notice] Heartbeat: It seems like we are not inthe cached consensus.
Jul 14 08:04:01.000 [notice] Heartbeat: Tor's uptime is 12:00 hours,with 1 circuits open. I've sent 3.46 MB and received 11.22 MB.
Jul 14 08:04:01.000 [notice] Average packaged cell fullness:12.450%. TLS write overhead: 47%
Jul 14 08:04:01.000 [notice] Circuit handshake stats since lasttime: 2/2 TAP, 1/1 NTor.
Jul 14 08:04:01.000 [notice] Since startup we initiated 0 andreceived 340 v1 connections; initiated 0 and received 0 v2 connections; initiated 0 and received 0 v3 connections; initiated 0 and
received 10 v4 connections; initiated 57 and received 246 v5connections.
Jul 14 08:04:01.000 [notice] DoS mitigation since startup: 0circuits killed with too many cells. 0 circuits rejected, 0 marked addresses. 0 connections closed. 0 single hop clients refused. 0
INTRODUCE2 rejected. Jul 14 14:04:01.000 [notice] Heartbeat: It seems like we are not inthe cached consensus.
Jul 14 14:04:01.000 [notice] Heartbeat: Tor's uptime is 18:00 hours,with 1 circuits open. I've sent 4.89 MB and received 15.33 MB.
Jul 14 14:04:01.000 [notice] Average packaged cell fullness:26.760%. TLS write overhead: 51%
Jul 14 14:04:01.000 [notice] Circuit handshake stats since lasttime: 2/2 TAP, 6/6 NTor.
Jul 14 14:04:01.000 [notice] Since startup we initiated 0 andreceived 493 v1 connections; initiated 0 and received 0 v2 connections; initiated 0 and received 0 v3 connections; initiated 0 and
received 18 v4 connections; initiated 64 and received 370 v5connections.
Jul 14 14:04:01.000 [notice] DoS mitigation since startup: 0circuits killed with too many cells. 0 circuits rejected, 0 marked addresses. 0 connections closed. 0 single hop clients refused. 0
INTRODUCE2 rejected. Atlas show the server as down:https://metrics.torproject.org/rs.html#details/AC601DBDB7FBD53454045EDC08DAE...
Accessing the status page on port 80 works. No FW on the machine. Any ideas? Thanks and regards Fran _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org <mailto:tor-relays@lists.torproject.org>
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays