Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Not able to ping or SSH to the instances from the router name space. But instance can ping the router.

Hello,

I have created a 3 node icehouse setup with GRE. The issue now I am facing is the instance is not reachable through ping or ssh from the router or dhcp name spaces. But the instance can ping the router and also the other instances in the same subnet. Please see the details below.

root@network:~# neutron net-list +--------------------------------------+------+-------------------------------------------------------+ | id | name | subnets | +--------------------------------------+------+-------------------------------------------------------+ | f94dc5db-49f0-4383-86c2-1c1cce2a22bc | demo | 867be7d4-7a4e-4f4b-8081-f69cc029bd40 192.168.200.0/24 | +--------------------------------------+------+-------------------------------------------------------+ root@network:~# neutron router-list +--------------------------------------+------+-----------------------+ | id | name | external_gateway_info | +--------------------------------------+------+-----------------------+ | 9b494f49-a408-4cf4-b198-003344a776a2 | demo | null | +--------------------------------------+------+-----------------------+ root@network:~# neutron router-port-list demo +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ | id | name | mac_address | fixed_ips | +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ | dc32a946-81d2-4df8-918e-c8181e06cc6a | | fa:16:3e:8a:71:63 | {"subnet_id": "867be7d4-7a4e-4f4b-8081-f69cc029bd40", "ip_address": "192.168.200.1"} | +--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+

root@network:~# ip netns list qdhcp-f94dc5db-49f0-4383-86c2-1c1cce2a22bc qrouter-9b494f49-a408-4cf4-b198-003344a776a2 root@network:~# ip netns exec qrouter-9b494f49-a408-4cf4-b198-003344a776a2 ping 192.168.200.1 PING 192.168.200.1 (192.168.200.1) 56(84) bytes of data. 64 bytes from 192.168.200.1: icmp_seq=1 ttl=64 time=0.125 ms

root@network:~# ip netns exec qrouter-9b494f49-a408-4cf4-b198-003344a776a2 ping 192.168.200.3 PING 192.168.200.3 (192.168.200.3) 56(84) bytes of data. 64 bytes from 192.168.200.3: icmp_seq=1 ttl=64 time=0.829 ms

root@network:~# ip netns exec qrouter-9b494f49-a408-4cf4-b198-003344a776a2 ping 192.168.200.2 PING 192.168.200.2 (192.168.200.2) 56(84) bytes of data. 2 packets transmitted, 0 received, 100% packet loss, time 1001ms

root@network:~# ip netns exec qrouter-9b494f49-a408-4cf4-b198-003344a776a2 ping 192.168.200.4 PING 192.168.200.4 (192.168.200.4) 56(84) bytes of data. 1 packets transmitted, 0 received, 100% packet loss, time 0ms

Thanks R

Not able to ping or SSH to the instances from the router name space. But instance can ping the router.

Hello,

I have created a 3 node icehouse setup with GRE. The issue now I am facing is the instance is not reachable through ping or ssh from the router or dhcp name spaces. But the instance can ping the router and also the other instances in the same subnet. Please see the details below.

root@network:~# neutron net-list
+--------------------------------------+------+-------------------------------------------------------+
| id                                   | name | subnets                                               |
+--------------------------------------+------+-------------------------------------------------------+
| f94dc5db-49f0-4383-86c2-1c1cce2a22bc | demo | 867be7d4-7a4e-4f4b-8081-f69cc029bd40 192.168.200.0/24 |
+--------------------------------------+------+-------------------------------------------------------+
root@network:~# neutron router-list
+--------------------------------------+------+-----------------------+
| id                                   | name | external_gateway_info |
+--------------------------------------+------+-----------------------+
| 9b494f49-a408-4cf4-b198-003344a776a2 | demo | null                  |
+--------------------------------------+------+-----------------------+
root@network:~# neutron router-port-list demo
+--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+
| id                                   | name | mac_address       | fixed_ips                                                                            |
+--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+
| dc32a946-81d2-4df8-918e-c8181e06cc6a |      | fa:16:3e:8a:71:63 | {"subnet_id": "867be7d4-7a4e-4f4b-8081-f69cc029bd40", "ip_address": "192.168.200.1"} |
+--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+

+--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+ root@network:~# ip netns list qdhcp-f94dc5db-49f0-4383-86c2-1c1cce2a22bc qrouter-9b494f49-a408-4cf4-b198-003344a776a2 root@network:~# ip netns exec qrouter-9b494f49-a408-4cf4-b198-003344a776a2 ping 192.168.200.1 PING 192.168.200.1 (192.168.200.1) 56(84) bytes of data. 64 bytes from 192.168.200.1: icmp_seq=1 ttl=64 time=0.125 ms

ms root@network:~# ip netns exec qrouter-9b494f49-a408-4cf4-b198-003344a776a2 ping 192.168.200.3 PING 192.168.200.3 (192.168.200.3) 56(84) bytes of data. 64 bytes from 192.168.200.3: icmp_seq=1 ttl=64 time=0.829 ms

ms root@network:~# ip netns exec qrouter-9b494f49-a408-4cf4-b198-003344a776a2 ping 192.168.200.2 PING 192.168.200.2 (192.168.200.2) 56(84) bytes of data. 2 packets transmitted, 0 received, 100% packet loss, time 1001ms

1001ms root@network:~# ip netns exec qrouter-9b494f49-a408-4cf4-b198-003344a776a2 ping 192.168.200.4 PING 192.168.200.4 (192.168.200.4) 56(84) bytes of data. 1 packets transmitted, 0 received, 100% packet loss, time 0ms

0ms

Thanks R