Anchor | ||||
---|---|---|---|---|
|
Include Page | ||||
---|---|---|---|---|
|
...
Parameter license_key_id
Optional parameter. 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. 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"
...
Serial port option | Description |
---|---|
type | The serial port type determines the protocol used on the serial port. Possible values are:
|
port | Each port is mapped to a TCP socket on the emulator host or to a physical line. This parameter defines the TCP port used or the name of the physical device. A TCP port number must be unique on the host system. A TCP port number is specified as Possible values for where-to-listen:
Default values:
A physical device is specified as " Example:
|
command | This parameter is optional. It can be used to specify a terminal emulation program that is started automatically when the emulated system is started. Charon-PAR provides preconfigured profiles for PuTTY (HPA-Socket HPA-Telnet HPA-Telnet-VT100) that can be used to connect to the emulated system via a serial line. |
...
- 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.
...