madman1133
Verified User
- Joined
- Jan 11, 2009
- Messages
- 8
Hello Everyone,
I have an interesting problem.
I'm trying to install / run DA in the Amazon EC2 cloud. As you may or may not be aware EC2 does allow what they call an elastic IP address. It's a lot like a static public IP with the exception that it is not directly bound on the server. This brings me to my problem. DA requires a public IP on the server and Amazon only provide a private IP. What sucks is that I do have a public IP allocated to the server but it's being NATed some how my Amazon's magic.
I'm running Ubuntu 8.10. Here is my network configuration.
eth0 Link encap:Ethernet HWaddr 12:31:3a:00:19:74
inet addr:10.251.30.130 Bcast:10.251.31.255 Mask:255.255.254.0
inet6 addr: fe80::1031:3aff:fe00:1974/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:17286 errors:0 dropped:0 overruns:0 frame:0
TX packets:5076 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:22275796 (22.2 MB) TX bytes:601479 (601.4 KB)
My public IP is 174.129.220.209. Keep in mind that this IP is only associated with my DA server on the cloud. So this is not some home network that is nated behind a firewall.
I think I have a legitimate need to have DA setup in this configuration. To be honest I think things are moving more towards the cloud setup and DA needs to work within the constraints provided by cloud providers.
I know there is a work around for this on the forums but I've spent the last few hours digging and I came up empty. If someone could point me in the right direction I would be grateful.
Thanks in Advance
Donny
I have an interesting problem.
I'm trying to install / run DA in the Amazon EC2 cloud. As you may or may not be aware EC2 does allow what they call an elastic IP address. It's a lot like a static public IP with the exception that it is not directly bound on the server. This brings me to my problem. DA requires a public IP on the server and Amazon only provide a private IP. What sucks is that I do have a public IP allocated to the server but it's being NATed some how my Amazon's magic.
I'm running Ubuntu 8.10. Here is my network configuration.
eth0 Link encap:Ethernet HWaddr 12:31:3a:00:19:74
inet addr:10.251.30.130 Bcast:10.251.31.255 Mask:255.255.254.0
inet6 addr: fe80::1031:3aff:fe00:1974/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:17286 errors:0 dropped:0 overruns:0 frame:0
TX packets:5076 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:22275796 (22.2 MB) TX bytes:601479 (601.4 KB)
My public IP is 174.129.220.209. Keep in mind that this IP is only associated with my DA server on the cloud. So this is not some home network that is nated behind a firewall.
I think I have a legitimate need to have DA setup in this configuration. To be honest I think things are moving more towards the cloud setup and DA needs to work within the constraints provided by cloud providers.
I know there is a work around for this on the forums but I've spent the last few hours digging and I came up empty. If someone could point me in the right direction I would be grateful.
Thanks in Advance
Donny