Opened 2 years 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: #5940 Points: 48
Reviewer: Sponsor:


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


Check the child tickets for details.

Child Tickets

#7193newTor's sybil protection doesn't consider IPv6Core Tor/Tor
#13112needs_revisionSome 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
#21044newORPort self reachability test happens also when it shouldn'tCore Tor/Tor
#23502assignedv3 Onion Services: don't make IPv4 mandatory because one day we'll have IPv6 only relaysCore Tor/Tor
#23873closedRemove the return value of node_get_prim_orport()Core Tor/Tor
#24181assignedv3 Onion Services: Put IPv6 and unrecognised link specifiers in onion service EXTEND cellsCore Tor/Tor
#24338closedneelDirAuths 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
#24451assignedPut 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
#24611newAdd a chutney network that does reachability testsCore Tor/Chutney
#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
#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
#26971newAdd rendezvous point unrecognised link specifiers to client introduce cellsCore Tor/Tor
#31088closedneelCheck IPv4 and IPv6 private addresses in descriptorsCore Tor/Tor
#32888assignedLog address config info when tor starts upCore Tor/Tor

Change History (12)

comment:1 Changed 2 years ago by teor

Parent ID: #4565

comment:2 Changed 2 years 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 2 years 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 22 months ago by nickm

Keywords: 034-triage-20180328 added

comment:5 Changed 22 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 22 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 18 months ago by teor

Owner: teor deleted

Not on any roadmap yet.

comment:8 Changed 8 months ago by gaba

Removing sponsor V as we do not have more time to include this tickets in the sponsor.

comment:9 Changed 8 months ago by gaba

Sponsor: SponsorV-can

Removing sponsor from tickets that we do not have time to fit in the remain of this sponsorship.

comment:10 Changed 7 months ago by teor

Parent ID: #4565#5940

comment:11 Changed 5 months ago by gaba

Points: 48

comment:12 Changed 5 months ago by teor

If we get funding for this ticket, we should triage the child tickets as our first step.

Note: See TracTickets for help on using tickets.