[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: Blocked by my ISP?-part2
- To: or-talk@xxxxxxxxxxxxx
- Subject: Re: Blocked by my ISP?-part2
- From: "Ringo Kamens" <2600denver@xxxxxxxxx>
- Date: Sun, 15 Jun 2008 22:30:13 -0400
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: or-talk-outgoing@xxxxxxxx
- Delivered-to: or-talk@xxxxxxxx
- Delivery-date: Sun, 15 Jun 2008 22:30:19 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=goNM5MXX4T0Foq//dnZdzJ0QGPas/GRvaTtbG+jcASk=; b=XdFNgjlFlAc4h/NSwsEQHLoForFLu4WNcVRPI3mmGQ5Z2nbtuL/ex2r72JYLWK9vNh 9yFd7XMwRVf/SSU35hOO2ThJn4v6LD5+JO6b4nG7SrZJpUYrVfUwvyYUyMSmwetfxaPw GekAN+QBAVgjcbFfyaMXNt6Cgpj8cP6paabwU=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=tvqs+fornNhD2BPghq2YTLJ2WdNETen5utuYcVxggqTVwFkhdopGxV/xK5lzfN1wWe LfrxzK0ZIi4JqjP7A+wXlsSsbq91XpV9+5QjxgkEgFQifQ1cyRV6t5sgf/qb9DHViEYa u9DPv/Arc8ygrAcFKuBVj8Mm8E8bQa/aIgj/k=
- In-reply-to: <827168.27929.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
- References: <827168.27929.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
That doesn't look like they're blocking. Have you tried connecting
through different HTTP proxies? Other versions of tor? Is the log mode
set on debug? Something more verbose could help.
Comrade Ringo Kamens
On Sun, Jun 15, 2008 at 9:19 PM, Luis Maceira <luis_a_maceira@xxxxxxxxx> wrote:
> signed-directory
> published 2008-06-15 23:32:35
> recommended-software
> 0.1.2.17,0.1.2.18,0.1.2.19,0.2.0.26-rc,0.2.0.27-rc,0.2.0.28-rc,0.2.1.1-alpha
> router-status
> dir-signing-key
> -----BEGIN RSA PUBLIC KEY-----
> MIGJAoGBAMQgV2gXLbXgesWgeAsj8P1Uvm/zibrFXqwDq27lLKNgWGYGX2ax3LyT
> 3nzI1Y5oLs4kPKTsMM5ft9aokwf417lKoCRlZc9ptfRbgxDx90c9GtWVmkrmDvCK
> ae59TMoXIiGfZiwWT6KKq5Zm9/Fu2Il3B2vHGkKJYKixmiBJRKp/AgMBAAE=
> -----END RSA PUBLIC KEY-----
>
> directory-signature tor26
> -----BEGIN SIGNATURE-----
> ncqJLN4ySE9d0ODHDKb7NDEpZtctXhlqj9I/kGBK7SR71BIqCc9EIspSuPaIR9AH
> KXaIWHEMOQrwtIzav5QOZp3mEeQGDdBgfBsRoWYiR2ahpd8Jqj8WYduzmqXNRQ1Z
> 2Fyd+yPRdNDerqLJ0W5uW9OX9LGMftOqCqSV+FB+J/A=
> -----END SIGNATURE-----
>
>
> This is what I get when I try to connect with my
> webbrowser to http://86.59.21.38/.An ancient client
> of my DSL ISP says in a newsgroup that right before
> he left this ISP was blocking proxy ports 80 and 8080
> and maybe this is a reason for Tor not effective to
> other user that was complaining about it,and that he
> should use foxyproxy to avoid this issue.
> How do I know if my ISP is blocking Tor and is
> the configuration of foxyproxy a good idea,but
> the configuration of privoxy should not be sufficient?
>
>
>
>
>
>
>
>
>
>