[tor-bugs] #29570 [Core Tor/Tor]: Enforce mutually exclusive logic for IPv6 ORPort flags

[Tor Bug Tracker & Wiki]

#29570: Enforce mutually exclusive logic for IPv6 ORPort flags
-------------------------------------------------+-------------------------
 Reporter:  s7r                                  |          Owner:  (none)
     Type:  defect                               |         Status:  new
 Priority:  Medium                               |      Milestone:  Tor:
                                                 |  unspecified
Component:  Core Tor/Tor                         |        Version:  Tor:
                                                 |  unspecified
 Severity:  Normal                               |     Resolution:
 Keywords:  tor-relay, ipv6, reachability,       |  Actual Points:
  needs-proposal-or-tor-dev-email                |
Parent ID:                                       |         Points:
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+-------------------------

Comment (by s7r):

 You are suggesting behavior that does not have any logic, is confusing for
 operators and it also turns this ticket into a state that is hard to
 follow up. Don't you see the logical fracture with advertising a v6 socket
 but not listening on one? Why not just listen to v4, since that's your
 only open socket?

 In this case I would like to have only a v6 socket open, and have only one
 `NoListen` IPv4 ORPort entry to be advertised. And I will use HaProxy to
 listen on that IPv4 addr:port and redirect to my IPv6 address. So I will
 be having in my descriptor both IPv4 (which is mandatory) and IPv6, and
 only listen on one IPv6 socket. You suggest this should be possible,
 right?

 Otherwise why would we have different behavior for same thing, but only
 different versions?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/29570#comment:19>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online