Delivery-Date: Mon, 12 Jan 2015 02:48:18 -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.8 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	RP_MATCHES_RCVD,URIBL_BLOCKED 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 B71AB1E0864
	for <archiver@seul.org>; Mon, 12 Jan 2015 02:48:16 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 28D233275C;
	Mon, 12 Jan 2015 07:48:12 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 2F01632740
 for <tor-talk@lists.torproject.org>; Mon, 12 Jan 2015 07:48:08 +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 MupzfzPsI9P8 for <tor-talk@lists.torproject.org>;
 Mon, 12 Jan 2015 07:48:08 +0000 (UTC)
Received: from server4.tvdw.eu (lauravdw.com [IPv6:2001:1af8:4100:a00d:4::2])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256
 bits)) (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id 0367C3250F
 for <tor-talk@lists.torproject.org>; Mon, 12 Jan 2015 07:48:08 +0000 (UTC)
Received: from g124058.upc-g.chello.nl ([80.57.124.58] helo=[10.0.0.164])
 by server4.tvdw.eu with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256)
 (Exim 4.84) (envelope-from <info@tvdw.eu>) id 1YAZjF-00051q-Oq
 for tor-talk@lists.torproject.org; Mon, 12 Jan 2015 08:48:01 +0100
From: Tom van der Woerdt <info@tvdw.eu>
Mime-Version: 1.0 (1.0)
Message-Id: <4224DACE-08E8-4C0B-81C5-D27E27B3D85F@tvdw.eu>
Date: Mon, 12 Jan 2015 08:48:01 +0100
References: <586274183.134130.1421047107274.JavaMail.zimbra@yetopen.it>
In-Reply-To: <586274183.134130.1421047107274.JavaMail.zimbra@yetopen.it>
To: "tor-talk@lists.torproject.org" <tor-talk@lists.torproject.org>
X-Mailer: iPhone Mail (12B440)
Subject: Re: [tor-talk] Question about linux-tor-prio.sh
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 Lorenzo,

1Mbit is 125Kbyte. :)

Tom



> On 12 Jan 2015, at 08:18, Lorenzo Milesi <maxxer@ufficyo.com> wrote:
> 
> Hi.
> I've recently set up a Tor node but bandwidth is running out quickly :)
> Since I don't want to throttle BW using Tor's options (which basically turns it down) I'd like to limit speed, so I found the suggested script above.
> I tuned config to fit my needs (my VPS has 1Mb/s speed) this way:
> 
> DEV=eth0
> TOR_UID=$(id -u debian-tor)
> RTT_LATENCY=40
> # RATE_UP must be less than your connection's upload capacity in
> # kbits/sec. If it is larger, then the bottleneck will be at your
> # router's queue, which you do not control. This will cause congestion
> # and a revert to normal TCP fairness no matter what the queing
> # priority is.
> RATE_UP=1000
> # RATE_UP_TOR is the minimum speed your Tor connections will have in
> # kbits/sec.  They will have at least this much bandwidth for upload.
> # In general, you probably shouldn't set this too low, or else Tor
> # users who use your node will be completely choked out whenever your
> # machine does any other network activity. That is not very fun.
> RATE_UP_TOR=500
> # RATE_UP_TOR_CEIL is the maximum rate allowed for all Tor trafic in
> # kbits/sec.
> RATE_UP_TOR_CEIL=900
> 
> CHAIN=OUTPUT
> MTU=1500
> AVG_PKT=900 # should be more like 600 for non-exit nodes
> 
> 
> But when I start the script, after some time the Atlas page reports a 125kb/s bandwidth for my node.
> 
> Am I configuring it wrong or what?
> thanks
> -- 
> Lorenzo Milesi - lorenzo.milesi@yetopen.it
> 
> YetOpen S.r.l. - http://www.yetopen.it/
> -- 
> 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
-- 
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

