Delivery-Date: Fri, 22 Jan 2016 07:55:37 -0500
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 972621E02F9;
	Fri, 22 Jan 2016 07:55:35 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id C364A395D4;
	Fri, 22 Jan 2016 12:55:29 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 4B16839563
 for <tor-talk@lists.torproject.org>; Fri, 22 Jan 2016 12:55:26 +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 ssEMX7QzyEJz for <tor-talk@lists.torproject.org>;
 Fri, 22 Jan 2016 12:55:26 +0000 (UTC)
Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com
 [IPv6:2a00:1450:400c:c09::234])
 (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 05AD03947E
 for <tor-talk@lists.torproject.org>; Fri, 22 Jan 2016 12:55:23 +0000 (UTC)
Received: by mail-wm0-x234.google.com with SMTP id u188so17736775wmu.1
 for <tor-talk@lists.torproject.org>; Fri, 22 Jan 2016 04:55:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to:content-type;
 bh=Z5rCXVUYiVM8Fsk9yHLh+5tXFBqg/FGTA6j2mCzxvyg=;
 b=rWceTv+kdYPJey3QVr5f/IlZW3EjHcijWJmG58/KTE1WKxVAn0ZgiSJkiMiaoU7tho
 Yak6pSKocpQ+/WOtIrpTS05kVgoQ8ikBZyahuoSZQSKibyBpPPewCozr3wWeQeMB6zmh
 r4cEaitHDLR6QOuLJWelT/qADVVP2X4Vh3CTnjRAyl7oCvKj/07pkXat/l/9aMuuDhs3
 vVb8BUs2GcHxcuwH6QryzSH2aY5OYP2u/OcLaoY8yGclp2EjurdDZyxJ65eAXR6xV4ov
 NHM0Pcb7ZvQE1qjWFygXfKNCC9RN/pJul4ZDLqvGoDGxwXskPI28dckD6+vwii2sJ/5l
 SHAg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:mime-version:date:message-id:subject:from:to
 :content-type;
 bh=Z5rCXVUYiVM8Fsk9yHLh+5tXFBqg/FGTA6j2mCzxvyg=;
 b=IN/IEAKwdhXD3gO0O3r2AADn8yXZC+5GiCRrboHWF4xGG3QoBZ7qf4Qx/yL3+phyjY
 MOMPjOy7QhR9BLx/+KBdASUVGdlnu9pf0d+DK63/h6kNjPSVK9tUNwUHdo/spLtgMF4s
 T/RGIVQGokG93jSYp5jeXZhigNQrLdJiuwOlb/MNGrCDoERGGYL4yLwTjBuGvBrDDb0z
 jqOz/iFin6B5QR1cqU90mxoXOz6d+zjx5+jzaR9BNWE630qtR4Eiw+glaQBDHnE85/5M
 glr/DAlNWeqsLTob5REDSH7UMwX3qCrGbxjyg7yruSYUsf2O19N6nROqu3idaL5rKzUQ
 YZYw==
X-Gm-Message-State: AG10YOT8qimrgpQKOB66RVT2qkyp+btFmWVc30TL9NNsZxNp3bKcsKkneTK7UV6dboTU/Yuno+QM2HNIuD3IuA==
MIME-Version: 1.0
X-Received: by 10.28.91.147 with SMTP id p141mr3405212wmb.19.1453467320085;
 Fri, 22 Jan 2016 04:55:20 -0800 (PST)
Received: by 10.194.31.229 with HTTP; Fri, 22 Jan 2016 04:55:20 -0800 (PST)
Date: Fri, 22 Jan 2016 20:55:20 +0800
Message-ID: <CAGP6POJ9Zo4e3498Pt_XKcyrMN+wiZjHDHxb3MumgrwB13Jcyw@mail.gmail.com>
From: Hongyi Zhao <hongyi.zhao@gmail.com>
To: tor-talk@lists.torproject.org
Subject: [tor-talk] Re-establishing a Tor circuit without restarting Tor.
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>

Hi all,

When I running Tor for a while, it will give me the following messages:

-------------
Jan 22 20:02:46.000 [notice] Your Guard superidatmynode1a
($3D1052D37DD20FA9E42CF813CB3B4A735BD119EE) is failing to carry more
streams on its circuits than usual. Most likely this means the Tor
network is overloaded or your network connection is poor. Use counts
are 22/32. Success counts are 97/283. 280 circuits completed, 10 were
unusable, 173 collapsed, and 11 timed out. For reference, your timeout
cutoff is 60 seconds.
Jan 22 20:03:30.000 [warn] Your Guard ireadconf
($B07FCCFAC6131953FE8523787B4A190D16DF6681) is failing an extremely
large amount of circuits. This could indicate a route manipulation
attack, extreme network overload, or a bug. Success counts are 18/153.
Use counts are 5/7. 145 circuits completed, 2 were unusable, 125
collapsed, and 6 timed out. For reference, your timeout cutoff is 60
seconds.
Jan 22 20:13:27.000 [warn] Your Guard torpidsUSwholesale
($510176C07005D47B23E6796F02C93241A29AA0E9) is failing an extremely
large amount of circuits. This could indicate a route manipulation
attack, extreme network overload, or a bug. Success counts are 15/229.
Use counts are 3/3. 228 circuits completed, 0 were unusable, 213
collapsed, and 2 timed out. For reference, your timeout cutoff is 60
seconds.
Jan 22 20:26:33.000 [warn] Your Guard gdl
($0642D2FF3054F77710D6B2AF1A5584DCF7FC8EDE) is failing an extremely
large amount of circuits. This could indicate a route manipulation
attack, extreme network overload, or a bug. Success counts are 8/202.
Use counts are 2/4. 201 circuits completed, 2 were unusable, 191
collapsed, and 28 timed out. For reference, your timeout cutoff is 60
seconds.
-------------

At this stage, basically it should means that the quality of Tor's
circuit is low or unusable.  In order to obtain a high quality of
Tor's circuit, I usually restarting Tor again and again.

So, my issue is as follows:

Is it possible to re-establish a Tor circuit without restarting Tor?

Regards
-- 
Hongyi Zhao <hongyi.zhao@gmail.com>
Xinjiang Technical Institute of Physics and Chemistry
Chinese Academy of Sciences
GnuPG DSA: 0xD108493
-- 
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

