Delivery-Date: Sun, 15 Jun 2014 13:41:29 -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.7 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID
	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 moria.seul.org (Postfix) with ESMTPS id C24CD1E0A51
	for <archiver@seul.org>; Sun, 15 Jun 2014 13:41:27 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 8F5742F70B;
	Sun, 15 Jun 2014 17:41:25 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id C26342FDB3
 for <tor-talk@lists.torproject.org>; Sun, 15 Jun 2014 17:33:03 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at eugeni.torproject.org
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 EqBuzvWJ6NK5 for <tor-talk@lists.torproject.org>;
 Sun, 15 Jun 2014 17:33:03 +0000 (UTC)
Received: from mail-wi0-x234.google.com (mail-wi0-x234.google.com
 [IPv6:2a00:1450:400c:c05::234])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 645302FD11
 for <tor-talk@lists.torproject.org>; Sun, 15 Jun 2014 17:33:00 +0000 (UTC)
Received: by mail-wi0-f180.google.com with SMTP id hi2so2970738wib.1
 for <tor-talk@lists.torproject.org>; Sun, 15 Jun 2014 10:32:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=from:content-type:subject:message-id:date:to:mime-version;
 bh=TCRcJ+WyXFw7KZiA2J/ldX13BZJ/DaOkAynKo8BAE/s=;
 b=iylsgkQ5M6UyWMi+QVZ0R6ZVdK+k+ssGNlUqmqnrisWItkFh9etcIoQpooAINLTPj6
 W4SR7E3a52cMiwse9NGwfQYD8QexkLmb/JA2uDrq831OOkc/J4WNRUI3XWPJSZZ5LE5y
 sEUDg/atk/YLZ/AXA3lA6JmaqHnuJSQElh/kOWoVY+8xtSTyv44amlDUhuz7FzzUbqp8
 a7oV4AZDEzTaQYuBB6sCU4eW/xz8Pmc7HZ+FFT2Fk1LDXxkHCulCZV4u2rKJoiYZwreL
 VeWi8gaLRyFo/teek7+gy9ncapIVPmlwXlW+z5w91JdRbj+FkLFyjjTsfbMDJgH4hZLn
 4qeA==
X-Received: by 10.194.21.103 with SMTP id u7mr21273154wje.14.1402853577217;
 Sun, 15 Jun 2014 10:32:57 -0700 (PDT)
Received: from [10.1.1.3] ([209.95.32.239])
 by mx.google.com with ESMTPSA id x3sm27967961een.17.2014.06.15.10.32.54
 for <tor-talk@lists.torproject.org>
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Sun, 15 Jun 2014 10:32:56 -0700 (PDT)
From: Zhuo Zhongliu <zhongliu.zhuo@gmail.com>
Message-Id: <364B5C4C-2BC2-41DF-A0A9-E77DEEBADB12@gmail.com>
Date: Mon, 16 Jun 2014 01:32:36 +0800
To: tor-talk@lists.torproject.org
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
X-Mailer: Apple Mail (2.1874)
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [tor-talk] Strange problmes when building Tor private network
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>

To someone might concerns, 
Hi~ Recently I was building a tor private network in local lan for experiment, one of my dirs is configured as follows:
Address 192.168.1.115
ORPort 5003
ORListenAddress 192.168.1.115:5003
SocksPort 7003
NickName dir3
DataDirectory /home/xxx/experiment/routers/3
TestingTorNetwork 1
ExitPolicyRejectPrivate 0
Log notice file /home/xxx/experiment/routers/3/log
Log debug file /home/xxx/experiment/routers/3/logdebug
SafeLogging 0
UseMicrodescriptors 1
ExitPolicy reject *:25
ExitPolicy reject *:119
ExitPolicy reject *:135-139
ExitPolicy reject *:445
ExitPolicy reject *:563
ExitPolicy reject *:1214
ExitPolicy reject *:4661-4666
ExitPolicy reject *:6346-6429
ExitPolicy reject *:6699
ExitPolicy reject *:6881-6999
ExitPolicy accept *:*
RelayBandwidthRate 75 MB
RelayBandwidthBurst 75 MB
ContactInfo dir3@dir3.com
DirPort 10003
DirListenAddress 192.168.1.115:10003
V3AuthoritativeDirectory 1
V2AuthoritativeDirectory 1
AuthoritativeDirectory 1
RecommendedVersions 0.2.4.19,0.2.4.20,0.4.2.21
DirServer dir1 v3ident=A16D7E41A4CDE487E1B430825FD89581268F33E3 orport=5001 192.168.1.167:10001 E782 525F 08D9 D7A8 2A99 4CA5 D44F BFB9 2671 77EE
DirServer dir2 v3ident=6323D6E95D1D6670E6C2D87A2BEB86D35702A4B8 orport=5002 192.168.1.178:10002 970D E51E 5307 8F3F 0017 786B C612 FD23 DC6A 9F93
DirServer dir3 v3ident=3F35F22D49E8DDF6B61912009549CC8AF24BD1CB orport=5003 192.168.1.115:10003 7856 81F0 4DBC B1C2 4511 2122 1420 3E04 5A9D 48B6
DirServer dir4 v3ident=2C0C3D5B3EC9FB119D2481E3FE2000773E721DF6 orport=5004 192.168.1.141:10004 85A5 B8C3 FB36 7250 82F5 10D9 59EF AB57 7C55 59F6
DirServer dir5 v3ident=425B092EC22C06C6CBBBBA4B8F051A5DD5DA5A0D orport=5005 192.168.1.167:10005 740B 6BC3 EAC4 D93E 2CED 4147 9041 AB90 B2B2 075F

However, when my tor client connected to those dirs, it got the cached-consensus correctly. The only thing which makes me confused is that the client-version and the server-version content in Cached-Consensus as well as the directory-footer is MISSING!!! After checking the log, I found the warning "Consensus with empty bandwidth: G=0 M=0 E=176 D=489 T=665".
So my questions are 
1)how tor decides the bandwidth in LAN in the consensus file? RelayBandwidthRate or else? It turns out that no matter how I changed the RelayBandwidthRate, the bandwidth in consensus file still the same as before.
2) compared with the real tor network, why some contents are missing in the Cached-Consensus file? 
3) is it possible to control the flags in the LAN private tor network?
could someone help me out? Thanks in advance~ 

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

