Date   

Re: experiences and lessons learned with a fresh Eumetcast install for WIndows and Linux

David Jean du Preez
 

Hi Ernst

I have done both those. In the log file the license check succeeds . 


Kind regards,
Jean du Preez


On Fri, 18 Sep 2020 at 12:16, Ernst Lobsiger via groups.io <ernst.lobsiger=belponline.ch@groups.io> wrote:
Jean

Have you set your "user_name" and "user_key" in cast-client.ini  (needs a restart of the client)?
Have you choosen your channels in cast-client-channels.ini  (can be done in a running system)?

Regards
Ernst


Re: experiences and lessons learned with a fresh Eumetcast install for WIndows and Linux

Ernst Lobsiger
 

Jean

Have you set your "user_name" and "user_key" in cast-client.ini  (needs a restart of the client)?
Have you choosen your channels in cast-client-channels.ini  (can be done in a running system)?

Regards
Ernst


Re: experiences and lessons learned with a fresh Eumetcast install for WIndows and Linux

David Jean du Preez
 

  Hi all

I thought this would be a suitable thread to post my problem with setting up a Eumetcast system. I basically started a new system besides using an existing dish which was aligned correctly. 

I am based in South Africa so I am using the Eumetcast Africa service, using a Norva satellite receiver on Windows 10. I installed the EKU, tellisat and configured the receiver. The EKU and receiver are working fine and I am able to connect to the  announcement channel (TSL-AFR-1) but none of the additional data channels appear even though the license is active.

I would appreciate any advice.

Kind regards,
Jean du Preez


On Fri, 18 Sep 2020 at 00:05, Andreas Mueller <juamueller@...> wrote:
On Thu, Sep 17, 2020 at 12:59 PM, Ernst Lobsiger wrote:
If your Windows setup allows for MODCOD selection
try to set 8PSK 2/3 only (you should see a remarkable improvement).
Ernst - can 100% confirm this - by setting the MODCOD in Win10's BDADataEx to '8PSK,3/5' i see 0 missed packets / missing keys - so for Basic Reception it's really great. Guess (as said) will try to get a 5925 and use your patched driver for my Linux environment.

Andreas


Re: experiences and lessons learned with a fresh Eumetcast install for WIndows and Linux

Andreas Mueller
 

On Thu, Sep 17, 2020 at 12:59 PM, Ernst Lobsiger wrote:
If your Windows setup allows for MODCOD selection
try to set 8PSK 2/3 only (you should see a remarkable improvement).
Ernst - can 100% confirm this - by setting the MODCOD in Win10's BDADataEx to '8PSK,3/5' i see 0 missed packets / missing keys - so for Basic Reception it's really great. Guess (as said) will try to get a 5925 and use your patched driver for my Linux environment.

Andreas


Re: experiences and lessons learned with a fresh Eumetcast install for WIndows and Linux

David J Taylor GM8ARV 🏴󠁧󠁢󠁳󠁣󠁴󠁿 🇪🇺
 

Hello David,
[]
1. tc-cast-client is buffering the logs. In result, upon start we saw
only like 5 first lines of expected logs and then nothing any more.
So when you are tailing the log ('tail -f recv_bas.log'), you would
think something is hanging (the last line was "Child connecting to
watchdog on port ..."). What was actually going on is that everything
ran smoothly and only when the logging buffers flushed the contents
to the disk (when some data is received, which can take a loong time
on BAS), we could see that everything is OK.
2. the second point of confusion was monitoring the tellicast web
interface. It relatively quickly connects to the announcements
channel, but then no data channel is active. What we did not know was
that transmissions on this channel happen only once per hour
approximately in the time block X:00 to X:15. And only when the
client is actually decoding the data it reports a connection to a
data channel. In result, for 45 minutes in every hour it seems that
the client is not connected, while actually everything is OK. Only in
retrospect we realised that of course this makes sense because our
Ayecka SR1 is sending UDP packets only when it receives something, so
there's no concept of a session and thus tellicast cannot report
"connected".
[]
Thanks again for all the help we received. This thread was very
informative and helpful.

Best,
Peter.
===================================

Peter,

Just a couple of points.

1. You can turn off the log buffering, I believe, but I've never done so:

[locations]
log_file=>>\EUMETCast\logs\recv.log

I recall (but it's not documented, so I'm probably wrong) that ">>" implied buffering. Perhaps it simply means "append". The ">>" may apply to something else in an earlier TelliCast, so please check. Maybe that wouldn't help in your case anyway.

2. Almost all BAS data should be sent every 15 minutes, with the possible exception of some meteorological data and some FSD. You must be looking for relatively obscure data!

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


Re: experiences and lessons learned with a fresh Eumetcast install for WIndows and Linux

Peter Novak
 

Hello David,

Perhaps prove the system and its components first on Windows - much, much
easier!
Well, that's not really an option for us. This is a headless server in a
rack we have there.

My own experience with Linux is that everything is version dependent -
sometime critically so. So if EUMETSAT recommend a particular distribution,
and a certain version of that distribution, it's better to use what is
recommended rather than deviate in any way.
Indeed, we now understand why that is the case too :-). Anyway, we
finally managed to set it up even on the not well supported Debian 10.
The trick was indeed the 10.7.77 SAC driver (we'll still test Andreas'
advice about libgtk). From then on, we managed to get the thing running.

