Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Hi Oscar,

For the private network, there is logical network created which is isolated from all other networks , aka network namespace for the private network. For more details refer to http://blog.scottlowe.org/2013/09/04/introducing-linux-network-namespaces/.

Now, you can do this :- 1. ip netns and copy the qrouter namespace , say qrouter-abcdef 2. then from network node, issue ip netns exec qrouter-abcdef ping 192.168.1.4

If you haven't checked, please check whether the 192.168.1.4 is actually present on instance interface (through vnc on horizon).

thanks.

Hi Oscar,

For the private network, there is logical network created which is isolated from all other networks , aka network namespace for the private network. For more details refer to http://blog.scottlowe.org/2013/09/04/introducing-linux-network-namespaces/.

Now, you can do this :- 1. :-

  1. ip netns and copy the qrouter namespace , say qrouter-abcdef 2. qrouter-abcdef

  2. then from network node, issue ip netns exec qrouter-abcdef ping 192.168.1.4

If you haven't checked, please check whether the 192.168.1.4 is actually present on instance interface (through vnc on horizon).

thanks.

Hi Oscar,

For the private network, there is logical network created which is isolated from all other networks , aka network namespace for the private network. For more details refer to http://blog.scottlowe.org/2013/09/04/introducing-linux-network-namespaces/.http://blog.scottlowe.org/2013/09/04/introducing-linux-network-namespaces/ or http://www.slideshare.net/mirantis/hk-openstack-namespaces1

Now, you can do this :-

  1. ip netns and copy the qrouter namespace , say qrouter-abcdef

  2. then from network node, issue ip netns exec qrouter-abcdef ping 192.168.1.4

If you haven't checked, please check whether the 192.168.1.4 is actually present on instance interface (through vnc on horizon).

thanks.