Date   

Re: Tellicast client version 2.14.4 for Linux

Hugo
 

Ernst,

Apparently a lot more effort is going in the development and maintenance of the Windows version of Tellicast than for the Linux version.
It was the first time I installed TC on Windows and the installation was going very smoothly ... Of course running TC on Windows in 'production' is not an option ....
I didn't use the tellicast installation script this time, ( i did everything manual) just to be sure nothing was going wrong.

One possibility to avoid all the different flavors of Linux is that Eumetsat roles his own Linux distribution with TC already installed. Something like this : https://devuan.org/os/partners/devuan-distros .
Ernst, I see some opportunities here for you ....:)

One of the advantages of open source is of course that Linux would have a 64 bit TC client version years ago, and that there would be a constant development on the software.
Now, TC for Linux it is just an afterthought in a Windows world.

Kind regards,

Hugo





Re: Tellicast client version 2.14.4 for Linux

Ernst Lobsiger
 

Hugo,

I compared my aksrte installation deb with the
latest v. p6 downloaded from EUMETSAT ftp site.
They are identical and the link you had to force
is actually generated though as a "link chain":

aksifdh.so-> aksifdh.so.1-> aksifdh.so.1.3-15.84

So the only problem EUMETSAT can be blamed for is
the content of /etc/udev/rules.d/20-etoken.rules:

ACTION=="add",    SUBSYSTEM=="usb_device", SYSFS{idVendor}=="0529", SYSFS{idProduct}=="0514", RUN="/etc/hotplug/usb/etoken" 
ACTION=="remove", SUBSYSTEM=="usb_device", SYSFS{idVendor}=="0529", SYSFS{idProduct}=="0514", RUN="/etc/hotplug/usb/etoken" 
ACTION=="add",    SUBSYSTEM=="usb",        SYSFS{idVendor}=="0529", SYSFS{idProduct}=="0514", RUN="/etc/hotplug/usb/etoken" 
ACTION=="remove", SUBSYSTEM=="usb",        SYSFS{idVendor}=="0529", SYSFS{idProduct}=="0514", RUN="/etc/hotplug/usb/etoken" 

Since Debian 7 I always had to change that to:

ACTION=="add",    SUBSYSTEM=="usb", ATTR{idVendor}=="0529", ATTR{idProduct}=="0514", RUN="/etc/hotplug/usb/etoken"
ACTION=="remove", SUBSYSTEM=="usb", ATTR{idVendor}=="0529", ATTR{idProduct}=="0514", RUN="/etc/hotplug/usb/etoken"

That's why I asked August 2nd: "Have you edited the
etoken rules?" (explained in attached STRETCH64.txt).

Maybe you should send a ticket to OPS and ask
them to change the rules or at least to clarify
the C9 problem in the trouble shooting guide.

Cheers,
Ernst


Re: Tellicast client version 2.14.4 for Linux

Ernst Lobsiger
 

Hugo,

Nice to hear you got it working. I just hope the Devuan people
have the strength to maintain this distro. Most distros have systemd
now which is something like "microsofting" the UNIX desktop. IMHO
this is unacceptable for a CLI based EUMETCast receiver. Why should
I want a monster that tries to do everything from time keeping, network
management to binary log files? My future TC receivers are all Devuan.

The missing link is something I told EUMETSAT many years ago.
This was then described as C11 in the trouble shooting guide.

