Delivery-Date: Sun, 04 Oct 2015 17:02:20 -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_SIGNED,
	FREEMAIL_FROM,RCVD_IN_DNSWL_MED,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 738791E0241;
	Sun,  4 Oct 2015 17:02:18 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id C45C638310;
	Sun,  4 Oct 2015 21:02:12 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 19BC638244
 for <tor-talk@lists.torproject.org>; Sun,  4 Oct 2015 21:02:09 +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 Wl0LSPIaWSNp for <tor-talk@lists.torproject.org>;
 Sun,  4 Oct 2015 21:02:09 +0000 (UTC)
Received: from tapuz.safe-mail.net (www.safe-mail.net [212.29.227.230])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id D3EE838138
 for <tor-talk@lists.torproject.org>; Sun,  4 Oct 2015 21:02:02 +0000 (UTC)
Received: by tapuz.safe-mail.net with Safe-mail (Exim 4.63)
 (envelope-from <force44@Safe-mail.net>) id 1ZiqPz-0007Bs-6s
 for tor-talk@lists.torproject.org; Sun, 04 Oct 2015 17:02:03 -0400
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=N1-0105; d=Safe-mail.net;
 b=FjBnGBy8kjZmPabyXomdmGDVF1FLZYNu7HXz1ModvxMdjExuIqi/gPfiZokuO9Ha
 EFV1fmi6gNFGkz9dpn0me6SVJsmQ2Y+j0Zex0WXLE76Cmxu6zDB/1P1id1ICTkMi
 890EO5nEf3QprggSVkItlRS4BXKBXT/QU+Xuht+pBoo=;
Received: from pc ([188.165.150.1]) by Safe-mail.net with https
Date: Sun, 4 Oct 2015 17:02:02 -0400
From: force44@Safe-mail.net
To: tor-talk@lists.torproject.org
X-SMType: Regular
X-SMRef: N1-27ppPMZjpO
Message-Id: <N1-27ppPMZjpO@Safe-mail.net>
MIME-Version: 1.0
X-SMSignature: z67LW2jtJ477uCiDMacFaVYCw/MDxTDYm3k6YWVVtAKFRhSVhBeGgkDXB6pY5JFU
 WMERxSVMl9rJLL+l2DbgIivx1kiolLXHiGuxf+VJCIkVbmRRZ6SA+tqVq0G/6czN
 KT7sCMSOHeaAeuQXK0QA8wsY2K5JGmtHO41Rtsezowc=
Subject: [tor-talk] TOR Browser - Change circuits
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>

Hello!

I understand that if a node used in a circuit is down, Tor will build a new route. But if all nodes used in a circuit are running correctly, how often will Tor change the route? Is there a way to control this?

Thank you
-- 
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

