Hi,
Your system is now lsted:
ec2bridgerocks001
https://atlas.torproject.org/#details/50855F45464DBE84E917B0ED74E2144E785BA0... -- Mit freundlichen Grüssen / Sincerely yours
Sebsstian Urbach
----------------------------------- Religion is a symptom of irrational belief and groundless hope. ----------------------------------- Gregory House, M.D.
On Sun, Dec 01, 2013 at 10:32:09PM +0100, Sebastian Urbach wrote:
Your system is now lsted:
ec2bridgerocks001
https://atlas.torproject.org/#details/50855F45464DBE84E917B0ED74E2144E785BA0...
It appears that you're running a *relay* on EC2?
With a nickname implying that you think it's a bridge?
Making it a public relay might be more expensive than you are expecting.
Did you have to reconfigure it manually to be a public relay, or was this an easy-to-make accident?
--Roger
I apologize for the delay in responding, getting ready to move to Texas, but anyway. My original intention was to run one EC2 as a public relay and another as a bridge, subject to bandwidth throttling, however, after thinking about it for about a day (I saw your email last night) I realized that a bridge that is bandwidth throttling might be more useful than a public relay that is bandwidth throttling.
So I'll fix it this evening, unless there's a reason not to.
Thanks.
On Sun, Dec 8, 2013 at 1:39 PM, Roger Dingledine arma@mit.edu wrote:
On Sun, Dec 01, 2013 at 10:32:09PM +0100, Sebastian Urbach wrote:
Your system is now lsted:
ec2bridgerocks001
https://atlas.torproject.org/#details/50855F45464DBE84E917B0ED74E2144E785BA0...
It appears that you're running a *relay* on EC2?
With a nickname implying that you think it's a bridge?
Making it a public relay might be more expensive than you are expecting.
Did you have to reconfigure it manually to be a public relay, or was this an easy-to-make accident?
--Roger
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
I built a new EC2 bridge at US East (NOVA) due to the fact that the one at California was published as a public relay. I apologize for the error Roger.
On an unrelated note, has there been any success in expanding the Tor cloud project to other cloud service providers? Is there anyway to volunteer to try to help out, if there's a willingness to expand it to other providers? Thanks.
--Rock
On Tue, Dec 10, 2013 at 4:37 PM, Conrad Rockenhaus conrad@rockenhaus.com wrote:
I apologize for the delay in responding, getting ready to move to Texas, but anyway. My original intention was to run one EC2 as a public relay and another as a bridge, subject to bandwidth throttling, however, after thinking about it for about a day (I saw your email last night) I realized that a bridge that is bandwidth throttling might be more useful than a public relay that is bandwidth throttling.
So I'll fix it this evening, unless there's a reason not to.
Thanks.
On Sun, Dec 8, 2013 at 1:39 PM, Roger Dingledine arma@mit.edu wrote:
On Sun, Dec 01, 2013 at 10:32:09PM +0100, Sebastian Urbach wrote:
Your system is now lsted:
ec2bridgerocks001
https://atlas.torproject.org/#details/50855F45464DBE84E917B0ED74E2144E785BA0...
It appears that you're running a *relay* on EC2?
With a nickname implying that you think it's a bridge?
Making it a public relay might be more expensive than you are expecting.
Did you have to reconfigure it manually to be a public relay, or was this an easy-to-make accident?
--Roger
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-- Conrad Rockenhaus
http://www.rockenhaus.com/ http://www.lagparty.org/~conradr/
On Thu, Dec 12, 2013 at 4:36 PM, Conrad Rockenhaus conrad@rockenhaus.com wrote:
On an unrelated note, has there been any success in expanding the Tor cloud project to other cloud service providers? Is there anyway to volunteer to try to help out, if there's a willingness to expand it to other providers? Thanks.
I did some research a year or so ago, but was unable to find anything that was as cheap *and* easy as AWS. There are cloud providers with lower prices, but they do not enable users to publish and use instance templates the same way AWS does.
On 12/16/2013 03:48 PM, Runa A. Sandvik wrote:
On an unrelated note, has there been any success in expanding the Tor cloud project to other cloud service providers? Is there anyway to volunteer to try to help out, if there's a willingness to expand it to other providers? Thanks.
I did some research a year or so ago, but was unable to find anything that was as cheap *and* easy as AWS. There are cloud providers with lower prices, but they do not enable users to publish and use instance templates the same way AWS does.
We're currently working on automating Tor relay and bridge deployment using Ansible scripts [ https://github.com/ansible/ansible ].
All it needs is SSH access, everything else will be pulled in and configured using Ansible. This should then work for all 'cloud providers' (or old-style VPS), and in my eyes is a more sustainable and decentralized way of doing "Tor cloud".
Another component that we work on at the moment is a homebrewed Python monitoring software for relays, which in the long term could be a nice feature to have apart from the generic traffic stats you get from Amazon.
We will have a first report end of this month with the specs, hopefully attracting more people to join the fun. Hannes, Daniel, Christian, feel free to share what you're doing with this list. :-)
I am setting one up on Azure right now. Will report back.
tor-relays@lists.torproject.org