Opened 9 years ago

Closed 9 years ago

Last modified 7 years ago

#1645 closed defect (fixed)

NIGERIA TOR PROBLEM DATA

Reported by: worm1 Owned by: phobos
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.2.1.26
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

this is the log i got after running tor on MTN Nigeria network and it was unable to connect.

Jul 01 20:27:30.665 [Notice] Tor v0.2.1.26. This is experimental software. Do not rely on it for strong anonymity. (Running on Windows "Longhorn" [workstation] {terminal services, single user})
Jul 01 20:27:30.670 [Notice] Initialized libevent version 1.4.12-stable using method win32. Good.
Jul 01 20:27:30.670 [Notice] Opening Socks listener on 127.0.0.1:9050
Jul 01 20:27:30.670 [Notice] Opening Control listener on 127.0.0.1:9051
Jul 01 20:27:30.772 [Notice] Parsing GEOIP file.

videlia status got stuck where it says "Establishing an encrypted directory connection".

i must also comment here that we are forced to browse through a proxy by MTN NIGERIA their proxy address is 10.199.212.2 and the proxy port is 8080.

i was unable to sniff the traffic because wireshark was unable to detect mtn's modem, i hope this info helps if there is any other
thing i can do i will be happy to help.

Child Tickets

Change History (11)

comment:1 Changed 9 years ago by worm1

i also got this info after running tor for several minutes

Jul 01 20:27:30.665 [Notice] Tor v0.2.1.26. This is experimental software. Do not rely on it for strong anonymity. (Running on Windows "Longhorn" [workstation] {terminal services, single user})
Jul 01 20:27:30.670 [Notice] Initialized libevent version 1.4.12-stable using method win32. Good.
Jul 01 20:27:30.670 [Notice] Opening Socks listener on 127.0.0.1:9050
Jul 01 20:27:30.670 [Notice] Opening Control listener on 127.0.0.1:9051
Jul 01 20:27:30.772 [Notice] Parsing GEOIP file.
Jul 01 20:35:50.425 [Warning] The https proxy sent back an unexpected status code 500 ("Generated error"). Closing.
Jul 01 20:46:00.763 [Warning] The https proxy sent back an unexpected status code 500 ("Generated error"). Closing.

comment:2 Changed 9 years ago by worm1

I Thought this might be more informative.

