Dear Nigerians, help us help you.

You've flooded the blog and tor-assistants with lots of cries for help about Tor, Freegate, Ultrasurf, and a slew of VPNs all being blocked. Sometimes this is through MTN Nigera, sometimes not.

http://www.herdict.org/web/explore/country/NG suggests access is a 50/50 chance for some sites.

https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#Iin…. That FAQ entry is a fine place to start. Telling us Tor doesn't work lets us know there is a problem. Sending in logs from Message Log would be a great start. We need to know what Tor records while trying to connect to the Tor Network.

Someone could further startup Wireshark and record the entire session of Tor starting up and ultimately failing to connect to the Tor Network.

There are lots of ways ISPs in Nigeria can block Tor and your favorite websites. DNS filtering, IP blacklisting, proxy server keyword filtering, govt mandated blackbox firewalls/proxy servers, or just simply blocking the published tor relays list. The worst case is Nigeria white lists the Internet, allowing you to only visit approved sites (and probably man-in-the-middled as well).

All we know right now is that some ISPs in Nigeria seem to be blocking many websites, tools, and Tor. More data is needed to figure out some solutions.

Updates 2010-07-01: Two people have given us some data from MTN and Etisalat ISPs. It seems these two ISPs have implemented some general "circumvention tool" blocking.

Anonymous

June 29, 2010

Permalink

"«we're unable to access the Tor Blog!!!!!» a typical post at the Tor Blog, sent by Nigerian scammers!!!!" lololol!!!!!!!!!!!!!!!!

lol!!! Yeah!!! that's the first thing i thought after reading this news!!!!!!!! hahahah!!!!!! it's just a joke though!!!!!!!!!!!!!!!!!!

Did you know that all honey bees are princes and princesses?!!!! it's because they all are children of a Queen Bee!!!!!!! yeah, it's true and so cute!!!!!

Well, just to write something that isn't too much offtopic, i want to ask a question!!!!!!!!!!!!!!!!!!!!!!! I ain't sure about this, but if TOR, when starts, downloads a list of known nodes and their public keys!! well, isn't possible for an ISP to fake the list and inject a list of controlled nodes?!!!!!!!!!?!!!!!! or even, replace all the exit nodes with "bad exit nodes" while keeping the internal relays?!!!!

~bee!!!!!!!!!!!!

Anonymous

June 29, 2010

Permalink

Recently here in Chie Tor is blocked too, even the bridges will not work. We checked this out in Xi'an, Beijing and Shenzhen too, so it seems to be a whole China problem.

Anonymous

June 29, 2010

Permalink

Recently here in China Tor is blocked too, even the bridges will not work. We checked this out in Xi'an, Beijing and Shenzhen too, so it seems to be a whole China problem.

Anonymous

June 29, 2010

Permalink

I REALLY LOVE TOR AND IT'S SUPPORT TERM, IT IS A VERY GOOD, FAST AND STRONG PROXY SOLUTION, BUT NOW OUR ISP HERE IN NIGERIA HAS OVER POWERED IT. THAT IS, IT IS NO LONGER WORKING WITH MTN NIGERIA

Anonymous

June 29, 2010

Permalink

Dear stupide people,

It is plainly obvious phobos and Tor know about the blocking problems in Nigeria. The topic and content of phobos' block post is all about TOR IS BLOCKED IN NIGERIA. They know it. SHUT UP ABOUT IT.

I'm so sick of reading these comments.

Please remove your heads from your rear-ends and PROVIDE DATA.

1) In Vidalia, Choose Message Log.
2) Change settings to INFO log level.
3) Click OK.
4) Restart Vidalia. And wait a few minutes.
5) Open a ticket at trac.torproject.org, copy and paste the Message Log contents. Use Select All.
6) PATIENTLY WAIT for a response.
7) now try again with bridges.

Without datum, all of us are blind. Endlessly stating Tor is blocked in Nigeria does not help.

Here is an analogue:

Kid: "I''m bleeding I'm bleeding! HELP ME!"
Doctor on tele: "Where are you bleeding?"
Kid: "I''m bleeding I'm bleeding! HELP ME!"
Doctor on tele: "Please describe the wound and how much blood?"
Kid: "I''m bleeding I'm bleeding! HELP ME!"
Kid: "I''m bleeding I'm bleeding! HELP ME!"
Kid: "I''m bleeding I'm bleeding! HELP ME!"
Kid: "I''m bleeding I'm bleeding! HELP ME!"
Doctor on tele: Please go to a medical centre. Or die. Cheers.
Kid: "I''m bleeding I'm bleeding! HELP ME!"

Hey, you can't be serious. You call them stupid people? Damn . . . you heard that fellas, you called for it and it's been given to you. Live with it or find something better to post next time. Try out what he suggests here, and if it works; Great!

But if it doesn't, he's the studpide person.

Cheers!

Dear stupid Phobos,

We have known who the stupid person is now. How can u call all Nigerian stupid people.

Afterall, you have been supplied what you asked for, creating ticket at trac.torproject.org and still no solution.

Phobos, who is now stupid. You better respect our country, idiot. Fourteen days and counting since the creation of ticket 1645 and no solution. Genius my foot.

Anonymous

July 01, 2010

Permalink

hey, you don't have to call them studpide people. It's not your fault, na dem too like awoof too.

Anonymous

July 01, 2010

Permalink

hello Admin this is what i was able to get hope it helps
i mean wen trying to connect to my tor am posting from nigeria

Jul 01 18:28:16.267 [Debug] connection_remove(): removing socket -1 (type Directory), n_conns now 10
Jul 01 18:28:16.340 [Notice] no known bridge descriptors running yet; stalling
Jul 01 18:29:36.356 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 01 18:29:36.364 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 01 18:29:36.365 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 01 18:29:36.366 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 01 18:29:36.366 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 01 18:29:36.367 [Debug] conn_close_if_marked(): Cleaning up connection (fd 472).
Jul 01 18:29:36.367 [Debug] connection_remove(): removing socket 472 (type Socks), n_conns now 9
Jul 01 18:29:36.367 [Debug] _connection_free(): closing fd 472.
Jul 01 18:29:36.367 [Debug] conn_close_if_marked(): Cleaning up connection (fd 488).
Jul 01 18:29:36.368 [Debug] connection_remove(): removing socket 488 (type Socks), n_conns now 8
Jul 01 18:29:36.368 [Debug] _connection_free(): closing fd 488.
Jul 01 18:29:36.368 [Debug] conn_close_if_marked(): Cleaning up connection (fd 484).
Jul 01 18:29:36.368 [Debug] connection_remove(): removing socket 484 (type Socks), n_conns now 7
Jul 01 18:29:36.368 [Debug] _connection_free(): closing fd 484.
Jul 01 18:29:36.368 [Debug] conn_close_if_marked(): Cleaning up connection (fd 480).
Jul 01 18:29:36.369 [Debug] connection_remove(): removing socket 480 (type Socks), n_conns now 6
Jul 01 18:29:36.369 [Debug] _connection_free(): closing fd 480.
Jul 01 18:29:36.369 [Debug] conn_close_if_marked(): Cleaning up connection (fd 476).
Jul 01 18:29:36.369 [Debug] connection_remove(): removing socket 476 (type Socks), n_conns now 5
Jul 01 18:29:36.369 [Debug] _connection_free(): closing fd 476.
Jul 01 18:29:42.348 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Jul 01 18:29:42.354 [Debug] conn_close_if_marked(): Cleaning up connection (fd 492).
Jul 01 18:29:42.355 [Debug] connection_remove(): removing socket 492 (type Socks), n_conns now 4
Jul 01 18:29:42.355 [Debug] _connection_free(): closing fd 492.