Perhaps you could post the last few lines of the TelliCast log file?
It turned out the whole setup worked, but there were two points which
caused confusion on our side:
1. tc-cast-client is buffering the logs. In result, upon start we saw
only like 5 first lines of expected logs and then nothing any more.
So when you are tailing the log ('tail -f recv_bas.log'), you would
think something is hanging (the last line was "Child connecting to
watchdog on port ..."). What was actually going on is that everything
ran smoothly and only when the logging buffers flushed the contents
to the disk (when some data is received, which can take a loong time
on BAS), we could see that everything is OK.
2. the second point of confusion was monitoring the tellicast web
interface. It relatively quickly connects to the announcements
channel, but then no data channel is active. What we did not know was
that transmissions on this channel happen only once per hour
approximately in the time block X:00 to X:15. And only when the
client is actually decoding the data it reports a connection to a
data channel. In result, for 45 minutes in every hour it seems that
the client is not connected, while actually everything is OK. Only in
retrospect we realised that of course this makes sense because our
Ayecka SR1 is sending UDP packets only when it receives something, so
there's no concept of a session and thus tellicast cannot report
"connected".

So now we have a setup basic service. Given that the process is backed
up by EUMETSAT and seems to be well supported on Windows out of the box
we did not expect the amount of confusion we would run into while
setting it up on Linux. But indeed, supporting this on different
versions of Linux is a bit bigger problem than on Windows where at least
there are not that many flavours and versions of binary environments in
which the software is running.

Thanks again for all the help we received. This thread was very
informative and helpful.

Best,

Peter.

--
Meandair B.V. | aviation navigation solutions
Olof Palmestraat 14 | 2616 LR Delft | The Netherlands
Tel +31 (0)638 167 279 | http://www.meandair.com/
Participant in ESA BIC Noordwijk, The Netherlands


Re: experiences and lessons learned with a fresh Eumetcast install for WIndows and Linux

David J Taylor GM8ARV 🏴󠁧󠁢󠁳󠁣󠁴󠁿 🇪🇺
 

From: Ernst Lobsiger via groups.io
[]
@David
Agreed, Windows must be far easier for setting up a TelliCast receiver.
K.-P. is doing his best to make GNU/Linux TC receivers still possible.
But as you said, different distributions make this "mission impossible".
On the other hand automatic updates from Microsoft must be a nightmare.
[]
================================

I'm unsure about Linux updates. On the one hand the lack of automatic updates concerns me, on the other many of the updates I've seen have major problems due to lack of backwards compatibility. Certain programs which you might expect to be stable (e.g. gpsd) on closer examination are just in permanent beta. "Oh, we don't support that now". "Oh, that changed on 3.20 (but 3.17 in the latest in the distribution)". "Oh, that won't work unless you recompile from source". "Oh, you need to [attempt to] uninstall the version from the distribution" - except that it doesn't completely uninstall. You'll gather I've spent weeks trying to get this to work, I'd rather not go there again!

Some packages, such as NTP, work nicely and are even cross-platform!

It's straight-forward to turn off Windows Updates if you don't want them, and you can delay them if you wish. They're on the second Tuesday of the month, so you know when to expect them. Usually the monthly "security" updates are without problems, the six monthly "feature" updates may have minor issues, but there are so many beta [Windows Insider] users that any issues are either fixed before release, or very well documented. The only significant one recently was that microphone access was disabled by default, and those who hadn't been keeping in touch found that some sound programs couldn't find a sound source. Easily fixed with a single click change.

In practice, Windows-10 updates are usually not a significant issue.

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


Re: Removal of Sentinel-3 OLCI Level-1 Full Resolution NRT data from EUMETCast Satellite service

Daniele Guardigli
 

Or they're slowly moving towards a web service?


Il giorno gio 17 set 2020 alle ore 13:26 James Brown <satellite@...> ha scritto:

> On 17 Sep 2020, at 11:39, David J Taylor GM8ARV 🏴󠁧󠁢󠁳󠁣󠁴󠁿 🇪🇺 via groups.io <david-taylor=blueyonder.co.uk@groups.io> wrote:
>
> EUMETSAT announcement:
>
> Sentinel-3 OLCI Level-1 Full Resolution (FR) Near Real Time (NRT) data will be removed from EUMETCast Satellite in July 2021.  The planned date for the removal of OLCI Level 1 FR NRT data from our EUMETCast Satellite service is 29 July 2021.
>
> Alternative services to access these data are available:
>
> See:
>
> https://www.eumetsat.int/website/home/News/DAT_5184373.html
>
> Cheers,
> David
> --
> SatSignal Software - Quality software for you
> Web: https://www.satsignal.eu
> Email: david-taylor@...
> Twitter: @gm8arv

I’m wondering which of the new services they are making space for?

Cheers.
James.







--
Daniele Guardigli


Re: experiences and lessons learned with a fresh Eumetcast install for WIndows and Linux

David J Taylor GM8ARV 🏴󠁧󠁢󠁳󠁣󠁴󠁿 🇪🇺
 

From: Andreas Mueller
[]
... or continue with Win10 (which I don't like much since i'm more with Linux like some others here)

Andreas
===============================

Andreas,

I don't particularly "like" Apple or iOS but I use it for my iPad because they get the job done.

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


Re: Removal of Sentinel-3 OLCI Level-1 Full Resolution NRT data from EUMETCast Satellite service

David J Taylor GM8ARV 🏴󠁧󠁢󠁳󠁣󠁴󠁿 🇪🇺
 

I’m wondering which of the new services they are making space for?

Cheers.
James.
===============================================

Perhaps one of these? MTG looks earlier.

MTG satellites, imagers and sounders - 2022-2042

https://www.eumetsat.int/website/home/Satellites/FutureSatellites/MeteosatThirdGeneration/index.html



MetOp-SG imagers/sounders and microwave imaging - 2023-2038

https://www.eumetsat.int/website/home/Satellites/FutureSatellites/EUMETSATPolarSystemSecondGeneration/index.html

(Linux date rollover - 2038 - could be fun!).

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


Re: experiences and lessons learned with a fresh Eumetcast install for WIndows and Linux

Andreas Mueller
 

On Thu, Sep 17, 2020 at 12:59 PM, Ernst Lobsiger wrote:
@ Andreas
I tried to patch the stv0910x driver (without HW documentation!) for MODCOD selection along the lines I did it for stv090x. Unfortunately no success ..
Ernst - yes it was my 'silent' hope to get a positive message on that - so guess i've just 2 options left - improve my SNR and/or watch out for a 5925 and use your patched driver ... or continue with Win10 (which I don't like much since i'm more with Linux like some others here)

Andreas


Re: experiences and lessons learned with a fresh Eumetcast install for WIndows and Linux

Andreas Mueller
 

@Peter,

i was also initally facing the tc-cast-client segfaults - by digging more into the SafenetAuthenticationClient-core-9.0.43-0_amd64.deb Package i found a SACSrv daemon to be installed which then showed status 'error' when executing 'sudo service SACSrv status' -> Starting SACSrv daemon: SACSrv/usr/bin/SACSrv: error while loading shared libraries: libgtk-x11-2.0.so.0: cannot open shared object file: No such file or directory.
After installing the missing component with 'sudo apt-get install libgtk2.0.0' it started right away with no issues. I'm using EumetCast's initial file from their FTP server - so no further patching was done. My tc-cast-client never hung nor restarted after fixing that.

Andreas


Re: Removal of Sentinel-3 OLCI Level-1 Full Resolution NRT data from EUMETCast Satellite service

James Brown
 

On 17 Sep 2020, at 11:39, David J Taylor GM8ARV 🏴󠁧󠁢󠁳󠁣󠁴󠁿 🇪🇺 via groups.io <david-taylor=blueyonder.co.uk@groups.io> wrote:

EUMETSAT announcement:

Sentinel-3 OLCI Level-1 Full Resolution (FR) Near Real Time (NRT) data will be removed from EUMETCast Satellite in July 2021. The planned date for the removal of OLCI Level 1 FR NRT data from our EUMETCast Satellite service is 29 July 2021.

Alternative services to access these data are available:

See:

https://www.eumetsat.int/website/home/News/DAT_5184373.html

Cheers,
David
--
SatSignal Software - Quality software for you
Web: https://www.satsignal.eu
Email: david-taylor@...
Twitter: @gm8arv
I’m wondering which of the new services they are making space for?

Cheers.
James.


Re: experiences and lessons learned with a fresh Eumetcast install for WIndows and Linux

Ernst Lobsiger
 

Andreas

Link Margins (LM) are something like:

16APSK 2/3 : LM = SNR - 9.3
  8PSK 2/3 : LM = SNR - 5.9

EUMETSAT recommends LM > = 4dB for good EUMETCast reception.
With SNR = 9.1 dB you have a negative LM for HVS-1. Unless you
have a real MODCOD filter (that sets MODCODs on the demod chip)
you cannot receive HVS-1 nor BASIC as this is disturbed by HVS-1
packets as well. If your Windows setup allows for MODCOD selection
try to set 8PSK 2/3 only (you should see a remarkable improvement).

Under GNU/Linux (apart from routers) you have limited possibilities:

1) Have a dedicated 1.25m dish with very accurate pointing to 10° East.
   Depending on your antenna position you can expect SNR up to 15dB.
2) Use a TBS5925 USB box or TBS6925 PCIe card with my patched driver
   for BASIC only. Both HW solutions deprecated, not produced anymore,
   use a first generation VCM capable chip for one transponder only.
3) Use a Technisat SkyStar 2 eXpress HD if you are lucky to find one on
   e-Bay. I recently tested this card again and Christian was able to
   get one for 20Euros that works in his 55Euro Ancalagon for BASIC only.
   With TBS drivers this makes a perfect GNU/Linux BASIC only receiver.

In the long run you cannot go with USB boxes as you need one box
per transponder the way you need one SR1 per EUMETCast transponder.
With a good SNR you can use a TBS6903 for T1+T2 with a single cable.
You can use a TBS6908 (equals 2 x TBS6903) for up to 4 transponders.
You should soon be able to use a "cheap" TBS6909X V2? for 4 EUMETCast
transponders (don't buy this card yet, latest HW changes are under way!).


Best regards
Ernst


@David
Agreed, Windows must be far easier for setting up a TelliCast receiver.
K.-P. is doing his best to make GNU/Linux TC receivers still possible.
But as you said, different distributions make this "mission impossible".
On the other hand automatic updates from Microsoft must be a nightmare.

@Peter
I use Devuan that is still systemd free and have good results. Some
scripts distributed by EUMETSAT are buggy (including the SACSrv SysV
script!) that can make installation a little bit harder. Some may also
be dependant on binutils installed (not mentionned). But once you have
a running GNU/Linux TC receiver it will work for years without updates.
You can use old surplus HW and even make DVB-Routers with PCIe cards.
I use TBS PCIe cards and have my own adapted multi transponder scripts.
I could/should publish all my latest findings, but I am 68 and time flies.


On Thu, Sep 17, 2020 at 03:09 AM, Andreas Mueller wrote:
Now for my environment the only hope would be to get a patched 5927 driver similar to the 5925 version - unfortunately this goes beyond my skills ...
@ Andreas
I tried to patch the stv0910x driver (without HW documentation!) for MODCOD selection along the lines I did it for stv090x. Unfortunately no success ..


Removal of Sentinel-3 OLCI Level-1 Full Resolution NRT data from EUMETCast Satellite service

David J Taylor GM8ARV 🏴󠁧󠁢󠁳󠁣󠁴󠁿 🇪🇺
 

EUMETSAT announcement:

Sentinel-3 OLCI Level-1 Full Resolution (FR) Near Real Time (NRT) data will be removed from EUMETCast Satellite in July 2021. The planned date for the removal of OLCI Level 1 FR NRT data from our EUMETCast Satellite service is 29 July 2021.

Alternative services to access these data are available:

See:

https://www.eumetsat.int/website/home/News/DAT_5184373.html

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


Re: experiences and lessons learned with a fresh Eumetcast install for WIndows and Linux

Andreas Mueller
 

Markus,

thanks for replying on that - also read your comments and was hoping there's a solution other than using a 5925 (for which a modified driver is available as per Ernst's last comments). What surprised me: on Windows there's no such issue when not filtering for certain MODCODs whereas for Linux this seems to be the case.

