[tor-bugs] #33222 [Core Tor/Tor]: Prop 311: 4.2. Implement IPv6 ORPort Reachability Self-Tests

[Tor Bug Tracker & Wiki]

#33222: Prop 311: 4.2. Implement IPv6 ORPort Reachability Self-Tests
---------------------------+------------------------------------
 Reporter:  teor           |          Owner:  teor
     Type:  enhancement    |         Status:  needs_review
 Priority:  Medium         |      Milestone:  Tor: 0.4.4.x-final
Component:  Core Tor/Tor   |        Version:
 Severity:  Normal         |     Resolution:
 Keywords:  ipv6, prop311  |  Actual Points:  1.1
Parent ID:  #33221         |         Points:  6
 Reviewer:  nickm          |        Sponsor:  Sponsor55-must
---------------------------+------------------------------------
Changes (by teor):

 * status:  assigned => needs_review


Comment:

 I've done another revision.

 This branch is not ready for merge yet, but the basic design and
 functionality should be there. I still have to:

 Replying to [comment:7 teor]:
 > * 4.2.1 Selecting the Final Extending Relay (this ticket)
 >   * 5. Declare Support for Subprotocol Version "Relay=3" (#33226)
 > * unit tests
 > * changes files

 Then I think we can safely merge.

 Since this PR is getting big, I'd like to make these changes in another PR
 and ticket:

 Replying to [comment:11 teor]:
 > My next priority is to:
 > * Separate tor's IPv4 and IPv6 reachability flags (#34067)
 >
 > So we know that we're actually getting IPv6 connections. (I'm pretty
 sure we are now, but we don't want to accidentally break them.)

 The extend_info changes in #34069, and dual-stack EXTEND2 cells aren't a
 high priority. The code will work either way.

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