Opened 13 years ago

Closed 13 years ago

#1409 closed defect (fixed)

Simulcrypt problems seca2/3 On all dutch canaldigitaal SD channels

Reported by: pic-o-matic Owned by:
Priority: blocker Component: DVBApi
Severity: high Keywords:
Cc: Sensitive: no

Description

Revision

4228

Issue Description

Simulcrypt problems seca2/3. On all dutch canaldigitaal SD channels on Astra 19.2 i get a lot of freezes. With oscam svn 3521 this problem does not occur!. I connect to a cccam server 2.011. (a real cccam client does not have this problem)

When the issue occurs

frequently

How the issue is reproducable

just watch dutch canal Digitaal channels using caid 0100. Somaone can use my server for debug!

log in attach.

Attachments (1)

oscam4228.log (9.1 KB ) - added by pic-o-matic 13 years ago.
debug log oscam 4228

Download all attachments as: .zip

Change History (6)

by pic-o-matic, 13 years ago

Attachment: oscam4228.log added

debug log oscam 4228

comment:1 by pic-o-matic, 13 years ago

Component: Please fill inDVBApi
Priority: Please fill inblocker
Severity: Please fill inhigh

I use SH4 bin on kathrein ufs 910

comment:2 by Admin, 13 years ago

Is this still an issue? Schlocke did lots of improvements to CCCam protocol recently so this should be fixed. Please report back.

comment:3 by Admin, 13 years ago

Resolution: fixed
Status: newclosed

No answer for 6 weeks, we are more than 1000 revisions later => Closed.

in reply to:  3 comment:4 by deeptho, 13 years ago

Resolution: fixed
Status: closedreopened

Replying to Admin:

No answer for 6 weeks, we are more than 1000 revisions later => Closed.

This is indeed still a problem (version 5436)

Take rtl4:
This has the following ca-info in the pmt
CA_SYSTEM_ID CA_PID
irdeto 0x0622 0x0565
nagra 0x1817 0x070b (private data: 02 00 6a)
seca2 0x0100 0x0643 (private data: 00 6a ff 00 08 00 00 00 00 02 04 2a dc)
seca3 0x0100 0x0000 (private data: 00 6a ff ff e0 00 00 00 00 00 00 2a dc)

First of all, seca3 does not work due to the 0x0000 pid. This is easily solved:
the real pid can be found by looking for nagra pids with provider 6a and then
filling in the missing pids as follows:

irdeto 0x0622 0x0565
nagra 0x1817 0x070b (private data: 02 00 6a)
seca2 0x0100 0x0643 (private data: 00 6a ff 00 08 00 00 00 00 02 04 2a dc)
seca3 0x0100 0x070b (private data: 00 6a ff ff e0 00 00 00 00 00 00 2a dc)

I proposed a patch for this part in another ticket, but can't find the ticket number.

After the patch, there seems to be still a conflict between seca2 and seca3. The symptom
is that the channel clears for a few seconds and then stops. With a proper I: line blocking
pid 0x0643 (for speed it is useful to alsoblock irdeto and nagra) all works fine.

I think oscam is somehow confused by the fact that seca2 and seca3 have the same provider id
and that it uses the seca2 pid when it gets a response from a seca3 card. I did not check this.
So it i is just a theory.

Eve

comment:5 by Admin, 13 years ago

Resolution: fixed
Status: reopenedclosed

You are referring to #1914. According to _network it was fixed in the code. If not then discuss there and don't reopen such old tickets instead.

Note: See TracTickets for help on using tickets.