Now for my environment the only hope would be to get a patched 5927 driver similar to the 5925 version - unfortunately this goes beyond my skills ...

Andreas


Re: experiences and lessons learned with a fresh Eumetcast install for WIndows and Linux

David J Taylor GM8ARV 🏴󠁧󠁢󠁳󠁣󠁴󠁿 🇪🇺
 

Hello,
[]
However, upon shutdown of such a hanged tc-cast-client, the logs reveal
that for a moment the launch initialises dongle, HTTP server, etc. and
then terminates. So this seems like some timing issue or so.

If anybody has advice on this, we would appreciate comments.

Best,
Peter.
==============================

Peter,

Perhaps prove the system and its components first on Windows - much, much easier!

My own experience with Linux is that everything is version dependent - sometime critically so. So if EUMETSAT recommend a particular distribution, and a certain version of that distribution, it's better to use what is recommended rather than deviate in any way.

Perhaps you could post the last few lines of the TelliCast log file?

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


Re: experiences and lessons learned with a fresh Eumetcast install for WIndows and Linux

Peter Novak
 

Hello,
continuation of this thread comes in quite timely for what we are doing.
We also are at the moment collecting "experiences" with a fresh install
of EUMETCast reception station with Ayecka SR1. Just yesterday we tried
to install Tellicast + Safenet Auth Client on Debian 10 Buster. Only
much later into the install we realised that Debian 10 is not yet well
supported, but we tried our luck. We have some mixed "feelings" about
that. Maybe this post could be useful to somebody and/or somebody will
be able to identify/explain the issues we had to work around.

