[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: Blocked by my ISP?
- To: or-talk@xxxxxxxxxxxxx
- Subject: Re: Blocked by my ISP?
- From: "Ringo Kamens" <2600denver@xxxxxxxxx>
- Date: Mon, 16 Jun 2008 03:29:05 -0400
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: or-talk-outgoing@xxxxxxxx
- Delivered-to: or-talk@xxxxxxxx
- Delivery-date: Mon, 16 Jun 2008 03:29:13 -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=QGHxqItkh7QIdRWH9FjRhCooyRXQlHpdAddn18PoRyY=; b=is0on/byBRWRh6dMicWKLkcIHHUrPtBjAFpYT8hOcS8J9RYednx+ysqCPv0m3a/MnQ 969D+FD518kx5K2H6Z1Vg21Av0LI0Bn0uR/3dOrcWaRFAC6VWg+7/pksUfI6XfnedixJ uW47T6HDomBzVj/6Rer4OZgaMjYD+EKM4q65M=
- 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=r1uqXYwr0TZ+LrW5I6C3ruy51+hTdEVZ53s6K9WDOP/ZNUPsCHpxYQ2TjTL5544prV lpEFEGvthUXM3ZP89PxUBE23Z9Jhe91BWYgW71KfgaP7kAeqPY+v8Z5o2PN4phmGb2fW UM3EputhkORdx6JlbxaTOXKA/Xyq50Oc+1veo=
- In-reply-to: <20080616042419.GJ15456@xxxxxxxxxxxxxx>
- References: <524183.87180.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <20080616042419.GJ15456@xxxxxxxxxxxxxx>
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
Here is information on how to get a more updated version by adding the
NoReply package repos:
https://wiki.torproject.org/noreply/TheOnionRouter/TorOnDebian
Comrade Ringo Kamens
On Mon, Jun 16, 2008 at 12:24 AM, Roger Dingledine <arma@xxxxxxx> wrote:
> On Sun, Jun 15, 2008 at 02:05:49PM -0700, Luis Maceira wrote:
>> Jun 15 16:22:23.376 [notice] Tor 0.1.2.17 opening log
>> file.
>
> You should be aware that you're using a Tor that was released almost 10
> months ago. Perhaps you're not using the right debian repository to keep
> up to date?
>
>> Jun 15 16:40:14.427 [warn] Received http status code
>> 400 ("Bad Request") from server '194.109.206.212:80'
>> while fetching
>> "/tor/server/d/BAFD4D5D2E0D98ADE50B3AC116F69909100C805C+BB1E75B4C8215DF5F4F18F50879318EF711426C7+BCA7AFCA9D852E4C7BF94DE1ACDC3FF8AA491854+BD44604B5840117E78FE65667FD94220D623F01E+BE667C6ED0748DF529AB9A690B68EC589ECF8B6B+BEC4F949D3E50E8A8FBD
>> .... several lines(30 or 40) like the above 2 lines!!!
>
> Could be that your ISP is filtering certain requests it doesn't like.
>
> I would suggest upgrading to Tor 0.2.0.28-rc. It fetches directory
> information in a different way, so it probably doesn't do the action
> that your ISP is trying to filter.
>
>> Jun 15 16:40:50.287 [notice] Tor has successfully
>> opened a circuit. Looks like client functionality is
>> working.
>
> This is weird to see here. It looks like you succeeded at getting enough
> directory information and establishing a circuit. So your Tor ought to
> work. Perhaps this is because you had directory information from using
> Tor recently when it wasn't filtered?
>
>> I am not able to use the Tor Network,I use Debian
>> Linux everything well-installed,but the logs are as
>> above everytime,and not once I could use Tor.
>> So I suspect that my ISP blocks Tor.
>
> That sounds like a reasonable guess.
>
>> Note:I use tor-button with
>> firefox.torcheck.xenobite.eu
>> always tells me tor not in place,the same using
>> showmyip.com the IP is my ISP IP.
>
> That makes it sound like you've screwed up your proxy settings. If your
> ISP blocks Tor, then your Tor requests ought to time out or otherwise
> fail. Not work and show up as being your own local IP address.
>
> So in summary, "maybe, but it sounds like you're confused about enough
> that I can't really guess."
>
> --Roger
>
>