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

Re: [tor-bugs] #3157 [Tor Client]: tor is not working on my 3G



#3157: tor is not working on my 3G
------------------------+---------------------------------------------------
 Reporter:  tor.tor     |          Owner:     
     Type:  defect      |         Status:  new
 Priority:  normal      |      Milestone:     
Component:  Tor Client  |        Version:     
 Keywords:              |         Parent:     
   Points:              |   Actualpoints:     
------------------------+---------------------------------------------------
Changes (by arma):

  * component:  Tor Relay => Tor Client


Comment:

 Replying to [ticket:3157 tor.tor]:
 > the second one is a 3G modem and it is not working at all
 > this the message log using 3G modem :
 [...]
 > ÙØÙÙ 12 15:20:51.448 [Debug] connection_tls_continue_handshake(): wanted
 read
 > ÙØÙÙ 12 15:21:21.054 [Info] circuit_expire_building(): Abandoning circ 0
 (state 2:connecting to server, purpose 5)
 > ÙØÙÙ 12 15:21:21.055 [Info] exit circ (length 1, exit
 BD6A829255CB08E66FBE7D3748363586E46B3810):
 $BD6A829255CB08E66FBE7D3748363586E46B3810(closed)
 > ÙØÙÙ 12 15:21:21.055 [Info] connection_ap_fail_onehop(): Closing one-hop
 stream to '$BD6A829255CB08E66FBE7D3748363586E46B3810/213.115.239.118'
 because the OR conn just failed.
 > ÙØÙÙ 12 15:21:21.056 [Debug] circuit_increment_failure_count():
 n_circuit_failures now 6.
 [...]
 > ÙØÙÙ 12 15:22:03.271 [Info] TLS error: <syscall error while handshaking>
 (errno=10054: Connection reset by peer [WSAECONNRESET ])
 > ÙØÙÙ 12 15:22:03.273 [Info] connection_tls_continue_handshake(): tls
 error [connection reset]. breaking connection.

 It looks like the ISP for your 3g connection is blocking connections to
 Tor relays. Or they are blocking all https flows, just like captive
 portals at hotels that prevent you from talking to the Internet until
 you've registered.

 Which ISP provides the 3g connection?

 Can you reach https://mail.google.com/ successfully?

 Have you tried bridges? https://torproject.org/docs/bridges

 Another approach would be to manually copy the cached-* files from the
 datadir on your Tor client that works to the datadir on the Tor client
 that doesn't work. That will give it more places to bootstrap from, and
 might help us narrow down the issue.

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