Opened 3 years ago

Last modified 21 months ago

#17636 new defect

Can a single IPv6 bridge failure stop Tor connecting?

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.2.6.10
Severity: Normal Keywords: tor-client tor-bridges, ipv6 needs-diagnosis
Cc: Actual Points:
Parent ID: Points: medium??
Reviewer: Sponsor:

Description

ln5's IPv6-only Linux system had 3 bridges, but 2 failed.
Then the tor instance stopped connecting, even though it still had one good bridge.

Does this happen on IPv4?
(Can we reproduce it on IPv6?)
How can we make this more robust?

Child Tickets

Change History (9)

comment:1 Changed 3 years ago by nickm

Milestone: Tor: 0.2.8.x-final

comment:2 Changed 3 years ago by nickm

Milestone: Tor: 0.2.8.x-finalTor: 0.2.9.x-final

Throw most 0.2.8 "NEW" tickets into 0.2.9. I expect that many of them will subsequently get triaged out.

comment:3 Changed 3 years ago by nickm

Points: medium??

comment:4 Changed 3 years ago by isabela

Keywords: isaremoved added
Milestone: Tor: 0.2.9.x-finalTor: 0.2.???

comment:5 Changed 2 years ago by teor

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

Milestone renamed

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

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:8 Changed 22 months ago by nickm

Keywords: isaremoved removed

comment:9 Changed 21 months ago by nickm

Keywords: tor-client tor-bridges needs-diagnosis added; bridges removed
Note: See TracTickets for help on using tickets.