Table of Contents
General description
It is strongly recommended to use only physical network adapters for CHARON-AXP networking to gain maximum performances. In situations where the host has only one network adapter, you can use Linux virtual network Interfaces ("TUN/TAP") and map individual CHARON-AXP instances to their own virtual interfaces. This can be done using the ncu utility.
It is also possible to perform the operations manually. Refer to your Operating System Network Administration guide for details.
On Red Hat Enterprise Linux 6 & 7 and CentOS 7, the following packages are needed:
bridge-utils
- optionaltunctl
- optional, need only if command 'ip tuntap' not workedethtool
- mandatoryvconfig
- optional, if VLAN is needed
Using "ncu" utility to establish CHARON virtual network
Login as root and start the ncu utility:
CHARON Network Configuration Utility, Version 1.6. Copyright (C) 2014-2019 STROMASYS SA.
|
Enter "3" to create a bridge between the host physical network adapter and the Linux virtual network interfaces (TAP) and specify the physical network interface ("eth1" in our example) and the number of virtual network interfaces to be created (2 in our example):
select action:
|
Now enter "7" to see the created virtual interfaces:
Interfaces Dedicated to State
|
In the example above we see 2 virtual network interfaces, "tap0" and "tap1", connected to the created bridge. The physical network interface "eth1" is used for the bridge to the virtual network interfaces.
The interfaces "tap0" and "tap1" are ready to be used in CHARON configurations, they do not need to be additionally dedicated to CHARON.
Enter "8" to quit the "ncu" utility.
Virtual interface creation
The creation of the desired number of virtual network interfaces (TAPs) can be performed in the following way:
|
where “tap<N>” is a name of an instance of the virtual network interface, i.e. “tap0”, “tap1” etc.
Once each virtual network interface instance is created it must be set to promiscuous mode:
|
Usage of the virtual interface in CHARON-AXP configuration
Once the “tap<N>” interfaces have been created, the load command maps those interfaces to CHARON-AXP:
|