Anonymous

July 02, 2010

Permalink

i have been trying to connect to tor, has been given this message

Jul 02 23:03:27.118 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Jul 02 23:03:28.119 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:03:29.116 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:03:31.122 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:03:55.126 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:03:58.132 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:04:12.193 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Jul 02 23:04:22.196 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Jul 02 23:04:25.154 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:04:26.271 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:04:27.206 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:04:28.207 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:04:29.206 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:04:32.208 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:04:35.751 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:04:48.252 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:05:09.613 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:05:12.669 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:05:25.304 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Jul 02 23:06:25.367 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Jul 02 23:06:26.367 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:06:28.679 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:06:35.370 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Jul 02 23:06:56.846 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:06:59.315 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:07:09.385 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:07:12.386 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:07:36.402 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:08:18.184 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:08:28.444 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Jul 02 23:08:28.454 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:08:36.288 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:08:36.380 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:08:36.380 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:08:36.381 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:08:36.381 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:08:36.414 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:08:36.414 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:08:56.482 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:08:59.485 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Jul 02 23:09:00.768 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:09:11.432 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:09:26.870 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:09:36.505 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Jul 02 23:09:36.617 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:09:36.617 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:09:36.629 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:10:07.716 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:10:18.546 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Jul 02 23:10:28.553 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Jul 02 23:10:31.325 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:10:36.592 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:10:36.592 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:10:36.593 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:10:36.593 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:10:36.593 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:10:36.594 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:10:36.594 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:10:36.869 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:11:00.569 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Jul 02 23:11:01.979 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:11:03.911 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:11:04.951 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:11:06.045 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:11:08.068 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:11:11.577 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Jul 02 23:11:26.592 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:11:36.599 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:11:36.600 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:11:36.601 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:11:37.057 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:11:37.058 [Notice] We're missing a certificate from authority with signing key D2C42303C3DC3C65AEA79052779A133528016BB3: launching request.
Jul 02 23:11:37.058 [Notice] We're missing a certificate from authority with signing key 805619341C7E0817219DF44E8C479988A15B9454: launching request.
Jul 02 23:11:37.058 [Notice] We're missing a certificate from authority with signing key 8F179DFCB311CD6DB3283D72279033704B719C98: launching request.
Jul 02 23:11:37.058 [Notice] We're missing a certificate from authority with signing key 7CD1526998E8946F4BE18F7D7B843F3A502BE808: launching request.
Jul 02 23:11:37.059 [Notice] We're missing a certificate from authority with signing key 665711AF821C459DC59A8491FAD1B9D7A7800ECF: launching request.
Jul 02 23:11:37.059 [Notice] We're missing a certificate from authority with signing key 08D85E2B51D1962DF9EAB4DAF1F1A0061FF0E954: launching request.
Jul 02 23:11:37.059 [Notice] We're missing a certificate from authority with signing key 6584DF098CFC68ACBF5E551532C8A58674586820: launching request.
Jul 02 23:12:07.623 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:12:08.082 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:12:31.629 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Jul 02 23:12:31.641 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:12:36.630 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:12:37.189 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:13:01.660 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Jul 02 23:13:02.792 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:13:03.655 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:13:04.118 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:13:04.654 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:13:05.110 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:13:06.162 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:13:06.667 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:13:08.188 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:13:08.660 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:13:12.682 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:13:33.088 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:13:37.274 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:13:37.679 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:13:53.725 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)

Anonymous

July 02, 2010

Permalink

This is another connection problem, as per below

Jul 02 23:15:08.737 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:15:12.740 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Jul 02 23:15:14.503 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:15:28.705 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:15:32.889 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:15:33.777 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:15:34.907 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:15:37.775 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:16:04.813 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:16:04.885 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:16:05.809 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:16:05.917 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:16:06.819 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:16:07.021 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:16:08.822 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:16:08.972 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:16:27.844 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:16:31.842 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Jul 02 23:16:31.985 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:16:33.757 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:16:33.843 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:16:37.848 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:16:37.996 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:16:40.006 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:16:59.975 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:17:04.657 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:17:04.900 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:17:05.678 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:17:05.901 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:17:06.902 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:17:08.901 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:17:14.904 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Jul 02 23:17:15.032 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:17:16.675 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:17:28.944 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:17:32.947 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:17:34.948 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:17:49.834 [Warning] The https proxy sent back an unexpected status code 502 ("Bad Gateway"). Closing.
Jul 02 23:17:56.730 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:18:04.990 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:18:05.995 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:18:07.003 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:18:08.998 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:18:31.046 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Jul 02 23:18:33.058 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:18:37.048 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:18:39.048 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:18:59.065 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Jul 02 23:19:03.254 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:19:03.363 [Warning] Problem bootstrapping. Stuck at 25%: Loading networkstatus consensus. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 1; recommendation warn)
Jul 02 23:19:03.497 [Warning] Problem bootstrapping. Stuck at 25%: Loading networkstatus consensus. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 2; recommendation warn)
Jul 02 23:19:04.148 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:19:05.146 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:19:15.315 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Jul 02 23:19:16.242 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Jul 02 23:19:22.725 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:19:23.068 [Warning] The https proxy sent back an unexpected status code 400 ("Bad Request"). Closing.
Jul 02 23:19:23.383 [Warning] The https proxy sent back an unexpected status code 400 ("Bad Request"). Closing.
Jul 02 23:19:27.485 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:19:56.540 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:19:58.028 [Warning] The https proxy sent back an unexpected status code 400 ("Bad Request"). Closing.
Jul 02 23:19:59.542 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:20:01.546 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Jul 02 23:20:02.550 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:20:31.572 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Jul 02 23:21:03.625 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Jul 02 23:21:22.645 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Jul 02 23:21:22.805 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:21:27.648 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:21:30.657 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:21:32.683 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:21:32.692 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:21:32.692 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:21:32.694 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:21:37.665 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:21:39.686 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:21:41.675 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:23:22.778 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Jul 02 23:23:34.813 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Jul 02 23:23:34.934 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:24:01.835 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:24:31.741 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:25:28.486 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:25:34.908 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Jul 02 23:25:47.920 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Jul 02 23:26:32.010 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:26:35.328 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:26:40.945 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:26:41.078 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:26:41.949 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:26:41.961 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:26:41.961 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:26:41.962 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:26:41.962 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:27:28.980 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Jul 02 23:27:30.293 [Notice] Application request when we're believed to be offline. Optimistically trying directory fetches again.
Jul 02 23:27:42.019 [Notice] Tried for 121 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:27:42.022 [Notice] Tried for 121 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jul 02 23:27:42.023 [Notice] Tried for 121 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)

