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

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

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

Comment (by dcf):

 Just a note as I'm searching trac, you get the same symptom (bootstrapping
 stops at 20%) if you are a client with UseBridges set and connect to a
 bridge that has neither BridgeRelay nor DirPort set. info logging is:
 {{{
 [notice] Bootstrapped 20%: Asking for networkstatus consensus
 [info] internal circ (length 1):
 $0000000000000000000000000000000000000000(open)
 [info] connection_ap_handshake_send_begin(): Sending relay cell 1 to begin
 stream 21318.
 [info] connection_ap_handshake_send_begin(): Address/port sent, ap socket
 -1, n_circ_id 3101216939
 [info] connection_ap_process_end_not_open(): Edge got end (not a
 directory) before we're connected. Marking for close.
 [info] internal circ (length 1):
 $0000000000000000000000000000000000000000(open)
 [info] stream_end_reason_to_socks5_response(): Reason for ending (526) not
 recognized; sending generic socks error.
 [info] connection_free_(): Freeing linked Socks connection [waiting for
 connect response] with 57 bytes on inbuf, 0 on outbuf.
 [info] connection_dir_client_reached_eof(): 'fetch' response not all here,
 but we're at eof. Closing.
 [info] connection_dir_request_failed(): Giving up on serverdesc/extrainfo
 fetch from directory server at '0.0.2.0'; retrying
 [info] connection_free_(): Freeing linked Directory connection [client
 reading] with 0 bytes on inbuf, 0 on outbuf.
 [info] compute_weighted_bandwidths(): Empty routerlist passed in to
 consensus weight node selection for rule weight as guard
 [info] smartlist_choose_node_by_bandwidth(): Empty routerlist passed in to
 old node selection for rule weight as guard
 [info] should_delay_dir_fetches(): Delaying dir fetches (no running
 bridges known)
 [info] compute_weighted_bandwidths(): Empty routerlist passed in to
 consensus weight node selection for rule weight as guard
 [info] smartlist_choose_node_by_bandwidth(): Empty routerlist passed in to
 old node selection for rule weight as guard
 [info] should_delay_dir_fetches(): Delaying dir fetches (no running
 bridges known)
 }}}
 I guess that #12538 will make it work to use any old relay as a bridge.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/12020#comment:10>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs