Opened 6 months ago

Last modified 8 weeks ago

#33246 assigned enhancement

Prop 312: 3.2.7. Automatically Enable an IPv6 ORPort

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

Description (last modified by teor)

After we implement #33233, relays (and bridges) should try to open an IPv6 ORPort.

The ORPort should be opened on the port configured in the relay's ORPort
torrc option. Relay operators can use the IPv4Only and IPv6Only options
to configure different ports for IPv4 and IPv6.

If the ORPort is auto-detected, there will not be any specific bind
address. (And the detected address may actually be on a NAT box, rather
than the local machine.) Therefore, relays should attempt to bind to all
IPv4 and IPv6 addresses (or all interfaces).

Some operating systems expect applications to bind to IPv4 and IPv6
addresses using separate API calls. Others don't support binding only to
IPv4 or IPv6, and will bind to all addresses whenever there is no specified
IP address (in a single API call). Tor should support both styles of
networking API.

In particular, if binding to all IPv6 addresses fails, relays should still
try to discover their public IPv6 address, and check the reachability of
that address. Some OSes may not support the IPV6_V6ONLY flag, but they may
instead bind to all addresses at runtime. (The tor install may also have
compile-time / runtime flag mismatches.)

See proposal 312, section 3.2.7, IPv6 ORPort part:

Once this ticket is implemented, we should test the different IPv4/IPv6 configs listed in #33235.

Child Tickets

Change History (4)

comment:1 Changed 3 months ago by teor

Description: modified (diff)

Note dependencies on #33233 and #33235.

comment:2 Changed 3 months ago by teor

Owner: teor deleted

Un-assign myself from future Sponsor 55 tasks.

comment:3 Changed 8 weeks ago by nickm

Keywords: 044-deferred added
Milestone: Tor: 0.4.4.x-finalTor: unspecified

Bulk-remove tickets from 0.4.4. Add the 044-deferred label to them.

comment:4 Changed 8 weeks ago by nickm

Milestone: Tor: unspecified

Bulk-move prop311 and prop312 to 0.4.5

Note: See TracTickets for help on using tickets.