Skip to main content
Skip table of contents

Using Cherry eHealth Card Terminal ST-1506 in USB RNDIS Mode with IGEL OS

If you, for example, do not have a free network socket, you can operate your Cherry eHealth Card Terminal ST-1506 via an endpoint in USB RNDIS (Remote Network Driver Interface Specification) mode. In this case, IGEL OS endpoint acts as a NAT router. The card terminal will use the network interface of your IGEL OS device.

For more information on ST-1506, see:

Requirements

  • IGEL OS 11.08.100 or higher

  • Cherry ST-1506 must have a static IP configuration  

Configuration on Your Cherry ST-1506

  1. Connect your card terminal to the IGEL OS device.

  2. In the Menu > Admin Menu, enter your admin PIN.

  3. Go to Connection > USB Ethernet.

  4. Activate RNDIS.

  5. Disable DHCP.

  6. Configure a static IP address

  7. As Gateway, specify the Host IP address which you configure on your IGEL OS device with the registry key devices.cherry.terminal%.rndis.host_ipaddress (Default: 192.168.42.1). See the instructions below.

  8. Save the settings.

Configuration on Your IGEL OS Device

Per each card terminal, one instance of the template devices.cherry.terminal%  must be created and configured. By default, none is configured and so the feature is essentially disabled. To add and configure an instance, proceed as follows:

  1. In the IGEL Setup or the configuration dialog in the UMS, go to System > Registry > devices > cherry > terminal% and click Add Instance.


    For the added instance, configure the following:

  2. For distinguishing purposes if multiple ST-1506 devices are connected, configure the registry key devices.cherry.terminal%.rndis.device_id. It may be left empty if only one card terminal shall be supported.
    Here, you specify:

    • a MAC address of the card terminal (To find it out, you can use, for example, the command ifconfig in the local terminal or view it directly on the ST-1506 in the admin menu)
      OR

    • the value of the udev property ID_NET_NAME_PATH (To find it out, you can use, for example, the command udevadm info --export-db| less)

  3. Configure the Device IP address:

    ParameterDevice IP address
    Registrydevices.cherry.terminal%.rndis.device_ipaddress
    Typestring
    Value192.168.42.42 (Default)
    Note

    Here, you specify a static IP you have configured on your ST-1506 via the admin menu.

    • You can leave the default value unchanged if you use it also on your ST-1506.
    • If you have multiple ST-1506 devices connected, you must configure a different IP for each card terminal.
  4. Configure the Host IP address

    ParameterHost IP address
    Registrydevices.cherry.terminal%.rndis.host_ipaddress
    Typestring
    Value192.168.42.1 (Default)
    NoteThis is the IP address which you must specify as Gateway on your ST-1506 via the admin menu.

  5. If required, configure the following registry keys:

    ParameterDevice TCP port
    Registrydevices.cherry.terminal%.rndis.device_tcpport
    Typestring
    Value4742 (Default)
    Note

    This port on the host will be passed through to the same port on the device. 

    • If you have multiple ST-1506 devices connected, you must configure a different port for each card terminal.
    ParameterPassed through device UDP port
    Registrydevices.cherry.terminal%.rndis.device_udpport
    Typestring
    Value4742 (Default)
    Note

    This port on the host will be passed through to the same port on the device.

    • If you have multiple ST-1506 devices connected, you must configure a different port for each card terminal.
    ParameterHost SSL port
    Registrydevices.cherry.terminal%.rndis.host_sslport
    Typestring
    Valueempty (Default)
    Note

    This port on the host will be forwarded to the device's port 443. Configure this registry key if you are using a web browser for the remote management of your ST-1506 devices.

    • If you have multiple ST-1506 devices connected, you must configure a different port for each added instance.


JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.