The really bad thing: In the installation files I use C11 was fixed
by EUMETSAT. That's what I remarked in my HOWTO. It seems
the very latest version from the ftp site has this problem again :-(.

The udev rule lines have changed several times. There is a C9
entry in the trouble shooting guide that should be updated too.
I think I figured out the latest working version some times back.

Cheers,
Ernst



Re: Tellicast client version 2.14.4 for Linux

Hugo
 

Ernst,

I found the reason why it didn't work... :}
One of the reasons was indeed the entry in /etc/udev/rules.d//20-etoken like you explained in your STRETCH.TXT.
But also I had to create the following symbolic link :
ln -sf /usr/local/lib/aksifdh.so.1.3-15.84 /usr/local/lib/aksifdh.so
In my previous (working) installations I never had to do that.

There isn't anything in the logging file where you can see that the etokend service was not working.
The errors for the entries in /etc/udev/rules.d//20-etoken are displayed at startup.
This time I took notes for the future !

Well, the whole experience was very educational , but sometimes frustrating !

I now have a working Eumetcast receiving station running on Devuan ASCII (amd64) ... hopefully for a few years...


And Ernst, thanks again for the help !

Kind regards,

Hugo



Austria weather....

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

Looks like storms over Aflenz causing signal level drops. Possibly a switch to the Vienna uplink instead.

Cheers,
David
--
SatSignal Software - Quality software written to your requirements
Web: http://www.satsignal.eu
Email: david-taylor@...
Twitter: @gm8arv


Re: Tellicast client version 2.14.4 for Linux

Hugo
 

Hi Ernst,

Yes I used the p6 version freshly downloaded from the Eumetsat ftp site ....
Tomorrow I will do a new install of Devuan 2.0 and do it all over again.
It must work ...


grts,

Hugo


Re: Tellicast client version 2.14.4 for Linux

Ernst Lobsiger
 

Hugo,

Where did you get your installation files from?
Did you really use the aksrte*.deb Version p6 as
described in my HOWTO and not an older p3?

Cheers,
Ernst


Re: Tellicast client version 2.14.4 for Linux

R. Alblas
 

Just in case, maybe this info helps "someone" to find where things go wrong with Tellicast/EKU:
If you start etoken/pcscd/tellicast one by one, and observe the EKU LED, you will see at start of etoken and pcscd one LED-flash ("off-on"), and at  start of tellicast a burst of flashes.
If e.g. start of etoken doesn't give the one flash then here is the problem, and it doesn't make sense to start pcscd etc. before this is solved.

See:

http://www.alblas.demon.nl/wsat/msg_info.html#check_eku

Rob.


On 08/04/2018 04:47 PM, Ernst Lobsiger wrote:
Hugo,

I always install GNU/Linux with language American English and UTF-8. With UNI-Code you never know ...

I run the TC-Client as root.

cd /var/log
and
grep etok *.log
should at least show a couple of lines from user.log

Good Luck
Ernst


Re: Tellicast client version 2.14.4 for Linux

Ernst Lobsiger
 

Hugo,

I always install GNU/Linux with language American English and UTF-8. With UNI-Code you never know ...

I run the TC-Client as root.

cd /var/log
and
grep etok *.log
should at least show a couple of lines from user.log

Good Luck
Ernst


Re: Tellicast client version 2.14.4 for Linux

Hugo
 

Good News ...

I installed the Tellicast soft on my Windows 10 laptop, and everything worked ! So my EKU is OK.
It is certainly easier to install on Windows than on Linux...
(the linux install script for 2.14.4-4 didn't work on my system)

One possibility for my problems could be that the USB controller is broken on my receiving PC or a setting that I keep missing ....

@Ernst
The tellicast log files just indicate the 'missing key' for all the encrypted channels. I receive the exact same channels ( SAF-Europe ,...)
with or without the dongle.
I will try to find some indication of problems in the GNU/Linus log files.

grts,

Hugo


Re: Tellicast client version 2.14.4 for Linux

Hartmut Schulla
 

In the attachment a screnshot of the license panel.

Screenshot 2018-08-04 15.47.45.png

 

Von: MSG-1@groups.io [mailto:MSG-1@groups.io] Im Auftrag von Ernst Lobsiger
Gesendet: Samstag, 4. August 2018 15:47
An: MSG-1@groups.io
Betreff: Re: [MSG-1] Tellicast client version 2.14.4 for Linux

 

Hugo,

You certainly also checked all the GNU/Linux and TelliCast log files and found nothing.
Sounds too bad. Maybe a last double check for user and password in the *.ini files :-) ?

Regards,
Ernst


Re: Tellicast client version 2.14.4 for Linux

Ernst Lobsiger
 

Hugo,

You certainly also checked all the GNU/Linux and TelliCast log files and found nothing.
Sounds too bad. Maybe a last double check for user and password in the *.ini files :-) ?

Regards,
Ernst


Re: Tellicast client version 2.14.4 for Linux

Hartmut Schulla
 

It’s normal that the 4th looks like host_key_4 = ****-****-****-****

Host-Key 1 to 3 should show 4 groups of hex values.

If you’re successful connected server address looks like:

 

Server Address: 
 

10.90.43.51

Regards

Hartmut

 

Von: MSG-1@groups.io [mailto:MSG-1@groups.io] Im Auftrag von Hugo
Gesendet: Samstag, 4. August 2018 15:29
An: MSG-1@groups.io
Betreff: Re: [MSG-1] Tellicast client version 2.14.4 for Linux

 

Ernst, David,

yes the pcscd and etokend deamons are running and I changed the 20-etoken.rules file, but to no avail...

The license web page is showing me for the fourth key nothing and it should be something like this

host_key_4 = ****-****-****-**** 

I start to think that my EKU dongle is broken ...

