Project

General

Profile

Feature #2056

Tvheadend: Add support for CI+ Cams

Added by Raymond Paulsen over 5 years ago. Updated 24 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Descrambling
Target version:
-
Start date:
2017-01-03
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)

Description

It would have been nice to see tvheadend with support for CI+ cams,
Vdr and mythtv has this kind of support.

at some time in the future this support will be needed.

Forum thread for discussion:
https://tvheadend.org/boards/5/topics/11529


Subtasks

Feature #4160: CI+ cam status?Rejected

Actions

History

#1

Updated by Hanspeter Müller over 5 years ago

Raymond Paulsen wrote:

It would have been nice to see tvheadend with support for CI+ cams,
Vdr and mythtv has this kind of support.

Errrrr, no, they don't, they have support for CI. There is no opensource implementation of any CI+, sadly, and it's unlikey that this is gonna ever happen officially (the whole purpose of the "+" are restrictions, which cannot be enforced if "those smelly bearded opensource hippies" could access the tv-programs) :(

If you meant "simple CI-Hardware-CAMs", there are multiple threads and bugs about this, the summary (how i understood it): Would be nice, but not gonna happen anytime soon, there's noone with the know-how and time in the core-team to implement it. Depending on how much you (and others) want this, maybe a Kickstarter-Style bounty would be the way to go...

#2

Updated by Raymond Paulsen over 5 years ago

Hanspeter Müller wrote:

Raymond Paulsen wrote:

It would have been nice to see tvheadend with support for CI+ cams,
Vdr and mythtv has this kind of support.

Errrrr, no, they don't, they have support for CI. There is no opensource implementation of any CI+, sadly, and it's unlikey that this is gonna ever happen officially (the whole purpose of the "+" are restrictions, which cannot be enforced if "those smelly bearded opensource hippies" could access the tv-programs) :(

If you meant "simple CI-Hardware-CAMs", there are multiple threads and bugs about this, the summary (how i understood it): Would be nice, but not gonna happen anytime soon, there's noone with the know-how and time in the core-team to implement it. Depending on how much you (and others) want this, maybe a Kickstarter-Style bounty would be the way to go...

As i described the support for CI is already in most other compareable software, if you knew what the Common interface is you probably know that CI+ is not supported by the listed programs i gave as a reference hence it would be incorect to say CI+ but CI support for tvheadend.

CI hardware cams is supported and working in other opensource solutions, why mention bugs? lol

what is wrong with opensource? by the way do you have a beard maybe?

why is this list called a feature list? have you thought about that? its to list features you want, do you see a time schedule for developers here? so why even mention that the core team has other things to use the time on?

the licensing for this software open up for anybody to contribute, where did you got the idea that this was something only core memembers could do?

#3

Updated by Markus Bonet over 5 years ago

I am using successfully using tvheadend with an OScam server.
The only issue I have seen in the past was EMM support crashing my cards, so tvheadend is not set to update them.

It might look a bit complex first but works fine for me.

#4

Updated by Raymond Paulsen over 5 years ago

Markus Bonet wrote:

I am using successfully using tvheadend with an OScam server.
The only issue I have seen in the past was EMM support crashing my cards, so tvheadend is not set to update them.

It might look a bit complex first but works fine for me.

Hi

Yes softcams works good, but the problem is its questionable due to TOS violations from the supplier and in some countrys its actualy illegal to use.

Dont get me wrong, OSCam, csp, mcs and CCcam is good software but its not something everybody want to use.

#5

Updated by Sam Stenvall over 5 years ago

Like Hanspeter said you'll likely to never see CI+ support in any open source software. You should perhaps update the topic and original post to talk about standard CI only since that is what's technically possible to implement and what is already implemented in rivaling software such as vdr. The fact is that many DVB tuners for Linux have missing driver support for their CAM devices since they are mostly seen as optional (often the hardware itself is optional too). That's probably one of the reasons why no one has ever bothered implementing CI support in tvheadend in the first place (coupled with the fact that Oscam works for the majority of cards).

#6

Updated by Hanspeter Müller over 5 years ago

Raymond Paulsen wrote:

what is wrong with opensource?

errr, have i said something against opensource?

by the way do you have a beard maybe?

Yes, i have ;). No offence intended, the bearded hippie reference was how we (opensource community) are usually perceived by big corporations, they dont want us accessing their "high value content", they wish to controll the entire chain.

so why even mention that the core team has other things to use the time on?

That's my interpretation of the various threads in the forum and bugtrackers, not a fact, as i wrote...

the licensing for this software open up for anybody to contribute, where did you got the idea that this was something only core memembers could do?

Again, no offence intended, my point was, CI+ is not going to happen (there simply are no hardware CI+ for PCs, they have to be certified and dont get the digital certificates to communicate with the CAMs without it), and CI is not something that's really easy to implement, currently i don't think there are too many people who really understand the code and could do it. Any, one could ask, is it really worth the effort, when more and more providers switch to CI+

/hp

#7

Updated by saen acro over 5 years ago

technicality CI is nothing more then device in PCMCIA slot
decrypting is on device so it is not interesting how work
real implementation is how to put channel pid to this device
and get decrypted one

http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-PROG.html
http://en.wikipedia.org/wiki/List_of_device_bandwidths#Portable

after that maby any PCMCIA card-reader on usb can be used

#8

Updated by saen acro over 5 years ago

technicality CI is nothing more then device in PCMCIA slot
decrypting is on device so it is not interesting how work
real implementation is how to put channel pid to this device
and get decrypted one

http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-PROG.html
http://en.wikipedia.org/wiki/List_of_device_bandwidths#Portable

after that maby any PCMCIA card-reader on usb can be used
and NDS will work

#9

Updated by Hanspeter Müller over 5 years ago

saen acro wrote:

technicality CI is nothing more then device in PCMCIA slot

technically thats true, but to my knowledge the is no implementation of a driver for CAMs, because officially, a CI is always connected to a DVB-Chip (even in linux-based boxes like dreambox), and not to a normal PCMCIA/PCI Controller, i guess simply because there never was any need for it (if you had a legal CAM, you used it in a real CI, and with a softcam you dont need the CI at all).

It would probably be pretty challenging to implement a CI driver (i don't think all documents are public) for a PCI-Based PCMCIA Slot, let alone CI+ (which uses all sorts of certificates, signatures, encryption, even Diffie-Hellman for the key-exchange), not even talking about the technical and legal issues of extracting a CI+ certificate from some certified device. I guess if someone can do it, it's the guys who develop oscam. Let's hope one of them get's pissed off enough by his provider to attempt this :D

after that maby any PCMCIA card-reader on usb can be used

If you're talking about something like this http://www.amazon.de/Terratec-Cinergy-Usb-externes-CI-Modul/dp/B000WL98O6 i don't think that would work, because this isn't really a PCMCIA Interface that transparently allows you to access the PCMCIA-Card, it's a usb-connected CI with a CI Controller. But something like http://www.amazon.de/M-Cab-PCMCIA-PCI-Add-On-Card/dp/B000W22UFE could work.

/hp

#10

Updated by Hanspeter Müller over 4 years ago

Hanspeter Müller wrote:

If you meant "simple CI-Hardware-CAMs", there are multiple threads and bugs about this, the summary (how i understood it): Would be nice, but not gonna happen anytime soon, there's noone with the know-how and time in the core-team to implement it.

Well, i'll be damned :D

https://github.com/tvheadend/tvheadend/commit/f3582868d9df6a195c74ee59843bea5f796bedaf

Now, CI+ is at least a possibility :-D

#11

Updated by B C over 4 years ago

CI yes, but CI+ ????

#12

Updated by Jaroslav Kysela over 4 years ago

CAM code using libdvben50221 is in v3.9-2706-gabb1409 . Closing. Create a new issue when you find a bug.

#13

Updated by Bengt Madeberg over 4 years ago

This is really nice news. Any special settings somewhere ? I did a quick test but bad result. I have not used my CAM for a while so will check with dvblast later.

2015-04-16 23:17:44.890 service: Boxer/570MHz/TV3 HD GÖTEBORG: Status changed to [Hardware input] 

2015-04-16 23:17:44.890 service: Boxer/570MHz/TV3 HD GÖTEBORG: Status changed to [Hardware input] [Input on service] 

2015-04-16 23:17:44.890 service: Boxer/570MHz/TV3 HD GÖTEBORG: Status changed to [Hardware input] [Input on service] [No access] 

2015-04-16 23:17:44.890 service: Boxer/570MHz/TV3 HD GÖTEBORG: Status changed to [Hardware input] [Input on service] [No available descrambler] [No access] 

2015-04-16 23:17:44.890 service: Boxer/570MHz/TV3 HD GÖTEBORG: Status changed to [Hardware input] [Input on service] [Demuxed packets] [No available descrambler] [No access] 

2015-04-16 23:17:44.932 service: Boxer/570MHz/TV3 HD GÖTEBORG: Status changed to [Hardware input] [Input on service] [Demuxed packets] [Reassembled packets] [No available descrambler] [No access] 

2015-04-16 23:17:45.017 pmt: sid 0D66 (3430)

2015-04-16 23:17:45.017 pmt:   pcr_pid 0D6F

2015-04-16 23:17:45.017 pmt:   pid 0D6F estype 27

2015-04-16 23:17:45.017 pmt:   caid 0500 (Viaccess) provider 00040D00 pid 00BE

2015-04-16 23:17:45.017 pmt:   caid 0500 (Viaccess) provider 00020500 pid 003F

2015-04-16 23:17:45.017 pmt:   caid 0500 (Viaccess) provider 00023200 pid 0040

2015-04-16 23:17:45.017 pmt:   type H264 position 0

2015-04-16 23:17:45.017 pmt:   pid 0D6E estype 17

2015-04-16 23:17:45.017 pmt:   caid 0500 (Viaccess) provider 00040D00 pid 00BE

2015-04-16 23:17:45.017 pmt:   caid 0500 (Viaccess) provider 00020500 pid 003F

2015-04-16 23:17:45.017 pmt:   caid 0500 (Viaccess) provider 00023200 pid 0040

2015-04-16 23:17:45.017 pmt:   type AAC position 0

2015-04-16 23:17:45.017 pmt:   language swe

2015-04-16 23:17:45.018 pmt:   pid 0BBE estype 6

2015-04-16 23:17:45.018 pmt:   type TELETEXT position 0

2015-04-16 23:17:45.018 pat: tsid 0006 (6)

2015-04-16 23:17:45.018 pat:   sid 0582 (1410) on pid 0582 (1410)

2015-04-16 23:17:45.018 pat:   sid 096A (2410) on pid 096A (2410)

2015-04-16 23:17:45.018 pat:   sid 0D66 (3430) on pid 0D66 (3430)

2015-04-16 23:17:45.018 pat:   sid 0D7A (3450) on pid 0D7A (3450)

2015-04-16 23:17:45.018 pat:   sid 1310 (4880) on pid 1310 (4880)

2015-04-16 23:17:45.018 pat:   sid 19D2 (6610) on pid 19D2 (6610)

2015-04-16 23:17:45.018 pat:   sid AF81 (44929) on pid 168C (5772)

2015-04-16 23:17:45.019 cat:   caid 0500 (1280) pid 0031 (49)

2015-04-16 23:17:45.019 cat:   caid 0500 (1280) pid 0037 (55)

2015-04-16 23:17:45.019 pmt: completed pid 3430 table 00000002 / 000000ff

2015-04-16 23:17:45.060 pat: completed pid 0 table 00000000 / 00000000

2015-04-16 23:17:45.060 cat: completed pid 1 table 00000001 / 000000ff

2015-04-16 23:17:45.381 nit: network 3193 (12691) [Teracom_Mux_6]

2015-04-16 23:17:45.381 nit:   onid 22F1 (8945) tsid 0006 (6) mux  (discovery)

2015-04-16 23:17:45.381 nit:   onid 22F1 (8945) tsid 0006 (6) mux 570MHz in Boxer

2015-04-16 23:17:45.381 nit:     service 0582 (1410) type 19 (25)

2015-04-16 23:17:45.381 nit:     service 096A (2410) type 19 (25)

2015-04-16 23:17:45.381 nit:     service 0D66 (3430) type 19 (25)

2015-04-16 23:17:45.381 nit:     service 19D2 (6610) type 19 (25)

2015-04-16 23:17:45.381 nit:     service 0D7A (3450) type 19 (25)

2015-04-16 23:17:45.381 nit:     sid 1410 lcn 61

2015-04-16 23:17:45.381 nit:     sid 2410 lcn 62

2015-04-16 23:17:45.381 nit:     sid 3430 lcn 63

2015-04-16 23:17:45.381 nit:     sid 6610 lcn 64

2015-04-16 23:17:45.381 nit:     sid 3450 lcn 65

2015-04-16 23:17:45.381 nit:     sid 4730 lcn 0

2015-04-16 23:17:45.381 nit:     sid 4880 lcn 0

2015-04-16 23:17:45.877 sdt: onid 22F1 (8945) tsid 0006 (6)

2015-04-16 23:17:45.877 sdt: mux 570MHz in Boxer

2015-04-16 23:17:45.877 sdt:   sid 0582 (1410) running 4 free_ca 0

2015-04-16 23:17:45.877 sdt:   sid 096A (2410) running 4 free_ca 0

2015-04-16 23:17:45.877 sdt:   sid 0D66 (3430) running 4 free_ca 1

2015-04-16 23:17:45.877 sdt:   sid 0D7A (3450) running 4 free_ca 1

2015-04-16 23:17:45.877 sdt:   sid 1310 (4880) running 4 free_ca 0

2015-04-16 23:17:45.877 sdt:   sid 19D2 (6610) running 4 free_ca 1

2015-04-16 23:17:46.000 mpegts: 570MHz in Boxer - close PID 0D66 (3430) [16/0x1590970]

2015-04-16 23:17:46.000 mpegts: 570MHz in Boxer - close PID 0D66 (3430) [8/0x1552eb0]

2015-04-16 23:17:46.000 mpegts: 570MHz in Boxer - close PID 0D6F (3439) [8/0x1552eb0]

2015-04-16 23:17:46.000 mpegts: 570MHz in Boxer - close PID 0D6E (3438) [8/0x1552eb0]

2015-04-16 23:17:46.000 mpegts: 570MHz in Boxer - close PID 0BBE (3006) [8/0x1552eb0]

2015-04-16 23:17:46.000 mpegts: 570MHz in Boxer - stopping mux

2015-04-16 23:17:46.000 linuxdvb: TurboSight TBS 5881 DVBT/T2 frontend : DVB-T #0 - stopping 570MHz in Boxer

2015-04-16 23:17:46.001 linuxdvb: TurboSight TBS 5881 DVBT/T2 frontend : DVB-T #0 - stopped dvr thread

2015-04-16 23:17:46.001 mpegts: 570MHz in Boxer - close PID 0000 (0) [20/0x1593610]

2015-04-16 23:17:46.001 mpegts: 570MHz in Boxer - close PID 0001 (1) [16/0x1594a80]

2015-04-16 23:17:46.001 mpegts: 570MHz in Boxer - close PID 0010 (16) [16/0x1595ef0]

2015-04-16 23:17:46.002 mpegts: 570MHz in Boxer - close PID 0011 (17) [16/0x15a02a0]

2015-04-16 23:17:46.002 mpegts: 570MHz in Boxer - close PID 0011 (17) [20/0x159ee30]

2015-04-16 23:17:46.002 mpegts: 570MHz in Boxer - close PID 0012 (18) [20/0x158f500]

2015-04-16 23:17:46.002 mpegts: 570MHz in Boxer - close PID 0039 (57) [16/0x15e1930]

2015-04-16 23:17:46.002 mpegts: 570MHz in Boxer - close PID 0BBA (3002) [16/0x15e2da0]

2015-04-16 23:17:46.002 mpegts: 570MHz in Boxer - close PID 0BBB (3003) [16/0x158e090]

2015-04-16 23:17:46.002 epggrab: grab done for 570MHz in Boxer (stolen)

2015-04-16 23:17:46.002 service: TV3 HD GÖTEBORG si 0x148dcc0 TurboSight TBS 5881 DVBT/T2 frontend : DVB-T #0 weight 0 prio 0 error 401

2015-04-16 23:17:48.000 service: TV3 HD GÖTEBORG si 0x148dcc0 TurboSight TBS 5881 DVBT/T2 frontend : DVB-T #0 weight 0 prio 0 error 401

2015-04-16 23:17:50.000 service: TV3 HD GÖTEBORG si 0x148dcc0 TurboSight TBS 5881 DVBT/T2 frontend : DVB-T #0 weight 0 prio 0 error 401

2015-04-16 23:17:50.000 subscription: 000D: No input source available for subscription "192.168.0.100 [ muy | XBMC Media Center ]" to channel "TV3 HD GÖTEBORG" 
#14

Updated by Bengt Madeberg over 4 years ago

When I start tvh

015-04-16 23:44:35.631 linuxdvb: ca0 slot 0 status changed to MODULE_READY

2015-04-16 23:44:36.880 linuxdvb: TurboSight TBS 5881 DVBT/T2 frontend : DVB-T #0 - poll TIMEOUT

2015-04-16 23:44:37.290 en50221: slot 0: Application type: 01

2015-04-16 23:44:37.290 en50221: slot 0: Application manufacturer: cafe

2015-04-16 23:44:37.290 en50221: slot 0: Manufacturer code: babe

2015-04-16 23:44:37.290 en50221: slot 0: Menu string: Viaccess Access

2015-04-16 23:44:43.212 en50221: slot 0 supported CAID: 0500 (Viaccess)

2015-04-16 23:44:43.212 en50221: slot 0 supported CAID: 0502 (Viaccess)

#15

Updated by Bengt Madeberg over 4 years ago

Just tested my CAM with dvblast and it works perfect. Which settings do I need to do in tvh ?

#16

Updated by Morten Vinding over 4 years ago

This is so cool!
I have been waiting to kill my messy setup with two tuners for so long.
Currently I have a tuner with a Danish Boxer CAM and card (Boxer-DK is using Secure Viaccess that is not supported by any softcams), running mumuDVB and multicasting to TVH on the same box.
TVH has it's own tuner card for receiving all the FTA channels.

I will test this as soon as I have setup a new box with unstable TVH, and let you know how far I get.

My tuner is a TechniSat CableStar Combo HD CI "DRXK DVB-C DVB-T".

#17

Updated by Morten Vinding over 4 years ago

So I finally got around to build a new TV box and test TVH 3.9
I am using Ubuntu server 15.04 Vivid Vervet but using the unstable package from 14.10 Utopic Unicorn since there is no package for 15.x

Everything seems to be working fine, but like Bengt I can get the CAM to work. I don't even get the output from the CAM like you Bengt. Where do you see that?

I tested with mumudvb and that is working just fine.

Any settings that need to be set? Is there somewhere you configure which CAM to use for which channel?

#18

Updated by Morten Vinding over 4 years ago

Sorry my bad. I didn't though about this is not standard in the Ubuntu build.

I have rolled my own build with --enable-dvben50221 and now I get the exact same errors as you Bengt :(

Apr 25 23:52:53 tvserver2 tvheadend[14806]: START: HTS Tvheadend version 3.9.2747~g3049486 started, running as PID:14806 UID:110 GID:44, CWD:/ CNF:/home/hts/.hts/tvheadend
Apr 25 23:52:53 tvserver2 tvheadend[14806]: mpegts: 714MHz in DK - tuning on DRXK DVB-C DVB-T : DVB-T #0
Apr 25 23:52:53 tvserver2 tvheadend[14806]: subscription: 0001: "epggrab" subscribing to mux "714MHz", weight: 4, adapter: "DRXK DVB-C DVB-T : DVB-T #0", network: "DK", service: "Raw PID Subscr
iption" 
Apr 25 23:52:53 tvserver2 tvheadend[14806]: linuxdvb: ca0 slot 0 status changed to MODULE_READY
Apr 25 23:52:53 tvserver2 tvheadend[14806]: htsp: Got connection from 192.168.1.19
Apr 25 23:52:53 tvserver2 tvheadend[14806]: htsp: 192.168.1.19: Welcomed client software: XBMC Media Center (HTSPv12)
Apr 25 23:52:55 tvserver2 tvheadend[14806]: htsp: 192.168.1.19 [ XBMC Media Center ]: Identified as user RPi stue
Apr 25 23:52:55 tvserver2 tvheadend[14806]: htsp: 192.168.1.19 [ RPi stue | XBMC Media Center ]: Privileges raised
Apr 25 23:52:55 tvserver2 tvheadend[14806]: en50221: slot 0: Application type: 01
Apr 25 23:52:55 tvserver2 tvheadend[14806]: en50221: slot 0: Application manufacturer: cafe
Apr 25 23:52:55 tvserver2 tvheadend[14806]: en50221: slot 0: Manufacturer code: babe
Apr 25 23:52:55 tvserver2 tvheadend[14806]: en50221: slot 0: Menu string: Viaccess Access
Apr 25 23:52:59 tvserver2 tvheadend[14806]: en50221: slot 0 supported CAID: 0500 (Viaccess)
Apr 25 23:53:45 tvserver2 tvheadend[14806]: mpegts: 730MHz in DK - tuning on DRXK DVB-C DVB-T : DVB-T #0
Apr 25 23:54:34 tvserver2 tvheadend[14806]: subscription: 0008: "192.168.1.19 [ RPi stue | XBMC Media Center ]" subscribing on channel "TV 2 (Lorry)", weight: 150, adapter: "DRXK DVB-C DVB-T : DVB-T #0", network: "DK", mux: "738MHz", provider: "TV 2", service: "TV 2 (Lorry)", profile="htsp", hostname="192.168.1.19", username="RPi stue", client="XBMC Media Center" 
Apr 25 23:54:34 tvserver2 tvheadend[14806]: subscription: 0005: "epggrab" unsubscribing
Apr 25 23:54:37 tvserver2 tvheadend[14806]: subscription: 0008: service instance is bad, reason: No access
Apr 25 23:54:38 tvserver2 tvheadend[14806]: mpegts: 738MHz in DK - tuning on DRXK DVB-C DVB-T : DVB-T #0
Apr 25 23:54:38 tvserver2 tvheadend[14806]: subscription: 000A: "epggrab" subscribing to mux "738MHz", weight: 4, adapter: "DRXK DVB-C DVB-T : DVB-T #0", network: "DK", service: "Raw PID Subscription" 
Apr 25 23:54:40 tvserver2 tvheadend[14806]: subscription: 0008: No input source available for subscription "192.168.1.19 [ RPi stue | XBMC Media Center ]" to channel "TV 2 (Lorry)" 
Apr 25 23:54:54 tvserver2 tvheadend[14806]: message repeated 7 times: [ subscription: 0008: No input source available for subscription "192.168.1.19 [ RPi stue | XBMC Media Center ]" to channel "TV 2 (Lorry)"]
Apr 25 23:54:54 tvserver2 tvheadend[14806]: subscription: 0008: "192.168.1.19 [ RPi stue | XBMC Media Center ]" unsubscribing from "TV 2 (Lorry)", hostname="192.168.1.19", username="RPi stue", username="XBMC Media Center" 

Same setup is working without issues on mumudvb:

MuMuDVB Version 1.7.1
 --- Build information ---
Built with CAM support.
Built without transcoding support.
Built with ATSC support.
Built with ATSC long channel names support.
Built with support for DVB API Version 5.
---------
Originally based on dvbstream 0.6 by (C) Dave Chapman 2001-2004
Released under the GPL.
Latest version available from http://mumudvb.braice.net/
Project from the [email protected] (http://www.crans.org)
by Brice DUBOST ([email protected])

Info:  Tune:  You will use DVB API version 5 for tuning your card.
WARN:  CAM:  You have enabled the support for conditionnal acces modules (scrambled channels). Please report any bug/comment
Info:  Main:  Full autoconfiguration, we activate SAP announces. if you want to deactivate them see the README.
Info:  Main:  Full autoconfiguration, we activate PAT rewritting. if you want to deactivate it see the README.
Info:  Main:  Full autoconfiguration, we activate SDT rewritting. if you want to deactivate it see the README.
Info:  Main:  Full autoconfiguration, we activate sorting of the EIT PID. if you want to deactivate it see the README.
Info:  Main:  ========== End of configuration, MuMuDVB version 1.7.1 is starting ==========
Info:  Autoconf:  The autoconfiguration auto update is enabled. If you want to disable it put "autoconf_pid_update=0" in your config file.
Info:  Main:  Streaming. Freq 738000
Info:  Tune:  Using DVB card "DRXK DVB-C DVB-T" tuner 0
Info:  Tune:  Tuning DVB-T to 738000000 Hz, Bandwidth: 8000000
Info:  Tune:  Tuning With DVB-API version 5. delivery system : 3
Info:  Tune:  FE_STATUS:
Info:  Tune:  FE_STATUS:
Info:  Tune:       FE_HAS_SIGNAL : found something above the noise level
Info:  Tune:       FE_HAS_CARRIER : found a DVB signal
Info:  Tune:       FE_HAS_VITERBI : FEC is stable
Info:  Tune:       FE_HAS_SYNC : found sync bytes
Info:  Tune:       FE_HAS_LOCK : everything's working... 
Info:  Tune:  Event:  Frequency: 738000000
Info:  Tune:  Signal strength: 56884
Info:  Tune:  SNR: 0
Info:  Tune:  FE_STATUS:
Info:  Tune:       FE_HAS_SIGNAL : found something above the noise level
Info:  Tune:       FE_HAS_CARRIER : found a DVB signal
Info:  Tune:       FE_HAS_VITERBI : FEC is stable
Info:  Tune:       FE_HAS_SYNC : found sync bytes
Info:  Tune:       FE_HAS_LOCK : everything's working... 
Info:  Main:  Card 0, tuner 0 tuned
WARN:  DVB:  An issue happened during the IOCTLS to take BER measurements error: Operation not supported
Info:  Autoconf:  Autoconfiguration Start
Info:  Autoconf:  Autoconfiguration done
Info:  Autoconf:  Diffusion 1 channel
Info:  Autoconf:  Channel number :   0, name : "TV 2 (Lorry)"  service id 3317 
Info:  Autoconf:      Multicast4 ip : 239.100.0.0:1234
Info:  Main:  Channel "TV 2 (Lorry)" is now higly scrambled (86% of scrambled packets). Card 0
Info:  CAM:  CAM Application type: 01
Info:  CAM:  CAM Application manufacturer: cafe
Info:  CAM:  CAM Manufacturer code: babe
Info:  CAM:  CAM Menu string: Viaccess Access
Info:  Main:  Channel "TV 2 (Lorry)" is now fully unscrambled (0% of scrambled packets). Card 0
Info:  Main:  Channel "TV 2 (Lorry)" down.Card 0
Info:  Main:  Channel "TV 2 (Lorry)" is now higly scrambled (86% of scrambled packets). Card 0
Info:  Main:  Channel "TV 2 (Lorry)" back.Card 0
Info:  CAM:  Received new PMT - sending to CAM...
Info:  CAM:  CA PMT (ADDED) sent for channel 0 : "TV 2 (Lorry)" 
Info:  Main:  Channel "TV 2 (Lorry)" is now partially unscrambled (9% of scrambled packets). Card 0
Info:  Main:  Channel "TV 2 (Lorry)" is now fully unscrambled (0% of scrambled packets). Card 0
#20

Updated by Morten Vinding over 4 years ago

Bengt Madeberg wrote:

I have done a bug report.

https://tvheadend.org/issues/2794#change-13068

Excellent!
I will wait eagerly for the solution then.
Let me know if there is anything I can help with, log, trace etc.

#21

Updated by Hanspeter Müller about 3 years ago

KICK

No activety for over a year :(

There has been an unfinished (according to the author) attempt of a CI+ implementation here:

https://github.com/dmarion/tvheadend/tree/ciplus

It does not work, but it is good enough to trigger an authentication of the CA by the CAM, so the TLS-handshake at least starts...

Anyone willing to have a crack at it...?

The needed certificates are "available" inside the package for dreamy-receivers (i don't want to link to these sites, but i assume, anyone who is able to implement something like this will be able to find them ;) )

/hp

#22

Updated by Un Known over 1 year ago

ping

#23

Updated by Victor S 25 days ago

They wont do it, because they are afraid of legal issues (tvheadend devs are scared of almost everything related to descrambling).
Dreambox packages are pirate, ci+ requires official certification. You have to take over that github and continue the work yourself, you wont find any help here, trust me. It's surprising they didn't shut this topic down yet =)

#24

Updated by Flole Systems 25 days ago

@Victor S: Thats complete bullshit. Feel free to implement this and I'm sure it would be merged.

@Jaroslav: Would you merge this if this is implemented in a proper and clean way or is there any reason to not do that?

#25

Updated by saen acro 24 days ago

Victor S wrote:

They wont do it, because they are afraid of legal issues (tvheadend devs are scared of almost everything related to descrambling).
Dreambox packages are pirate, ci+ requires official certification. You have to take over that github and continue the work yourself, you wont find any help here, trust me. It's surprising they didn't shut this topic down yet =)

https://tvheadend.org/issues/4160#note-7

#26

Updated by Jaroslav Kysela 24 days ago

Victor S wrote:

They wont do it, because they are afraid of legal issues (tvheadend devs are scared of almost everything related to descrambling).
Dreambox packages are pirate, ci+ requires official certification. You have to take over that github and continue the work yourself, you wont find any help here, trust me. It's surprising they didn't shut this topic down yet =)

There are two parts:

1) implementation (it may be added to tvheadend's code)
2) the cryptographic keys (this is legal only if you are permitted to use those keys)

Also available in: Atom PDF