[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-bugs] #19408 [Obfuscation]: Tor cannot work in China

Subject: [tor-bugs] #19408 [Obfuscation]: Tor cannot work in China
From: "Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>
Date: Mon, 13 Jun 2016 18:16:13 -0000
Auto-submitted: auto-generated
Delivered-to: archiver@xxxxxxxx
Delivery-date: Mon, 13 Jun 2016 14:16:25 -0400
List-archive: <http://lists.torproject.org/pipermail/tor-bugs/>
List-help: <mailto:tor-bugs-request@lists.torproject.org?subject=help>
List-id: "auto: Tor bug tracker status mails" <tor-bugs.lists.torproject.org>
List-post: <mailto:tor-bugs@lists.torproject.org>
List-subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs>, <mailto:tor-bugs-request@lists.torproject.org?subject=subscribe>
List-unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-bugs>, <mailto:tor-bugs-request@lists.torproject.org?subject=unsubscribe>
Reply-to: tor-assistants@xxxxxxxxxxxxxx
Sender: "tor-bugs" <tor-bugs-bounces@xxxxxxxxxxxxxxxxxxxx>

#19408: Tor cannot work in China
-----------------------------+------------------------------
     Reporter:  sam1275      |      Owner:
         Type:  defect       |     Status:  new
     Priority:  High         |  Milestone:
    Component:  Obfuscation  |    Version:  Tor: unspecified
     Severity:  Blocker      |   Keywords:  block
Actual Points:               |  Parent ID:
       Points:               |   Reviewer:
      Sponsor:               |
