I understand that for EUMETCast EUMETSAT recommend adding route command like:

route -p -4 ADD 224.0.0.0 mask 240.0.0.0 192.168.238.238

I'm thinking that if you have multiple network adapters, would it better to specify the network in a little more detail:

BAS: 224.223.222.n

HVS-1: 224.223.223.n

HVS-2: 224.223.224.n

with the appropriate netmask? I was also wondering what happens in Linux as I vaguely recall that a route must be set for each data stream. Is there a list of the routing which is used - something like an "smcroute print" command? If such output exists, it would be helpful to see that list!

Thanks,
David
--
SatSignal Software - Quality software for you
Web: https://www.satsignal.eu
Email: david-taylor@...
Twitter: @gm8arv

David,

the basis of the setup under GNU/Linux is the attached file. AFAIK it has not been updated by EUMETSAT after K.-P. retired. Meanwhile PID 300, 301 became obsolete. I only eliminated them in the PID_LIST_* on top which means the lines below containing PID 300, 301 are skipped in the setup. For all PIDs in use a dvb interface is setup. For many years smcroute was used to maintain static multicast routes to the final multicast interface. In the latest setup smcroute is not needed anymore: All dvb-interfaces use channel bonding to interface dvbond0. That's where all Tellicast clients attach to. You should find the multicast addresses as well on the EUMETSAT web page with EUMETCast channels and PIDs. Not sure it's up to date.

https://eumetsatspace.atlassian.net/wiki/spaces/DSEC/pages/700055570/Channels+and+Packet+Identifiers+PIDs

Regards,
Ernst

On 27/03/2023 13:01, Ernst Lobsiger via groups.io wrote:

David,
the basis of the setup under GNU/Linux is the attached file. AFAIK it has not been updated by EUMETSAT after K.-P. retired. Meanwhile PID 300, 301 became obsolete. I only eliminated them in the PID_LIST_* on top which means the lines below containing PID 300, 301 are skipped in the setup. For all PIDs in use a dvb interface is setup. For many years smcroute was used to maintain static multicast routes to the final multicast interface. In the latest setup smcroute is not needed anymore: All dvb-interfaces use channel bonding to interface dvbond0. That's where all Tellicast clients attach to. You should find the multicast addresses as well on the EUMETSAT web page with EUMETCast channels and PIDs. Not sure it's up to date.
https://eumetsatspace.atlassian.net/wiki/spaces/DSEC/pages/700055570/Channels+and+Packet+Identifiers+PIDs <https://eumetsatspace.atlassian.net/wiki/spaces/DSEC/pages/700055570/Channels+and+Packet+Identifiers+PIDs>
Regards,
Ernst

Thanks, Ernst.

That's a useful file to have. I need to look in detail and study the implications.

I'm setting up a new system and have had issues with a particular dual-port network card getting reset every two minutes, so I' restarting with a single network card and using the Ayecka SR1 for both BAS and HVS-1, which I've not actually done before.


Cheers,
David
--
SatSignal Software - Quality software for you
Web: https://www.satsignal.eu
Email: david-taylor@...
Twitter: @gm8arv