Anonymous

July 03, 2010

Permalink

pls some one should help me with the latest configuration for tor in Nigeria with any network at all.

Anonymous

July 06, 2010

Permalink

check out ticket #1665. Hope to get a favourable and once-and-for-all solution to this problem. Plssssssssssssssssssssssssss, help us out here in Nigeria.

We plead!

Anonymous

July 08, 2010

Permalink

pls tor is not going
what do u mean by ticket #1665.
pls why dont u take time to resolve this issue once and for all
i love tor it is the best i have ever come across,pls whats the problem why we are no more connecting from nigeria is dat ur server is down or u have been finally blocked bye mtn nigeria
pls do someting about that
dout u have have anoda proxy we can link up with apart from 10.199.212.2 [port 8080)

gentlemen pls do something about dat,we have been cut off
and our freedom to browse blocked tor pls help am down on my knees....cyber

Anonymous

July 11, 2010

Permalink

PLEASE KINDLY HELP ME, I HAVEN'T BROWSE SINCE WHEN TOR HAS STOPPED BROWSING IN NIGERIA....HELP US ALL...THANK YOU.

Anonymous

July 13, 2010

Permalink

Dear stupid Phobos,

We have known who the stupid person is now. How can u call all Nigerian stupid people.

Afterall, you have been supplied what you asked for, creating ticket at trac.torproject.org and still no solution.

Phobos, who is now stupid. You better respect our country, idiot. Fourteen days and counting since the creation of ticket 1645 and no solution. Genius my foot.

For the record, an anonymous commenter called people stupid. I did not. My posts are clearly labeled as "phobos", such as this one.

As for ticket 1645, someone should upload more data or answer the questions asked.

It's clear tor is blocked in Nigeria, at least with MTN Nigeria and Etisalat ISPs.

No one has been able to tell me if using bridges works, or very recent public tor relays works, or given me any network traffic dumps showing how the ISP is blocking tor. I suspect the block is simply a list of public tor relays' IP and tcp port combination, like every other country does it. However, without someone doing testing from inside the country, I can't help solve the problem.

Anonymous

July 14, 2010

Permalink

so in essence u are no more a genius mr Phobos
what a pity
i was thinking tor was unbeatable
what a pity
i guess we may have to check out for a better option atleast when ione door closes anoda one must open

but come to think of it which other information do u require,we connect throught bridges,proxy and ports and its no more going through now

I never claimed I was a genius. Luckily, it doesn't take a genius to do some basic troubleshooting and problem solving. A few things get in the way of me doing my own proper debugging:

1) I'm not in Nigeria.

2) I'm not a customer of neither MTN nor Etisalat. Customer service won't talk to me unless I can produce an account or phone number. I'd like to find out if this blocking is mandated by the Nigerian Government or something each ISP decided to do on their own.

3) No one has provided contacts in Nigeria that are sufficiently technical to start reverse engineering the blocking. Alternately, no one has provided a shell server in Nigeria for us to do our own research on the issue.

4) We need data. Raw tor logs and/or traffic samples of controlled situations to see what is going on. Controlled situations could be:
a) raw tor (we have these)
b) raw tor with tcpdump traffic samples
c) tor using a published bridge from either https or smtp bridge pools
d) tor using an unpublished bridge
e) tor using a very new public relay as a bridge

5) Is the blocking just for MTN and Etisalat or are all ISPs doing the blocking? As of late 2009, 6 ISPs were not blocking. See http://opennet.net/research/profiles/nigeria

These 5 steps are just a start to figuring out what's going on in Nigeria.

And for comparison, we've done these steps in other countries, like China, Qatar, Germany, Belgium, UK, Iran, Turkey, Lebanon, etc.

The goal isn't to just fix the issue with a quick work around, the goal is to completely solve the problem and force the censors to take drastic measures or think very, very hard about the next step in the arms race. Such drastic measures, like blocking all SSL connections or say, all of google.com, may have overwhelming financial and/or political costs the censors are not willing to incur. Most of Turkey didn't care about censorship so much until they blocked all of google. Now, your average business is unable to get its mail and respond with paying customers. Now a far larger portion of your population cares about Internet censorship. This is a similar situation to what occurred in Iran during the June protests in 2009. Many businesses didn't so much care about the protests, but they really cared about the censorship forced on the country.

Thanks phobos for your effort. Tor has been of great help. i want to provide all the information you need from Nigerian to get Tor back.
i will pass the required information via a ticket unless you wish to provide a different channel.
contact
nline30@gmail.com
i can provide phone no if there is need for it.

If the people from Nigeria themselfs are not able to test these things, i'm sure you or some other people from Tor are able to find one or more proxy servers from within Nigeria to test these problems that obviously now have started to occur for the Nigerian Tor users .

Anonymous

July 15, 2010

Permalink

hello Phobos
tnx for ur reply.sorry my dear if we sounded so rude u know when one is so pressed or despirate he would try to do all he can to gain freedom,
tnx for ur elaborate expanation its shows u are becoming concerned.

wel once again i would like to say that when i was using Tor here in nigeria it was simply splendid,easy connection,good downloadspeed,opens all website and so on ...

Quite unfortunate that when i was trying to get used to lt,
it was now blocked,
wel conccering the questions u asked above i would try and give u the candid answers i have and i hope it helps also bear in mind that my skills in computer is average so i may not meet up with ur technical level and requirements,so u may please stoop a bit low to make urself clear awell clearly explain the technical/engineering details u may require so that i can easily flow with u ok.

As regards to whether it is been blocked by the federal Government i dont think so.
In Nigeria we have a poor consumer protection hence there is no protection of the consumer,the network provider does what they feel like doing without haveing the consumer in mind,what they are interested is to amass wealth from a fertile market here in nigeria without any major inpuback to the people to show appreciation

