Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:  Tor: 0.3.4.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:  fixed
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:  nickm |Sponsor:
--+
Changes (by nickm):

 * status:  needs_review => closed
 * resolution:   => fixed
 * milestone:  Tor: unspecified => Tor: 0.3.4.x-final


Comment:

 I believe that the proposed patch above is the same patch as for #28912,
 which should be fixed in 0.3.4.10 and 0.3.5.7.  Please reopen if this
 happens between a client and a relay running those versions or later?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by loskiq):

 I compiled the latest stable version of Tor (0.3.4.9), replacing the
 ''main.c'' file with yours. It works!

 Replying to [comment:29 dgoulet]

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by dgoulet):

 See https://trac.torproject.org/projects/tor/ticket/28912#comment:10

 We've used the mainloop patch for now instead of going with reactivating
 the linked connection if it still has data to send. The reason is that it
 is a safer fix because <= 0.3.3 has that behavior. Doing the latter would
 require new tricky code that could introduce more issues :S.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by cypherpunks3):

 See old code for "called_loop_once =
 smartlist_len(active_linked_connection_lst) ? 1 : 0;"
 Stucked at:
 {{{
 diff --git a/src/or/connection.c a/src/or/connection.c
 index 0a2a635..0e051a5 100644
 --- a/src/or/connection.c
 +++ b/src/or/connection.c
 @@ -3428,6 +3428,8 @@ connection_handle_read_impl(connection_t *conn)

  if (!buf_datalen(linked->outbuf) && conn->active_on_link)
connection_stop_reading_from_linked_conn(conn);
 +/* Now. Now. If code still reading from connection then code */
 +/* must to reactivate event. It's linked connection. */
}
/* If we hit the EOF, call connection_reached_eof(). */
if (!conn->marked_for_close &&
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by arma):

 I am running this patch on moria1 now.

 (I wonder if weasel's surprisingly varying bootstrap times for tor clients
 has to do with directory authorities, or fallbackdirs, now running
 substantially on Tor 0.3.4.x or later.)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by arma):

 * status:  new => needs_review


Comment:

 an irc user reports being happy with this patch on #28912 (which sounds
 from the ticket titles like the same issue)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by dgoulet):

 Hmmm... I'm able to reproduce on `154.16.245.120:443` but it is working on
 my bridge listed in TB that is running 0.3.4.9 (Lisbeth,
 
https://metrics.torproject.org/rs.html#details/D9C805C955CB124D188C0D44F271E9BE57DE2109).
 Bridge line:

 `Bridge obfs4 192.95.36.142:443 CDF2E852BF539B82BD10E27E9115A31734E378C2
 cert=qUVQ0srL1JI/vO6V6m/24anYXiJD3QP2HgzUKQtQ7GRqqUvs7P+tG43RtAqdhLOALP7DJQ
 iat-mode=0`

 I think there is an issue with the bridge `154.16.245.120` itself, some
 sort of heavy throttling maybe. In the debug logs of the tor client, I see
 bursts of cells (no clear patterns but between 30 and 60 cells every 2 to
 5 minutes) and then it get stuck waiting for more, tor just sits there
 idle waiting for I'm guessing the download to complete... I bet if I let
 it sit there long enough, the download would finish.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by cypherpunks3):

 {{{
 diff --git a/src/or/main.c b/src/or/main.c
 index bc01e07..dd1f0d6 100644
 --- a/src/or/main.c
 +++ b/src/or/main.c
 @@ -404,6 +404,9 @@ connection_unlink(connection_t *conn)
connection_free(conn);
  }

 +/** Event that invokes schedule_active_linked_connections_cb. */
 +static mainloop_event_t *schedule_active_linked_connections_event = NULL;
 +
  /**
   * Callback: used to activate read events for all linked connections, so
   * libevent knows to call their read callbacks.  This callback run as a
 @@ -420,11 +423,10 @@
 schedule_active_linked_connections_cb(mainloop_event_t *ev
 * so that libevent knows to run their callbacks. */
SMARTLIST_FOREACH(active_linked_connection_lst, connection_t *, conn,
  event_active(conn->read_event, EV_READ, 1));
 +  if (smartlist_len(active_linked_connection_lst)) //QQQ: vvv safe?
 +mainloop_event_activate(schedule_active_linked_connections_event);
  }

 -/** Event that invokes schedule_active_linked_connections_cb. */
 -static mainloop_event_t *schedule_active_linked_connections_event = NULL;
 -
  /** Initialize the global connection list, closeable connection list,
   * and active connection list. */
  STATIC void
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by cypherpunks3):

 Dieses problem wurde bei linked-verbindungen aufgespürt. Dies war nie
 richtig funktioniert aber bei älteren versionen und normal geladenen
 relais.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by cypherpunks3):

 {{{
   o Minor bugfixes (bandwidth management):
 - Consider ourselves "low on write bandwidth" if we have exhausted
   our write bandwidth some time in the last second. This was the
   documented behavior before, but the actual behavior was to change
   this value every TokenBucketRefillInterval. Fixes bug 25828;
   bugfix on 0.2.3.5-alpha.
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by cypherpunks3):

 {{{
 - The bandwidth-limitation logic has been refactored so that
   bandwidth calculations are performed on-demand, rather than every
   TokenBucketRefillInterval milliseconds. This change should improve
   the granularity of our bandwidth calculations, and limit the
   number of times that the Tor process needs to wake up when it is
   idle. Closes ticket 25373.
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by loskiq):

 Replying to [comment:18 dcf]:
 > If you have time, you can help by testing versions between 0.2.9.17 and
 0.3.4.9 to see which versions work.

 I tested different versions of Tor, and here is the result:

 || Tor version 0.2.9.17. || working ||
 || Tor version 0.3.2.10 (git-31cc63deb69db819). || working ||
 || Tor version 0.3.3.10 (git-2e94df92caee0fca). || working ||
 || Tor version 0.3.3.6 (git-7dd0813e783ae16e). || working ||
 || Tor version 0.3.3.7 (git-035a35178c92da94). || working ||
 || Tor version 0.3.3.9 (git-45028085ea188baf). || working ||
 || Tor version 0.3.4.1-alpha (git-deb8970a29ef7427). || not working ||
 || Tor version 0.3.4.2-alpha (git-bc951e83aac770d1). || not working ||
 || Tor version 0.3.4.6-rc (git-6045c26d8442913e). || not working ||
 || Tor version 0.3.4.7-rc (git-8465a8d84647c349). || not working ||
 || Tor version 0.3.4.8 (git-da95b91355248ad8). || not working ||
 || Tor version 0.3.4.9 (git-4ac3ccf2863b86e7). || not working ||

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by cypherpunks3):

 {{{
 Dec 07 06:51:49.000 [info] directory_send_command(): Downloading consensus
 from 154.16.245.120:443 using /tor/status-vote/current/consensus-
 microdesc/0232AF+14C131+23D15D+27102B+49015F+D586D1+E8A9C4+ED03BB+EFCBE7.z
 Dec 07 06:51:49.000 [info] internal circ (length 1):
 $072AF4D16146012D6E8DFA8518B169345D8CEA51(open)
 Dec 07 06:51:49.000 [info] link_apconn_to_circ(): Looks like completed
 circuit to [scrubbed] does allow optimistic data for connection to
 [scrubbed]
 Dec 07 06:51:49.000 [info] connection_ap_handshake_send_begin(): Sending
 relay cell 1 on circ 4041868625 to begin stream 5333.
 Dec 07 06:51:49.000 [info] connection_ap_handshake_send_begin():
 Address/port sent, ap socket -1, n_circ_id 4041868625
 Dec 07 06:51:49.000 [info] connection_edge_process_inbuf(): data from edge
 while in 'waiting for connect response' state. Sending it anyway.
 package_partial=0, buflen=194
 Dec 07 06:51:49.000 [info] connection_edge_process_inbuf(): data from edge
 while in 'waiting for connect response' state. Sending it anyway.
 package_partial=1, buflen=194
 Dec 07 06:51:50.000 [info] connection_edge_process_relay_cell_not_open():
 'connected' received for circid 4041868625 streamid 5333 after 1 seconds.
 Dec 07 06:51:50.000 [info] internal circ (length 1):
 $072AF4D16146012D6E8DFA8518B169345D8CEA51(open)
 Dec 07 06:51:50.000 [notice] Bootstrapped 25%: Loading networkstatus
 consensus
 Dec 07 06:56:56.000 [info] run_connection_housekeeping(): Expiring wedged
 directory conn (fd -1, purpose 14)
 Dec 07 06:56:56.000 [info] entry_guards_note_guard_failure(): Recorded
 failure for primary confirmed guard
 $072AF4D16146012D6E8DFA8518B169345D8CEA51
 ($072AF4D16146012D6E8DFA8518B169345D8CEA51)
 Dec 07 06:56:56.000 [info] should_delay_dir_fetches(): Delaying dir
 fetches (no running bridges known)
 Dec 07 06:56:56.000 [info] connection_free_minimal(): Freeing linked
 Directory connection [client reading] with 32975 bytes on inbuf, 0 on
 outbuf.
 Dec 07 06:56:56.000 [info] connection_edge_reached_eof(): conn (fd -1)
 reached eof. Closing.
 Dec 07 06:56:56.000 [info] connection_free_minimal(): Freeing linked Socks
 connection [open] with 0 bytes on inbuf, 0 on outbuf.
 Dec 07 06:56:57.000 [info] should_delay_dir_fetches(): Delaying dir
 fetches (no running bridges known)
 Dec 07 06:56:57.000 [info] should_delay_dir_fetches(): Delaying dir
 fetches (no running bridges known)
 Dec 07 06:56:57.000 [notice] Delaying directory fetches: No running
 bridges
 Dec 07 06:56:58.000 [info] circuit_mark_for_close_(): Circuit 0 (id: 1)
 marked for close at command.c:610 (orig reason: 521, new reason: 0)
 Dec 07 06:56:58.000 [info] circuit_free_(): Circuit 0 (id: 1) has been
 freed.
 Dec 07 06:56:58.000 [info] should_delay_dir_fetches(): Delaying dir
 fetches (no running bridges known)
 Dec 07 06:56:58.000 [info] should_delay_dir_fetches(): Delaying dir
 fetches (no running bridges known)
 Dec 07 06:56:59.000 [info] should_delay_dir_fetches(): Delaying dir
 fetches (no running bridges known)
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by dcf):

 Replying to [comment:17 loskiq]:
 > I just installed the bridge version 0.2.9.17, and the client immediately
 started working. I believe that the problem of 25% is related to the new
 version of the bridge.

 Oh! How surprising. I see from attachment:tor_bridge.log that formerly you
 were using 0.3.4.9. So downgrading from 0.3.4.9 to 0.2.9.17 on the bridge
 (keeping the client at 0.3.4.9) made the bridge start working.

 This also matches with the bridges you posted in comment:16.
 ||154.16.245.120:443 ||not working ||0.3.4.9
 
||[https://metrics.torproject.org/rs.html#details/F80D5303AEDF76071D205788B375719605736F2C
 relay search] [https://archive.is/fI6o0 (archive)] ||
 ||93.190.138.248:41248 ||working ||0.2.9.17
 
||[https://metrics.torproject.org/rs.html#details/BDBA3779B358235EE22161C171A74BFE0E004E66
 relay search] [https://archive.is/7ELUI (archive)] ||

 I'll ask and see if any core-tor developer have an idea about what it
 wrong. If you have time, you can help by testing versions between 0.2.9.17
 and 0.3.4.9 to see which versions work.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by loskiq):

 I just installed the bridge version 0.2.9.17, and the client immediately
 started working. I believe that the problem of 25% is related to the new
 version of the bridge.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by loskiq):

 I have just tested working with another obfs4 bridge received from
 brid...@torproject.org. The problem persists. Stuck in 25%. But there is a
 bridge with which the client works correctly.

 The bridges I checked:

 Not worked
 {{{
 obfs4 154.16.245.120:443 072AF4D16146012D6E8DFA8518B169345D8CEA51
 cert=/nZrKfIZrw39ij9PLfoY0Uq+CCyQIYpP0BefZJbe2yf9cbJtXynlsWLwV77pVbKK4xDvHw
 iat-mode=0
 }}}

 Worked
 {{{
 obfs4 93.190.138.248:41248 577059FF2CADFB6AEFBCC78FFAB4DBEC1AF8A57B
 cert=d5ijyl75isX32Vx9yQkSDZicYPiamD413fnyKf/5TQxBTytobCVrzX7ATtBKZGOwIQ4IYg
 iat-mode=0
 }}}

 I think this problem is related to bridges, not clients...

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by loskiq):

 It seems with obfs4proxy all right

 Replying to [comment:14 dcf]:

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by loskiq):

 * Attachment "obfs4proxy_client.log" added.

 obfs4proxy log of client

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by loskiq):

 * Attachment "obfs4proxy_server.log" added.

 obfs4proxy log of server

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by dcf):

 Replying to [comment:13 loskiq]:
 > By the way, with the same configuration, the client successfully works
 with other bridges.

 I see. This means my guess was wrong.

 I don't have any other good ideas, except to turn on obfs4proxy logging.
 In the client torrc, use
 {{{
 ClientTransportPlugin obfs4 exec /usr/local/bin/obfs4proxy --enableLogging
 --logLevel=DEBUG
 }}}
 In the bridge torrc, use
 {{{
 ServerTransportPlugin obfs4 exec /usr/local/bin/obfs4proxy --enableLogging
 --logLevel=DEBUG
 }}}
 In both cases, the log file will appear in
 /pt_state/obfs4proxy.log.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by loskiq):

 By the way, with the same configuration, the client successfully works
 with other bridges.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by loskiq):

 Thank you for your answer, but unfortunately it did not help me. First I
 deleted ''/state'' and restarted bridge, then I changed
 ''DataDirectory'' to ''/tmp'', restarted bridge and wrote the necessary
 changes to torrc of client. Client still unable to connect and stuck in
 25%.

 Replying to [comment:11 dcf]:

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by dcf):

 Replying to [ticket:28717 loskiq]:
 > {{{
 > Dec 04 10:47:39.000 [notice] Delaying directory fetches: No running
 bridges
 > }}}

 I have seen this error before while testing PTs. I think it is a tor bug.
 I don't know the exact cause, but after a few bridge failures, tor will
 cache the fact that it thinks all bridges are down, and refuse even to try
 connecting to them. See:
  * comment:3:ticket:26891
  * #11301

 My usual workaround is to delete the /state file and restart tor.
 You can also try adding a line like this to your torrc:
 {{{
 DataDirectory tmp-datadir
 }}}
 If that works, then the problem is likely the one I described.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by loskiq):

 * Attachment "tor_bridge.log" added.

 log on bridge

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by loskiq):

 * Attachment "tor_client.log" added.

 log on client

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by teor):

 The client can connect to your bridge, but your bridge has no descriptor:
 {{{
 Dec 05 17:57:29.000 [info] handle_response_fetch_desc(): Received server
 info (body size 0) from server '54.93.104.200:40635'
 Dec 05 17:57:29.000 [info] handle_response_fetch_desc(): Received http
 status code 404 ("Servers unavailable") from server '54.93.104.200:40635'
 while fetching "/tor/server/authority.z". I'll try again soon.
 }}}

 That's really strange, because your bridge has a descriptor:
 {{{
 Dec 04 09:07:05.000 [notice] Guessed our IP address as 54.93.104.200
 (source: 79.137.112.4).
 Dec 04 09:07:05.000 [notice] Self-testing indicates your ORPort is
 reachable from the outside. Excellent. Publishing server descriptor.
 }}}

 Can you please post the logs from your bridge, *after* you changed the IP
 address and restarted the bridge?

 Can you post info-level logs from your client and bridge, that contain the
 lines that your client and bridge log when the client tries to connect?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by loskiq):

 * Attachment "tor.log" added.

 log on the client

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by teor):

 Ok, tor has a logging bug.

 And it's still not clear why your client can't connect to your bridge.
 Can you connect to the obfs4 port from your client's IP address?
 Is the bridge line correct?
 Can you collect info-level logs on the client, and post them here.
 (You can redact if you want to.)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by loskiq):

 I checked port 40635 on IPv4 via nmap, and it is open. I just changed the
 IP address of my bridge. Sorry. The correct IP address of my bridge is
 54.93.104.200, not 79.103.124.21


 {{{
 loskiq@loskiq-work:~$ nmap 54.93.104.200 -p 40635

 Starting Nmap 7.40 ( https://nmap.org ) at 2018-12-05 17:33 MSK
 Nmap scan report for ec2-54-93-104-200.eu-central-1.compute.amazonaws.com
 (54.93.104.200)
 Host is up (0.070s latency).
 PORT  STATE SERVICE
 40635/tcp open  unknown

 Nmap done: 1 IP address (1 host up) scanned in 0.28 seconds
 }}}

 And I removed the option ''HardwareAccel''. Thanks for this.

 Replying to [comment:7 teor]:

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by teor):

 It looks like your obfs4 is only listening on IPv6:
 {{{
 Dec 04 08:12:04.000 [notice] Registered server transport 'obfs4' at
 '[::]:40635'
 }}}

 But your client is configured to connect via IPv4:
 {{{
 Bridge obfs4 79.103.124.21:40635 3E0CFCEE7183970DCC70ABC2D10518BC288BF0DE
 cert=ZzN5WrKqUZCkHYlb8gh0Ew1B5tMgO+oP60jxfar1r3A8yMH/syZ0T3td4x13VbEj1+G4EQ
 iat-mode=0
 }}}

 Unless you changed the IPv4 address to an IPv6 address when you redacted
 it.
 (Please don't change logs without telling us what you changed, it makes
 debugging much harder.)

 Can you check if port 40635 is open on IPv4, IPv6, or both?
 If it's open on IPv4, tor has a logging bug.

 If it's not, you can use ServerTransportListenAddress to set the correct
 address.
 And tor has a default IP version bug.

 Also, you probably don't need this torrc option, it doesn't do anything on
 most systems:
 HardwareAccel 1

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by loskiq):

 This ip address belongs to my bridge. I wanted to hide it and therefore I
 changed the address in the logs, but missed this line.

 Replying to [comment:5 cypherpunks3]:
 > > Guessed our IP address as 54.93.104.200 (source: 79.137.112.4).
 >
 > This.
 >
 > 54.93.104.200 works for me

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by cypherpunks3):

 > Guessed our IP address as 54.93.104.200 (source: 79.137.112.4).

 This.

 54.93.104.200 works for me

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by loskiq):

 Attached. Yes, bridge is bootstrapped

 Replying to [comment:3 teor]:
 > What do the logs on the bridge say?
 > Has the bridge bootstrapped?
 >
 > Can you attach your bridge and client torrcs?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by loskiq):

 * Attachment "torrc_of_the_bridge.txt" added.

 torrc of the bridge

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by loskiq):

 * Attachment "log_of_the_bridge.txt" added.

 log of the bridge

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by loskiq):

 * Attachment "torrc_of_the_client.txt" added.

 torrc of the client

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by teor):

 * milestone:   => Tor: unspecified


Comment:

 What do the logs on the bridge say?
 Has the bridge bootstrapped?

 Can you attach your bridge and client torrcs?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by loskiq):

 P.S. The attached logs belongs to the Tor client, not the bridge

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by loskiq):

 * cc: loskiq@… (added)
 * component:  - Select a component => Core Tor/Tor


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs