Opened 6 years ago

Last modified 9 months ago

#5788 new enhancement

Add support for relays without an IPv4 address

Reported by: ln5 Owned by: ln5
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: ipv6, tor-relay non-clique
Cc: kwadronaut@…, pterjan, teor, dominik@… Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

A relay with only IPv6 address(es) doesn't work for several reasons.
That's OK for quite a while -- we probably don't want a network with
relays which can connect only to a (smallish) subset of the other
routers.

But there are also limitations in the code today making a relay use
the mandatory IPv4 address in ways it shouldn't have to. An example
is a bridge requiring that an IpV4 address is configured (but not
necessarily being used) in order to work.

This enhancement ticket collects the kind of bugs which are not
strictly showstoppers for a mixed IPv4/IPv6 network to function but
which should be fixed anyway.

Child Tickets

TicketTypeStatusOwnerSummary
#4565projectassignedln5Enable relays to talk to other relays via IPv6
#4847defectassignedln5Fix IPv6 bridges with a private/dynamic IPv4 address
#17060defectclosedrouterset_parse doesn't accept IPv6 addresses
#17066tasknewAvoid assuming relays have a single IPv4/IPv6 address

Change History (15)

comment:1 Changed 6 years ago by nickm

Milestone: Tor: 0.2.4.x-final

comment:2 Changed 5 years ago by nickm

Keywords: tor-relay added

comment:3 Changed 5 years ago by nickm

Component: Tor RelayTor

comment:4 Changed 5 years ago by nickm

Milestone: Tor: 0.2.4.x-finalTor: 0.2.5.x-final

comment:5 Changed 4 years ago by nickm

Milestone: Tor: 0.2.5.x-finalTor: 0.2.???

comment:6 Changed 3 years ago by lva

Any progress on this? It appears that this just keeps getting pushed forward indefinitely.

I have bandwidth and resources to spare, but public IPv4 addresses are getting scarce, and asking people to sacrifice a public v4 address for tor - or, perish the thought, host tor on the same machine next to other services - is difficult.

comment:7 Changed 3 years ago by kwadronaut

Cc: kwadronaut@… added

comment:8 Changed 2 years ago by pterjan

Cc: pterjan added

comment:9 Changed 2 years ago by teor

Cc: teor added

comment:10 Changed 2 years ago by teor

Severity: Normal

lva, I'm starting work on bootstrapping over IPv6.
We'll likely implement it in clients first.

Unfortunately, tor assumes relays are fully-connected, and so an IPv6-only relay would cause path building to fail when it couldn't connect to an IPv4-only relay.

comment:11 Changed 15 months ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:12 Changed 14 months ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:13 Changed 14 months ago by rathann

Cc: dominik@… added

comment:14 Changed 9 months ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:15 Changed 9 months ago by nickm

Keywords: non-clique added
Note: See TracTickets for help on using tickets.