Delivery-Date: Fri, 18 Mar 2016 02:32:35 -0400
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.1 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,T_DKIM_INVALID,T_RP_MATCHES_RCVD
	autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 2C3501E0B14;
	Fri, 18 Mar 2016 02:32:33 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id EB98F390B2;
	Fri, 18 Mar 2016 06:32:28 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id BF2E5386E6
 for <tor-talk@lists.torproject.org>; Fri, 18 Mar 2016 06:32:24 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id mMvpSSbyPZbD for <tor-talk@lists.torproject.org>;
 Fri, 18 Mar 2016 06:32:24 +0000 (UTC)
Received: from mail-vk0-x242.google.com (mail-vk0-x242.google.com
 [IPv6:2607:f8b0:400c:c05::242])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 972F023900
 for <tor-talk@lists.torproject.org>; Fri, 18 Mar 2016 06:32:24 +0000 (UTC)
Received: by mail-vk0-x242.google.com with SMTP id e185so8809407vkb.2
 for <tor-talk@lists.torproject.org>; Thu, 17 Mar 2016 23:32:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to;
 bh=nQm9tWUugTYNT8o407IBucyiQHKbE7WxcmdqDh4+E70=;
 b=bzalrmU0q+cXdAAh3M21puyuHj/PjuCzjjSQlbDaZza+30awLkOEUbRgXOWi3C53BM
 AKSgttGvNZh/RJX7OlTZiRd/NnMUX2olD1IXuWY0t0PFDfHOUddb70QwK4StkFMoBT/u
 YqmbBJwH959IfPd7MgQ2BEIqKuGecYJiYlJ7oBLAGyl3RoIIYE4YnONN2uwQTVSpX+VD
 sEyhCli7gC45z/Map1idtkz1Ya6MsBY2K1I8mh/ik78FtmlRl69/rMySHv84p9YjQ+sI
 jk5ShiHymwVIMQzz934teJIr32j/l11YQtk3GGPyPomTkIL5gNWGJ3FZXpOHFnpDY2LE
 noLg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:mime-version:in-reply-to:references:date
 :message-id:subject:from:to;
 bh=nQm9tWUugTYNT8o407IBucyiQHKbE7WxcmdqDh4+E70=;
 b=hutgCH3uv9NX42LxT4B1cNu7CAkrhf9xbC5yTzeZa0Ktd2Fg/fQHVUx4ZfuMJv0W4n
 97q/iBt6TQS7DKoO3qAMTU+DPlcD6aucmhpKhC8wBFZT59ho2Bv3mDl4/nmx5MWwLcCt
 Sp0J/OS4pgGDUBec3g8oZZ0gc+eXLHYaOfCHWwp6rATOzn326LbqzuX92BycyosKAEmN
 i7CR/GbrBRTvGBthTNARe2Fhh5FwYDr/lLhHzbO7xNE6zSXOdxCRzd12GSyQKn6EsGtT
 Q//MoBUAu+TIrkYknxBv8RWuQ46E/N6lWtzcHd+10g7RFJxFDXtBHrd8Lq7V8nh+RfLe
 CZ1w==
X-Gm-Message-State: AD7BkJKoyQnM0/+e9AU+De96aBwU3nnt5i2qck5GYbLYyW8u894xZPRIIkR4/vJJq9a06nWH9J9HPyQtOBq2iw==
MIME-Version: 1.0
X-Received: by 10.31.141.2 with SMTP id p2mr15682520vkd.37.1458282742126; Thu,
 17 Mar 2016 23:32:22 -0700 (PDT)
Received: by 10.176.69.5 with HTTP; Thu, 17 Mar 2016 23:32:21 -0700 (PDT)
In-Reply-To: <20160316161339.GP8732@moria.seul.org>
References: <loom.20160316T091856-306@post.gmane.org>
 <20160316161339.GP8732@moria.seul.org>
Date: Fri, 18 Mar 2016 02:32:21 -0400
Message-ID: <CAD2Ti2_qM40cPA3dL_AR2MW199HDdxDyQJyJCwKpG9pk1k-42w@mail.gmail.com>
From: grarpamp <grarpamp@gmail.com>
To: tor-talk@lists.torproject.org
Subject: Re: [tor-talk] Why my tor-assigned IP address differs from that of
 exit node ?
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

On 3/16/16, Roger Dingledine <arma@mit.edu> wrote:
> On Wed, Mar 16, 2016 at 08:26:17AM +0000, jb wrote:
>> Why does it happen, and is it something to worry about or a bug ?
>
> It's nothing to worry about, and also not a bug.

However it's also not something to just ignore.
A "Red", for all the reasons it may occur good or bad, should
still be investigated before using tor. Even if all that means is
that you hit "NEWNYM, new circuit / identity, whatever the button
for that is in TBB" and try for green again before assuming
your setup works and then surfing the net. If you get all red's,
or even more than a percent of all exits, that could be a real
problem to ask about.

I've been trying to get a blurb to the effect that "red may happen
on occaision, please read some wiki faq link and try again" added
to the check screen.

> But this case raises some legitimate questions:
> http://tor.stackexchange.com/questions/598/sorry-you-are-not-using-tor-strange-issue-72-52-91-18-19?lq=1

Unlike the ORPort IP, tor [operator] simply may not have bound
any [scannable] ports to the actual resultant exit IP.

"Quality Score" is something different and not on primary topic.
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

