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

Re: another bad exit

To: or-talk@xxxxxxxxxxxxx
Subject: Re: another bad exit
From: Gitano <ran6oony7r9deku5@xxxxxxxxxxxxxx>
Date: Sun, 19 Jul 2009 12:06:53 +0200
Delivered-to: archiver@xxxxxxxx
Delivered-to: or-talk-outgoing@xxxxxxxx
Delivered-to: or-talk@xxxxxxxx
Delivery-date: Sun, 19 Jul 2009 06:07:01 -0400
In-reply-to: <200907190901.n6J91lmP010534@xxxxxxxxxxxxx>
Organization: Private
References: <200907190901.n6J91lmP010534@xxxxxxxxxxxxx>
Reply-to: or-talk@xxxxxxxxxxxxx
Sender: owner-or-talk@xxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.22 (X11/20090608)

Scott Bennett wrote:

>      So I tried it again, appending .spacecowboy.exit, and can now confirm
> that node "spacecowboy" is indeed returning the error page, rather than
> simply returning the SOCKS failure, only this time it said that the name
> server said that the domain name doesn't exist, which is false:  tor-resolve
> returns 204.152.186.46 as the address for the target web site.  (Most of
> the page is in German, but some of it is close enough to English for me
> to understand it, and the message about squid is in English.)
>      The above described behavior clearly meets the criteria for flagging
> spacecowboy at 87.152.109.208 as a BadExit.

http://torstatus.blutmagie.de/router_detail.php?FP=6de93ee8597daa086d5f23c2f32bfd4dcf64ed11

It looks like this node has reached its physical bandwidth limit.

References:
- another bad exit
  - From: Scott Bennett

Prev by Author: Re: Yahoo Mail and Tor
Next by Author: Re: VoIP telephony building like Tor
Previous by thread: Re: another bad exit
Next by thread: Re: another bad exit
Index(es):
- Author
- Thread