Greetings!
I currently have 1 bridge relay running on my AWS account.
Is it possible to add another 2 bridge relays to run as separate instances from the same AWS account?
I'm wondering if there might be issues with IP address allocation?
For example, would I need to make any ammendment to the tor configuration file a la 'tor family' to differentiate between the different nodes running on the same amazon account?
Any advise appreciated.
Best regards,
Johnnie
On Tue, May 21, 2013 at 07:04:12PM +0100, torrelay@mail.md wrote:
I currently have 1 bridge relay running on my AWS account.
Is it possible to add another 2 bridge relays to run as separate instances from the same AWS account?
I'm wondering if there might be issues with IP address allocation?
For example, would I need to make any ammendment to the tor configuration file a la 'tor family' to differentiate between the different nodes running on the same amazon account?
If you provision a separate "instance" on AWS it will have a different IP. From the outside world we can't tell what Amazon userid is responsible for each IP address.
-andy
On Tue, May 21, 2013 at 6:04 PM, torrelay@mail.md wrote:
Greetings!
Hi,
I currently have 1 bridge relay running on my AWS account.
Great!
Is it possible to add another 2 bridge relays to run as separate instances from the same AWS account?
Yes.
I'm wondering if there might be issues with IP address allocation?
All three instances will have different IP addresses. Note that the Amazon free tier offer (if you have that) is only for one instance.
For example, would I need to make any ammendment to the tor configuration file a la 'tor family' to differentiate between the different nodes running on the same amazon account?
No, you don't have to do anything.
Hej,
I have three :) obfsproxy AWS accounts going but I can't prove they are working usefully. There's in-out activity but not as much as I'd guess. The FAQ at cloud.torproject advises to use the public DNS address+443 i.e. ec2-192-0-2-27.compute-1.amazonaws.com= 192.0.2.27:443 but Firefox says not so.
Robert
____________________________________________________________ FREE 3D EARTH SCREENSAVER - Watch the Earth right on your desktop! Check it out at http://www.inbox.com/earth
On Tue, May 21, 2013 at 10:38 PM, I beatthebastards@inbox.com wrote:
Hej,
Hi,
I have three :) obfsproxy AWS accounts going but I can't prove they are working usefully. There's in-out activity but not as much as I'd guess. The FAQ at cloud.torproject advises to use the public DNS address+443 i.e. ec2-192-0-2-27.compute-1.amazonaws.com= 192.0.2.27:443 but Firefox says not so.
Have you tried connecting to your bridge with Tor? You should have :443 (bridge), :40872 (obfs2), and :52176 (obfs3).
Thank you Runa.
Tor browser on a desktop didn't get through using (ip changed) ec2-192-0-2-27.compute-1.amazonaws.com ec2-192-0-2-27.compute-1.amazonaws.com:443, and 40872 and 52176 192.0.2.27 and :443 40872 52176
Orweb didn't work either using http and https plus the above.
Robert
I have three :) obfsproxy AWS accounts going but I can't prove they are working usefully. There's in-out activity but not as much as I'd guess. The FAQ at cloud.torproject advises to use the public DNS address+443 i.e. ec2-192-0-2-27.compute-1.amazonaws.com= 192.0.2.27:443 but Firefox says not so.
Have you tried connecting to your bridge with Tor? You should have :443 (bridge), :40872 (obfs2), and :52176 (obfs3).
____________________________________________________________ FREE 3D MARINE AQUARIUM SCREENSAVER - Watch dolphins, sharks & orcas on your desktop! Check it out at http://www.inbox.com/marineaquarium
On Mon, May 27, 2013 at 11:20 PM, I beatthebastards@inbox.com wrote:
Thank you Runa.
Tor browser on a desktop didn't get through using (ip changed) ec2-192-0-2-27.compute-1.amazonaws.com ec2-192-0-2-27.compute-1.amazonaws.com:443, and 40872 and 52176 192.0.2.27 and :443 40872 52176
Orweb didn't work either using http and https plus the above.
Did create firewall (security group) rules for these ports?
Runa,
I made exceptions in XP's firewall for each.
Rob
____________________________________________________________ GET FREE SMILEYS FOR YOUR IM & EMAIL - Learn more at http://www.inbox.com/smileys Works with AIM®, MSN® Messenger, Yahoo!® Messenger, ICQ®, Google Talk™ and most webmails
On Thu, May 30, 2013 at 1:07 AM, I beatthebastards@inbox.com wrote:
Runa,
I made exceptions in XP's firewall for each.
You need to create the rules in the AWS Security Group.
On Tue, May 21, 2013 at 6:04 PM, torrelay@mail.md wrote:
Greetings!
I currently have 1 bridge relay running on my AWS account.
Is it possible to add another 2 bridge relays to run as separate instances from the same AWS account?
I'm wondering if there might be issues with IP address allocation?
If all you want to do is provide a bridge on multiple IP addresses, all you need to do is add extra ORPort lines to your /etc/tor/torrc that correspond to any additional IP addresses you have available on the _same_ amazon ec2 instance.
For example: OrPort 1.3.1.5:443 OrPort 1.3.1.7:443
The bridge-authority and BridgeDB will take care of handing out the extra addresses without any extra work on your part.
For example, would I need to make any ammendment to the tor configuration file a la 'tor family' to differentiate between the different nodes running on the same amazon account?
If you want to run multiple bridges on separate amazon ec2 instances from your amazon account, please do, but don't add any extra stuff to your torrc.
From the torrc manpage:
MyFamily node,node,... ... snip ... Do not list any bridge relay as it would compromise its concealment.
The reason is that knowledge of a single bridge should not let you learn about other bridges (which is what the MyFamily entry would do).
--Aaron
p.s. You should definitely try and set up bridges that provide the obfs3 transport (the torproject deb mirror provide packages for easy use) as we have the least of these.
Take a look at: https://lists.torproject.org/pipermail/tor-relays/2013-April/002089.html https://www.torproject.org/projects/obfsproxy-debian-instructions.html.en https://www.torproject.org/projects/obfsproxy-instructions.html.en https://blog.torproject.org/blog/new-tor-cloud-images-obfs3
Any advise appreciated.
Best regards,
Johnnie
______________________________**_________________ tor-relays mailing list tor-relays@lists.torproject.**org tor-relays@lists.torproject.org https://lists.torproject.org/**cgi-bin/mailman/listinfo/tor-**relayshttps://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On Tue, May 21, 2013 at 7:01 PM, Aaron aagbsn@extc.org wrote:
p.s. You should definitely try and set up bridges that provide the obfs3 transport (the torproject deb mirror provide packages for easy use) as we have the least of these.
The Tor Cloud images are all obfs3 by default (actually, they are normal bridges, obfs2, and obfs3).
tor-relays@lists.torproject.org
-
Aaron -
Andy Isaacson -
I -
Runa A. Sandvik -
torrelay＠mail.md