Opened 6 years ago

Closed 3 years ago

#12446 closed enhancement (wontfix)

OutboundBindAddress should imply expected Address, ORBindAddress, and ORPort settings

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


mjt identified an issue where OutboundBindAddress and ORPort were set according to a secondary IP on a multi-homed host yet Tor utilized the default/primary IP when making outbound connections. This is only remedied by setting Address in addition to other Bind directives which is not friendly nor intuitive.

Make the default OutboundBindAddress imply expected Address, ORBindAddress, ORPort settings if not explicitly set, and verify config behavior with apropos unit tests.

Child Tickets

Change History (3)

comment:1 Changed 6 years ago by arma

Should we make a new uber torrc option that sets all of these for you?

OutboundBindAddress, by its name, is pretty clear about what it does and doesn't do.

comment:2 Changed 6 years ago by nickm

Milestone: Tor: unspecified

comment:3 Changed 3 years ago by nickm

Resolution: wontfix
Severity: Normal
Status: newclosed
Note: See TracTickets for help on using tickets.