Hi all, so as of Google Clouds pricing plans on outgoing traffic, I am attempting to set my relay to hibernate after sending 100 mbits of data per month. Does this torrc configuration look like it would do that?
SOCKSPort 0
ORPort 65534
ExitPolicy reject *:*
ContactInfo keiferDoTblyAtgmaildOtcom
Nickname torworld
RelayBandwidthRate 100 MBits
RelayBandwidthBurst 100 MBits
AccountingMax 100 MBits
AccountingStart month 1 00:00
AccountingRule out
Thanks all.
--Keifer
Mbits is a measure of data speed, not amount.
You have to specify the accounting in MBytes GBytes etc. MB GB
You need to find out what your amount of transfer limit is, and cap accordingly.
If Google is saying that you can use 100 Mbps of outbound bandwidth on average, then you just need the relay bandwidth & burst rates.
It will prevent it from using more than 100 Mbps so you won't go over.
Thanks,
Matt Westfall President & CIO ECAN Solutions, Inc. Everything Computers and Networks 804.592.1672
------ Original Message ------ From: "Keifer Bly" keifer.bly@gmail.com To: tor-relays@lists.torproject.org Sent: 6/3/2019 1:20:29 PM Subject: [tor-relays] Setting Tor Relay to Hibernate After 100Mbits
Hi all, so as of Google Clouds pricing plans on outgoing traffic, I am attempting to set my relay to hibernate after sending 100 mbits of data per month. Does this torrc configuration look like it would do that?
SOCKSPort 0
ORPort 65534
ExitPolicy reject *:*
ContactInfo keiferDoTblyAtgmaildOtcom
Nickname torworld
RelayBandwidthRate 100 MBits
RelayBandwidthBurst 100 MBits
AccountingMax 100 MBits
AccountingStart month 1 00:00
AccountingRule out
Thanks all.
--Keifer
On 6/3/19 13:20, Keifer Bly wrote:
Hi all, so as of Google Clouds pricing plans on outgoing traffic, I am attempting to set my relay to hibernate after sending 100 mbits of data per month. Does this torrc configuration look like it would do that?
SOCKSPort 0
ORPort 65534
ExitPolicy reject *:*
ContactInfo keiferDoTblyAtgmaildOtcom
Nickname torworld
RelayBandwidthRate 100 MBits
RelayBandwidthBurst 100 MBits
AccountingMax 100 MBits
AccountingStart month 1 00:00
AccountingRule out
Thanks all.
100 Megabits is 12.5 Megabytes, and approximately ~10 page loads of the average web page these days (as unscientifically eye-balled by me).
Further, setting RBR and RBB to 100 Mbits (per second) means you could theoretically hit your tiny AccountingMax in the first second of every month.
An AccountingMax of 100 Megabits is almost assuredly not what you actually want.
I'm wondering if there was some confusion about the difference between speed and a simple of bytes. Confusingly, Tor uses the same unit strings (like "MBits") for both, but mentally we should be adding "per second" for torrc options like RelayBandwidthRate.
100 Megabits per second is a reasonable RBR setting for a reasonable relay. 100 Megabits per month is a useless relay.
Hope that helps.
Matt
On Mon, 3 Jun 2019 13:39:43 -0400 Matt Traudt pastly@torproject.org wrote:
100 Megabits per second is a reasonable RBR setting for a reasonable relay.
Most likely though you don't want to be running a 100 Mbit/sec relay on Google Cloud, as their bandwidth pricing is outrageous, starting at $85 per TB: https://cloud.google.com/network-tiers/pricing Elsewhere you could get an entire high-spec dedicated server with an unmetered connection for that price. Yes even if not counting OVH, Online and Hetzner.
In fact personally I'm can't come up with justification to run *anything* on Google Cloud with such pricing, as multiple other (many orders of magnitude cheaper) options exist.
So I am trying to limit as google cloud has strict pricing plans. Perhaps I should go back to just running a bridge for now. What would the traffic limit for a useful relay be? Thanks.
On Mon, Jun 3, 2019 at 10:40 AM Matt Traudt pastly@torproject.org wrote:
On 6/3/19 13:20, Keifer Bly wrote:
Hi all, so as of Google Clouds pricing plans on outgoing traffic, I am attempting to set my relay to hibernate after sending 100 mbits of data per month. Does this torrc configuration look like it would do that?
SOCKSPort 0
ORPort 65534
ExitPolicy reject *:*
ContactInfo keiferDoTblyAtgmaildOtcom
Nickname torworld
RelayBandwidthRate 100 MBits
RelayBandwidthBurst 100 MBits
AccountingMax 100 MBits
AccountingStart month 1 00:00
AccountingRule out
Thanks all.
100 Megabits is 12.5 Megabytes, and approximately ~10 page loads of the average web page these days (as unscientifically eye-balled by me).
Further, setting RBR and RBB to 100 Mbits (per second) means you could theoretically hit your tiny AccountingMax in the first second of every month.
An AccountingMax of 100 Megabits is almost assuredly not what you actually want.
I'm wondering if there was some confusion about the difference between speed and a simple of bytes. Confusingly, Tor uses the same unit strings (like "MBits") for both, but mentally we should be adding "per second" for torrc options like RelayBandwidthRate.
100 Megabits per second is a reasonable RBR setting for a reasonable relay. 100 Megabits per month is a useless relay.
Hope that helps.
Matt _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On 03.06.2019 22:26, Keifer Bly wrote:
So I am trying to limit as google cloud has strict pricing plans. Perhaps I should go back to just running a bridge for now. What would the traffic limit for a useful relay be? Thanks.
At mine Relays ~20Mbit/s advertised bandwith = 40TB - 60TB in one month.
Note: 40TB = 20TB incoming and 20TB outgoing traffic.
Traffic is unfortunately expensive and always too little. :-(
Yes, I’ll have to go back to just running a bridge until I figure something out. Google chargers per GB of data that is sent. Is Microsoft VPS much better I wonder?
On Tue, Jun 4, 2019 at 1:05 AM lists@for-privacy.net wrote:
On 03.06.2019 22:26, Keifer Bly wrote:
So I am trying to limit as google cloud has strict pricing plans. Perhaps I should go back to just running a bridge for now. What would the traffic limit for a useful relay be? Thanks.
At mine Relays ~20Mbit/s advertised bandwith = 40TB - 60TB in one month.
Note: 40TB = 20TB incoming and 20TB outgoing traffic.
Traffic is unfortunately expensive and always too little. :-(
-- Ciao Marco! _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays@lists.torproject.org
-
Keifer Bly -
lists＠for-privacy.net -
Matt Traudt -
Matt Westfall -
Roman Mamedov