On Sun, Mar 11, 2012 at 12:27:03AM +0100, andr...@fastmail.fm wrote: > In trying to access Tor while using a certain network the following > error/problem message appears in the log; > > Mar 1 02:45:41.518 [Notice] Tor v0.2.2.35 (git-XXXXXXXXf). This is > experimental software. Do not rely on it for strong anonymity. (Running > on NONE OF YOUR BUSINESS i686) > Mar 1 02:45:41.519 [Notice] Initialized libevent version 2.0.17-stable > using method epoll. Good. > Mar 1 02:45:41.519 [Notice] Opening Socks listener on 127.0.0.1:0 > Mar 1 02:45:41.519 [Notice] Socks listener listening on port 35968. > Mar 1 02:45:41.519 [Notice] Opening Control listener on 127.0.0.1:0 > Mar 1 02:45:41.519 [Notice] Control listener listening on port 41910. > Mar 1 02:45:41.519 [Notice] Parsing GEOIP file ./Data/Tor/geoip. > Mar 1 02:45:44.069 [Notice] Bootstrapped 5%: Connecting to directory > server. > Mar 1 02:45:53.090 [Warning] Problem bootstrapping. Stuck at 5%: > Connecting to directory server. (No route to host; NOROUTE; count 2; > recommendation warn) > > Any idea how to fix this?
Your Tor is unable to complete the TCP connection to whichever directory authority it chose. A) Are you behind a captive portal? Is your network actually on? What else can you reach? B) Try using a Tor bridge: https://www.torproject.org/docs/bridges if "a certain network" is blocking the Tor directory authorities by IP address. C) You could try the obfsproxy bundle: https://www.torproject.org/projects/obfsproxy but based on your log I bet it won't help. --Roger _______________________________________________ tor-talk mailing list tor-talk@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk