Eumetcast supporting software for Linux: ecast_cfg

ecast_cfg is a gui managing Eumetcast reception for Linux kernel 2.6. Especially handy if you want to have start/stop and channel choice under manual control.

Each Eumetcast channel transmitted is tagged with a certain PID, and IP destination address. ecast_cfg uses the IP address to decide if the channel has to be routed to Tellicast or not, depending on the selection made in the gui.

The tool can be used for both USB and ethernet receivers.

  • Tested with USB device: Opera DVB-S
  • Tested with ethernet device: Ayecka

    Related tool for selection by altering recv-channels.ini:


    A screenshot: (mode "USB device")

    Channels selected; Tellicast is running.

    In ethernet mode the 'Tuner' and 'DVB Traffic' part are missing.


    ecast_cfg uses the commands and methodology described here.
    The dvb related tools (dvbnet, dvbtraffic) and femon are integrated (no system calls); other tools (szap, ifconfig, smcroute) are activated by system calls.

    A difference compared to the other mentioned tools (tqchansel, msgreceive) is that channel selection is not done by changing the recv-channels.ini file. Instead actual routing is adapted, using smcroute. The recv-channels.ini needs therefore to enable all channels.

    Start of tool

    ecast_cfg can run in 2 modes: The mode is defined using commandline option: At start ecast_cfg first reads the config-files dvb-eumetcast.cfg(USB mode) and eumetcast-channels.cfg; the last one is used to set-up the gui. Because some channel names are not very clear (e.g. "EUMETSAT Data Channel 2" for the channel carrying HRIT MSG2) a more convenient name mapping can be defined by the user, in file eumetcast_buttonnames.cfg. Each line in this file should define the original name and the desired button name, between quotes, e.g.:
    "EUMETSAT Data Channel 2" "HRIT"
    ecast_cfg will use this file for 3 purposes: A list of actions done by ecast_cfg:
    program startUSBPID filteringdvbnet-like function
    USBconnect PID to IPifconfig
    USBset-up multicast routingifconfig
    USB,ETHstart smcroute daemonsmcroute -d
    by userUSBstart receiverbutton receive
    USBshow trafficbutton Mon Traffic
    USB,ETHselect channelsbuttons under Select
    USB,ETHactivate selectionbutton Activate selection
    USB,ETHstart/stop Tellicastbutton Start under Tellicast
    program stopUSB,ETHstop Tellicastbutton Quit removing config
    USB,ETHremove all routing, filtering etc.
    USB,ETHstop receiving
    USB,ETHkeep all settings, continue receivingbutton Quit keep config

    At restart ecast_cfg will examine which channel selection was kept at stop (using ip mroute) and the state of all selection buttons will be restored.


    v2_0 Eumetcast config
    channel select
    ecast_cfg 304k Linux only
    v1_0 Eumetcast config
    channel select
    ecast_cfg_v1.tgz 320k Linux only


    In short:

    Remaining needed tools are usually already present (part of normal Linux distro)

    In more detail:

    ecast_cfg uses the gtk toolkit (gtk2.0), which is present at about each Linux installation.

    The following tools are used:
    toolname Mode description source
    szap USB Tuner config Linux-distro
    pkill, pgrep USB others Linux-distro
    ifconfig USB configure network Linux-distro
    smcroute USB,ETH Static Multicast Router Linux-distro
    pcscd USB,ETH pcsc server Linux/Eumetsat script
    etokend USB,ETH Aladdin eToken Linux/Eumetsat script
    tellicast-client USB,ETH Tellicast Eumetsat

    The following files are used:
    filename Mode description source
    eumetcast-receiver.cfg USB Tuner config. (frequency etc.) attached to tarbal
    dvb-eumetcast.cfg USB IP mc-addresses etc. Eumetsat
    eumetcast-channels.cfg USB,ETH eumetcast channels Eumetsat
    eumetcast_buttonnames.cfg USB,ETH User channel names example attached to tarbal
    All files are searched first in the start-dir., if not present then in /etc.


    Note: Tools like smcroute, used by ecast_cfg, probably need root privileges. In that case ecast_cfg needs to be started as root. NOTE: up to now nothing is saved to harddisk! Note: The tree in the most right part is for information only. See screenshot below:

    Eumetcast network between receiver and Tellicast

    (Click on image to enlarge.)