veth Mode

You can also create special veth virtual adapters inside your Containers and make the Containers operate in the veth mode. The following figure represents an example of the network structure where all Containers ( Container#1 and Container#2 ) are operating in the veth mode:

In the veth mode, a separate veth virtual adapter is created for each Container on the server. You are allowed to create several veth adapters for a Container. Any veth virtual adapter consists of two interfaces:

• An Ethernet interface inside the Container. This interface represents a counterpart of a physical network adapter installed on a standalone server. As any other physical adapter, it has a MAC address (e.g., 00-0A-CC-32-F1-FF and 00-0A-CC-32-F1-BB ), can be assigned one or more IP addresses (e.g., 192.168.200.101 and 192.168.200.102 ) and included in different network environments, etc. Refer to the Configuring veth Adapter Parameters section for detailed information on configuring Ethernet interfaces inside Containers.
• An Ethernet interface on the server. This interface is responsible for the adapter operation in the server context and mostly used to maintain the interaction and communication between the server and the Ethernet interface inside the Container. Each Ethernet interface on the server should be assigned a MAC address (e.g., AA-00-0B-CC-11-BB and AA-00-0B-CC-11-CC ). Detailed information on how to manage Ethernet interfaces on the server is provided in the Configuring veth Adapter Parameters section .

Both interfaces are closely linked to each other, which means that an IP packet entering one interface will always come out from the other one.