Opened 3 years ago

Last modified 2 years ago

#22571 new defect

AssumeReachable 1 on a relay doesn't make it publish quickly

Reported by: arma Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: regression, 032-unreached
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


According to the man page for AssumeReachable,

           If set
           to 1, don’t do self-reachability testing; just upload your server
           descriptor immediately.

But sometime between then and now, perhaps when we messed with the "we don't publish until dirport is reachable too" logic, we lost that 'immediately' property.

It looks like now we don't do some of the checks, and also we don't publish immediately, and then we end up publishing "after a while" when some other condition triggers to consider publishing.

I'm guessing the fix could be as simple as "when we bootstrap to 100%, check if assumereachable, and if so trigger a publish then."

Child Tickets

Change History (1)

comment:1 Changed 2 years ago by nickm

Keywords: 032-unreached added
Milestone: Tor: 0.3.2.x-finalTor: unspecified

Mark a large number of tickets that I do not think we will do for 0.3.2.

Note: See TracTickets for help on using tickets.