[tor-relays] One pubblic IP, two or more relay on different ports

[MLTorNode]

nusenu ha scritto il 03/03/2018 alle 20:03:
 >
 >
 > MLTorNode:
 >> Is it possibile? I have one dynamic public IP with one relay server 
published on
 >> ORPort 443 and DIRport 80 (with IPv6 ORPort too).
 >> Can i add a second relay with OR and DIR natted on other ports 
published on the
 >> same IP of the first server?
 >
 > you can run up to two tor relay instances on a single public IPv4.
 >
 > You can not run more than 2 instances per public IPv4.

Yes, but i have a strange problem: my first relay is MLTorNode (Linux 
Debian), with ORPort NATted on public port 443 and DIRPort NATted on 
public port 80. This relay works without problems, i can see the 
configuration in Atlas.

The second relay (MLTorNode02) is running on another PC with Windows 
2016 Server. It publish ORPort on NATted 9001 public port.
In this relay, however, I have strange NOTICE in log and very very few 
connections.
These are the logs:

=============================
[...]
Mar 03 23:33:45.000 [notice] No circuits are opened. Relaxed timeout for 
circuit 26 (a General-purpose client 3-hop circuit in state doing 
handshakes with channel state open) to 60000ms. However, it appears the 
circuit has timed out anyway.
Mar 03 23:34:01.000 [notice] Tor has successfully opened a circuit. 
Looks like client functionality is working.
Mar 03 23:34:01.000 [notice] Bootstrapped 100%: Done
Mar 03 23:34:01.000 [notice] Now checking whether ORPort 
82.51.162.68:9001 and DirPort 82.51.162.68:9030 are reachable... (this 
may take up to 20 minutes -- look for log messages indicating success)
Mar 03 23:34:19.000 [notice] Self-testing indicates your DirPort is 
reachable from the outside. Excellent.
Mar 03 23:34:21.000 [notice] Self-testing indicates your ORPort is 
reachable from the outside. Excellent. Publishing server descriptor.
Mar 03 23:34:22.000 [notice] Performing bandwidth self-test...done.
Mar 04 02:31:36.000 [notice] Your relay has a very large number of 
connections to other relays. Is your outbound address the same as your 
relay address? Found 12 connections to 8 relays. Found 12 current 
canonical connections, in 0 of which we were a non-canonical peer. 4 
relays had more than 1 connection, 0 had more than 2, and 0 had more 
than 4 connections.
Mar 04 03:31:35.000 [notice] Your relay has a very large number of 
connections to other relays. Is your outbound address the same as your 
relay address? Found 13 connections to 8 relays. Found 13 current 
canonical connections, in 0 of which we were a non-canonical peer. 5 
relays had more than 1 connection, 0 had more than 2, and 0 had more 
than 4 connections.
Mar 04 04:31:37.000 [notice] Your relay has a very large number of 
connections to other relays. Is your outbound address the same as your 
relay address? Found 15 connections to 10 relays. Found 15 current 
canonical connections, in 0 of which we were a non-canonical peer. 5 
relays had more than 1 connection, 0 had more than 2, and 0 had more 
than 4 connections.
Mar 04 05:31:35.000 [notice] Heartbeat: Tor's uptime is 5:59 hours, with 
0 circuits open. I've sent 7.50 MB and received 17.31 MB.
Mar 04 05:31:35.000 [notice] Circuit handshake stats since last time: 
0/0 TAP, 21/21 NTor.
Mar 04 05:31:35.000 [notice] Since startup, we have initiated 0 v1 
connections, 0 v2 connections, 0 v3 connections, and 9 v4 connections; 
and received 0 v1 connections, 3 v2 connections, 0 v3 connections, and 
18 v4 connections.
=============================

Thanks in advance,

-- 
Marlenio (MLTorNode)
FE4033D750831C32A957174ADD11E40F558A14A9