Re: [tor-bugs] #26823 [Core Tor/Tor]: TOR doesn't work at all on slow connections. TOR is fully broken

[Tor Bug Tracker & Wiki]

#26823: TOR doesn't work at all on slow connections. TOR is fully broken
-+-
 Reporter:  white_supremacy_pedo |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Immediate|  Milestone:
Component:  Core Tor/Tor |Version:  Tor:
 |  unspecified
 Severity:  Blocker  | Resolution:
 Keywords:  slow connection, pedo, cp, tor,  |  Actual Points:
  broken |
Parent ID:   | Points:
 Reviewer:  pastly   |Sponsor:
 |  SponsorR
-+-

Comment (by white_supremacy_pedo):

 When the bug happens TOR log is spammed with lines like this:
 [NOTICE] Rend stream is 120 seconds late. Giving up on address
 '[scrubbed].onion'.
 [NOTICE] Tried for 120 seconds to get a connection to [scrubbed]:80.
 Giving up.
 [NOTICE] Tried for 120 seconds to get a connection to [scrubbed]:443.
 Giving up. (waiting for circuit)
 [NOTICE] Tried for 120 seconds to get a connection to [scrubbed]:80.
 Giving up. (waiting for circuit)

 occasionally I get other lines like (not in order, just examples):
 [NOTICE] Have tried resolving or connecting to address '[scrubbed]' at 3
 different places. Giving up.
 [NOTICE] We tried for XX seconds to connect to '[scrubbed]' using exit XXX
 at XXX. Retrying on a new circuit.
 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
 [NOTICE] Our IP address has changed.  Rotating keys...
 [NOTICE] No circuits are opened. Relaxed timeout for circuit XXX (a
 Measuring circuit timeout 3-hop circuit in state doing handshakes with
 channel state open) to ms. However, it appears the circuit has timed
 out anyway.
 [NOTICE] Tor has not observed any network activity for the past XX
 seconds. Disabling circuit build timeout recording.
 [NOTICE] Your Guard XXX is failing more circuits than usual. Most likely
 this means the Tor network is overloaded. Success counts are XXX/XXX. Use
 counts are XX/XX. XXX circuits completed, XX were unusable, XX collapsed,
 and XX timed out. For reference, your timeout cutoff is XX seconds.
 [NOTICE] Your Guard XXX is failing to carry more streams on its circuits
 than usual. Most likely this means the Tor network is overloaded or your
 network connection is poor. Use counts are XX/XX. Success counts are
 XXX/XXX. XXX circuits completed, XX were unusable, XX collapsed, and XX
 timed out. For reference, your timeout cutoff is XX seconds.

 XXX - removed

--
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

[tor-bugs] #26823 [Core Tor/Tor]: TOR doesn't work at all on slow connections. TOR is fully broken

[Tor Bug Tracker & Wiki]

#26823: TOR doesn't work at all on slow connections. TOR is fully broken
-+-
 Reporter:   |  Owner:  (none)
  white_supremacy_pedo   |
 Type:  defect   | Status:  new
 Priority:  Immediate|  Milestone:
Component:  Core Tor/Tor |Version:  Tor: unspecified
 Severity:  Blocker  |   Keywords:  slow connection, pedo,
 |  cp, tor, broken
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:  pastly
  Sponsor:  SponsorR |
-+-
 tor stops working on slow connections for no reasons. it is unusable at
 all in countries with slow connections.

 how to get this bug:
 1. connect to internet using slow connection ( <150kbit/s, 200ms+ latency)
 2. start torbrowser. it connects fast, no problems.
 3. start browsing cp websites or dark markets. everything works.
 4. now go to kitchen, cook and eat some food, leave PC running.
 5. after 10-50 minutes, go back to your PC.
 6. click something on TorBrowser, a link. DOESN'T WORK. when I click link
 there is zero network activity, so Tor doesn't even try to request it
 but when I look tor.exe actually is connected to tor entry node with
 status Established. but nothing is sent or received when you click in
 TorBrowser (or if you try to use 127.0.0.1:9150 with other application, so
 it's not a TorBrowser bug).
 7. while Tor doesn't work at all, clearnet works perfectly with low
 latency.
 8. now I kill tor.exe external TCP connections (read again. I am not
 killing process, just it's external connections).
 9. tor.exe instantly reconnects to those TCP connections. But when I click
 something in TorBrowser there is zero network activity.
 10. I repeat step 9 again. tor.exe reconnects again (but to different
 entry node?) and it INSTANTLY works again. I can click links on TorBrowser
 and they load.
 11. After some minutes pass, go back to step 5.

 In steps 8-10, instead of killing TOR tcp connections you can also kill
 tor.exe to start working again. TorBrowser will restart it and it will
 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