Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Added macvtap information.

Anchor
TOC
TOC
Include Page
KBCOMMON:KB-CSSstyle
KBCOMMON:KB-CSSstyle

...

Parameter license_key_id 

Optional parameter for HASP licenses, mandatory for VE licenses.

Insert excerpt
Initial Emulator License Configuration
Initial Emulator License Configuration
nameMutuallyExclusive
nopaneltrue

Parameter Use for HASP Licenses

There can be several license_key_id parameters in this section. They define a prioritized list of license keys. The first entry has the highest priority. If no key with this ID is available, the next key in the list will be tried. If a higher priority key becomes available, the emulator will switch to this license at the next periodic license check.

Syntax:

license_key_id "key-id-prio1"

...

Optional parameter for HASP licensing. There can be several license_id parameters in this section. They define a prioritized list of product license IDs. The first entry has the highest priority. If no key with this product license ID is available, the next product license ID in the list will be attempted. If a higher priority license becomes available, the emulator will switch to this license at the next periodic license check.

Syntax:

license_id "lic-id-prio1"

...

ParameterValues
mapping_mode

Possible values:

  • RAW: the emulated Ethernet card is mapped to a physical interface on the Charon host that is dedicated to the Charon guest system. This setting is the default value.
  • TAP: the emulated Ethernet card is mapped to a TAP device on the Charon host. If the parameter iface is not set or the specified interface does not exist, it is created by the emulator.
  • MACVTAP: links the emulated NIC to a physical NIC on the host via an automatically configured TAP interface. Different from a  bridge, it allows using the same MAC as the host NIC when used in passthrough mode. This makes it suitable for cloud environments. MACVTAP mode is planned for Charon-PAR version 3.0.9.
  • DUMMY: presents a network interface without any actual network connectivity to the guest system. All other Ethernet parameters are ignored if this parameter is set.
    It will be set automatically, if
    • iface="dummy",
    • or iface="" and mapping_mode="RAW".
iface

Specifies the name of the host interface mapped to the emulated interface.

For mapping_mode="RAW": this parameter must be set to an interface dedicated to the emulator.

For mapping_mode="TAP": the parameter can be

  • empty: the emulator will choose a name for the TAP interface and create it automatically at startup (and delete it when stopped).
  • name of non-existing TAP interface: the emulator will create the interface automatically at startup (and delete it when stopped).
  • name of an existing TAP interface: the emulator will use this interface.

For any mapping_mode: the value dummy will cause the emulator to present a dummy network interface to the guest system.

Upon emulator start, Charon-PAR will set a variable IFACE to contain the interface name. This variable can then be used in the initialization command to refer to the interface name.

macaddr

Can be set to override the default (same as host interface) MAC address of the interface.
By default, when using mapping_mode RAW, the interface is put into promiscuous mode, and the original MAC address of the interface is not overwritten.
If the legacy_mode is configured for the interface, it is not set into promiscuous mode, and the MAC address of the corresponding host NIC is changed to the configured address. The original MAC address is restored upon emulator exit.
The format of the MAC address is: XX-XX-XX-XX-XX-XX where X is a hexadecimal number.

Please note: the above behavior is new starting with version 3.0.1 build 21.500. In older versions, when the MAC address was changed, it was not reset automatically when the emulator was stopped.

initialize_command

Command(s) to initialize the host interface for use with the Charon emulator.

  • For physical interfaces (RAW): all offload parameters active on the interface should be turned off, as shown by the example in the configuration file template.
  • For TAP interfaces: the TAP interface should be activated, if needed, and added to the appropriate bridge interface (example: "ip link set $IFACE up; ip link set $IFACE master br0"); the exact configuration depends on the customer requirements.

The variable IFACE is set by the emulator and defined automatically for the execution of the initialization command.

adapter_mode

Defines the speed and duplex settings of the interface that are reported to the guest system.

Possible values: auto, 10BaseT-HD, 10BaseT-FD, 100BaseT-HD, 100BaseT-FD
Default: 100BaseT-FD

...