[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: Asynchronous bandwidth limiting
- To: or-talk@xxxxxxxxxxxxx
- Subject: Re: Asynchronous bandwidth limiting
- From: John Brooks <special@xxxxxxxxxxxxxxxx>
- Date: Tue, 13 Jan 2009 14:58:49 -0700
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: or-talk-outgoing@xxxxxxxx
- Delivered-to: or-talk@xxxxxxxx
- Delivery-date: Tue, 13 Jan 2009 16:58:54 -0500
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=pZBW4XosW/e0W+qwRBQXHKEE9SaupOGMLfKX5j+v2M4=; b=S6/EHfMI4UZG/cWdCZptgYLCc9Yg+TQRvVnDVJ+E5V5kkOfgr1tAnC6oTD1mhMdANA AY3cuYr59tGwuzvhZX6oilJVXsdTd2hKPuRwKZZsnxDmqqGR05rb7G//p5UGO/aiXmke IdT/gM9TLg0dakngo2Yhl9Vil+hu9Rnx/G3hU=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=W5+75GNIYfhv1ehoFxRNIu1mCRCxJxzkfoKuzE7jRxYjy+lEH6UrcIhNI7Hv7WPL7q E5XhgYSh9JGFdUuoVSM9JDZEmkKPldS2APovsKppSYceTQ8oU0ST37QyfxTYUY0nc7lB 3itTFJanpLNbUBNCsXN3POyDdTrnE1+OKdsq8=
- In-reply-to: <496D0C48.7030402@xxxxxxxxxxxxxxxx>
- References: <496D0C48.7030402@xxxxxxxxxxxxxxxx>
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
First off, thanks for running a node - the network always needs more bandwidth.
As far as i'm aware, it isn't possible to specify incoming and outgoing limits separately, and if it were, the outgoing would always be higher. For the most part, relayed traffic is pretty close to 1:1; for everything that comes in, there is equal data going out (to the next node in the chain, the source, or the destination). The one major exception to this is the directory; requests for the directory are very small, but the results can be pretty large - but, that just means more outgoing than incoming. There is no benefit to having more incoming bandwidth than you do outgoing bandwidth. You can always disable the directory (DirPort 0) if you want to avoid that little bit of outgoing traffic, but usually it isn't too significant.
Hope that helps.
- John Brooks
On Tue, Jan 13, 2009 at 2:48 PM, Sebastian Lechte <seb@xxxxxxxxxxxxxxxx>
I plan to set up a tor node later this week and have been reading
documentation and different wikis. I have found how I can limit the
total bandwidth the server will consume.
My hoster only limits outgoing traffic, but as far as I understand, it
is not possible to specify bandwidth-limits separately for incoming and
Would it be good to be able to specify limits for outgoing or incoming
traffic separately, or would that only complicate matters without
providing any benefit?
Do incoming and outgoing traffic/bandwidth even differ significantly?
Does this depend on the type of node and exit-policy (if any) one uses?
I have no experience and have not found specific information on this, so
I hope that the list members can provide information on this question or
provide directions for further reading.