Ask Your Question

Can't reach instances by floating IPs; can ping router

asked 2017-10-19 10:07:04 -0500

zerorobben gravatar image


I have an interesting problem I've not encountered before. I have recently created a new OpenStack environment that is functional in every respect but networking. I can instantiate instances and associate floating IPs, but when I attempt to ping or ssh, I receive no response from the nodes. I can ping the router from my external network.

I have configured my external network as a flat network with network address and gateway, according to my physical network. I then created a local internal network with address and gateway I created a router and added the two networks ( and as interfaces).

I can ping the router:

$ ping -q -c 3
PING ( 56(84) bytes of data.

--- ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 0.153/0.171/0.200/0.023 ms

I can also associate floating IPs with my instances. However, I cannot reach the instances themselves:

$ ping -q -c 3
PING ( 56(84) bytes of data.

--- ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2015ms
pipe 3

If I try to add instances to the external network itself, I cannot ping them, which leads me to believe there is some issue with my network configuration.

Is there some configuration file or any more information I could provide that could help with this?

I appreciate any information.


edit retag flag offensive close merge delete


First thing to check: Does the instance's security group allow ping/ssh. Next, use console to see if the instance has received its fixed IP address. Can you ping the router from the instance. Can you ping external addresses from the instance. Can you ping the fixed IP from the DHCP namespace.

Bernd Bausch gravatar imageBernd Bausch ( 2017-10-21 03:08:32 -0500 )edit

Dear Bernd, when you answer questions, could you please do it with the "Add answer" functionality instead of "Add comment"? That would make it easier to see which questions already got answered. Thanks a lot! David

rabel-b1 gravatar imagerabel-b1 ( 2017-10-27 03:57:23 -0500 )edit

I didn't consider it an answer, as I don't know exactly where the problem is.

Bernd Bausch gravatar imageBernd Bausch ( 2017-10-27 09:18:30 -0500 )edit

2 answers

Sort by » oldest newest most voted

answered 2017-12-14 02:23:48 -0500

zlcviobxcio2 gravatar image

Same Problem waiting for solve

basic info: centos 7 x64 eth0: gateway: wan eth1: gateway: wan flat ipaddresses: setup guide by Pike install docs,I choosed the provider network at neutron setup step. Then I make eth1 as provider in the conf file.And log into horizon with admin account,select Admin->Network->Networks to create network: <first page=""> Name: outoutoutNet Provider Network Type:flat Physical Network:provider √ Enable Admin State √ Shared √ External Network √ Create Subnet <second page=""> Subnet Name:uuuuco Network Address: IP Version:IPv4 Gateway IP: <third page=""> √ Enable DHCP Allocation Pools:, DNS Name Servers: Host Routes:


the add a vroute at horizon console connected to outoutoutNet. done And now I create a instance and running it,it could get a ip addr It cannot ping at all,and other like ping or other wan ip it doesn't work too.

from outside,I can ping,and now this ip belong to br vnic, from ip netns the q-dhcp and q-router couldn't ping too,from instance I cannot ping too It really bother me alot

edit flag offensive delete link more

answered 2019-03-07 09:32:47 -0500

d@kj gravatar image

I've the same problem on my lab. here my post (here) May all together we can solve.

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2017-10-19 10:07:04 -0500

Seen: 974 times

Last updated: Mar 07 '19