[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #7763 [Tor Cloud]: Tor Cloud and elastic IPs
#7763: Tor Cloud and elastic IPs
-----------------------+----------------------------------------------------
Reporter: runa | Owner: runa
Type: defect | Status: new
Priority: normal | Milestone:
Component: Tor Cloud | Version:
Keywords: | Parent:
Points: | Actualpoints:
-----------------------+----------------------------------------------------
Comment(by AdamColligan):
Replying to [ticket:7763 runa]:
> A user (RT-#6268) wants to know if it is possible to associate an AWS
elastic IP with a Tor Cloud instance.
I think that I'm the user this is referencing. I've copied below my
original query to provide more texture, though it isn't structured well as
a feature request per se.
___
I have an old 10.04 Tor Cloud instance running with pretty much everything
outdated, and my understanding is that I need to start a new instance in
order to get all the necessary upgrades and have Obfsproxy working and all
of that.
One thing that bothered me about this is the loss of the IP address, since
my instance has been around for quite a while now and gets a fair amount
of traffic.
It occurred to me that in order to prevent an IP switch in the future, I
could generate an Elastic IP and associate it with any instance that I use
now or in the future. I had a few concerns about this, though, and I
know next to nothing about IP infrastructure.
1. If I associate the Elastic IP with my instance, does Amazon change any
setting on the instance itself that the Tor software would recognize?
I.e., would the bridge automatically pull down the Elastic IP address from
a network setting in the box and report it to the big bridges directory,
or would it still continue to report a different, instance-specific IP
that would be lost with each reboot or upon termination?
2. Assuming the answer to (1) is "no, it doesn't do it automatically" then
I understand from IRC that that the torrc would need to be edited so that
"OutboundBindAddress and "Address" are set to the Elastic IP.
(a) Would I need to add these as text in the torrc file and re-upload it
via sftp, or is there an easy way to set them through tor-arm in ssh that
maybe I'm missing?
(b) Are there any other settings that would need to be changed?
(c) Would these settings generally persist through updates and reboots,
provided it's still the same instance? When I upgrade my own PC Vidalia
client, I manually deselect torrc while going through the overwrite
prompts in Windows rather than saying "Yes to all."
(d) Are there any other potential complications that I should be aware of
(mismatch with local IP that tor might be using for something, IPv6
teething issues with manually binding addresses, etc.)?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/7763#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs