...
If running Charon-PAR in a cloud environment please consider that every cloud environment has specific networking characteristics that could conflict with interface configurations made by the user of the Charon-PAR host system. Please refer to the documentation provided by the cloud provider and the network-specific sections in the Getting Started guides Guide of your product to understand the networking behavior of your cloud instance before you change any interface settings (failing to do so may end with your cloud instance being permanently unreachable).
With respect to the supported Charon-PAR emulated Ethernet configurations (RAW or TAP), please bear in mind the following when deploying Charon in a cloud environment:
- If dedicating a host NIC to the emulator, the emulated system and the guest system must use the same MAC address and IP address on the interface that were assigned to the interface by the cloud provider.
- If using a TAP interface, the bridge must be an internal bridge (not connected to the cloud LAN via a host NIC). The bridge must use a private address range different from the cloud LAN. The emulator can then communicate with the outside world via NAT, or with other other private networks via a routing configuration.
Red Hat and CentOS Version 7.x
...
Example of a minimal ifcfg-<interface> file in /etc/sysconfig/network-scripts/:
|
Example of a minimal bridge configuration via ifcfg-<interface> files in /etc/sysconfig/network-scripts/:
| Bridge definition | Physical NIC | TAP interface |
|---|---|---|
|
|
|
Please refer to your host system’s man-pages for additional information about the NetworkManager.
There are other settings required to disable certain off-load functions on interfaces dedicated to a Charon-PAR guest system. These settings are configured in the emulator configuration file and described further down in this document.
| Div | ||
|---|---|---|
| ||
Red Hat and CentOS Version 8.x
...
The network-scripts package can be installed optionally to maintain the same network management methods as used in Linux version 7. However, there is no guarantee how long the package will still be available.
...
| class | pagebreak |
|---|
Example for graphical user interface
...
The following image shows a sample configuration that disables the IPv4 configuration for an interface that is to be dedicated to the emulator using the GNOME network settings.
| Div | ||
|---|---|---|
| ||
Also, make sure to include the option Make available to other users in the Details tab:
You can use the following command to disable IPv6 for an interface (enp0s8 in the example):
...
To make this setting permanent, add it to /etc/sysctl.conf.
| Div | ||
|---|---|---|
| ||
Example for non-graphical interface
...
On a non-graphical interface, you can use the nmcli command-line utility to create a network connection as shown in the following example:
# nmcli conn add type ethernet autoconnect yes \con-name <physical-int-name> \ifname <pysical-int-name> ip4 0.0.0.0
Or you can use the nmtui text-based utility (separate RPM package). It provides a text-based configuration menu.
Please note: after changes via nmcli or nmtui you must restart the NetworkManager (systemctl restart NetworkManager.service).
...