1. after the installation according to EUMETSAT instructions Tellicast
did not work out of the box. The EKU dongle was recognised as
"Aladdin Knowledge Systems Token JC", but Tellicast was constantly
crashing with logs like these:
[Sep15 13:09] tc-cast-client[1046]: segfault at 968 ip 00007f6f3a73f8bb sp 00007ffce06ee290 error 4 in libpthread-2.28.so[7f6f3a73f000+f000]
[ +0.000003] Code: 00 00 0f 05 89 82 d0 02 00 00 48 8d 82 10 03 00 00 64 48 89 04 25 10 05 00 00 64 c6 04 25 12 06 00 00 01 48 8b 2d 35 57 01 00 <48> 8b 85 68 09 00 00 64 48 89 04 25 20 06 00 00 48 8d ba e0 02 00
2. we found Ernst's write-up at https://groups.io/g/MSG-1/topic/experiences_and_lessons/71144718?p=Created,,,20,1,0,0&jump=1
This was very useful for understanding of how shaky the whole
installation process can be on various Linux distros. We applied most
of the relevant advice in that post, but did not get rid of those
segfaults.
3. we diagnosed that Tellicast cannot connect to the EKU as
`tc-cast-client -k` was unable to list the host_key_4 as "Aladdin
EToken PRO" correctly. This led to suspicion that maybe the dongle
drivers are the culprit.
4. we also quickly realised that the SAC software is some 3rd party
piece operating the dongle. Some googling around revealed that
actually EUMETSAT publishes an old version of the driver (9.0.43).
Since we are on a relatively new Linux distro, we figured that 9.0.43
might be incompatible with our system and simply fails silently.
5. at this point, we decided to just install another version of that
driver to see what happens. If we'd be lucky, Tellicast won't mind
and on the other hand, the new driver might be happy with Debian 10.
We found version 10.7.77 published by GlobalSign at
https://support.globalsign.com/ssl/ssl-certificates-installation/safenet-drivers#Linux%20Debian.
This is probably not safe and feels fishy, but we hoped to get a
debugging data point out of that. So we gave it a try.
6. long story short, the whole thing worked. Suddenly Tellicast stopped
crashing and started to decode Announcement Channel packets. After
some fiddling, we even managed to start receiving Basic Service.
7. this is not yet a full success, because we observe that most of the
time (say 5 out of 7) Tellicast hangs upon start as follows:
MSG:2020-09-15 12:12:45.353:Program started =============
MSG:2020-09-15 12:12:45.353:Watchdog starting... [3520]
MSG:2020-09-15 12:12:45.353:Watchdog started [3520].
MSG:2020-09-15 12:12:45.405:Starting new child...
MSG:2020-09-15 12:12:45.405:Started new child [3523].
VRB:2020-09-15 12:12:45.606:Child connecting to watchdog on port 46857 ...

