Opened 20 months ago

Closed 20 months ago

Last modified 20 months ago

#26199 closed defect (duplicate)

"Your relay has a very large number of connections to other relays." potential bug in OutboundBindAddress?

Reported by: cypherpunks Owned by:
Priority: Medium Milestone:
Component: Core Tor/Tor Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: #24841 Points:
Reviewer: Sponsor:

Description

I run 8 non-exit tor relays on a single highbw server with 8 IPv4/v6 addresses.

I see the following in my logs:

 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.
 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 14 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.
 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.
 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.
 Your relay has a very large number of connections to other relays. Is your outbound address the same as your relay address? Found 17 connections to 11 relays. Found 16 current canonical connections, in 0 of which we were a non-canonical peer. 6 relays had more than 1 connection, 0 had more than 2, and 0 had more than 4 connections.
 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 12 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.
 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.
 Your relay has a very large number of connections to other relays. Is your outbound address the same as your relay address? Found 14 connections to 9 relays. Found 14 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.
 Your relay has a very large number of connections to other relays. Is your outbound address the same as your relay address? Found 14 connections to 9 relays. Found 14 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.
 Your relay has a very large number of connections to other relays. Is your outbound address the same as your relay address? Found 14 connections to 9 relays. Found 14 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.
 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.
 Your relay has a very large number of connections to other relays. Is your outbound address the same as your relay address? Found 14 connections to 9 relays. Found 14 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.
 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 9 current canonical connections, in 0 of which we were a non-canonical peer. 3 relays had more than 1 connection, 0 had more than 2, and 0 had more than 4 connections.
 Your relay has a very large number of connections to other relays. Is your outbound address the same as your relay address? Found 17 connections to 11 relays. Found 16 current canonical connections, in 0 of which we were a non-canonical peer. 6 relays had more than 1 connection, 0 had more than 2, and 0 had more than 4 connections.
 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 12 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.

Every tor instance has its own IPv4/v6 address.
torrc:

ORPort <IPv4>:443
ORPort <IPv6>:443
OutboundBindAddress <IPv4>
OutboundBindAddress <IPv6>
Address <IPv4>

Tor Version: 0.3.3.6

Is there a bug in OutboundBindAddress that results in all tor instances to use a single IP instead of the one configure in the torrc files?

Child Tickets

Change History (2)

comment:1 Changed 20 months ago by cypherpunks

Resolution: duplicate
Status: newclosed

comment:2 Changed 20 months ago by teor

Parent ID: #24841
Note: See TracTickets for help on using tickets.