[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: Cisco firewall filtering Tor?
I am not sure what the problem is, but I operate kgabertgoldmine2 and
recently saw in my logs (only a few of these, but more than one, and
only from a few days ago, nothing in the last three days):
[notice] We stalled too much while trying to write 2775410 bytes to
addr [scrubbed]. If this happens a lot, either something is wrong
with your network connection, or something is wrong with theirs. (fd
394, type Control, state 2, marked at control.c:2733).
I'm not sure if it is related, but I have not seen those before.
If this means that something is set up wrong on my side, then I will
be happy to fix it, but because you need 3 unique entry points I don't
think this [potential] issue would be causing these problems for you.
I hope that you can figure this out soon!
On 6/15/07, Roger Dingledine <arma@xxxxxxx> wrote:
On Fri, Jun 15, 2007 at 06:11:39PM -0400, Jay Goodman Tamboli wrote:
> >Try sending "GET /tor/status/all". (Some filters look for the "/tor/"
> That also seems to work.
> >And if that works, try sending the same thing to 184.108.40.206 port 9031.
> Connection refused. I don't think that 9031 is allowed for outgoing
Ok. Go look at add_default_trusted_dirservers() in src/or/config.c and
try each of those, then. :)
(I think dizum is down right now, but the rest should work.)