However, upon shutdown of such a hanged tc-cast-client, the logs reveal
that for a moment the launch initialises dongle, HTTP server, etc. and
then terminates. So this seems like some timing issue or so.

If anybody has advice on this, we would appreciate comments.

Best,

Peter.

On Wed, Sep 16, 2020 at 01:24:25PM -0700, Andreas Mueller wrote:

Ernst,

thanks for taking care ...

yes i've picked both 64bit versions:
ftp.eumetsat.int/pub/OPS/out/user/EUMETCast_Support/EUMETCast_Licence_cd/Linux/EKU_software/SafenetAuthenticationClient-core-9.0.43-0_amd64.deb
ftp.eumetsat.int/pub/OPS/out/user/EUMETCast_Support/EUMETCast_Licence_cd/Linux/Tellicast/tellicast-client-2.14.6-1_amd64.deb

For the TBS driver build i followed https://github.com/tbsdtv/linux_media/wiki

Andreas




--
Meandair B.V. | aviation navigation solutions
Olof Palmestraat 14 | 2616 LR Delft | The Netherlands
Tel +31 (0)638 167 279 | http://www.meandair.com/
Participant in ESA BIC Noordwijk, The Netherlands


Re: experiences and lessons learned with a fresh Eumetcast install for WIndows and Linux

Peter Novak
 

Hello,
this thread comes in quite timely for what we are doing. We also are at
the moment collecting "experiences" with a fresh install of EUMETCast
reception station with Ayecka SR1. Just yesterday we tried to install
Tellicast + Safenet Auth Client on Debian 10 Buster. Only much later
into the install we realised that Debian 10 is not yet well supported,
but we tried our luck. We have some mixed "feelings" about that. Maybe
this post could be useful to somebody and/or somebody will be able to
identify/explain the issues we had to work around.