Jul 01 21:34:57.680 [Debug] connection_connect(): Connection to [scrubbed]:80 in progress (sock 356).
Jul 01 21:34:57.680 [Debug] connection_add(): new conn type OR, socket 356, address 38.229.70.34, n_conns 5.
Jul 01 21:34:57.680 [Debug] circuit_handle_first_hop(): connecting in progress (or finished). Good.
Jul 01 21:34:57.681 [Debug] connection_add(): new conn type Directory, socket -1, address 38.229.70.34, n_conns 6.
Jul 01 21:34:57.681 [Debug] conn_read_callback(): socket -1 wants to read.
Jul 01 21:34:57.681 [Debug] connection_dir_finished_flushing(): client finished sending command.
Jul 01 21:34:57.795 [Debug] conn_write_callback(): socket 356 wants to write.
Jul 01 21:34:57.799 [Debug] connection_or_finished_connecting(): OR connect() to router at 38.229.70.34:443 finished.
Jul 01 21:34:57.799 [Debug] connection_or_finished_flushing(): finished sending CONNECT to proxy.
Jul 01 21:34:58.667 [Debug] global_write_bucket now 10485760.
Jul 01 21:34:58.671 [Debug] global_relayed_write_bucket now 10485760.
Jul 01 21:35:23.341 [Debug] conn_read_callback(): socket 356 wants to read.
Jul 01 21:35:23.345 [Debug] conn_close_if_marked(): Cleaning up connection (fd -1).
Jul 01 21:35:23.345 [Debug] circuit_n_conn_done(): or_conn to $7F0C0CB78F949256D30EF8C16FD6AA2B529AA458/38.229.70.34, status=0
Jul 01 21:35:23.346 [Debug] entry_guard_register_connect_status(): Failed to connect to unreachable entry guard 'williamhaines' (7F0C0CB78F949256D30EF8C16FD6AA2B529AA458). It has been unreachable since 2010-06-28 19:35:31.
Jul 01 21:35:23.346 [Debug] circuit_increment_failure_count(): n_circuit_failures now 4.
Jul 01 21:35:23.346 [Debug] entry_guard_register_connect_status(): Failed to connect to unreachable entry guard 'williamhaines' (7F0C0CB78F949256D30EF8C16FD6AA2B529AA458). It has been unreachable since 2010-06-28 19:35:31.
Jul 01 21:35:23.347 [Debug] connection_remove(): removing socket -1 (type OR), n_conns now 6
Jul 01 21:35:23.347 [Debug] conn_close_if_marked(): Cleaning up connection (fd -1).
Jul 01 21:35:23.347 [Debug] connection_remove(): removing socket -1 (type Socks), n_conns now 5
Jul 01 21:35:23.348 [Debug] conn_read_callback(): socket -1 wants to read.
Jul 01 21:35:23.348 [Debug] conn_close_if_marked(): Cleaning up connection (fd -1).
Jul 01 21:35:23.349 [Debug] connection_remove(): removing socket -1 (type Directory), n_conns now 4
Jul 01 21:37:43.345 [Debug] conn_read_callback(): socket 360 wants to read.
Jul 01 21:37:43.348 [Debug] conn_read_callback(): socket 360 wants to read.
Jul 01 21:37:43.348 [Debug] conn_read_callback(): socket 360 wants to read.
Jul 01 21:37:43.349 [Debug] conn_read_callback(): socket 360 wants to read.
Jul 01 21:37:43.350 [Debug] conn_read_callback(): socket 360 wants to read.
Jul 01 21:37:43.351 [Debug] conn_read_callback(): socket 360 wants to read.
Jul 01 21:37:43.351 [Debug] conn_read_callback(): socket 360 wants to read.
Jul 01 21:37:43.352 [Debug] conn_read_callback(): socket 360 wants to read.
Jul 01 21:37:43.352 [Debug] conn_read_callback(): socket 360 wants to read.
Jul 01 21:37:43.353 [Debug] conn_read_callback(): socket 360 wants to read.
Jul 01 21:37:43.353 [Debug] conn_read_callback(): socket 360 wants to read.
Jul 01 21:37:43.354 [Debug] conn_read_callback(): socket 360 wants to read.
Jul 01 21:37:43.354 [Debug] conn_read_callback(): socket 360 wants to read.
Jul 01 21:37:43.355 [Debug] conn_read_callback(): socket 360 wants to read.
Jul 01 21:37:43.355 [Debug] conn_read_callback(): socket 360 wants to read.
Jul 01 21:37:43.355 [Debug] conn_read_callback(): socket 360 wants to read.
Jul 01 21:37:43.356 [Debug] conn_read_callback(): socket 360 wants to read.
Jul 01 21:37:43.356 [Debug] conn_read_callback(): socket 360 wants to read.
Jul 01 21:37:43.356 [Debug] conn_read_callback(): socket 360 wants to read.
Jul 01 21:37:43.357 [Debug] resolve_my_address(): Guessed local host name as 'Amos-PC'
Jul 01 21:37:43.357 [Debug] conn_read_callback(): socket 360 wants to read.
Jul 01 21:37:43.357 [Debug] conn_read_callback(): socket 360 wants to read.
Jul 01 21:37:43.358 [Debug] conn_read_callback(): socket 360 wants to read.
Jul 01 21:37:43.358 [Debug] conn_read_callback(): socket 360 wants to read.
Jul 01 21:37:43.358 [Debug] conn_read_callback(): socket 360 wants to read.
Jul 01 21:37:43.358 [Debug] conn_read_callback(): socket 360 wants to read.
Jul 01 21:37:43.359 [Debug] conn_read_callback(): socket 360 wants to read.

comment:3 Changed 9 years ago by erinn

Component: TracTor - Tor client

comment:4 Changed 9 years ago by phobos

Milestone: Tor: unspecified
Owner: set to phobos
Priority: blockernormal
Status: newassigned
Version: Tor: 0.2.1.26

comment:5 Changed 9 years ago by phobos

Status: assignedaccepted

I suspect their forced proxy is blocking all connects to public tor relays. Do you have any bridges configured?

comment:6 Changed 9 years ago by worm1

i am sure about that their forced proxy is blocking connection, i got recent bridges from https://bridges.tor.org but still no connection.

comment:7 Changed 9 years ago by worm1

phobos is there any possible solution to this prob.

comment:8 Changed 9 years ago by arma

Jul 01 20:46:00.763 [Warning] The https proxy sent back an unexpected status code 500 ("Generated error"). Closing.

That's the key line here. Your https proxy is refusing to allow connections
to the IP address you tried to connect to.

So the next step for debugging this is to figure out what sorts of addresses your https proxy is allowing, and what sort it is refusing.

For example, if you go to https://www.torproject.org/, does it work? If so, that would argue that *some* addresses do work.

And then if you go to https://38.229.70.34/ I would guess it will give the "Generated error" line, since that's the address of the Tor relay from your logs above that failed.

How about https://38.229.70.35/ then?

It's possible your https proxy is specifically blocking Tor relays. It could also just be blocking any https connections to IP addresses (as opposed to more normal hostnames).

comment:9 Changed 9 years ago by worm1

i debugged using the step you provided with no luck, https connection to other website connects just fine, https://www.torproject.org opened fine in my browser(mozilla firefox, the bottom line is that they are blocking tor directory servers and relays.

comment:10 Changed 9 years ago by phobos

Resolution: fixed
Status: acceptedclosed

From confirmation with other Nigerians, mtn and etisalat closed a loophole which allowed non-subscribers to get free 'net access. paid subscribers can use tor just fine.

comment:11 Changed 7 years ago by nickm

Component: Tor ClientTor
Note: See TracTickets for help on using tickets.