Cannot ping external network from VM [closed]

Hello, i got a problem with OpenStack Havana deployment using nova-network FlatDHCPmanager i was following the setup of:

http://docs.openstack.org/havana/inst...

The deal is simple, im using Centos 6.5 and the latest version of Havana i have:

2 Node NIC's

• eth0 internal (192.168.0.11, X.X.X.12)
• eth1 external (DHCP)

Controller Node

• eth0 internal (192.168.0.10)
• eth1 external (10.0.0.253)

So i have everthing well done until here, the problem comes when I launch the instances, I cannot ping their respective floating IP from any node on the "cluster", moreover, I can ssh from external network (Like my house for example), but the virtual machine cannot ping 8.8.8.8 nor ping www.google.com , I dont know why.

Tracing with tcpdump shows that packets arrive to br100 on each node (im using multi_host=True) but they cant reach to the physical eth1 of my compute nodes

Can anyone tell me where can be my problem in nova? I can post logs, conf files if ask for any

Regards Gerardo.

edit retag reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by SamYaple close date 2014-03-31 14:56:06.845420

Sort by » oldest newest most voted

Thanks for your responses, we finally managed to solve this problem.

We had to change in the compute nova.conf file this line

public_interface = eth1

for this:

public_interface = eth0

And when we create the virtual network we had to change some params:

nova network-create vmnet --fixed-range-v4=10.0.0.0/24 \
--bridge=br100 --multi-host=T


For this:

nova network-create vmnet --fixed-range-v4=10.0.0.0/24 \
--bridge=br100 --bridge-interface=eth0 --multi-host=T


By the way we have a sub-interface (eth0:0) thats where the internet comes from =)

Regards Gerardo.

more

I am also facing same issue, I am using Fuel 4.0 installer and same network setup as the one mentioned above. I could not understand the solution completely . Can you please help me with this ? Where should I change the parameters related to virtual network? I have public_interface = eth1 in nova.conf. Is this correct ?

( 2014-04-01 00:01:05 -0500 )edit

Yeah, you need to make the change on every node with nova-network in your multi-host installation my friend.

And the step of creating the Virtual Network on Installing Compute Services (Nova) must have the --brige interface set. Hope you can fix it. Regards Gerardo

( 2014-04-01 00:11:40 -0500 )edit

I am also facing similar issue.

more

I too faced same issue.

I also used the same configuration with 2 NIC:

Please refer this steps for creating routers for VM which helped me fix my issue:

cheers

more

Does this work with nova-network installation? I think this if for neutron and im using the basic install

( 2014-03-31 11:54:23 -0500 )edit

I face the same things since a few months but i really don't know if this is a bug or intended. The floating ips are routed with NAT from your Openstack node so instances shouldn't be able to know which floating ip is allocated to them.

It's like in your local network. Your PC doesn't know which ports on your router he gets to talk with the rest of the internet, does he? Just because we are using now full IPs instead of IP+Ports doesn't mean NAT-behaviour will change.

I'm just using internal IPs and told all my colleagues to do the same. But perhaps I'm wrong and someone will post a solution and I can make my colleagues happy again.

more

1

I dont understand why it happens, i wouldn't mind if I couldn't make ssh from external network, but my issue is that I cannot make even apt-get install "stuff" or a simple ping. I believe there is something wrong with those NAT rules but i don't understand them

( 2014-03-31 11:53:10 -0500 )edit

I have to say that I seem to ignored to a few facts from your first post. It's not normal that you can't ping external IPs (e.g. www.google.de ). I tought that you can't ping other instances with their respective floating ip from another instance. But you seem to have found the solution!

( 2014-04-07 05:03:56 -0500 )edit

Hello,

I got a similar issue after installing test configuration based OpenStack training guides pages for VirtualBox ( http://docs.openstack.org/training-guides/content/bk001-preface.html (http://docs.openstack.org/training-gu...) ).

After install reboot, I was unable to reach external network (8.8.8.8, http://google.com or even host machine).

I modified /etc/network/interfaces configuration file provided by training guide because two gateways were declared in this file and it was probably the origin of the issue (See following bug link in order to see my current interfaces configuration). As I'm not a network expert, I can't ensure my configuration is 100% OK.

Regards, Dan

more