Opened 3 years ago

Closed 2 years ago

#21506 closed defect (fixed)

Client with current microdesc consensus but no descriptors chooses down fallback every time

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.2.8.1-alpha
Severity: Normal Keywords: ipv6, tor-client fallback-directory bootstrap
Cc: Actual Points:
Parent ID: Points: 1
Reviewer: Sponsor:

Description

Tor 0.2.9.9 doesn't have the fix for a similar issue in #20996, but 0.3.0.2-alpha does.

But this issue is different from that issue: the client downloads the consensus, then tries the same fallback (a down fallback) every time.

This really shouldn't happen: the client should choose a different relay every time.

My guess is that this relay is chosen because it's down, and all the up relay descriptors are unavailable. This is pathological behaviour.

I think we fixed it in 0.3.0.2-alpha with the patch to #20996, but I'm logging this bug just in case.

http://pastebin.ca/3769463

Child Tickets

Change History (2)

comment:1 Changed 2 years ago by nickm

Keywords: fallback-directory bootstrap added

Do we still think this is maybe an issue?

comment:2 Changed 2 years ago by teor

Resolution: fixed
Status: newclosed

Let's reopen if it happens again

Note: See TracTickets for help on using tickets.