Opened 3 years ago

Closed 3 years ago

#18394 closed enhancement (wontfix)

Allow relays to have an IPv6 DirPort on the same port as the IPv4 DirPort

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: 0.2.9.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: easy ipv6
Cc: Actual Points:
Parent ID: Points: 2
Reviewer: Sponsor:

Description

Currently, to do this, relay operators need to say DirPort [IPv6-address]:80 NoAdvertise, or they get a warning "Can't advertise more than one DirPort."

This supports clients on IPv6 in 0.2.8.

Child Tickets

Change History (5)

comment:1 Changed 3 years ago by nickm

Hm. Clients don't actually make connections to DirPort, do they? They should just be connecting to the ORPort and making a tunneled connection.

comment:2 in reply to:  1 Changed 3 years ago by teor

Replying to nickm:

Hm. Clients don't actually make connections to DirPort, do they? They should just be connecting to the ORPort and making a tunneled connection.

Most of the time they use a tunneled ORPort connection, but if they:

  • don't know an ORPort for a relay,
  • are firewalled from the relay's ORPort, or
  • they FetchDirInfoEarly,

then they fetch directly from the DirPort.
(See directory_command_should_use_begindir.)

comment:3 Changed 3 years ago by nickm

Points: small/medium

comment:4 Changed 3 years ago by nickm

Points: small/medium2

small/medium => 2.

comment:5 Changed 3 years ago by teor

Resolution: wontfix
Status: newclosed

This was obsoleted by #18809, which made clients only use begindir over IPv4 or IPv6 ORPorts.
And relays only use IPv4 ORPorts or DirPorts.

So there's no need for an IPv6DirPort.

Note: See TracTickets for help on using tickets.