P.S. I forgot to tell you that I also installed Devuan 2.0 ASCII (amd64) with the Eumetcast software. But no cigar ...:(

It's time to email OPS for a new EKU ....

grts,
Hugo

 

 


Re: Tellicast client version 2.14.4 for Linux

Hugo
 

Ernst, David,

yes the pcscd and etokend deamons are running and I changed the 20-etoken.rules file, but to no avail...

The license web page is showing me for the fourth key nothing and it should be something like this
host_key_4 = ****-****-****-**** 
I start to think that my EKU dongle is broken ...

P.S. I forgot to tell you that I also installed Devuan 2.0 ASCII (amd64) with the Eumetcast software. But no cigar ...:(

It's time to email OPS for a new EKU ....

grts,
Hugo
   


Re: Tellicast client version 2.14.4 for Linux

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

Ernst,

I'm afraid that I played all my cards...
First, I installed Ubuntu 18.04 (64bit) : no encrypted channels
then Debian 9.5 (64bit) : same result
then Debian 9.5 (32bit) : same result

I installed the eToken driver on Windows 10 and the info displayed the following :

Name: eToken
eToken category: Hardware
Reader name: AKS ifdh 0
Serial number: 0x40993614
Total memory capacity: 32768
eToken card free space: 25846
Hardware version: 1.2
Firmware version: 0.4
Card ID: 22 21 aa 0e 07 0b
Product name: eToken PRO
Model: Token P0514 F4.2.5.4
Card Type: Card OS
OS version: CardOS/M4.01 (C) Siemens AG 1994-2001
Mask version: N/A
Color: Blue
Supported key size: 1024
User password: Present
User password retries remaining: 0
Maximum user password retries: 0
Administrator password: Absent
CSP: eToken Base Cryptographic Provider

The 'Maximum user password retries : 0' is a bit strange for me. The install help file of the driver has 15 for this entry.
The Aladdin EKU could also simply be broken ...

Installing tellicast on windows to test the EKU is probably my next step.

grts,
Hugo
=======================================

Hugo,

Sorry to hear of your issues. Just checked my eToken on this Win10/64 system and it's basically the same, except:

Maximum user password retries: 15
Color: Red (but the case is blue?)
This is absent: "CSP: eToken Base Cryptographic Provider"

On the Licence Web page, Client Identification: the user name show unencrypted as mine, the first two entries are mixed hex, the third 0000-0000-0000-0808, and the fourth is ****_****_****_****.

Hope that helps.

Cheers,
David
--
SatSignal Software - Quality software written to your requirements
Web: http://www.satsignal.eu
Email: david-taylor@...
Twitter: @gm8arv


Re: Tellicast client version 2.14.4 for Linux

Ernst Lobsiger
 

Hugo,

I installed Devuan ASCII 2.0 amd64, wich is Debian 9 systemd free, jesterday with no problems.
I also had/have several Debian 9 i386 and amd64 receivers that worked/work fine. Christian uses
Debian 9 amd64 as well,

Once again:

Have you edited the line in file /etc/udev/rules.d/20-etoken.rules
according to my HOWTO?

Is pcscd and etokend running (pgrep pcscd, pgrep etokend) ?
If not a final insserv pcscd and reboot might help,

Your strange password zeros could mean unlimited?!

Good Luck
Ernst


Re: Tellicast client version 2.14.4 for Linux

Hugo
 

Ernst,

I'm afraid that I played all my cards...
First, I installed Ubuntu 18.04 (64bit) : no encrypted channels
then Debian 9.5 (64bit) : same result
then Debian 9.5 (32bit) : same result

I installed the eToken driver on Windows 10 and the info displayed the following :

Name: eToken
eToken category: Hardware
Reader name: AKS ifdh 0
Serial number: 0x40993614
Total memory capacity: 32768
eToken card free space: 25846
Hardware version: 1.2
Firmware version: 0.4
Card ID: 22 21 aa 0e 07 0b
Product name: eToken PRO
Model: Token P0514 F4.2.5.4
Card Type: Card OS
OS version: CardOS/M4.01 (C) Siemens AG 1994-2001
Mask version: N/A
Color: Blue
Supported key size: 1024
User password: Present
User password retries remaining: 0
Maximum user password retries: 0
Administrator password: Absent
CSP: eToken Base Cryptographic Provider

The 'Maximum user password retries : 0' is a bit strange for me. The install help file of the driver has 15 for this entry.
The Aladdin EKU could also simply be broken ...

Installing tellicast on windows to test the EKU is probably my next step.

grts,


Hugo






Re: Gibertini OP 125L

Mads Kristoffersen
 

Perfect, thanks :)

Regards
Mads


Re: Gibertini OP 125L

Ernst Lobsiger
 

Mads,

Below my Triax TD 110 elevation rod. You can turn it with a
screw driver from below. Inside the clamp is a hard PVC block
with two slightly displaced perpendicular drillings. One takes
the horizontal center bolt and the vertical drilling is threaded
for the elevation rod. Arne made a version that is easier to homebrew
with things you get in any hardware store. Instead of my PVC block
he simply took a scew nut and a window hinge. He had an article
somewhere (GEO ?) but I don't remember a link. Here are his pictures:

http://home.hccnet.nl/a.van.belle/GEO/TriaxElevationAdjustment1.jpg

http://home.hccnet.nl/a.van.belle/GEO/TriaxElevationAdjustment2.jpg

http://home.hccnet.nl/a.van.belle/GEO/TriaxElevationAdjustment3.jpg

Sorry Arne for the deep links :-) but Google knows them anyway ...


Cheers,
Ernst


Re: Gibertini OP 125L

Mads Kristoffersen
 

Hi Ernst

Can you post a image of your special elevation rod?

My system is out of business for the moment but maybe I have a chance putting it into service and I would love to have a better elevation-option on my Triax (TD-110).

Regards
Mads