TNT-Sat läuft nicht auf Oscam: Configfehler?

[kalehrl]

AW: TNT-Sat läuft nicht auf Oscam: Configfehler?

I don't have an easymouse2 unfortunately.
I restarted the reader and get this strange error at the end of the card initialization:

2015/07/24 19:55:51 0F7A56F3 r   (reader) tntsat [viaccess] CA 28 initialisation failed! No boxkey or deskey!

I've never noticed this error before but the reader works after restart and sends valid CWs.

 

[kalehrl]

AW: TNT-Sat läuft nicht auf Oscam: Configfehler?

Again the reader went out!
Everything was fine and then these lines appeared:

Spoiler

2015/07/24 22:09:18 7E46DD48 r   (reader) tntsat [viaccess] ECM: Invalid ECM structure. Rejecting
2015/07/24 22:09:18 7DEAA426 c      (ecm) xxxx (0500@030B00/030B/2F84/12A:xxxxxxxxxxxx): not found (81 ms) by tntsat (F/4/4/4) - NT1 (key to use is not the curren
2015/07/24 22:10:53 2873F609 c      (ecm) xxxx (0500@030B00/1511/2010/D8:xxxxxxxxxxxx): not found (1 ms) by tntsat - FRANCE 3 (provider(030b00) or key(8) n
2015/07/24 22:11:27 3194C58A c      (ecm) xxxx (0500@030B00/1511/264F/D8:xxxxxxxxxxxx): not found (1 ms) by tntsat - F3 CHAMP ARDENNE (provider(030b00) or key(8) n
2015/07/24 22:12:02 3194C58A c      (ecm) xxxx (0500@030B00/1511/2010/D8:xxxxxxxxxxxx): not found (0 ms) by tntsat - FRANCE 3
2015/07/24 22:13:33 3194C58A c      (ecm) xxxx (0500@030B00/1517/2329/D8:xxxxxxxxxxxx): not found (1 ms) by tntsat - TF1 HD (provider(030b00) or key(8) n
2015/07/24 22:14:38 7E46DD48 r   (reader) tntsat [viaccess] ECM: Invalid ECM structure. Rejecting
2015/07/24 22:14:38 7DEAA426 c      (ecm) xxxx (0500@030B00/030B/2F84/12A:xxxxxxxxxxxx): not found (83 ms) by tntsat (F/4/4/4) - NT1 (key to use is not the curren
2015/07/24 22:19:11 3194C58A c      (ecm) xxxx (0500@030B00/1517/2458/D8:xxxxxxxxxxxx): not found (0 ms) by tntsat - W9 HD (provider(030b00) or key(8) n

 

[stefan4u]

AW: TNT-Sat läuft nicht auf Oscam: Configfehler?

So your problem starts with a failed request / corrupted ecm.
This is what makes your reader to crash!!

These corrupted ecm’s are a real plague and often produced by cheapie receivers.
You can try to filter harder…

Try longer ecm header filter:

Spoiler

ecmheaderwhitelist = 8070D5018033D2,8170D5018033D2,80712701802F90,81712 701802F90,80713F008033D2,81713F008033D2

Try to add chid filters in the reader

Spoiler

chid = 0500:001511,001514,001517,00150D,00030B

and admit only three ecm lengths

Spoiler

ecmwhitelist = 0500@030B00:142,12A,D8

If you are still in trouble (very likely, if the ecm is corrupted somewhere in the middle) ban that client if he/her don’t want to spend money for an adequate receiver...

Regards stefan

 

[kalehrl]

AW: TNT-Sat läuft nicht auf Oscam: Configfehler?

Thank you for you help.
I've been using 4-byte ecm headers but now I use your 7-byte ones.
Also, I had those 3 ecm whitelists but they obviously weren't enough to prevent reader crashes.
I didn't know viaccess had chids - I only expected irdeto to have those and I added them.
00030B chid should not be needed because it is used with C8 ecm length for which TNT Sat card gives bad CW (black picture).
I haven't had a single reader crash since last night so your advice must have worked.

 

[HarryHase]

AW: TNT-Sat läuft nicht auf Oscam: Configfehler?

Can anyone post the complete config, including the keys (yes it's allowed here) i lost the thread and diffrent possibilities of configuration!

oscam.conf

oscam.server

oscam.dvbapi

....

 

[kalehrl]

AW: TNT-Sat läuft nicht auf Oscam: Configfehler?

oscam.conf:

[global]
logfile                       = stdout
waitforcards                  = 0

[dvbapi]
enabled                       = 1
user                          = localuser
boxtype                       = dreambox

[webif]
httpport                      = 16004
httprefresh                   = 10
httpallowed                   = 127.0.0.1,192.168.0.0-192.168.255.255

oscam.server:

[reader]
label                         = tntsat
protocol                      = internal
device                        = /dev/sci0
caid                          = 0500
ecmwhitelist                  = 0500@030B00:142,D8,12A
ecmheaderwhitelist            = 8070D5018033D2,8170D5018033D2,80712701802F90,81711F701802F9,80713F008033D2,81713F008033D2
detect                        = cd
mhz                           = 450
cardmhz                       = 2700
ident                         = 0500:030B00,FFF400
chid                          = 0500:001511,001514,001517,00150D,00030B
aeskeys                       = 0500@030B00:0,0,0,0,0,0,0,0,0,0,0,0,0,2504B382B16D8C6758DB960E311E9351,0,0,0,F62C3BE300E98BBB378DFA38BB6EEEF1,0,0,6B1B024D36F60974973CB81FA5E8F01C,0,0,1DE5B042AD670BB16A3A76BDAD2F7AC0
group                         = 1

oscam.user:

[account]
user                          = localuser
group                         = 1

oscam.dvbapi:

P: 0500:030B00:2013:04A9 # TMC
P: 0500:030B00:2027:04A9 # TMC

 

[stefan4u]

AW: TNT-Sat läuft nicht auf Oscam: Configfehler?

If you wants to receive/decode NT1 sd you need chid 00030B...

Regards stefan

 

[kalehrl]

AW: TNT-Sat läuft nicht auf Oscam: Configfehler?

You are correct. I didn't check carefully enough.

 

[kalehrl]

AW: TNT-Sat läuft nicht auf Oscam: Configfehler?

Does anyone have global oscam.whitelist for TNT Sat channels?
I would like to eliminate wrong chid and length requests globally on my server.

 

[stefan4u]

AW: TNT-Sat läuft nicht auf Oscam: Configfehler?

No, I don't have a global Filterlist, exept the whitelist for keylenght only...
oscam.whitelist

Spoiler

w:0500:030B00::::142,D8,12A # TNTSAT 19.2E

But if you filter the reader the way as I told you, the majority of the wrong requests will be eliminated (except corrupted ecm's)

If you wants a more decidedly whitelist entry you could try it the following way.

Spoiler

caid/provider/srvid::chid/Key

This, for example works for ARTE HD
w:0500:030B00:2455::1517: D8 #arte HD test2 OK!

But his would mean a seperate entry for each service....


or

Spoiler

caid/provider:::chid/Key, no srvid but wildcard )

w:0500:030B00:::15118
w:0500:030B00:::1514:142
w:0500:030B00:::15178
w:0500:030B00:::030B:12A
w:0500:030B00:::150D:142

MAYBE this can be reduced to:

Spoiler

w:0500:030B00:::1511,15178
w:0500:030B00:::1514,150D:142
w:0500:030B00:::030B:12A

Actually I have not tested it, because filtering the reader itself works very good for me... But whatever you do, something like "[FONT=&amp]not found (2 ms) by tntsat - NT 1 (Unknown ECM type)" [/FONT]will still appear, if the ECM is corrupted somewhere in the middle...

Regards stefan

 

[kalehrl]

AW: TNT-Sat läuft nicht auf Oscam: Configfehler?

Thanks for your comprehensive reply.
I get a lot of bad ECMs like this:

 (0500@030B00/4003/245A/33:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx)

They are, of course, filtered by the ecmlength filter in the reader section.
I added:

w:0500:030B00:::1511:D8  # TNTSAT 19.2E
w:0500:030B00:::1514:142 # TNTSAT 19.2E
w:0500:030B00:::1517:D8  # TNTSAT 19.2E
w:0500:030B00:::150D:142 # TNTSAT 19.2E
w:0500:030B00:::030B:12A # TNTSAT 19.2E
w:

hoping I wouldn't get such requests at all but they are still present.
I guess oscam.whitelist doesn't work that way.

 

[stefan4u]

AW: TNT-Sat läuft nicht auf Oscam: Configfehler?

Sorry this was just an idea...
Actually this does really not work, as intented. I,ve seen that too after a short test.
You get indeed error messsages like "not found by..." or " [viaccess] ECM: Invalid ECM structure. Rejecting". This is BAD!!

The only way I can mange this, is filtering the reader directly, then 99.?% of the wrong requests will be rejected suddenly with " rejected group (0 ms)". Only very rarely you will get something like this:"not found (2 ms) by tntsat - NT 1 (Unknown ECM type)"

Use these entries, as proposed a few postings earlier

Spoiler

ecmwhitelist = 0500@030B00:142,12A,D8
ecmheaderwhitelist = 8070D5018033D2,8170D5018033D2,80712701802F90,81712701802F90,80713F008033D2,81713F008033D2
chid = 0500:001511,001514,001517,00150D,00030B

A global oscam.whitelist entry of
w:0500:030B00::::142,D8,12A # TNTSAT 19.2E
does not hurt, but has very limited benefit...

Regards stefan

 

[kalehrl]

AW: TNT-Sat läuft nicht auf Oscam: Configfehler?

If I just put:

w:0500:030B00:::1511:D8  # TNTSAT 19.2E
w:0500:030B00:::1514:142 # TNTSAT 19.2E
w:0500:030B00:::1517:D8  # TNTSAT 19.2E
w:0500:030B00:::150D:142 # TNTSAT 19.2E
w:0500:030B00:::030B:12A # TNTSAT 19.2E

It doesn't work with other channels with different encryption sustem but if I add

w:

at the end, then it works with other channels.
It doesn't have any effect on wrong ECM lengths being sent to tnt sat reader.
I guess I will have to live with around 12% of bad ECMs.

 

[stefan4u]

AW: TNT-Sat läuft nicht auf Oscam: Configfehler?

Are you sure?

It should eliminate wrong lenghts and wrong chid... Additional ecmheader in the reader itself does filter even more (in my case) than lenght/header filter...

Anyway do you have a rate of 12% NOK if filtered by len/header/chid in the reader directly too??

[FONT=&amp]If so, and the reader crashes repeatedly because of these bad requests, I surely would NOT share my tntsat card to that client. I disabled the tntsat services for one client too by this matter, later i improved the filters. This way (improved filtering) the problem is acceptable, most requests of that one client are rejected (pity for him, but even unfiltered the card simply cannot answer correctly), but the reader stays alive! I like to watch/record movies on arte hd(fr) for example, because of the additional original language track and Good dam these people annoying me, may stress their own Cards!![/FONT]

Regards stefan

 

[kalehrl]

AW: TNT-Sat läuft nicht auf Oscam: Configfehler?

Anyway do you have a rate of 12% NOK if filtered by len/header/chid in the reader directly too??

Yes, and they mostly come from just 2 peers.
The reader doesn't crash anymore probably because of the longer ECM headers and chids.
I just thought I could tweak the reader a little more to eliminate bad ECM requests but it can't be done obviously.