1. after the installation according to EUMETSAT instructions Tellicast
did not work out of the box. The EKU dongle was recognised as
"Aladdin Knowledge Systems Token JC", but Tellicast was constantly
crashing with logs like these:
[Sep15 13:09] tc-cast-client[1046]: segfault at 968 ip 00007f6f3a73f8bb sp 00007ffce06ee290 error 4 in libpthread-2.28.so[7f6f3a73f000+f000]
[ +0.000003] Code: 00 00 0f 05 89 82 d0 02 00 00 48 8d 82 10 03 00 00 64 48 89 04 25 10 05 00 00 64 c6 04 25 12 06 00 00 01 48 8b 2d 35 57 01 00 <48> 8b 85 68 09 00 00 64 48 89 04 25 20 06 00 00 48 8d ba e0 02 00
2. we found Ernst's write-up at https://groups.io/g/MSG-1/topic/experiences_and_lessons/71144718?p=Created,,,20,1,0,0&jump=1
This was very useful for understanding of how shaky the whole
installation process can be on various Linux distros. We applied most
of the relevant advice in that post, but did not get rid of those
segfaults.
3. we diagnosed that Tellicast cannot connect to the EKU as
`tc-cast-client -k` was unable to list the host_key_4 as "Aladdin
EToken PRO" correctly. This led to suspicion that maybe the dongle
drivers are the culprit.
4. we also quickly realised that the SAC software is some 3rd party
piece operating the dongle. Some googling around revealed that
actually EUMETSAT publishes an old version of the driver (9.0.43).
Since we are on a relatively new Linux distro, we figured that 9.0.43
might be incompatible with our system and simply fails silently.
5. at this point, we decided to just install another version of that
driver to see what happens. If we'd be lucky, Tellicast won't mind
and on the other hand, the new driver might be happy with Debian 10.
We found version 10.7.77 published by GlobalSign at
https://support.globalsign.com/ssl/ssl-certificates-installation/safenet-drivers#Linux%20Debian.
This is probably not safe and feels fishy, but we hoped to get a
debugging data point out of that. So we gave it a try.
6. long story short, the whole thing worked. Suddenly Tellicast stopped
crashing and started to decode Announcement Channel packets. After
some fiddling, we even managed to start receiving Basic Service.
7. this is not yet a full success, because we observe that most of the
time (say 5 out of 7) Tellicast hangs upon start as follows:
MSG:2020-09-15 12:12:45.353:Program started =============
MSG:2020-09-15 12:12:45.353:Watchdog starting... [3520]
MSG:2020-09-15 12:12:45.353:Watchdog started [3520].
MSG:2020-09-15 12:12:45.405:Starting new child...
MSG:2020-09-15 12:12:45.405:Started new child [3523].
VRB:2020-09-15 12:12:45.606:Child connecting to watchdog on port 46857 ...

However, upon shutdown of such a hanged tc-cast-client, the logs reveal
that for a moment the launch initialises dongle, HTTP server, etc. and
then terminates. So this seems like some timing issue or so.

If anybody has advice on this, we would appreciate comments.

Best,

Peter.

On Wed, Sep 16, 2020 at 01:24:25PM -0700, Andreas Mueller wrote:

Ernst,

thanks for taking care ...

yes i've picked both 64bit versions:
ftp.eumetsat.int/pub/OPS/out/user/EUMETCast_Support/EUMETCast_Licence_cd/Linux/EKU_software/SafenetAuthenticationClient-core-9.0.43-0_amd64.deb
ftp.eumetsat.int/pub/OPS/out/user/EUMETCast_Support/EUMETCast_Licence_cd/Linux/Tellicast/tellicast-client-2.14.6-1_amd64.deb

For the TBS driver build i followed https://github.com/tbsdtv/linux_media/wiki

Andreas




--
Meandair B.V. | aviation navigation solutions
Olof Palmestraat 14 | 2616 LR Delft | The Netherlands
Tel +31 (0)638 167 279 | http://www.meandair.com/
Participant in ESA BIC Noordwijk, The Netherlands


Re: experiences and lessons learned with a fresh Eumetcast install for WIndows and Linux

Markus Kempf
 

Andreas,

I have a very similar setup (Debian 10, backport kernel 5.5, TBS 5925, 100cm dish (78cm before)). Fiddling with a lot of kernel, network and cpu state parameters did not solve the missing key/packets problem. In fact, I set most things to be energy efficient now, because this system runs 24/7 and electricity is very expensive. The system is also loaded with three RTL-SDR receivers for ADSB and radio sonde reception and another DVB receiver for Sat-TV plus TVheadend and works as a NAS for my home network. Despite all these tasks, the load is around 50% and I don't loose packets. Why? The simple reason was already given by Ernst. You need either a bigger dish or move 10E to the center of your dish or a Linux driver that can filter for the right MODCOD for BAS only (or another DVB receiver with different HW/FW). When I achieved SNRs above 10.5, the problem went away for BAS+HVS. For BAS only I had no problems with the patched driver provided by Ernst and SNRs above ~8.5.

Markus

Am 16/09/2020 um 23:19 schrieb Andreas Mueller:

Ernst,

you just asked the 2nd Question while i hit reply ... so:

yes in general everything works fine - i'm receiving data, the Web Interface works, the EKU works including the test with 'tc-cast-client -k' - its just the many missing keys / packets which seems not to be ok.

Andreas