[tor-relays] New Relay Online/Working on AWS Cloud Torproject

[Conrad Rockenhaus]

Hello,

ConradsAWSRelay was started back up on a new AWS instance running Amazon Linux and it’s hash is now 9F7F05699131E1E2A22F70B83E8CBB4671F5FEE2. I have upgraded to Tor 0.3.1.9…. I had issues with getting the libevent development header dependencies resolved on Amazon Linux so I just compiled it on Red Hat and brought it over. More than likely I overlooked something and caused a cascade of failures from there, anyway, it’s up.

Additionally, I brought up ConradsAWSExit, 1B47E33F9D422CC97BD2DDA1F082BFF2FC58E79A, to help out with that area. I may bandwidth limit this one depending on load,  I will have to wait and see how much traffic it gets since I don’t have unlimited $$$ to allocate to my new hobby :).

If someone could take another look and provide me any feedback/constructive criticism about these two nodes, I would greatly appreciate it.

Thank you for everyone’s advise! I also appreciate the input regarding the revitalization of the Cloud project again. Another person has also volunteered to assist in the project so hopefully things should start moving here pretty soon!

Thanks,

Conrad

> On Dec 19, 2017, at 9:02 PM, Conrad Rockenhaus <conrad at rockenhaus.com> wrote:
> 
> 
> 
>> On Dec 19, 2017, at 8:55 PM, teor <teor2345 at gmail.com <mailto:teor2345 at gmail.com>> wrote:
>> 
>> 
>> On 20 Dec 2017, at 13:28, Conrad Rockenhaus <conrad at rockenhaus.com <mailto:conrad at rockenhaus.com>> wrote:
>> 
>>> Howdy,
>>> 
>>> Early this morning (3 AM CST) I brought a non-exit relay named “ConradsAWSRelay” online. I would appreciate it if someone would take an objective look at it to see if the relay is fast enough and bringing useful services to the tor network.
>> 
>> Please upgrade your relay to the latest Tor version:
>> https://lists.torproject.org/pipermail/tor-announce/2017-December/000147.html <https://lists.torproject.org/pipermail/tor-announce/2017-December/000147.html>
>> 
> 
> I noticed this when I started it up. It appears that the version of Tor on EPEL is out of date. I’ll build it out of source to fix it. I’ll probably have to do that for the Cloud solution as well since the lifecycle of EPEL is normally behind. I’ll fix this now.
> 
>> Your relay might take a few weeks to be used:
>> https://blog.torproject.org/lifecycle-new-relay <https://blog.torproject.org/lifecycle-new-relay>
> I completely forgot about that. Thank you for reminding me :D.
> 
>> 
>>> Additionally, I know that people have been working on ansible solutions regarding the installation of tor and what not, but that being said, I’m working on an AWS specific solution to replace the previous Cloud torproject that we had years ago. I will keep everyone in the loop, but I think its time that we have a cloud specific solution for rolling out tor.
>> 
>> Thanks!
>> It would be great to have this again.
> 
> I’m making progress and will advise all when I hit certain points so I can get feedback. I would like this new solution to have significant community input so I have all of my i’s dotted and my t’s crossed.
> 
> Thanks,
> 
> Conrad
> 
>> 
>> T
>> _______________________________________________
>> tor-relays mailing list
>> tor-relays at lists.torproject.org <mailto:tor-relays at lists.torproject.org>
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20171220/4a551d0b/attachment-0001.html>