[tor-relays] AccountingMax and RelayBandwidthRate

Chuck Peters cp at axs.org
Sun Nov 23 06:07:25 UTC 2014


teor said:
> 
> > Date: Sat, 22 Nov 2014 17:58:37 -0800
> > From: Seth <list at sysfu.com>
> > 
> > I should have also mentioned in my previous post I put the following in  
> > /etc/tor/torrc
> > 
> > # Bandwidth and data caps
> > AccountingStart day 19:45 # calculate once a day at 7:45pm
> > AccountingMax 33 GBytes # 33GB X 30 days = 10GB shy of 1000GB/mo.
> > RelayBandwidthRate 3000 KBytes
> > RelayBandwidthBurst 3750 KBytes # allow higher bursts but maintain average
> 
> There are 7/12 months that have 31 days, where your 33GB per day will result in a (potential) 23GB overuse. (And that's not including non-tor traffic like OS updates.)
> 
> Why not use 32GB x 31 days = 992GB, or 31GB x 31 days = 961GB ?

The number for the RelayBandwidthRate seems on the high side as well.  

One thing I have noticed since I changed my configuration is I keep 
maxing out the 32GB and my node doesn't seem to be flagged as a Guard 
node.  The main reason I chose port 80 is to make it available to some 
users that are otherwise blocked, but if the node doesn't obtain a Guard 
flag it seems kind of pointless to use port 80.  So what is better in 
terms of health of the Tor Network?

Current config: iptables redirects port 80 to 9001.
ORPort 198.211.99.146:80 IPv4Only NoListen
ORPort 198.211.99.146:9001 IPv4Only NoAdvertise
AccountingMax 32 GB
AccountingStart day 05:00


Proposed config change:
ORPort 198.211.99.146:80 IPv4Only NoListen
ORPort 198.211.99.146:9001 IPv4Only NoAdvertise
AccountingMax 32 GB
AccountingStart day 05:00
RelayBandwidthRate 1000 KBytes
RelayBandwidthBurst 3000 KBytes


Note I should actually calculate the RelayBandwidthRate for 1TB 
transfer, but given the stats from the past week, I think it is a 
reasonable rough approximation.


Chuck


More information about the tor-relays mailing list