I am about to run a relay, but I don't want it using more than 1000GB a month. I prefer to manage this using the *BandwidthRate** *but I don't know the math* *to constrain it over a 1000GB a month. * * I also want to relay the directory. Is there a way to also use vidalia to interface? I'll be relaying on a linux (ubuntu) server remotly, and I'm using a windows system to set it all up. I'll be using SSH to shell in, but I'd love to use vidalia.
Thanks, Jon
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 14.09.2013 21:47, Jonathan W wrote:
I am about to run a relay, but I don't want it using more than 1000GB a month. I prefer to manage this using the *BandwidthRate** *but I don't know the math* *to constrain it over a 1000GB a month. * * I also want to relay the directory. Is there a way to also use vidalia to interface? I'll be relaying on a linux (ubuntu) server remotly, and I'm using a windows system to set it all up. I'll be using SSH to shell in, but I'd love to use vidalia.
Thanks, Jon
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Hello Jon,
this is quite easy to determine.
We have a known time frame of a month, lets say the average month has 30 days. Then: Timeframe = ~30 days = 30 * 24 * 60 * 60 seconds = 30 * 86400 seconds = 2592000 seconds
Since Tor specifies Bandwidth in kB (per second) lets convert your traffic limit to that.
Traffic-Limit = 1000 GB = 1000 * 1024 MB = 1000 * 1024 * 1024 kB = 1048510000 kB
- From that we can derive the average speed to reach (or stay below) your traffic limit. Depending on whether your provider counts TX+RX or just TX you may or may not have to half the bandwidth.
Avg. Bandwidth = Traffic-Limit / Timeframe = 1048510000 kB / 2592000 seconds = 404,517746914 kB / s
Cheers!
Martin
I'm so sorry.. I follow a little, how do I convert that into the value used by *BandwidthRate* **
On Sat, Sep 14, 2013 at 3:27 PM, Martin Weinelt tor@linuxlounge.net wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 14.09.2013 21:47, Jonathan W wrote:
I am about to run a relay, but I don't want it using more than 1000GB a month. I prefer to manage this using the *BandwidthRate** *but I don't know the math* *to constrain it over a 1000GB a month. * * I also want to relay the directory. Is there a way to also use vidalia to interface? I'll be relaying on a linux (ubuntu) server remotly, and I'm using a windows system to set it all up. I'll be using SSH to shell in, but I'd love to use vidalia.
Thanks, Jon
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Hello Jon,
this is quite easy to determine.
We have a known time frame of a month, lets say the average month has 30 days. Then: Timeframe = ~30 days = 30 * 24 * 60 * 60 seconds = 30 * 86400 seconds = 2592000 seconds
Since Tor specifies Bandwidth in kB (per second) lets convert your traffic limit to that.
Traffic-Limit = 1000 GB = 1000 * 1024 MB = 1000 * 1024 * 1024 kB = 1048510000 kB
- From that we can derive the average speed to reach (or stay below)
your traffic limit. Depending on whether your provider counts TX+RX or just TX you may or may not have to half the bandwidth.
Avg. Bandwidth = Traffic-Limit / Timeframe = 1048510000 kB / 2592000 seconds = 404,517746914 kB / s
Cheers!
Martin -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.21 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJSNMazAAoJEL1KoFKPY/F+kacH/2anBFcoXjgwSdT/TPj2mYnN IrVo9+wKTM40PjiaB5UoHpIFQm31EjdJk6iQ3mzv71UmtrXXBiEN+Vzp7e/NCZVO SMiQoGqrU1yA6ebmAxKXVK4HrMR+YqSunmn9xhbt7PlZQLwvjMU1S1PyQWR/29Tb AiCPTlCsYHSm7McKnRxEU8jlKRHt5QEa7Bu7jcAx68Asdy+w7PEqOXxgT5ixK1En U2MFIpTz60Ke4iZNDEXQ5KgC4XsML+gyBMeiTEt2jUsfbx5q4OIFE0kfbKjNVeJ/ ADvY1e8RyYNX9sbne2gEeJD1XQ6fG+t8uFJLfp7XigPAtZeiizCr9EdA/jZPvds= =C9CB -----END PGP SIGNATURE----- _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On 09/14/2013 09:47 PM, Jonathan W wrote:
I am about to run a relay, but I don't want it using more than 1000GB a month. I prefer to manage this using the *BandwidthRate*//but I don't know the math//to constrain it over a 1000GB a month.
1000GB in both directions means 500GB per month. You can spread this across the whole month, but it probably makes more sense to have a high bandwidth relay that is only active for some, say two, weeks. I don't have any numbers, but I would guess there are many relays that start accounting at the 1st of every month and thus stop relaying traffic during the month. So, I would suggest to move the account period, which you can do using the AccountingStart directive. The following setting sets it to use 500 GB per direction per accounting period, uses a monthly accounting period, and starts from the 15th of every month (to the 15th of the next month).
AccountingMax 500 GB # per direction AccountingStart month 15 0:00
Additionally, you correctly want to use BandwidthRate to not burn 500GB on a single day. If your goal is to hit 500GB after around 2 weeks: 500GB/14days = (500*1024*1024)KB/(14*24*60*60)seconds = 433 KB/s
BandwidthRate 430 KB
There's some mystery around BandwidthBurst, but the following should not hurt:
BandwidthBurst 1000 KB
I also want to relay the directory. Is there a way to also use vidalia to interface? I'll be relaying on a linux (ubuntu) server remotly, and I'm using a windows system to set it all up. I'll be using SSH to shell in, but I'd love to use vidalia.
No, this is not possible. A wonderful Tor controller for Linux command line is "arm", https://www.torproject.org/projects/arm.html.en
Thank you, I have installed ARM.. It it nice. So if I gather the above correctly, rate limiting 430 KB will insure that the totals of the TX and RX should not exceed 500GB in 2 weeks? Thank you all for your help again.
On Sat, Sep 14, 2013 at 3:28 PM, Moritz Bartl moritz@torservers.net wrote:
On 09/14/2013 09:47 PM, Jonathan W wrote:
I am about to run a relay, but I don't want it using more than 1000GB a month. I prefer to manage this using the *BandwidthRate*//but I don't know the math//to constrain it over a 1000GB a month.
1000GB in both directions means 500GB per month. You can spread this across the whole month, but it probably makes more sense to have a high bandwidth relay that is only active for some, say two, weeks. I don't have any numbers, but I would guess there are many relays that start accounting at the 1st of every month and thus stop relaying traffic during the month. So, I would suggest to move the account period, which you can do using the AccountingStart directive. The following setting sets it to use 500 GB per direction per accounting period, uses a monthly accounting period, and starts from the 15th of every month (to the 15th of the next month).
AccountingMax 500 GB # per direction AccountingStart month 15 0:00
Additionally, you correctly want to use BandwidthRate to not burn 500GB on a single day. If your goal is to hit 500GB after around 2 weeks: 500GB/14days = (500*1024*1024)KB/(14*24*60*60)seconds = 433 KB/s
BandwidthRate 430 KB
There's some mystery around BandwidthBurst, but the following should not hurt:
BandwidthBurst 1000 KB
I also want to relay the directory. Is there a way to also use vidalia to interface? I'll be relaying on a linux (ubuntu) server remotly, and I'm using a windows system to set it all up. I'll be using SSH to shell in, but I'd love to use vidalia.
No, this is not possible. A wonderful Tor controller for Linux command line is "arm", https://www.torproject.org/projects/arm.html.en
-- Moritz Bartl https://www.torservers.net/ _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On 09/15/2013 12:09 AM, Jonathan W wrote:
Thank you, I have installed ARM.. It it nice. So if I gather the above correctly, rate limiting 430 KB will insure that the totals of the TX and RX should not exceed 500GB in 2 weeks? Thank you all for your help again.
Accounting is done per direction, so setting AccountingMax to 500 GB will make it not exceed 1000 GB in total (RX+TX). Limiting BandwidthRate will additionally make sure that your relay is up at least two weeks, after that it will go into hibernation. Add all three lines to your torrc:
BandwidthRate 430 KB AccountingMax 500 GB AccountingStart month 15 0:00
On 13-09-14 04:28 PM, Moritz Bartl wrote:
... but I would guess there are many relays that start accounting at the 1st of every month and thus stop relaying traffic during the month. So, I would suggest to move the account period, which you can do using the AccountingStart directive. The following setting sets it to use 500 GB per direction per accounting period, uses a monthly accounting period, and starts from the 15th of every month (to the 15th of the next month).
AccountingMax 500 GB # per direction AccountingStart month 15 0:00
According to the manual for stable [0], Tor will wait until a random point in each period before waking up, so perhaps gaming the month start date isnt needed anymore.
On 09/15/2013 01:05 AM, krishna e bera wrote:
According to the manual for stable [0], Tor will wait until a random point in each period before waking up, so perhaps gaming the month start date isnt needed anymore.
Ah. Cool. Thanks for the heads up/reminder.
tor-relays@lists.torproject.org
-
Jonathan W -
krishna e bera -
Martin Weinelt -
Moritz Bartl