Lets take MTN for example that has the highest customer in Nigeria had been onground for about 2years before Globacom came in still sold a line @ about Ten thousand nigeria naira about 66.6 USD ,
but wen Glo came up they sold their sim free but u must buy with airtime before MTN brouht out theirs
also
MTN billing was per minuite,hence if u make a second call or willing making a call and it cuts off u re charged for that minuite and when people complained they said before they could revert to per second billing it would be in about a years time,immiediately Glo was was lunched with free simpack and persecond billing MTN quickly reveted to persecond billing by texting a code to their call centre,what they said would be possible in about a years time,what do we enjoy as mtn customers,nothing,no free sms,call tariff not subsidized,no reduced of free internet service,just free call from 12:30midnite to 4:30am,pls tel me who would stay awake to make/receive calls at dat time.

wel whether they like it or not FREE BROWSEING IS OUR RIGHT AND WE MUST ACHIEVE IT.

Secondly what do u mean by shell server
raw tor with tcpdump traffic samples how do u generate that

wel as far as i know, i have known TOR to be working with MTN only it does not work other GSM network providers (i stand to be corrected) such as Glo,Etisalat,Zain.
probabily no one has tried to see it it works i tried with zain but it did not work.

Zain has aGPRS and EDGE
Etisalate has EdGE
GLo has GPRS
MTN 3G,EDGE,HSDPA

1)below is my the tor data connecting using MTN
i use proxy to access the internet 10.199.212.2 Port 8080
type HTTP/HTTPS

2) Allowed ports 8080,80

3) Bridges used i obtained from Get bridges@tor projects

212.123.146.152:9031
84.113.26.199:9001
178.83.135.249:443
173.203.116.133:9142
213.49.144.172:9001
211.218.159.37:443
151.57.200.101:9001
209.20.82.104:9090
24.10.92.124:443
69.31.93.90:9001
77.166.18.207:443
217.144.132.22:135

Message log
Jul 15 19:40:09.585 [Notice] Opening Control listener on 127.0.0.1:9025
Jul 15 19:40:10.024 [Notice] Parsing GEOIP file.
Jul 15 19:40:11.635 [Debug] conn_read_callback(): socket 372 wants to read.
Jul 15 19:40:11.636 [Debug] conn_read_callback(): socket 372 wants to read.
Jul 15 19:40:11.636 [Debug] conn_read_callback(): socket 372 wants to read.
Jul 15 19:40:22.620 [Info] smartlist_choose_by_bandwidth_weights(): Empty routerlist passed in to consensus weight node selection for rule weight as guard
Jul 15 19:40:22.621 [Info] smartlist_choose_by_bandwidth(): Empty routerlist passed in to old node selection for rule weight as guard
Jul 15 19:40:22.621 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Jul 15 19:40:33.621 [Info] smartlist_choose_by_bandwidth_weights(): Empty routerlist passed in to consensus weight node selection for rule weight as guard
Jul 15 19:40:33.622 [Info] smartlist_choose_by_bandwidth(): Empty routerlist passed in to old node selection for rule weight as guard
Jul 15 19:40:33.622 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Jul 15 19:40:44.621 [Info] smartlist_choose_by_bandwidth_weights(): Empty routerlist passed in to consensus weight node selection for rule weight as guard
Jul 15 19:40:44.622 [Info] smartlist_choose_by_bandwidth(): Empty routerlist passed in to old node selection for rule weight as guard
Jul 15 19:40:44.622 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Jul 15 19:40:55.622 [Info] smartlist_choose_by_bandwidth_weights(): Empty routerlist passed in to consensus weight node selection for rule weight as guard
Jul 15 19:40:55.623 [Info] smartlist_choose_by_bandwidth(): Empty routerlist passed in to old node selection for rule weight as guard
Jul 15 19:40:55.623 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Jul 15 19:41:06.623 [Info] smartlist_choose_by_bandwidth_weights(): Empty routerlist passed in to consensus weight node selection for rule weight as guard
Jul 15 19:41:06.624 [Info] smartlist_choose_by_bandwidth(): Empty routerlist passed in to old node selection for rule weight as guard
Jul 15 19:41:06.624 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Jul 15 19:41:12.622 [Info] smartlist_choose_by_bandwidth_weights(): Empty routerlist passed in to consensus weight node selection for rule weight as guard
Jul 15 19:41:12.623 [Info] smartlist_choose_by_bandwidth(): Empty routerlist passed in to old node selection for rule weight as guard
Jul 15 19:41:12.623 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Jul 15 19:41:17.624 [Info] smartlist_choose_by_bandwidth_weights(): Empty routerlist passed in to consensus weight node selection for rule weight as guard
Jul 15 19:41:17.690 [Info] smartlist_choose_by_bandwidth(): Empty routerlist passed in to old node selection for rule weight as guard
Jul 15 19:41:17.693 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Jul 15 19:41:28.625 [Info] smartlist_choose_by_bandwidth_weights(): Empty routerlist passed in to consensus weight node selection for rule weight as guard
Jul 15 19:41:28.631 [Info] smartlist_choose_by_bandwidth(): Empty routerlist passed in to old node selection for rule weight as guard
Jul 15 19:41:28.637 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Jul 15 19:41:39.626 [Info] smartlist_choose_by_bandwidth_weights(): Empty routerlist passed in to consensus weight node selection for rule weight as guard
Jul 15 19:41:39.633 [Info] smartlist_choose_by_bandwidth(): Empty routerlist passed in to old node selection for rule weight as guard
Jul 15 19:41:39.640 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Jul 15 19:41:50.625 [Info] smartlist_choose_by_bandwidth_weights(): Empty routerlist passed in to consensus weight node selection for rule weight as guard
Jul 15 19:41:50.628 [Info] smartlist_choose_by_bandwidth(): Empty routerlist passed in to old node selection for rule weight as guard
Jul 15 19:41:50.631 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)
Jul 15 19:42:01.635 [Info] smartlist_choose_by_bandwidth_weights(): Empty routerlist passed in to consensus weight node selection for rule weight as guard
Jul 15 19:42:01.642 [Info] smartlist_choose_by_bandwidth(): Empty routerlist passed in to old node selection for rule weight as guard
Jul 15 19:42:01.649 [Info] should_delay_dir_fetches(): delaying dir fetches (no running bridges known)

DEBUG MESSAGES

Jul 15 19:45:43.861 [Notice] Tor v0.2.2.13-alpha (git-feb8c1b5f67f2c6f). This is experimental software. Do not rely on it for strong anonymity. (Running on Windows 7 [workstation])
Jul 15 19:45:43.863 [Notice] Initialized libevent version 1.4.13-stable using method win32. Good.
Jul 15 19:45:43.863 [Notice] Opening Socks listener on 127.0.0.1:9050
Jul 15 19:45:43.863 [Notice] Opening Control listener on 127.0.0.1:9025
Jul 15 19:45:44.190 [Notice] Parsing GEOIP file.
Jul 15 19:45:45.875 [Debug] conn_read_callback(): socket 372 wants to read.
Jul 15 19:45:45.875 [Debug] conn_read_callback(): socket 372 wants to read.
Jul 15 19:45:45.875 [Debug] conn_read_callback(): socket 372 wants to read.

