[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: Cisco firewall filtering Tor?

To: or-talk@xxxxxxxxxxxxx
Subject: Re: Cisco firewall filtering Tor?
From: "Ringo Kamens" <2600denver@xxxxxxxxx>
Date: Thu, 14 Jun 2007 20:31:05 -0400
Delivered-to: archiver@xxxxxxxx
Delivered-to: or-talk-outgoing@xxxxxxxx
Delivered-to: or-talk@xxxxxxxx
Delivery-date: Thu, 14 Jun 2007 20:31:14 -0400
Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=NhQ0kj3LP/mzUbmFJEU2f+9vUw+fY+XFXuh4Jws+p0+EN/HZfKgt1yaJqvNOJ6dz5oatqa7CsFYtYVmpHTTfapBxt5QPVfm6QfxPQbiAJ5VUuXaKNzwkEP3+5THSkTUhe782xFQXcBfyEJugjP+nKvFkWhCeeg0oA7rgSe78ksU=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=JVYO7WuY+wgP8xOcN484hE7bQsjnKChhLlUXMiak/zf4xlrjpmMRb9YV2oDzJpl9QGkO4BArHBJzutn/K8VD2hwuwnf3WpdTAtAWUtX0ehsLOmoQO51RnnnAWGVpZMUHwHfK7Q6RROyC/IPthmzAbXdIsoJnP40kSt2mtF0zvwU=
In-reply-to: <b6bd62cf0706141711r15e54d50u1eb92479a617c35c@xxxxxxxxxxxxxx>
References: <b6bd62cf0706141711r15e54d50u1eb92479a617c35c@xxxxxxxxxxxxxx>
Reply-to: or-talk@xxxxxxxxxxxxx
Sender: owner-or-talk@xxxxxxxxxxxxx

It's probably just blocking by IP address.
Comrade Ringo Kamens

On 6/14/07, Jay Goodman Tamboli <jay@xxxxxxxxxx> wrote:

I'm stuck behind a FascistFirewall part of the day, and I've been
trying to get Tor to work as a client. I've added a line to my torrc:

ReachableAddresses *:443

Oddly, I can see that Skype is using TCP connections on port 443. I
can't tell if they're working, but Skype is keeping them up (and Skype
as a whole seems to be working).

Tor, on the other hand, is not working. netstat shows established
connections on port 443, but Tor doesn't seem to be accepting them as
usable. I have debug logging on, but I'm not sure what to look for,
since it seems to be trying to create circuits in parallel. Is there a
message printed when a OR connection fails, giving a reason?

Is it possible the firewall is looking at the :443 connections and
somehow telling that it's Tor rather than HTTPS?

/jgt
--
http://tamboli.cx/

References:
- Cisco firewall filtering Tor?
  - From: Jay Goodman Tamboli

Prev by Author: Re: What will happen to Tor after the new German data retention law takes effect?
Next by Author: Re: Cisco firewall filtering Tor?
Previous by thread: Cisco firewall filtering Tor?
Next by thread: Re: Cisco firewall filtering Tor?
Index(es):
- Author
- Thread