Ask Your Question
0

Enabling two-way network bridging on instances?

asked 2013-08-28 18:50:31 -0600

filpano gravatar image

updated 2013-08-28 19:17:36 -0600

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.

edit retag flag offensive close merge delete

Comments

Why I don't see the complete message?

gadLinux gravatar imagegadLinux ( 2014-01-23 12:20:54 -0600 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2013-10-10 11:28:33 -0600

McDice gravatar image

You are simply doing NAT'ing from the outside world to your VM. The 'floating ip' your VM has is: 172.23.3.100. It sounds like you have ssh allowed in what ever security group you have deployed but not http.

Would you verify which security group your VM is deployed to and if that security group is allowing port 80 inbound?

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2013-08-28 18:50:31 -0600

Seen: 95 times

Last updated: Oct 10 '13