-----------------------------+------------------------------
 Sadly Tor is not working in China without VPN, it cannot even work with
 any plugin such as obfs4, amazon, and with new bridges also no help. This
 problem exist on any OS for a long time.
 Here's a example log:
 6/13/2016 23:36:52 PM.200 [NOTICE] DisableNetwork is set. Tor will not
 make or accept non-control network connections. Shutting down all existing
 connections.
 6/13/2016 23:37:17 PM.700 [NOTICE] DisableNetwork is set. Tor will not
 make or accept non-control network connections. Shutting down all existing
 connections.
 6/13/2016 23:37:17 PM.700 [NOTICE] DisableNetwork is set. Tor will not
 make or accept non-control network connections. Shutting down all existing
 connections.
 6/13/2016 23:37:17 PM.700 [NOTICE] DisableNetwork is set. Tor will not
 make or accept non-control network connections. Shutting down all existing
 connections.
 6/13/2016 23:37:17 PM.700 [NOTICE] Opening Socks listener on
 127.0.0.1:9150
 6/13/2016 23:37:24 PM.400 [NOTICE] Bootstrapped 5%: Connecting to
 directory server
 6/13/2016 23:37:24 PM.400 [NOTICE] Bootstrapped 10%: Finishing handshake
 with directory server
 6/13/2016 23:37:45 PM.500 [WARN] Proxy Client: unable to connect to
 109.105.109.165:10527 ("general SOCKS server failure")
 6/13/2016 23:37:45 PM.500 [WARN] Proxy Client: unable to connect to
 154.35.22.12:80 ("general SOCKS server failure")
 6/13/2016 23:37:45 PM.500 [WARN] Proxy Client: unable to connect to
 154.35.22.10:443 ("general SOCKS server failure")
 6/13/2016 23:37:45 PM.500 [WARN] Proxy Client: unable to connect to
 83.212.101.3:41213 ("general SOCKS server failure")
 6/13/2016 23:37:45 PM.500 [WARN] Proxy Client: unable to connect to
 104.131.108.182:56880 ("general SOCKS server failure")
 6/13/2016 23:37:45 PM.500 [WARN] Proxy Client: unable to connect to
 109.105.109.147:13764 ("general SOCKS server failure")
 6/13/2016 23:37:45 PM.500 [WARN] Proxy Client: unable to connect to
 192.99.11.54:443 ("general SOCKS server failure")
 6/13/2016 23:37:45 PM.500 [WARN] Proxy Client: unable to connect to
 198.245.60.50:443 ("general SOCKS server failure")
 6/13/2016 23:38:26 PM.000 [WARN] Proxy Client: unable to connect to
 154.35.22.13:443 ("general SOCKS server failure")
 6/13/2016 23:38:27 PM.900 [WARN] Proxy Client: unable to connect to
 154.35.22.9:60873 ("general SOCKS server failure")
 6/13/2016 23:38:27 PM.900 [WARN] Proxy Client: unable to connect to
 154.35.22.11:49868 ("general SOCKS server failure")
 6/13/2016 23:52:45 PM.300 [WARN] Proxy Client: unable to connect to
 109.105.109.165:10527 ("general SOCKS server failure")
 6/13/2016 23:52:45 PM.300 [WARN] Proxy Client: unable to connect to
 154.35.22.12:80 ("general SOCKS server failure")
 6/13/2016 23:52:45 PM.300 [WARN] Proxy Client: unable to connect to
 154.35.22.10:443 ("general SOCKS server failure")
 6/13/2016 23:52:45 PM.300 [WARN] Proxy Client: unable to connect to
 154.35.22.13:443 ("general SOCKS server failure")
 6/13/2016 23:52:45 PM.300 [WARN] Proxy Client: unable to connect to
 83.212.101.3:41213 ("general SOCKS server failure")
 6/13/2016 23:52:45 PM.300 [WARN] Proxy Client: unable to connect to
 104.131.108.182:56880 ("general SOCKS server failure")
 6/13/2016 23:52:45 PM.300 [WARN] Proxy Client: unable to connect to
 109.105.109.147:13764 ("general SOCKS server failure")
 6/13/2016 23:52:45 PM.300 [WARN] Proxy Client: unable to connect to
 192.99.11.54:443 ("general SOCKS server failure")
 6/13/2016 23:52:45 PM.700 [WARN] Proxy Client: unable to connect to
 198.245.60.50:443 ("general SOCKS server failure")
 6/13/2016 23:53:24 PM.700 [WARN] Proxy Client: unable to connect to
 154.35.22.9:60873 ("general SOCKS server failure")
 6/13/2016 23:53:26 PM.200 [WARN] Proxy Client: unable to connect to
 154.35.22.11:49868 ("general SOCKS server failure")
 6/14/2016 0:07:45 AM.200 [WARN] Proxy Client: unable to connect to
 109.105.109.165:10527 ("general SOCKS server failure")
 6/14/2016 0:07:45 AM.200 [WARN] Proxy Client: unable to connect to
 154.35.22.12:80 ("general SOCKS server failure")
 6/14/2016 0:07:45 AM.200 [WARN] Proxy Client: unable to connect to
 154.35.22.10:443 ("general SOCKS server failure")
 6/14/2016 0:07:45 AM.200 [WARN] Proxy Client: unable to connect to
 83.212.101.3:41213 ("general SOCKS server failure")
 6/14/2016 0:07:45 AM.200 [WARN] Proxy Client: unable to connect to
 104.131.108.182:56880 ("general SOCKS server failure")
 6/14/2016 0:07:45 AM.200 [WARN] Proxy Client: unable to connect to
 109.105.109.147:13764 ("general SOCKS server failure")
 6/14/2016 0:07:45 AM.300 [WARN] Proxy Client: unable to connect to
 192.99.11.54:443 ("general SOCKS server failure")
 6/14/2016 0:07:46 AM.900 [WARN] Proxy Client: unable to connect to
 198.245.60.50:443 ("general SOCKS server failure")
 6/14/2016 0:08:26 AM.000 [WARN] Proxy Client: unable to connect to
 154.35.22.11:49868 ("general SOCKS server failure")
 6/14/2016 0:08:27 AM.700 [WARN] Proxy Client: unable to connect to
 154.35.22.13:443 ("general SOCKS server failure")
 6/14/2016 0:08:28 AM.000 [WARN] Proxy Client: unable to connect to
 154.35.22.9:60873 ("general SOCKS server failure")
 6/14/2016 0:43:12 AM.700 [NOTICE] Closing no-longer-configured Socks
 listener on 127.0.0.1:9150
 6/14/2016 0:43:12 AM.700 [NOTICE] DisableNetwork is set. Tor will not make
 or accept non-control network connections. Shutting down all existing
 connections.
 6/14/2016 0:43:12 AM.700 [NOTICE] Closing old Socks listener on
 127.0.0.1:9150

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

Follow-Ups:
- Re: [tor-bugs] #19408 [Obfuscation]: Tor cannot work in China
  - From: Tor Bug Tracker & Wiki
- Re: [tor-bugs] #19408 [Obfuscation]: Tor cannot work in China
  - From: Tor Bug Tracker & Wiki

Prev by Author: Re: [tor-bugs] #19407 [Core Tor/Torsocks]: Support FD passing on Unix socket
Next by Author: Re: [tor-bugs] #17094 [Core Tor/Tor]: implicitly set 'UseBridges 1' when using 'Bridge [transport] IP:ORPort [fingerprint]'
Previous by thread: [tor-bugs] [Tor Bug Tracker & Wiki] Batch modify: #11727, #13184, #14322, #16355, #16432, #16433, #16434, #16435, #16934, #16991, #17340, #17475, #17478, #17479, #17618, #17743, #17936, #17980, #19376
Next by thread: Re: [tor-bugs] #19408 [Obfuscation]: Tor cannot work in China
Index(es):
- Author
- Thread