[tor-talk] I can't use Tor via "obfs3" or other methods.

[isis]

Jason Long transcribed 3.4K bytes:
> 
> 
> Any idea?
> 
> 
> On Tuesday, September 29, 2015 11:17 PM, Jason Long <hack3rcon at yahoo.com> wrote:
> Hello.
> I can't use Tor via "obfs3" or other methods. I used Bridges too but not matter. What is your idea? my Tor log is :
> 
> 09/29/2015 10:49:47.200 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 
> 09/29/2015 10:50:02.500 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 
> 09/29/2015 10:50:02.500 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 
> 09/29/2015 10:50:02.500 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 
> 09/29/2015 10:50:02.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 
> 09/29/2015 10:50:03.000 [NOTICE] Bootstrapped 5%: Connecting to directory server 
> 09/29/2015 10:50:03.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server 
> 09/29/2015 10:55:07.000 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 3; recommendation warn; host 3BECEABD174AE41C5CCC17254A40DD24EC5372CD at 148.251.156.199:443) 
> 09/29/2015 10:55:07.000 [WARN] 3 connections have failed: 
> 09/29/2015 10:55:07.000 [WARN]  2 connections died in state handshaking (Tor, v3 handshake) with SSL state SSL negotiation finished successfully in OPEN 
> 09/29/2015 10:55:07.000 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object) 
> 09/29/2015 10:55:46.800 [NOTICE] Bootstrapped 15%: Establishing an encrypted directory connection 
> 09/29/2015 10:55:47.000 [NOTICE] Bootstrapped 20%: Asking for networkstatus consensus 
> 09/29/2015 10:55:48.400 [WARN] Problem bootstrapping. Stuck at 20%: Asking for networkstatus consensus. (No route to host; NOROUTE; count 4; recommendation warn; host 6E689CABD837ADE88A7179A4A9FD18EE73A00D2C at 133.236.115.222:100) 
> 09/29/2015 10:55:48.400 [WARN] 3 connections have failed: 
> 09/29/2015 10:55:48.400 [WARN]  2 connections died in state handshaking (Tor, v3 handshake) with SSL state SSL negotiation finished successfully in OPEN 
> 09/29/2015 10:55:48.400 [WARN]  1 connections died in state connect()ing with SSL state (No SSL object) 
> 09/29/2015 10:55:49.700 [NOTICE] new bridge descriptor 'puerta' (fresh): $3BECEABD174AE41C5CCC17254A40DD24EC5372CD~puerta at 148.251.156.199 
> 09/29/2015 10:55:49.700 [NOTICE] I learned some more directory information, but not enough to build a circuit: We have no usable consensus. 
> 09/29/2015 10:55:49.700 [NOTICE] Bootstrapped 25%: Loading networkstatus consensus 
> 09/29/2015 10:55:58.400 [WARN] Problem bootstrapping. Stuck at 25%: Loading networkstatus consensus. (No route to host; NOROUTE; count 5; recommendation warn; host 6E689CABD837ADE88A7179A4A9FD18EE73A00D2C at 133.236.115.222:100) 
> 09/29/2015 10:55:58.400 [WARN] 4 connections have failed: 
> 09/29/2015 10:55:58.400 [WARN]  2 connections died in state handshaking (Tor, v3 handshake) with SSL state SSL negotiation finished successfully in OPEN 
> 09/29/2015 10:55:58.400 [WARN]  2 connections died in state connect()ing with SSL state (No SSL object) 
> 
> 
> I use Tor on Debian Jessie x64.
> 
> Thank you.

Hello Jason,

First, please try not to paste Bridge IP addresses and ports (i.e.
"148.251.156.199:443") or Bridge fingerprints (i.e.
"3BECEABD174AE41C5CCC17254A40DD24EC5372CD") into public communications channels.
It's dangerous for you, because now people know which Bridges you are going to
try to connect to when you start up Tor.  It's also potentially dangerous for
other people, since there may be other people using these Bridges.  Lastly, it's
bad for the Bridges themselves, since they will likely now be blocked by several
censors and will no longer work in those places.

To answer your question, it looks like your SSL connections are somehow dying.
This could mean many things.  It could simply be that the router at your
house/office/café/etc. is doing strange things.  Or, it might mean that someone
somewhere is tampering with your connections.  Or it could mean something else
entirely.

I would recommend that you email BridgeDB at mailto:bridges at torproject.org and
request some new bridges.  Perhaps try using obfs4 instead, if you can?

-- 
 ♥Ⓐ isis agora lovecruft
_________________________________________________________
OpenPGP: 4096R/0A6A58A14B5946ABDE18E207A3ADB67A2CDB8B35
Current Keys: https://blog.patternsinthevoid.net/isis.txt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 1240 bytes
Desc: Digital signature
URL: <http://lists.torproject.org/pipermail/tor-talk/attachments/20150930/09c20e8d/attachment.sig>