Opened 4 months ago

Last modified 4 weeks ago

#33240 assigned enhancement

Prop 312: 3.2.4. Use Own Hostname IPv6 Addresses

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: 0.4.4.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: prop312, ipv6
Cc: Actual Points:
Parent ID: #33049 Points: 1
Reviewer: Sponsor: Sponsor55-must

Description (last modified by teor)

This ticket depends on Address IPv6 support in #33233 and IPv6 resolution support in #33234.

If they don't have usable Address, ORPort, or interface addresses, relays (and bridges) should get their local hostname, look
up its addresses, and use them as its IPv4 and IPv6 addresses.

We propose to use the same underlying lookup functions to look up the IPv4
and IPv6 addresses for:

  • the Address torrc option (see section 3.2.1), and
  • the local hostname.

However, OS APIs typically only return a single hostname. (Rather than a
separate hostname for IPv4 and IPv6.)

The hostname lookup should ignore private addresses on public relays. If
multiple IPv4 or IPv6 addresses are returned, the first public address from
each family should be used.

See proposal 312, section 3.2.4:

Child Tickets

Change History (5)

comment:1 Changed 4 months ago by teor

Description: modified (diff)

comment:2 Changed 4 months ago by teor

Description: modified (diff)

comment:3 Changed 4 months ago by teor

Description: modified (diff)

comment:4 Changed 4 weeks ago by teor

Description: modified (diff)

comment:5 Changed 4 weeks ago by teor

Owner: teor deleted

Un-assign myself from future Sponsor 55 tasks.

Note: See TracTickets for help on using tickets.