Opened 3 years ago

Last modified 16 months ago

#17787 new defect

Improve address detection on multihomed relays

Reported by: teor Owned by:
Priority: Low Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Minor Keywords: tor-relay ipv6 multihome address-detection
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

If tor finds multiple publicly routable interface addresses, it will choose the first one returned by the syscall.

Do we know if the syscall always returns addresses in the same order?

If not, we should sort them, or perhaps include both addresses in the descriptor?

This issue can be mitigated by the operator explicitly choosing an address using the Address torrc option.

Only an operator knows the preferred address on a multihomed relay, or if they want to use both.

Therefore, I'm marking this low priority.

Child Tickets

Change History (4)

comment:1 Changed 2 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:2 Changed 23 months ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:3 Changed 17 months ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:4 Changed 16 months ago by nickm

Keywords: tor-relay ipv6 multihome address-detection added
Note: See TracTickets for help on using tickets.