CONNECTING WITHOUT BRIDGES
Jul 15 19:53:50.295 [Debug] conn_read_callback(): socket -1 wants to read.
Jul 15 19:53:50.295 [Debug] connection_dir_finished_flushing(): client finished sending command.
Jul 15 19:53:50.440 [Debug] conn_write_callback(): socket 392 wants to write.
Jul 15 19:53:50.465 [Debug] connection_or_finished_connecting(): OR connect() to router at 208.83.223.34:80 finished.
Jul 15 19:53:50.466 [Debug] connection_proxy_connect(): set state PROXY_HTTPS_WANT_CONNECT_OK
Jul 15 19:53:50.743 [Debug] global_write_bucket now 10485760.
Jul 15 19:53:50.745 [Debug] global_relayed_write_bucket now 10485760.
Jul 15 19:54:18.796 [Debug] conn_read_callback(): socket 392 wants to read.
Jul 15 19:54:18.798 [Debug] conn_close_if_marked(): Cleaning up connection (fd -1).
Jul 15 19:54:18.798 [Debug] circuit_n_conn_done(): or_conn to $0AD3FA884D18F89EEA2D89C019379E0E7FD94417/208.83.223.34, status=0
Jul 15 19:54:18.799 [Debug] circuit_increment_failure_count(): n_circuit_failures now 3.
Jul 15 19:54:18.800 [Debug] connection_remove(): removing socket -1 (type OR), n_conns now 7
Jul 15 19:54:18.801 [Debug] conn_close_if_marked(): Cleaning up connection (fd -1).
Jul 15 19:54:18.801 [Debug] connection_remove(): removing socket -1 (type Socks), n_conns now 6
Jul 15 19:54:18.834 [Debug] conn_read_callback(): socket -1 wants to read.
Jul 15 19:54:18.835 [Debug] conn_close_if_marked(): Cleaning up connection (fd -1).
Jul 15 19:54:18.835 [Debug] directory_initiate_command_rend(): anonymized 0, use_begindir 1.
Jul 15 19:54:18.835 [Debug] directory_initiate_command_rend(): Initiating consensus network-status fetch
Jul 15 19:54:18.835 [Debug] connection_add(): new conn type Socks, socket -1, address (Tor_internal), n_conns 6.
Jul 15 19:54:18.835 [Debug] circuit_get_open_circ_or_launch(): considering 1, $F2044413DAC2E02E3D6BCF4735A19BCA1DE97281
Jul 15 19:54:18.835 [Debug] onion_pick_cpath_exit(): Launching a one-hop circuit for dir tunnel.
Jul 15 19:54:18.836 [Debug] onion_extend_cpath(): Path is 0 long; we want 1
Jul 15 19:54:18.836 [Debug] onion_extend_cpath(): Chose router F2044413DAC2E02E3D6BCF4735A19BCA1DE97281 for hop 1 (exit is F2044413DAC2E02E3D6BCF4735A19BCA1DE97281)
Jul 15 19:54:18.836 [Debug] onion_extend_cpath(): Path is complete: 1 steps long
Jul 15 19:54:18.836 [Debug] circuit_handle_first_hop(): Looking for firsthop '80.190.246.100:8080'
Jul 15 19:54:18.836 [Debug] connection_connect(): Connecting to [scrubbed]:8080.
Jul 15 19:54:18.837 [Debug] connection_connect(): Connection to [scrubbed]:8080 in progress (sock 392).
Jul 15 19:54:18.837 [Debug] connection_add(): new conn type OR, socket 392, address 80.190.246.100, n_conns 7.
Jul 15 19:54:18.837 [Debug] circuit_handle_first_hop(): connecting in progress (or finished). Good.
Jul 15 19:54:18.837 [Debug] connection_add(): new conn type Directory, socket -1, address 80.190.246.100, n_conns 8.
Jul 15 19:54:18.837 [Debug] connection_remove(): removing socket -1 (type Directory), n_conns now 8
Jul 15 19:54:18.837 [Debug] conn_read_callback(): socket -1 wants to read.
Jul 15 19:54:18.837 [Debug] connection_dir_finished_flushing(): client finished sending command.
Jul 15 19:54:18.951 [Debug] conn_write_callback(): socket 392 wants to write.
Jul 15 19:54:18.953 [Debug] connection_or_finished_connecting(): OR connect() to router at 80.190.246.100:8080 finished.
Jul 15 19:54:18.954 [Debug] connection_proxy_connect(): set state PROXY_HTTPS_WANT_CONNECT_OK
Jul 15 19:54:19.742 [Debug] global_write_bucket now 10485760.
Jul 15 19:54:19.745 [Debug] global_relayed_write_bucket now 10485760.
Jul 15 19:54:47.300 [Debug] conn_read_callback(): socket 392 wants to read.
Jul 15 19:54:47.301 [Debug] conn_close_if_marked(): Cleaning up connection (fd -1).
Jul 15 19:54:47.301 [Debug] circuit_n_conn_done(): or_conn to $F2044413DAC2E02E3D6BCF4735A19BCA1DE97281/80.190.246.100, status=0
Jul 15 19:54:47.302 [Debug] entry_guard_register_connect_status(): Failed to connect to unreachable entry guard 'gabelmoo' (F2044413DAC2E02E3D6BCF4735A19BCA1DE97281). It has been unreachable since 2010-07-01 16:30:20.
Jul 15 19:54:47.302 [Debug] circuit_increment_failure_count(): n_circuit_failures now 4.
Jul 15 19:54:47.303 [Debug] entry_guard_register_connect_status(): Failed to connect to unreachable entry guard 'gabelmoo' (F2044413DAC2E02E3D6BCF4735A19BCA1DE97281). It has been unreachable since 2010-07-01 16:30:20.
Jul 15 19:54:47.303 [Debug] connection_remove(): removing socket -1 (type OR), n_conns now 7
Jul 15 19:54:47.303 [Debug] conn_close_if_marked(): Cleaning up connection (fd -1).
Jul 15 19:54:47.304 [Debug] connection_remove(): removing socket -1 (type Socks), n_conns now 6
Jul 15 19:54:47.329 [Debug] conn_read_callback(): socket -1 wants to read.
Jul 15 19:54:47.330 [Debug] conn_close_if_marked(): Cleaning up connection (fd -1).
Jul 15 19:54:47.330 [Debug] connection_remove(): removing socket -1 (type Directory), n_conns now 5
Jul 15 19:55:50.764 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Jul 15 19:55:50.769 [Debug] conn_close_if_marked(): Cleaning up connection (fd 388).
Jul 15 19:55:50.770 [Debug] connection_remove(): removing socket 388 (type Socks), n_conns now 4
Jul 15 19:55:50.772 [Debug] _connection_free(): closing fd 388.
Jul 15 19:55:55.765 [Debug] directory_initiate_command_rend(): anonymized 0, use_begindir 1.
Jul 15 19:55:55.769 [Debug] directory_initiate_command_rend(): Initiating consensus network-status fetch
Jul 15 19:55:55.770 [Debug] connection_add(): new conn type Socks, socket -1, address (Tor_internal), n_conns 4.
Jul 15 19:55:55.772 [Debug] circuit_get_open_circ_or_launch(): considering 1, $F2044413DAC2E02E3D6BCF4735A19BCA1DE97281
Jul 15 19:55:55.773 [Debug] onion_pick_cpath_exit(): Launching a one-hop circuit for dir tunnel.
Jul 15 19:55:55.774 [Debug] onion_extend_cpath(): Path is 0 long; we want 1
Jul 15 19:55:55.775 [Debug] onion_extend_cpath(): Chose router F2044413DAC2E02E3D6BCF4735A19BCA1DE97281 for hop 1 (exit is F2044413DAC2E02E3D6BCF4735A19BCA1DE97281)
Jul 15 19:55:55.777 [Debug] onion_extend_cpath(): Path is complete: 1 steps long
Jul 15 19:55:55.780 [Debug] circuit_handle_first_hop(): Looking for firsthop '80.190.246.100:8080'
Jul 15 19:55:55.781 [Debug] connection_connect(): Connecting to [scrubbed]:8080.
Jul 15 19:55:55.783 [Debug] connection_connect(): Connection to [scrubbed]:8080 in progress (sock 388).
Jul 15 19:55:55.784 [Debug] connection_add(): new conn type OR, socket 388, address 80.190.246.100, n_conns 5.
Jul 15 19:55:55.785 [Debug] circuit_handle_first_hop(): connecting in progress (or finished). Good.
Jul 15 19:55:55.786 [Debug] connection_add(): new conn type Directory, socket -1, address 80.190.246.100, n_conns 6.
Jul 15 19:55:55.787 [Debug] conn_read_callback(): socket -1 wants to read.
Jul 15 19:55:55.788 [Debug] connection_dir_finished_flushing(): client finished sending command.
Jul 15 19:55:55.929 [Debug] conn_write_callback(): socket 388 wants to write.
Jul 15 19:55:55.932 [Debug] connection_or_finished_connecting(): OR connect() to router at 80.190.246.100:8080 finished.
Jul 15 19:55:55.933 [Debug] connection_proxy_connect(): set state PROXY_HTTPS_WANT_CONNECT_OK
Jul 15 19:55:56.103 [Debug] conn_read_callback(): socket 388 wants to read.
Jul 15 19:55:56.106 [Debug] read_to_chunk(): Read 589 bytes. 589 on inbuf.
Jul 15 19:55:56.107 [Debug] connection_read_proxy_handshake(): enter state PROXY_HTTPS_WANT_CONNECT_OK
Jul 15 19:55:56.108 [Debug] fetch_from_buf_http(): headerlen 189, bodylen 400.
Jul 15 19:55:56.109 [Debug] fetch_from_buf_http(): Got a contentlen of 400.
Jul 15 19:55:56.110 [Warning] The https proxy sent back an unexpected status code 400 ("Bad Request"). Closing.
Jul 15 19:55:56.111 [Debug] connection_read_proxy_handshake(): leaving state PROXY_HTTPS_WANT_CONNECT_OK
Jul 15 19:55:56.112 [Warning] Proxy Client: unable to connect to 80.190.246.100:8080
Jul 15 19:55:56.113 [Debug] conn_close_if_marked(): Cleaning up connection (fd 388).
Jul 15 19:55:56.113 [Debug] circuit_n_conn_done(): or_conn to $F2044413DAC2E02E3D6BCF4735A19BCA1DE97281/80.190.246.100, status=0
Jul 15 19:55:56.114 [Debug] entry_guard_register_connect_status(): Failed to connect to unreachable entry guard 'gabelmoo' (F2044413DAC2E02E3D6BCF4735A19BCA1DE97281). It has been unreachable since 2010-07-01 16:30:20.
Jul 15 19:55:56.115 [Debug] circuit_increment_failure_count(): n_circuit_failures now 5.
Jul 15 19:55:56.118 [Debug] entry_guard_register_connect_status(): Failed to connect to unreachable entry guard 'gabelmoo' (F2044413DAC2E02E3D6BCF4735A19BCA1DE97281). It has been unreachable since 2010-07-01 16:30:20.
Jul 15 19:55:56.119 [Debug] connection_remove(): removing socket 388 (type OR), n_conns now 6
Jul 15 19:55:56.119 [Debug] _connection_free(): closing fd 388.
Jul 15 19:55:56.119 [Debug] conn_close_if_marked(): Cleaning up connection (fd -1).
Jul 15 19:55:56.119 [Debug] connection_remove(): removing socket -1 (type Socks), n_conns now 5
Jul 15 19:55:56.120 [Debug] conn_read_callback(): socket -1 wants to read.
Jul 15 19:55:56.120 [Debug] conn_close_if_marked(): Cleaning up connection (fd -1).
Jul 15 19:55:56.120 [Debug] connection_remove(): removing socket -1 (type Directory), n_conns now 4
Jul 15 19:55:56.764 [Debug] global_read_bucket now 10485760.
Jul 15 19:55:56.766 [Debug] global_write_bucket now 10485760.
Jul 15 19:55:56.767 [Debug] global_relayed_read_bucket now 10485760.
Jul 15 19:55:56.767 [Debug] global_relayed_write_bucket now 10485760.

