The TSReader needs to have an additional table in the stream. You need to add Service Description Table SDT to the output stream. No matter if there is a connection to the data in the EIT or not, just add SDT.
Copy the .cts file below in the
Now you will see something like this
No. ringelspiel is only generating the output stream. The Linux OS decides where the stream will be sent or. correctly said routed. The behavior of this is defined in the routing table. You can check the current routing table with
and you will receive something like this (this depends on your network configuration):
Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
route add -net 126.96.36.199 netmask 240.0.0.0 eth1
all multicast traffic will be sent to interface eth1. This is shown in the updated routing table:
Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 188.8.131.52 * 240.0.0.0 U 0 0 0 eth1
The changes to the routing table will be active only until restart of the system. To make them permanent you have to
write them to /etc/network/interfaces e.g.
up ip route add 184.108.40.206/4 dev eth1
Yes. There are many ways to handle the time to live (TTL) or hop limit value.
One of them is to configure IPTABLES. Just run this from command-line
iptables -t mangle -A OUTPUT -d 220.127.116.11 -j TTL --ttl-set 128
The changes to iptables will be active only until restart of the system. For a permanent solution take a look at the iptables-persistent.deb package.
Fill your event data in the Simple schedule spreadsheet formatted XLS file and specify the SimpleXLS as parser in your scheme file.
Yes. There is a special option Announcement where text information of present and/or following events can be overwritten.
This option is available only in the commercial version of cherryEPG.
The reason for such a large EIT is the full-mesh building feature. This means that each TS contains event information for all other TS. This can be partially disabled by entering service numbers in the exclusion field (these services are then not included in the creation process).
The full-mesh building feature can be also disabled per EIT. Just add the NOMESH keyword to the option list in your Excel scheme file. Take a look at the sample scheme.
There is a workaround for this. Basically you have to define multiple different multicasts with different TSID but overwrite the TSID at the final stage of building the chunk.