Anchor | ||||
---|---|---|---|---|
|
Include Page | ||||
---|---|---|---|---|
|
...
Parameter license_key_id
Optional parameter for HASP licenses, mandatory for VE licenses.
Insert excerpt Initial Emulator License Configuration Initial Emulator License Configuration name MutuallyExclusive nopanel true
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"
...
- physical host interface,
- a TAP interface connected to a virtual bridge on the host, or
- (planned for since Charon-PAR 3.0.9) a MACVTAP interface linked to a physical NIC on the host.
Notes for TAP physical interfaces:
- A TAP interface can either be created by the user or will be created automatically by the emulator if it does not already exist.
- For automatically created TAP interfaces, the user can specify a name or let the emulator select a name.
- A automatically created TAP interface is not automatically If used directly as a guest interface, offloading parameters must be turned off using the initialization command parameter in the configuration file.
- In cloud environments, the necessary interface settings are not always reflected correctly on the cloud-provided NICs. For such installation settings a MACVTAP interface can be used to provide a dedicated connection without connecting the emulator directly to the physical interface.
Notes for TAP interfaces:
- A TAP interface can either be created by the user or will be created automatically by the emulator if it does not already exist.
- For automatically created TAP interfaces, the user can specify a name or let the emulator select a name.
- A automatically created TAP interface is not automatically added to a bridge, this must be configured via the initialize_command (see the Ethernet Configuration Parameter table below).
- An automatically created TAP interface is deleted automatically upon emulator stop.If used in a cloud environment, only internal virtual bridges (no connection to the cloud LAN) are supportedautomatically created TAP interface is deleted automatically upon emulator stop.
- If used in a cloud environment, only internal virtual bridges (no connection to the cloud LAN) are supported.
Notes for MACVTAP interfaces:
- Introduces a transparent bridge interface associated with on physical NIC on the host, and provides a dedicated interface to the emulator.
- Provides an abstraction layer between physical NIC and emulator.
- Physical interface requires no changes in the offloading configuration.
- Fragmentation is performed by Linux on the MACVTAP interface. Jumbo frames on the physical interface will not cause problems.
- Uses same MAC address as the physical interface.
- Suited for associating a dedicated host Ethernet interface to the emulator in cloud environments.
Notes for network configurations on VMware:
...
Parameter | Values |
---|---|
mapping_mode | Possible values:
|
iface | Specifies the name of the host interface mapped to the emulated interface. For mapping_mode="RAW" or "MACVTAP": this parameter must be set to an interface dedicated to the emulator. For mapping_mode="TAP": the parameter can be
For any mapping_mode: the value dummy will cause the emulator to present a dummy NIC 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 if this parameter is used together with mapping_mode RAW, the interface is put into promiscuous mode, and the original MAC address of the interface is not overwritten. 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.
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 |
...
Parameter (cont'd) | Values |
---|---|
legacy_mode | New starting with version 3.0.1 build 21.500. Only applicable to mapping_mode RAW . PA64 uses a physical network adapter in promiscuous mode by default. This parameter allows to change the mode to non-promiscuouswith a manually configured MAC address. Possible values:
Default: false |
pkg_dump | Can be used to enable a packet dump to the log file. |
rx_fifo_size | Can be used to set the size of the RX FIFO buffer (in KB). Do not change unless advised to do so by Stromasys support. |
ignore_tx_start_error | Possible values: true or false |
...