Opened 8 years ago

Closed 7 years ago

Last modified 7 years ago

#3563 closed enhancement (implemented)

Bridge/entry support for ipv6

Reported by: nickm Owned by: ln5
Priority: High Milestone: Tor: 0.2.3.x-final
Component: Core Tor/Tor Version:
Severity: Keywords: ipv6 tor-bridge
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

We should be able to have bridges listening on ipv6 addresses, and ipv6-only clients able to connect to them.

This will probably require proposal 118 to be implemented as a prerequisite.

Child Tickets

TicketTypeStatusOwnerSummary
#3785taskclosednickmWrite proposal 186 to replace 118, and implement it
#3786taskclosedln5Make clients and bridges use their IPv6 address
#3787taskclosedln5Bridge-specific issues with IPv6
#3788taskclosedAdd code for tor to advertise an IPv6 address
#3789taskclosedln5Client-specific issues with IPv6
#4875defectclosedln5router_new_address_suggestion is not IPv6 aware

Change History (7)

comment:1 Changed 8 years ago by ln5

Cc: linus@… added

comment:2 Changed 8 years ago by ln5

Cc: linus@… removed
Owner: set to ln5
Status: newaccepted

comment:3 Changed 7 years ago by ln5

Implementation is completed for _private_ bridges but we still lack
support in several places before we're able to use BridgeDB for
distribution of IPv6 addresses.

What's a good milestone for this?

comment:4 Changed 7 years ago by ln5

Keywords: ipv6 added

comment:5 Changed 7 years ago by ln5

Resolution: implemented
Status: acceptedclosed

comment:6 Changed 7 years ago by nickm

Keywords: tor-bridge added

comment:7 Changed 7 years ago by nickm

Component: Tor BridgeTor
Note: See TracTickets for help on using tickets.