Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Enabling two-way NAT on instances?

I'm trying to setup a testing environment using Openstack on a Debian 7 host. My node is located on a private network, at 172.23.3.8 and hosts several different VMs, but I'll take my Webserver VM as an example.

Openstack tells me that the DHCP server assigned the Webserver VM with the IP 172.23.3.100. Similarly, the internal service assigned the private IP 10.0.0.3 to the Webserver VM.

The issue is however, this seems to be a one-way bridge! I can SSH into 172.23.3.100 and I can access the VM located at the internal IP 10.0.0.3. However, the VM itself isn't aware of the mapping. I wished to set up an Apache2 server, and no suprise, I cannot access it from outside the internal 10.x VM network.

Is this intended? Is there a way to circumvent this and allow for two-way mapping? I have been consulting the documentation but haven't found anything that seems promising.

Enabling two-way NAT network bridging on instances?

I'm trying to setup a testing environment using Openstack on a Debian 7 host. My node is located on a private network, at 172.23.3.8 and hosts several different VMs, but I'll take my Webserver VM as an example.

Openstack tells me that the DHCP server assigned the Webserver VM with the IP 172.23.3.100. Similarly, the internal service assigned the private IP 10.0.0.3 to the Webserver VM.

The issue is however, this seems to be a one-way bridge! I can SSH into 172.23.3.100 and I can access the VM located at the internal IP 10.0.0.3. However, the VM itself isn't aware of the mapping. I wished to set up an Apache2 server, and no suprise, I cannot access it from outside the internal 10.x VM network.

Is this intended? Is there a way to circumvent this and allow for two-way mapping? I have been consulting the documentation but haven't found anything that seems promising.