Re: cached-directory update always failure via proxy

["Martin Balvers" <m.balvers@xxxxxxxxxx>]

Hi,

One part of the problem is that there are not enough servers running on
ports 443 and 80.

If you use this commandline:

> When using tor.exe -httpsproxy 127.0.0.1:8888 -fascistfirewall 1
> -firewallports 443, see following:

You will only use port 443. I don't think there are any servers running
with DirPort 443, so this will fail.

I am behind a very restrictive firewall/proxy at work, but I don't have
any problems.
This is what I have added to the default torrc file:

FascistFirewall 1
HttpsProxy 192.168.2.14:8080
HttpProxy 192.168.2.14:8080
KeepalivePeriod 30

I hope this helps,
Martin

> Hello TOR developers,
>
> There is a problem existing long time that the cached-directory
> almostly can not be updated via parent fascist proxy.
>
> The detail:
> Environment:LAN, fascist http/https proxy, remote port only 80, 443
> allowed.
>
> When using tor.exe -httpsproxy 127.0.0.1:8888 -fascistfirewall 1
> -firewallports 443, see following:
> ===========================================================Jun 24
> 10:21:53.326 [notice] Tor v0.1.0.10. This is experimental software. Do no
> t rely on it for strong anonymity.
> Jun 24 10:21:53.386 [notice] Initialized libevent version 1.1a using
> method win3
> 2
> Jun 24 10:22:23.620 [notice] Tor has successfully opened a circuit. Looks
> like i
> t's working.
> Jun 24 10:52:18.100 [notice] directory_get_from_dirserver(): No running
> dirserve
> rs known. Not trying. (purpose 1)
> Jun 24 11:02:16.961 [notice] directory_get_from_dirserver(): No running
> dirserve
> rs known. Not trying. (purpose 2)
> Jun 24 11:32:18.452 [notice] directory_get_from_dirserver(): No running
> dirserve
> rs known. Not trying. (purpose 1)
> ...
> ===========================================================or
> ===========================================================Jun 24
> 12:51:15.043 [notice] Tor v0.1.0.10. This is experimental software. Do no
> t rely on it for strong anonymity.
> Jun 24 12:51:15.093 [notice] Initialized libevent version 1.1a using
> method win3
> 2
> Jun 24 12:51:46.608 [warn] connection_dir_client_reached_eof(): Received
> http st
> atus code 504 ("Proxy Timeout ( Connection timed out. For more information
> about
>  this event, see ISA Server Help. )") from server '80.190.251.24'.
> Failing.
> ==========================================================When using
> tor.exe -httpproxy 127.0.0.1:8888 -fascistfirewall 1
> -firewallports 80, see following:
> ===========================================================Jun 24
> 20:33:26.257 [notice] Tor v0.1.0.10. This is experimental software. Do no
> t rely on it for strong anonymity.
> Jun 24 20:33:26.307 [notice] Initialized libevent version 1.1a using
> method win3
> 2
> Jun 24 20:33:27.508 [warn] router_choose_random_node(): No available nodes
> when
> trying to choose node. Failing.
> Jun 24 20:33:27.508 [warn] onion_extend_cpath(): Failed to find node for
> hop 0 o
> f our path. Discarding this circuit.
> Jun 24 20:33:28.510 [warn] router_choose_random_node(): No available nodes
> when
> trying to choose node. Failing.
> Jun 24 20:33:28.510 [warn] onion_extend_cpath(): Failed to find node for
> hop 0 o
> f our path. Discarding this circuit.
> ...
> ==========================================================And I find
> something in the firewall monitor that TOR not only connect
> proxy but also try to directly connect to some remote servers' IP port
> 9001/9030 although parent proxy is declared. But very very few times,
> when using tor.exe -httpproxy 127.0.0.1:8888 -fascistfirewall 1
> -firewallports 80, TOR can successfully download the latest
> cached-directory.
>
> Can you give some explanations or it's a real problem of proxy support?
>
> Best regards,
> Arthur
> 2005/06/24
>


-- 
GPG key id: B72BEC80
Keyserver: http://sks.keyserver.penguin.de