Jul 15 19:59:26.888 [Debug] conn_read_callback(): socket -1 wants to read.
Jul 15 19:59:26.888 [Debug] conn_close_if_marked(): Cleaning up connection (fd -1).
Jul 15 19:59:26.888 [Debug] connection_remove(): removing socket -1 (type Directory), n_conns now 5
Jul 15 20:00:30.812 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Jul 15 20:00:30.819 [Debug] conn_close_if_marked(): Cleaning up connection (fd 388).
Jul 15 20:00:30.824 [Debug] connection_remove(): removing socket 388 (type Socks), n_conns now 4
Jul 15 20:00:30.828 [Debug] _connection_free(): closing fd 388.
Jul 15 20:01:00.816 [Debug] directory_initiate_command_rend(): anonymized 0, use_begindir 1.
Jul 15 20:01:00.818 [Debug] directory_initiate_command_rend(): Initiating consensus network-status fetch
Jul 15 20:01:00.818 [Debug] connection_add(): new conn type Socks, socket -1, address (Tor_internal), n_conns 4.
Jul 15 20:01:00.818 [Debug] circuit_get_open_circ_or_launch(): considering 1, $F2044413DAC2E02E3D6BCF4735A19BCA1DE97281
Jul 15 20:01:00.818 [Debug] onion_pick_cpath_exit(): Launching a one-hop circuit for dir tunnel.
Jul 15 20:01:00.819 [Debug] onion_extend_cpath(): Path is 0 long; we want 1
Jul 15 20:01:00.819 [Debug] onion_extend_cpath(): Chose router F2044413DAC2E02E3D6BCF4735A19BCA1DE97281 for hop 1 (exit is F2044413DAC2E02E3D6BCF4735A19BCA1DE97281)
Jul 15 20:01:00.819 [Debug] onion_extend_cpath(): Path is complete: 1 steps long
Jul 15 20:01:00.821 [Debug] circuit_handle_first_hop(): Looking for firsthop '80.190.246.100:8080'
Jul 15 20:01:00.821 [Debug] connection_connect(): Connecting to [scrubbed]:8080.
Jul 15 20:01:00.821 [Debug] connection_connect(): Connection to [scrubbed]:8080 in progress (sock 388).
Jul 15 20:01:00.821 [Debug] connection_add(): new conn type OR, socket 388, address 80.190.246.100, n_conns 5.
Jul 15 20:01:00.822 [Debug] circuit_handle_first_hop(): connecting in progress (or finished). Good.
Jul 15 20:01:00.822 [Debug] connection_add(): new conn type Directory, socket -1, address 80.190.246.100, n_conns 6.
Jul 15 20:01:00.827 [Debug] conn_read_callback(): socket -1 wants to read.
Jul 15 20:01:00.827 [Debug] connection_dir_finished_flushing(): client finished sending command.
Jul 15 20:01:00.964 [Debug] conn_write_callback(): socket 388 wants to write.
Jul 15 20:01:00.965 [Debug] connection_or_finished_connecting(): OR connect() to router at 80.190.246.100:8080 finished.
Jul 15 20:01:00.965 [Debug] connection_proxy_connect(): set state PROXY_HTTPS_WANT_CONNECT_OK
Jul 15 20:01:01.133 [Debug] conn_read_callback(): socket 388 wants to read.
Jul 15 20:01:01.134 [Debug] read_to_chunk(): Read 589 bytes. 589 on inbuf.
Jul 15 20:01:01.134 [Debug] connection_read_proxy_handshake(): enter state PROXY_HTTPS_WANT_CONNECT_OK
Jul 15 20:01:01.135 [Debug] fetch_from_buf_http(): headerlen 189, bodylen 400.
Jul 15 20:01:01.135 [Debug] fetch_from_buf_http(): Got a contentlen of 400.
Jul 15 20:01:01.135 [Warning] The https proxy sent back an unexpected status code 400 ("Bad Request"). Closing.
Jul 15 20:01:01.135 [Debug] connection_read_proxy_handshake(): leaving state PROXY_HTTPS_WANT_CONNECT_OK
Jul 15 20:01:01.135 [Warning] Proxy Client: unable to connect to 80.190.246.100:8080
Jul 15 20:01:01.135 [Debug] conn_close_if_marked(): Cleaning up connection (fd 388).
Jul 15 20:01:01.135 [Debug] circuit_n_conn_done(): or_conn to $F2044413DAC2E02E3D6BCF4735A19BCA1DE97281/80.190.246.100, status=0
Jul 15 20:01:01.135 [Debug] entry_guard_register_connect_status(): Failed to connect to unreachable entry guard 'gabelmoo' (F2044413DAC2E02E3D6BCF4735A19BCA1DE97281). It has been unreachable since 2010-07-01 16:30:20.
Jul 15 20:01:01.136 [Debug] circuit_increment_failure_count(): n_circuit_failures now 8.
Jul 15 20:01:01.137 [Debug] entry_guard_register_connect_status(): Failed to connect to unreachable entry guard 'gabelmoo' (F2044413DAC2E02E3D6BCF4735A19BCA1DE97281). It has been unreachable since 2010-07-01 16:30:20.
Jul 15 20:01:01.137 [Debug] connection_remove(): removing socket 388 (type OR), n_conns now 6
Jul 15 20:01:01.137 [Debug] _connection_free(): closing fd 388.
Jul 15 20:01:01.137 [Debug] conn_close_if_marked(): Cleaning up connection (fd -1).
Jul 15 20:01:01.138 [Debug] connection_remove(): removing socket -1 (type Socks), n_conns now 5
Jul 15 20:01:01.138 [Debug] conn_read_callback(): socket -1 wants to read.
Jul 15 20:01:01.138 [Debug] conn_close_if_marked(): Cleaning up connection (fd -1).
Jul 15 20:01:01.138 [Debug] connection_remove(): removing socket -1 (type Directory), n_conns now 4
Jul 15 20:01:01.814 [Debug] global_read_bucket now 10485760.
Jul 15 20:01:01.815 [Debug] global_write_bucket now 10485760.
Jul 15 20:01:01.815 [Debug] global_relayed_read_bucket now 10485760.
Jul 15 20:01:01.815 [Debug] global_relayed_write_bucket now 10485760.

I HOPE THIS HELPS MR PHOBOS
IF U NEED ANY OTHER INFOR PLS DO NOT FAIL TO CONTACT ME ON
cku2g@yahoo.com

Anonymous

July 18, 2010

Permalink

Free browsing is our right, we wil fight for it since our government are only concern wit politics, can't they see wat the finland government are doing to their citizen?? Every finland citizen has a legal right to free high internet access.our service providers are taking dis opportunity to do wat do feel lik cos dere is no consumer protection. But we are tellin dem enough is enough. So phobos we ar asking for a help to get us back on the track wit tor. tor is part of our lifes. I deeply appreciate ur concern. ayiddalal@gmail.com

Anonymous

July 18, 2010

Permalink

I dont know if you guys need any other encryption but TOR precedure is just
connecting to tor
bla bla bla
(but stops at) establishing to tor circuit

Anonymous

July 19, 2010

Permalink

no solution yet for tor, your freedom had same issue but they debuged it and found a way to bypass mtn... so tor can do the same... creat a new version with the post below....Jul 19 07:57:18.744 [Notice] No current certificate known for authority gabelmoo; launching request.
Jul 19 07:57:18.744 [Notice] No current certificate known for authority dannenberg; launching request.
Jul 19 07:57:18.744 [Notice] No current certificate known for authority urras; launching request.
Jul 19 07:58:43.960 [Notice] Tor v0.2.1.26. This is experimental software. Do not rely on it for strong anonymity. (Running on Windows "Longhorn" Service Pack 1 [workstation] {personal} {terminal services, single user})
Jul 19 07:58:44.068 [Notice] Initialized libevent version 1.4.12-stable using method win32. Good.
Jul 19 07:58:44.068 [Notice] Opening Socks listener on 127.0.0.1:9050
Jul 19 07:58:44.068 [Notice] Opening Control listener on 127.0.0.1:9051
Jul 19 07:58:44.068 [Notice] Parsing GEOIP file.
Jul 19 07:58:47.974 [Notice] Bootstrapped 10%: Finishing handshake with directory server.
Jul 19 07:58:49.000 [Notice] Ignoring directory request, since no bridge nodes are available yet.
Jul 19 07:59:19.613 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 1; recommendation warn)
Jul 19 07:59:19.887 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 2; recommendation warn)
Jul 19 07:59:19.889 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 3; recommendation warn)
Jul 19 07:59:19.890 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 4; recommendation warn)
Jul 19 07:59:19.891 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 5; recommendation warn)
Jul 19 07:59:19.892 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 6; recommendation warn)
Jul 19 07:59:19.893 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 7; recommendation warn)
Jul 19 07:59:19.894 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 8; recommendation warn)
Jul 19 07:59:19.896 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 9; recommendation warn)
Jul 19 07:59:19.897 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 10; recommendation warn)
Jul 19 07:59:19.898 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 11; recommendation warn)
Jul 19 07:59:19.899 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 12; recommendation warn)
Jul 19 07:59:19.900 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 13; recommendation warn)
Jul 19 07:59:19.909 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 14; recommendation warn)
Jul 19 07:59:19.910 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 15; recommendation warn)
Jul 19 07:59:19.911 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 16; recommendation warn)
Jul 19 07:59:19.912 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 17; recommendation warn)
Jul 19 07:59:19.913 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 18; recommendation warn)
Jul 19 07:59:19.915 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 19; recommendation warn)
Jul 19 07:59:19.916 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 20; recommendation warn)
Jul 19 07:59:19.917 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 21; recommendation warn)
Jul 19 07:59:19.919 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 22; recommendation warn)
Jul 19 07:59:19.920 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 23; recommendation warn)
Jul 19 07:59:19.921 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 24; recommendation warn)
Jul 19 07:59:19.924 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 25; recommendation warn)
Jul 19 07:59:19.925 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 26; recommendation warn)
Jul 19 07:59:19.926 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 27; recommendation warn)
Jul 19 07:59:19.927 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 28; recommendation warn)
Jul 19 07:59:19.928 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 29; recommendation warn)
Jul 19 07:59:19.929 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 30; recommendation warn)
Jul 19 07:59:19.930 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 31; recommendation warn)
Jul 19 07:59:19.932 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 32; recommendation warn)
Jul 19 07:59:19.933 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 33; recommendation warn)
Jul 19 07:59:19.934 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 34; recommendation warn)
Jul 19 07:59:19.935 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 35; recommendation warn)
Jul 19 07:59:19.936 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 36; recommendation warn)
Jul 19 07:59:19.937 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 37; recommendation warn)
Jul 19 07:59:19.938 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 38; recommendation warn)
Jul 19 07:59:19.941 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 39; recommendation warn)
Jul 19 07:59:19.947 [Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 40; recommendation warn)

Anonymous

July 19, 2010

Permalink

hello Phobos
these are the bridges i was using before it was bocked,and now when i try to connect using briges
it says Authenticating Tor and never connects...

212.123.146.152:9031
84.113.26.199:9001
178.83.135.249:443
173.203.116.133:9142
213.49.144.172:9001
211.218.159.37:443
151.57.200.101:9001
209.20.82.104:9090
24.10.92.124:443
69.31.93.90:9001
77.166.18.207:443
217.144.132.22:135

pls phobos what is wrong
dont tel me u cant find a way out,we are trying to give u all the info u need at our disposal
pls do something

cku2g@yahoo.com

Anonymous

July 19, 2010

Permalink

phobes no bridges work here in Nigeria. How your freedom solved it are very simple, they wrap all their connection in sslv3 and tunnel it, with means woith or without the default ip and port connections to their servers would be established in a couple of seconds... thats the means of my connection right now... pls creat a beta version that uses ssl and other more features.... we would be glad to let you know that even the bridges are not strong enough for our isp now... if you have any solution pls kindly help us.... thats 4m vince in lagos

Anonymous

July 20, 2010

Permalink

Hi Phobos, we've tried using bridges and also proxies but still to no avail ... for now I think your-freedom's got the edge, I still wonder how those guys do it!

Anonymous

July 21, 2010

Permalink

yea Phobos freedom works now,but the protocol of the settings is quite cunbersome and they are equally rationing it now.
so am still waiting for tor 2bounce back, its quite clear u have been blocked
tried connecting with bridges and is saying autenticating tor
but when freedom is going and i use
127.0.0.1 p0rt 8080 on tor setting it rocks,but wen freedom goes off it no more connects
what other infor do u need,
pls don give up so soon

cku2g@yahoo.com

In general, a comment about this "censorship" in Nigeria. I've heard from others that Nigeria is not censoring the Internet, but rather ISPs have closed the loophole that allowed users to get internet access without paying for it. Their tests show that with a paid account, nothing is blocked, not even Tor.

Can you comment on that?

yes we know this and even our isps know this also... thats why they allow certain level of browsing is allowed thats why with sslv3 one can connect to the internet with the MTN network... the bridges are no more useful. my opinion would be to change the pathern of our new version of tor to meet this thread.

you are 100% right about that i use mtn a network provider in Nigeria but really others who want to use Tor not for that purpose are begin blocked too now even ur site or any link with the key word tor is being blocked by our isp provide which is not fair and in some way its kind of censoring

No Sir though i have not tried it but i dont think it connects cos i once tried it with ETISALAT Nigeria which i do pay for and browse legally but TOR didnt connect. I think what the YOUR-FREEDOM people do is to change their server from time to time that is why when ever YOUR-FREEDOM is blocked by MTN Nigeria it connects after they change their server. Hope this information is helpful to you and by the way sir I MISS MY TOR

Anonymous

July 22, 2010

Permalink

NON-SENSE..ALL D NETWORK PROVIDER EXCEPT GLO EXPLOIT THE GENERAL MASSES...IMAGINE YOU PAYING 4 INTERNET BROWSING ALMOST $100 PER MONTH....WHERE IS IT DONE....AND ALMOST 67% ARE LIVING BELOW $1 SO WHO CARES THE GOVT OFFICIALS ARE CORRUPT SO WHY WOULDN'T I BROWSE FREE..................

ANY YOUR-FREEDOM GIVES US FREE BROWSING 4 NOW...JUST THAT IT'S ONLY ONE HOUR...TORS GIVES 24HRS

PLS TOR HELP US OUT
TOOZEALOUS