Attaching the router to the internal network

Using the openstack router add subnet command, attach the PROJECT_SUBNET subnet to MyLegacyRouter:

# openstack router add subnet MyLegacyRouter PROJECT_SUBNET

No output is provided if the command is successful. Using the openstack port list command, determine the internal IP of the router:

In this example, the IP address assigned to the router's internal interface is 192.168.200.1. When a port ID or IP address is not specified when attaching the router to a subnet, the IP address assigned to the router's internal interface defaults to the address set as the gateway_ip&nbsp;for the subnet.

Inside the router namespace, a new interface has been added with a prefix of qr. A qr interface is an internal interface of the router:

When using the Open vSwitch interface driver, the interface is connected directly to the integration bridge. When using the Linux bridge interface driver, as in this example, every qr interface is one end of a veth pair whose other end is connected to a bridge on the host:

For easy identification, the bridge name includes the first ten characters of the respective Neutron network ID. In addition, each end of the veth pair includes the first ten characters of the Neutron port ID associated with the interface.

The router namespace is able to communicate with other devices in the same subnet through the bridge. The&nbsp;eth2.43 interface&nbsp;in the bridge tags traffic as VLAN 43 as it exits the bridge out to the parent interface&nbsp;eth2.

Table of Contents for Attaching the router to the internal network

Create new playlist

Sign In

Sign Up

Table of Contents for
Attaching the router to the internal network