Opened 13 months ago

Last modified 5 months ago

#24403 assigned task

Propose and implement IPv6 ORPort reachability checks on relays

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: ipv6, tor-relay, 034-triage-20180328, 034-removed-20180328
Cc: Actual Points:
Parent ID: #4565 Points:
Reviewer: Sponsor: SponsorV-can

Description

This is the top-level task for relay IPv6 ORPort reachability checks.

See:
https://trac.torproject.org/projects/tor/wiki/org/roadmaps/Tor/IPv6Features#ReachabilityChecks

Check the child tickets for details.

Child Tickets

TicketStatusOwnerSummaryComponent
#6939needs_revisionMissing IPv6 ORPort reachability checkCore Tor/Tor
#7193newTor's sybil protection doesn't consider IPv6Core Tor/Tor
#10519newtor uses default IP for dirport instead of the one defined in DirPortCore Tor/Tor
#13112needs_revisionteorSome things are probably broken when we advertise multiple ORPorts and only some are reachableCore Tor/Tor
#17782needs_revisionRelays may publish descriptors with incorrect IP addressCore Tor/Tor
#19919newIf ORPort address is publicly routable, use it to guess AddressCore Tor/Tor
#21044newORPort self reachability test happens also when it shouldn'tCore Tor/Tor
#22781needs_revisiondgouleths: Unify link specifier API/ABICore Tor/Tor
#23873closedRemove the return value of node_get_prim_orport()Core Tor/Tor
#24000needs_revisionnickmcircuit_send_intermediate_onion_skin() and extend_cell_format() should check for IPv6Core Tor/Tor
#24338newDirAuths that have IPv6 addresses don't include them in their vote on themselfCore Tor/Tor
#24393closedneelClients should check IPv4 and IPv6 subnets when choosing circuit pathsCore Tor/Tor
#24404newPropose a relay protover that allows IPv6 extendsCore Tor/Tor
#24405newImplement relay IPv6 extends with proposed protoverCore Tor/Tor
#24406newImplement IPv6 ORPort reachability fallbackCore Tor/Tor
#24451accepteddgouletPut IPv6 link specifiers in client EXTEND cellsCore Tor/Tor
#24535newDocument which address functions we should use, and whenCore Tor/Tor
#24603needs_informationUpdate control spec to allow decorated IPv6 addresses in reachability eventsCore Tor/Tor
#24604newDecorate IPv6 addresses in connection_t->address to avoid ambiguityCore Tor/Tor
#24731newStop checking routerinfos for addresses when we use microdescs for circuitsCore Tor/Tor
#24732needs_revisionRemove unused IPv6 DirPort codeCore Tor/Tor
#24734closedneelRemove the return value of fascist_firewall_choose_address_node()Core Tor/Tor
#24735needs_revisionAlways check for the null address when calling address functionsCore Tor/Tor
#24777newMake relays try IPv6 ORPorts for directory uploads and downloadsCore Tor/Tor
#24867newDo relays keep more than one canonical connection when they extend over IPv6?Core Tor/Tor
#25182closedsystemd unit file starts Tor before IPv6 address is availableCore Tor/Tor

Change History (7)

comment:1 Changed 13 months ago by teor

Parent ID: #4565

comment:2 Changed 12 months ago by teor

Owner: set to teor
Status: newassigned

I am happy to coordinate this, please feel free to help out with child tickets.

comment:3 Changed 11 months ago by teor

Milestone: Tor: 0.3.3.x-finalTor: 0.3.4.x-final

The 0.3.3 feature freeze deadline has passed

comment:4 Changed 9 months ago by nickm

Keywords: 034-triage-20180328 added

comment:5 Changed 9 months ago by nickm

Keywords: 034-removed-20180328 added

Per our triage process, these tickets are pending removal from 0.3.4.

comment:6 Changed 8 months ago by nickm

Milestone: Tor: 0.3.4.x-finalTor: unspecified

These tickets, tagged with 034-removed-*, are no longer in-scope for 0.3.4. We can reconsider any of them, if time permits.

comment:7 Changed 5 months ago by teor

Owner: teor deleted

Not on any roadmap yet.

Note: See TracTickets for help on using tickets.