Opened 6 years ago

Last modified 16 months ago

#14939 new defect

Support ipv6 addresses in Tor Circuit DIsplay

Reported by: arthuredelstein Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords: tbb-circuit-display, tbb-usability
Cc: mcs, teor, Parckwart Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description (last modified by arthuredelstein)

Bridges and other nodes may have ipv6 addresses, and we need to fix the tor circuit display so that it handles these correctly.

Child Tickets

Change History (6)

comment:1 Changed 6 years ago by mcs

Cc: mcs added

comment:2 Changed 6 years ago by arthuredelstein

Description: modified (diff)

comment:3 Changed 5 years ago by teor

Severity: Normal

#17840 adds client support for bootstrapping and connecting to guards over IPv6.
But Tor Browser shows the guard's IPv4 address, not the address that tor is actually connected to.

comment:4 Changed 5 years ago by gk

Cc: teor added

#18584 is a duplicate.

comment:5 Changed 2 years ago by gk

Cc: Parckwart added

#27954 is a duplicate.

comment:6 Changed 16 months ago by teor

This issue confused a user on IRC today:

after some playing around with my tor browser bundle, I found I had to set ClientUseIPv6 to 1, and also set ClientUseIPv4 to 0. after doing that, despite TBB telling me IPv4 addresses in the circuit list, wireshark confirmed it was in-fact connecting over IPv6 :)

Note: See TracTickets for help on using tickets.