Ask Your Question
0

can't ping my cirros instance on devstack

asked 2017-04-06 03:58:59 -0600

mehdi92 gravatar image

Hello everyone,

I'm new to openstack, i m on windows and i used virtualbox to install ubuntu 16.04 LTS. Then I followed the official doc to install devstack. Everything is fine.

I created 2 networks : one private and another one public (external), i linked them by a router and then i created a cirrOS instance.

My security group has ssh and ICMP allowed, I can ping the gateway for the public network but i can't ping my instance (associated to a floating IP) and i get : host unreachable as an error ...

I spent the past week trying to solve the problem but no success ...

Could anyone help me please ?

Thank you guys,

edit retag flag offensive close merge delete

Comments

Have you tried pinging your instance from the router namespace? Or can your instance ping router private ip and public ip?

kuro gravatar imagekuro ( 2017-04-06 08:25:39 -0600 )edit

That's the problem, i could get the console on horizon to work, so basicly i could not do anything from the instance itself ... could u please tell me how to ping the instance from the router namespace as u said ? but when i used tracepath the floating ip of the instance it works Thank u

mehdi92 gravatar imagemehdi92 ( 2017-04-07 02:32:43 -0600 )edit
1

Check your router id from horizon. Then in Controller node, get the router namespace using ip netns | grep router which will have the same id as your router. Then you can try pinging your instance from router namespace using ip netns exec <router_namespace> ping <instance ip>

kuro gravatar imagekuro ( 2017-04-07 03:24:24 -0600 )edit

i m able to ping in instance from the router, but from the instance i cannot ping the external network, i think this is where the problem came from, u have an idea ? thank you

mehdi92 gravatar imagemehdi92 ( 2017-04-07 07:06:03 -0600 )edit

Can you capture in the router namespace using ip netns exec <router_namespace> tcpdump -i any icmp -nn to check if you ping from instance, whether the packet is forwarded by router or not and if there is any reply from the destination coming to the router or not

kuro gravatar imagekuro ( 2017-04-07 08:38:34 -0600 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2017-04-10 03:37:25 -0600

mehdi92 gravatar image

First of all, to have and idea about my network topology :

http://hpics.li/1b8668e (Network Topology)

and the gateway of my external network is : 192.168.122.1

When I capture in the router namespace and I ping for the instance the gateway of the external network by using :

ip netns exec <router_namespace> tcpdump -i any icmp -nn

I got :

10:05:07.805982 IP 192.168.0.10 > 192.168.122.1: ICMP echo request, id 24321,                                                                                                                                   seq 0, length 64
10:05:08.808850 IP 192.168.0.10 > 192.168.122.1: ICMP echo request, id 24321, se                                                                                                                              q 1, length 64
10:05:09.810047 IP 192.168.0.10 > 192.168.122.1: ICMP echo request, id 24321, se                                                                                                                                  q 2, length 64
10:05:10.809102 IP 192.168.122.200 > 192.168.0.10: ICMP host 192.168.122.1 unrea                                                                                                                                  chable, length 92
10:05:10.809138 IP 192.168.122.200 > 192.168.0.10: ICMP host 192.168.122.1 unrea                                                                                                                                  chable, length 92
10:05:10.809147 IP 192.168.122.200 > 192.168.0.10: ICMP host 192.168.122.1 unrea                                                                                                                                  chable, length 92
10:05:10.810718 IP 192.168.0.10 > 192.168.122.1: ICMP echo request, id 24321, se                                                                                                                                  q 3, length 64
10:05:11.811284 IP 192.168.0.10 > 192.168.122.1: ICMP echo request, id 24321, se                                                                                                                                  q 4, length 64
10:05:12.812171 IP 192.168.0.10 > 192.168.122.1: ICMP echo request, id 24321, se                                                                                                                                  q 5, length 64
10:05:13.808613 IP 192.168.122.200 > 192.168.0.10: ICMP host 192.168.122.1 unrea                                                                                                                                  chable, length 92
10:05:13.808633 IP 192.168.122.200 > 192.168.0.10: ICMP host 192.168.122.1 unrea                                                                                                                                  chable, length 92
10:05:13.808637 IP 192.168.122.200 > 192.168.0.10: ICMP host 192.168.122.1 unrea                                                                                                                                  chable, length 92
10:05:13.812479 IP 192.168.0.10 > 192.168.122.1: ICMP echo request, id 24321, se                                                                                                                                  q 6, length 64
10:05:14.814060 IP 192.168.0.10 > 192.168.122.1: ICMP echo request, id 24321, se                                                                                                                                  q 7, length 64
10:05:15.815577 IP 192.168.0.10 > 192.168.122.1: ICMP echo request, id 24321, se                                                                                                                                  q 8, length 64
10:05:16.808625 IP 192.168.122.200 > 192.168.0.10: ICMP host 192.168.122.1 unrea                                                                                                                                  chable, length 92
10:05:16.808672 IP 192.168.122.200 > 192.168.0.10: ICMP host 192.168.122.1 unrea                                                                                                                                  chable, length 92
10:05:16.808676 IP 192.168.122.200 > 192.168.0.10: ICMP host 192.168.122.1 unrea                                                                                                                                  chable, length 92
10:05:16.820334 IP 192.168.0.10 > 192.168.122.1: ICMP echo request, id 24321, se                                                                                                                                  q 9, length 64
10:05:19 ...
(more)
edit flag offensive delete link more

Comments

Can you try pinging from controller to 192.168.122.1? And also from router using ip netns exec <router_namespace> ping 192.168.122.1

kuro gravatar imagekuro ( 2017-04-10 04:40:10 -0600 )edit

Here what I got :

mehdi@mehdi:~/devstack$ sudo ip netns exec qrouter-9af6ee8a-9951-40fd-b4c6-07667 PING 192.168.122.1 (192.168.122.1) 56(84) bytes of data. From 192.168.122.209 icmp_seq=1 Destination Host Unreachable
mehdi92 gravatar imagemehdi92 ( 2017-04-10 07:18:25 -0600 )edit

But I can ping it directly, have you any idea where this proble; could come from?

mehdi92 gravatar imagemehdi92 ( 2017-04-10 07:18:58 -0600 )edit

here's the result for ip route:

10.0.2.0/24 dev enp0s3  proto kernel  scope link  src 10.0.2.15
192.168.1.224/27 dev br-ex  proto kernel  scope link  src 192.168.1.225
192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1 linkdown
mehdi92 gravatar imagemehdi92 ( 2017-04-10 07:27:14 -0600 )edit

If the ip route you provided is from controller machine, it looks like br-ex have cidr 192.168.1.224/27. So, shouldn't be external gateway connected to that ip? How are you getting floating ip from 192.168.122.0/24 cidr which is associated with virbr0. Or I am wrong with the assumption?

kuro gravatar imagekuro ( 2017-04-10 08:51:23 -0600 )edit

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

2 followers

Stats

Asked: 2017-04-06 03:57:24 -0600

Seen: 1,299 times

Last updated: Apr 10 '17