[tor-bugs] #25529 [Applications/Tor Browser]: Tor meeks works smoothly when starting from Tor Browser, while hangs a lot when starting from command line

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

#25529: Tor meeks works smoothly when starting from Tor Browser, while hangs a lot
when starting from command line
-------------------------------------+-------------------------------------
     Reporter:  omareg94             |      Owner:  tbb-team
         Type:  defect               |     Status:  new
     Priority:  Medium               |  Milestone:
    Component:  Applications/Tor     |    Version:  Tor: 0.3.2.10
  Browser                            |   Keywords:  meek tor-browser-bundle
     Severity:  Normal               |  configuration bridge pluggable-
                                     |  transports connection
Actual Points:                       |  Parent ID:
       Points:                       |   Reviewer:
      Sponsor:                       |
-------------------------------------+-------------------------------------
 I'm using this command in order to start Tor from command line
 (**''Windows 10''**):

 {{{
 cd "C:\Tor Browser\Browser\"
 "C:\Tor Browser\Browser\TorBrowser\Tor\tor.exe" -f "C:\Tor
 Browser\Browser\TorBrowser\Data\Tor\torrc" | more
 }}}

 Some times Tor is able to connect successfully, but many times problems
 occur. On the other side when starting Tor from Browser, the problems
 never happen and every thing go smoothly.

 ----

 Comparison between my experience of starting Tor from command line and
 starting it from Tor Browser:


 == When starting Tor from command line:
 Connection hangs a lot. And when I have some request like:

 {{{
 curl --socks5-hostname localhost:9050 http://checkip.amazonaws.com/
 }}}
 I get:
 {{{
 curl: (7) Can't complete SOCKS5 connection to 0.0.0.0:0. (6)
 }}}

 == When starting Tor from Tor Browser:
 Everything goes very smooth and no hanging happens. Even the same meek
 address is being used and hasn't changed.

 So, I guess the problem isn't with the meek address, I think I'm missing
 something with the configuration when starting Tor from command line.


 A log snippet of starting Tor **from command line**:

 {{{
 Mar 11 05:04:03.000 [notice] Tor 0.3.2.10 opening new log file.
 Mar 11 05:04:03.000 [notice] Tor 0.3.2.10 running on Windows 8 with
 Libevent 2.0.22-stable, OpenSSL 1.0.2n, Zlib 1.2.8, Liblzma N/A, and
 Libzstd N/A.
 Mar 11 05:04:03.000 [notice] Tor can't help you if you use it wrong! Learn
 how to be safe at https://www.torproject.org/download/download#warning
 Mar 11 05:04:03.000 [notice] Read configuration file "C:\Tor
 Browser\Browser\TorBrowser\Data\Tor\torrc".
 Mar 11 05:04:03.000 [notice] Scheduler type KISTLite has been enabled.
 Mar 11 05:04:03.000 [notice] Opening Socks listener on 127.0.0.1:9050
 Mar 11 05:04:03.000 [notice] Opening Control listener on 127.0.0.1:9051
 Mar 11 05:04:03.000 [notice] Parsing GEOIP IPv4 file C:\Tor
 Browser\Browser\TorBrowser\Data\Tor\geoip.
 Mar 11 05:04:04.000 [notice] Parsing GEOIP IPv6 file C:\Tor
 Browser\Browser\TorBrowser\Data\Tor\geoip6.
 Mar 11 05:04:06.000 [notice] Bootstrapped 0%: Starting
 Mar 11 05:04:10.000 [notice] Starting with guard context "bridges"
 Mar 11 05:04:10.000 [notice] new bridge descriptor 'TorLandMeek' (cached):
 $A1A1234A123AB12345A1234A1A1234A123456789~TorLandMeek at 0.0.2.0
 Mar 11 05:04:10.000 [notice] Bootstrapped 80%: Connecting to the Tor
 network
 Mar 11 05:04:12.000 [notice] Bootstrapped 85%: Finishing handshake with
 first hop
 Mar 11 05:04:13.000 [notice] Delaying directory fetches: No running
 bridges
 Mar 11 05:07:12.000 [notice] Tried for 120 seconds to get a connection to
 [scrubbed]:80. Giving up. (waiting for circuit)
 Mar 11 05:07:39.000 [notice] Application request when we haven't received
 a consensus with exits. Optimistically trying known bridges again.
 Mar 11 05:07:41.000 [notice] Delaying directory fetches: No running
 bridges
 Mar 11 05:09:39.000 [notice] Tried for 120 seconds to get a connection to
 [scrubbed]:80. Giving up. (waiting for circuit)
 Mar 11 05:09:49.000 [notice] Application request when we haven't received
 a consensus with exits. Optimistically trying known bridges again.
 Mar 11 05:09:51.000 [notice] Delaying directory fetches: No running
 bridges
 Mar 11 05:11:50.000 [notice] Tried for 120 seconds to get a connection to
 [scrubbed]:80. Giving up. (waiting for circuit)
 }}}


 A log snippet of starting Tor **from Tor Browser**:

 {{{
 Mar 11 05:12:10.000 [notice] Tor 0.3.2.10 opening log file.
 Mar 11 05:12:10.000 [notice] Tor 0.3.2.10 running on Windows 8 with
 Libevent 2.0.22-stable, OpenSSL 1.0.2n, Zlib 1.2.8, Liblzma N/A, and
 Libzstd N/A.
 Mar 11 05:12:10.000 [notice] Tor can't help you if you use it wrong! Learn
 how to be safe at https://www.torproject.org/download/download#warning
 Mar 11 05:12:10.000 [notice] Read configuration file "C:\Tor
 Browser\Browser\TorBrowser\Data\Tor\torrc-defaults".
 Mar 11 05:12:10.000 [notice] Read configuration file "C:\Tor
 Browser\Browser\TorBrowser\Data\Tor\torrc".
 Mar 11 05:12:10.000 [notice] Scheduler type KISTLite has been enabled.
 Mar 11 05:12:10.000 [notice] Opening Control listener on 127.0.0.1:9051
 Mar 11 05:12:10.000 [notice] Opening Control listener on 127.0.0.1:9151
 Mar 11 05:12:10.000 [notice] DisableNetwork is set. Tor will not make or
 accept non-control network connections. Shutting down all existing
 connections.
 Mar 11 05:12:10.000 [notice] Parsing GEOIP IPv4 file C:\Tor
 Browser\Browser\TorBrowser\Data\Tor\geoip.
 Mar 11 05:12:10.000 [notice] Parsing GEOIP IPv6 file C:\Tor
 Browser\Browser\TorBrowser\Data\Tor\geoip6.
 Mar 11 05:12:11.000 [notice] Bootstrapped 0%: Starting
 Mar 11 05:12:12.000 [notice] Starting with guard context "bridges"
 Mar 11 05:12:12.000 [notice] new bridge descriptor 'TorLandMeek' (cached):
 $A1A1234A123AB12345A1234A1A1234A123456789~TorLandMeek at 0.0.2.0
 Mar 11 05:12:12.000 [notice] Delaying directory fetches: DisableNetwork is
 set.
 Mar 11 05:12:12.000 [notice] New control connection opened from 127.0.0.1.
 Mar 11 05:12:13.000 [notice] DisableNetwork is set. Tor will not make or
 accept non-control network connections. Shutting down all existing
 connections.
 Mar 11 05:12:13.000 [notice] Tor 0.3.2.10 opening log file.
 Mar 11 05:12:13.000 [notice] New control connection opened from 127.0.0.1.
 Mar 11 05:12:13.000 [notice] DisableNetwork is set. Tor will not make or
 accept non-control network connections. Shutting down all existing
 connections.
 Mar 11 05:12:13.000 [notice] Tor 0.3.2.10 opening log file.
 Mar 11 05:12:13.000 [notice] Opening Socks listener on 127.0.0.1:9150
 Mar 11 05:12:13.000 [notice] Tor 0.3.2.10 opening log file.
 Mar 11 05:12:14.000 [notice] Bootstrapped 80%: Connecting to the Tor
 network
 Mar 11 05:12:14.000 [notice] Bootstrapped 85%: Finishing handshake with
 first hop
 Mar 11 05:12:17.000 [notice] Bootstrapped 90%: Establishing a Tor circuit
 Mar 11 05:12:20.000 [notice] new bridge descriptor 'TorLandMeek' (fresh):
 $A1A1234A123AB12345A1234A1A1234A123456789~TorLandMeek at 0.0.2.0
 Mar 11 05:12:25.000 [notice] Tor has successfully opened a circuit. Looks
 like client functionality is working.
 Mar 11 05:12:25.000 [notice] Bootstrapped 100%: Done
 Mar 11 05:12:37.000 [notice] New control connection opened from 127.0.0.1.
 }}}

 I'm looking for making Tor (when started from command line) **work as
 smooth as** it is when started from Tor Browser.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25529>
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