[tor-bugs] #12020 [Tor]: Bootstrap gets stuck at 20% when connecting through a bridge.

[Tor Bug Tracker & Wiki]

#12020: Bootstrap gets stuck at 20% when connecting through a bridge.
-------------------------+--------------------------------
     Reporter:  yawning  |      Owner:
         Type:  defect   |     Status:  new
     Priority:  normal   |  Milestone:  Tor: 0.2.5.x-final
    Component:  Tor      |    Version:  Tor: 0.2.5.4-alpha
   Resolution:           |   Keywords:  tor-bridge
Actual Points:           |  Parent ID:
       Points:           |
-------------------------+--------------------------------

Comment (by yawning):

 Replying to [comment:5 arma]:
 > Tor won't retry fetching the bridge descriptor just 60 seconds later --
 it failed, so it's unlikely to succeed again so soon after:
 > {{{
 >   V(TestingBridgeDownloadSchedule, CSV_INTERVAL, "3600, 900, 900,
 3600"),
 > }}}
 >
 > If indeed it hasn't generated its descriptor yet, then just using it as
 a vanilla bridge on its orport should fail too. That should remove some
 components from your situation.

 I have observed this in the past when testing (ORport not working).

 > What does the bridge say about its reachability testing? Or does it not
 even get to that because it thinks it has no publicly routable address?

 Haven't tried letting it go that far (and it would fail anyway since I
 don't forward the port).

 I've been doing my development with `Address` set and haven't ran into
 this again, so I believe your diagnosis is correct.

 In light of that, I'm not sure if there's a bug here, it may be nice to
 have a warning when fetching the bridge descriptor fails, but bridges in
 the wild presumably have a real address and won't trigger this issue in
 the first place.

 Sorry for taking up your time, and please feel free to close this if all
 of this behaviour is ok.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/12020#comment:6>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online