Opened 7 months ago

Last modified 5 months ago

#33607 new defect

Stop forcing IPv4 and IPv6 traffic on non-SOCKSPorts

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: 0.4.5.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points: 0.1
Reviewer: Sponsor: Sponsor55-can

Description (last modified by teor)

After #32994, the defaults in port_cfg_new() will apply to all parsed ports. (Not just default ports.)

I am not sure what we should do with the extra settings in connection_listener_new():

  if (type != CONN_TYPE_AP_LISTENER) {
    lis_conn->entry_cfg.ipv4_traffic = 1;
    lis_conn->entry_cfg.ipv6_traffic = 1;
    lis_conn->entry_cfg.prefer_ipv6 = 1;

Here are our options:

  • leave them there: non-SOCKSPorts will always have IPv4, IPv6, and prefer IPv6 traffic
  • copy the defaults from port_cfg_new(): non-SOCKSPorts will always have DNS, Onion, and prefer IPv6 virtual addresses. Forcing these options on might make some configs break.
  • delete them: non-SOCKSPorts can now disable IPv4, IPv6, and prefer IPv4 traffic. Some rare configs might break, because they relied on the options being forced on.

Here's what I think we should do long-term:

  • set reasonable defaults (in #32994)
  • stop forcing options on (this ticket)
  • warn users that some rare configs might break, and they should remove NoIPv4Traffic or NoIPv6Traffic as needed (this changes file)

"prefer IPv6 traffic" was added in #32637 in We don't want to force that option on in 0.4.3, that makes the problem worse, and might break some existing configs. See #33608 for a fix.

Child Tickets

#33608closedteorStop forcing prefer IPv6 on non-SOCKSPortsCore Tor/Tor

Change History (2)

comment:1 Changed 7 months ago by teor

Description: modified (diff)

comment:2 Changed 5 months ago by nickm

Keywords: 044-should removed
Milestone: Tor: 0.4.4.x-finalTor: 0.4.5.x-final
Sponsor: Sponsor55-can
Note: See TracTickets for help on using tickets.