Ask Your Question
1

Unable to ping the tenant router gateway from external network

asked 2014-10-28 16:03:02 -0500

Glix gravatar image

updated 2014-10-30 23:05:43 -0500

I have followed the guide for installing Icehouse on Ubuntu 14.04, but I have not been able to ping the tenant router gateway. I even initialized a VI and assigned it an external IP through neutron but still cant see that either. The attached image is how I have the physical system setup.

image description

From the qrouter I can ping the gateway but that's it:

root@network:~# ip netns
qrouter-f2be9e4f-f3af-48f8-8f3f-edb38cb7e2f7
qdhcp-2aece67b-fe2c-4ad8-974b-808d41fee406
root@network:~# ip netns exec qrouter-f2be9e4f-f3af-48f8-8f3f-edb38cb7e2f7 ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
14: qr-08ba5665-87: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default 
    link/ether fa:16:3e:ec:43:21 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.1/24 brd 192.168.1.255 scope global qr-08ba5665-87
       valid_lft forever preferred_lft forever
    inet6 fe80::f816:3eff:feec:4321/64 scope link 
       valid_lft forever preferred_lft forever
15: qg-5b31b6b8-72: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default 
    link/ether fa:16:3e:39:13:f2 brd ff:ff:ff:ff:ff:ff
    inet 192.168.2.102/24 brd 192.168.2.255 scope global qg-5b31b6b8-72
       valid_lft forever preferred_lft forever
    inet 192.168.2.103/32 brd 192.168.2.103 scope global qg-5b31b6b8-72
       valid_lft forever preferred_lft forever
    inet6 fe80::f816:3eff:fe39:13f2/64 scope link 
       valid_lft forever preferred_lft forever
root@network:~# ip netns exec qrouter-f2be9e4f-f3af-48f8-8f3f-edb38cb7e2f7 ping -c 4 192.168.2.102
PING 192.168.2.102 (192.168.2.102) 56(84) bytes of data.
64 bytes from 192.168.2.102: icmp_seq=1 ttl=64 time=0.027 ms
64 bytes from 192.168.2.102: icmp_seq=2 ttl=64 time=0.040 ms
64 bytes from 192.168.2.102: icmp_seq=3 ttl=64 time=0.016 ms
64 bytes from 192.168.2.102: icmp_seq=4 ttl=64 time=0.040 ms

--- 192.168.2.102 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 0.016/0.030/0.040/0.012 ms
root@network:~# ip netns exec qrouter-f2be9e4f-f3af-48f8-8f3f-edb38cb7e2f7 ping -c 4 192.168.2.103
PING 192.168.2.103 (192.168.2.103) 56(84) bytes of data.
From 192.168.2.103 icmp_seq=1 Destination Host Unreachable
From 192.168.2.103 icmp_seq=2 Destination Host Unreachable
From 192.168.2.103 icmp_seq=3 Destination Host Unreachable
From 192.168.2.103 icmp_seq=4 Destination Host Unreachable

--- 192.168.2.103 ping statistics ---
4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 2999ms
pipe 3
edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2014-10-29 21:04:18 -0500

bdastur-s gravatar image

Can you give more details on what troubleshooting you already did.

Can you see if you can reach out from your tenant router namespace.

ip netns will give you the qrouter and qdhcp namespaces. Now you can execute any command from within that namespace: eg ip netns exec <qrouter-namespace> ping <gw ip="">

edit flag offensive delete link more

Comments

I have updated my question

Glix gravatar imageGlix ( 2014-10-30 23:06:31 -0500 )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

1 follower

Stats

Asked: 2014-10-28 16:03:02 -0500

Seen: 1,338 times

Last updated: Oct 30 '14