After reading on Hacker News about Tor's request for bridges for Syria and Iran, I thought perhaps I could use my el-cheapo VPS for this. I use it to run an anonymous forwarding proxy for my own use. It gets very little use, so I can do without the proxy for a few months. Mem is limited to 128MB, with bursts to 256MB. Bandwidth is 500GB up and down per month. Tor can have half of this (note the up *and* down). The caveat is that, because it is a dirt cheap VPS, I don't get a warning about any violation of the TOS. If I go outside the guidelines, they cancel my account. So I need to be fairly certain, or somehow limit Tor, that its memory use in normal circumstances will not exceed ~100MB. Is it feasible to run a bridge within these limits? If so, any suggestions on config options welcome. thanks, Nick
I've been running a Tor Relay doing 15Mbit/s on chvps.com with 128MB of ram. Plenty of kernel messages saying "Hey man, put some more RAM" but i just ignored them, added "file based" a +256mb of swap, and the machine has been running fine for some more than 1 month. This doesn't means it's the perfect environment. Fabio On 2/14/12 2:42 AM, tor-relays@nickcoleman.org wrote:
After reading on Hacker News about Tor's request for bridges for Syria and Iran, I thought perhaps I could use my el-cheapo VPS for this. I use it to run an anonymous forwarding proxy for my own use. It gets very little use, so I can do without the proxy for a few months.
Mem is limited to 128MB, with bursts to 256MB.
Bandwidth is 500GB up and down per month. Tor can have half of this (note the up *and* down).
The caveat is that, because it is a dirt cheap VPS, I don't get a warning about any violation of the TOS. If I go outside the guidelines, they cancel my account. So I need to be fairly certain, or somehow limit Tor, that its memory use in normal circumstances will not exceed ~100MB.
Is it feasible to run a bridge within these limits? If so, any suggestions on config options welcome.
thanks, Nick _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Hi Fabio, On Tue, Feb 14, 2012 at 07:47:06AM +0100, Fabio Pietrosanti (naif) wrote:
I've been running a Tor Relay doing 15Mbit/s on chvps.com with 128MB of ram.
Plenty of kernel messages saying "Hey man, put some more RAM" but i just ignored them, added "file based" a +256mb of swap, and the machine has been running fine for some more than 1 month.
This doesn't means it's the perfect environment.
Have you talked to them explicitly about running a TOR exit node? Are they ok with it? Their prices are much better than my current provider (though my current provider is ok w/ TOR), so I might consider switching if they're on board. Thanks! \t
On 02/14/2012 02:42 AM, tor-relays@nickcoleman.org wrote:
Bandwidth is 500GB up and down per month. Tor can have half of this (note the up *and* down).
excerpt of config from my torrc (running 0.2.2.35): RelayBandwidthRate 150 KBytes RelayBandwidthBurst 300 KBytes ExitPolicy reject *:* traffic stats from my hoster for 01/2012: 222.78 GB IN / 225.37 GB OUT / 448.14 GB TOTAL note that this is a public relay with open directory port, but without obfusproxy. i can't tell how much overhead you will get from running OBFS (and how much idle time you get as a bridge). still, for the first month you might want to tune your BandwidthRates with 20% overhead in mind, just to be on the safe side.
On Tue, 14 Feb 2012 10:46:22 +0100 krugar <tor-admin@krugar.de> allegedly wrote:
On 02/14/2012 02:42 AM, tor-relays@nickcoleman.org wrote:
Bandwidth is 500GB up and down per month. Tor can have half of this (note the up *and* down).
excerpt of config from my torrc (running 0.2.2.35):
RelayBandwidthRate 150 KBytes RelayBandwidthBurst 300 KBytes ExitPolicy reject *:*
traffic stats from my hoster for 01/2012:
222.78 GB IN / 225.37 GB OUT / 448.14 GB TOTAL
Also useful to add accounting limits if you wish to restrict overall usage within a particular period. For example, I have about 750 GB pcm to donate to Tor. I manage to stay within this by setting a daily accounting limit as below: AccountingStart day 18:00 AccountingMax 13 GB Note that the AccountingMax figure is /each way/ so we need to double this to 26 GB to see what the actual maximum traffic will be restricted to. As the manual page explains, it is better to have a collection of fast servers which are up most of the time rather than a host of slow servers which are always up. And you (Nick) might want to consider getting a VPS to dedicate to Tor. They are pretty cheap these days. But if you can't do this, then donate a sum (say $5 a month) to the tor project who will use it to provide additional bandwidth. Every little helps. Mick --------------------------------------------------------------------- blog: baldric.net fingerprint: E8D2 8882 F7AE DEB7 B2AA 9407 B9EA 82CC 1092 7423 ---------------------------------------------------------------------
participants (5)
-
Fabio Pietrosanti (naif) -
krugar -
mick -
tor-relays＠nickcoleman.org -
Tycho Andersen