Examining the routers
Virtual routers are implemented as network namespaces on one or more nodes. In our single-node environment, the two routers that have been created so far can both be found on the same node. Using the ip netns
command as root
or a user with sudo
privileges, you can list all network namespaces on a host, like so:

The two qrouter
namespaces in the list correspond to the two routers we've created so far:

Using the ip netns exec <namespace>
command, you can specify a command to execute within the specified namespace. Useful commands such as ip
, netstat
, ps
, and iptables
provide details within the scope of the namespace they're executed in. A quick look at the MySimpleRouter
network namespace shows the virtual interface created by Neutron when we attached the router to the MySimpleSubnet
subnet earlier in this chapter:

Using the ovs-vsctl
show command, we can see the qr-2e525501-5f
interface attached to the integration bridge in a local VLAN mapped to MySimpleNetwork
:

Additional...