Is a single DVBAPI client able to descramble two or more encrypted channels at the same time?

Matej Munih

Hello,

I have an Intel Nuc with Ubuntu 16.0.4 OS. On this system is running an oscam server and a tvheadend server. I have a smargo usb reader connected to the same intel nuc with an italian tivusat smardard. The tuner is a TBS 5927 DVB-S2 Usb tuner.

The oscam is successfully decoding the card and sending the key to the tvheadend using DVBAPI. I can watch all the encrypted channels from the Tivusat platform.

Now, I would like to add a second TBS 5927 tuner in order to be able to watch two encrypted tivusat channels at the same time on two different computers.

My question is: is tvheadend/oscam able to decode (using a single DVBAPI client) two different encrypted tivusat channels using only one smargo with one tivusat smartcard?

Thanks

Saen Acro

First try to decode 2+ channels from same transponder to see if card able to decode more then one channel at time.
I have bad experience with dvbapi and multiple tuners.
TVH after version 4.3-117 support N and C lines

Matej Munih

Hi, thanks for you reply.

I am now watching a single channel with DVBAPI and it is working like a charm... I am sad to hear that this would not be the case if I had a second tuner.

For N line do you mean the newcamd protocol? I tried to connect to oscam using newcamd but every time I got the message "connection refused" while dvbapi was instantly connected to oscam. I have the latest tvheadend release, 4.2.2

Thanks

Saen Acro

"connection refused"
1. not set Newcam port:caid
2. no user/password correct
3. not same DES key

Matej Munih

I understand, I will try to check if there is an error

Anyway, is this the right configuration of port/caid in oscam newcamd config? 9001@183E:000000,005411

In tvheadend, which is the right configuration in CA section? I am asking it because when I go to tvheadend -> CA -> newcamd -> port and try to put 9001@183E:000000,005411 I can put here only the port number. I am not allowed to put any ":" or "@".

Saen Acro

In TVH only port.
In oscam config port and what port do have to serve

Matej Munih

So, in tvheadend only port = 9001

and in oscam port = 9001@183E:000000,005411

About the DES key:

in oscam 0102030405060708091011121314

in tvheadend 0102030405060708091011121314

Am I right?

Saen Acro

correct

Matej Munih

Alright,

I changed the CA client in tvheadend and changed the newcamd config in oscam. I rebooted the system and the the tvheadend client was successfully connected to oscam. The problem is that I was not able to descramble the tivusat channels

Any advice?

Saen Acro

are reader and user are in same group?

Always after change restart oscam.


[account]
User	= Tivusat
Pwd	= Tivusat
Uniq	= 4
Group	= 1
caid = 0183D, 0183E
ident = 0183D:000000,005411;0183E:000000,005411
au	= 1

Matej Munih

Now the newcamd client in tvheadend is connecting and based on the tvheadend log everything is working fine. But I am stil not able to have the video descrambled in VLC :( :( :(

This is my configuration

Oscam.conf

[newcamd]
port = 15000@183E:000000,005411
serverip = 127.0.0.1
allowed = 127.0.0.1,192.168.0.0-192.168.255.255,10.0.0.0-10.255.255.255,255.255.255.255
key = 0102030405060708091011121314

keepalive = 1

Oscam.server

[reader]
label = tivusat2
description = tivusat
protocol = smargo
device = /dev/ttyUSB0
caid = 183E
rsakey = XXXX-censored-XXXX
detect = cd
nagra_read = 1
mhz = 534
cardmhz = 369
ident = 183E:005411,000000
group = 1
emmcache = 1,3,2,0

blockemm-unknown = 1

oscam.user

[account]
user = Tivusat
pwd = Tivusat
caid = 183E
uniq = 4
au = 1
group = 1

ident = 183E:000000,005411

The screeenshot of tvheadend client is attached here bellow

Saen Acro

oscam log?

Matej Munih

here is the log from /var/log/oscam.log

20.05.17 11:21:50 17.8 0.0.0.0 0 5 0 0 0 0 0 1495271822 1495271911 00:00:42 dvbapi 183E@000000:4534 183E@000000:4534 unknown
20.05.17 11:21:50 17.8 0.0.0.0 0 5 0 0 0 0 0 1495271822 1495271911 00:01:29 dvbapi FFFE@FFFFFE:FFFE FFFE@FFFFFE:FFFE unknown
20.05.17 11:22:34 0.0 127.0.0.1 40062 0 0 0 0 0 0 1495272154 1495272154 00:00:00 newcamd 0000@000000:0000

20.05.17 11:22:34 0.0 127.0.0.1 40062 0 0 0 0 0 0 1495272154 1495272154 00:00:00 newcamd FFFE@FFFFFE:FFFE FFFE@FFFFFE:FFFE unknown

As you can see, with dvbapi the channel is recognized, while with the newcamd is not

this is the "live log" from oscam webif

2017/05/20 11:22:34 00000000 s (main) init for all local cards done
2017/05/20 11:22:34 00000000 s (anticasc) anti cascading disabled
2017/05/20 11:22:34 562F5DA8 c (newcamd) client connected to 15000 port
2017/05/20 11:22:34 562F5DA8 c (client) anonymous disconnected from 127.0.0.1
2017/05/20 11:22:35 6E7B489F c (newcamd) client connected to 15000 port
2017/05/20 11:22:35 6E7B489F c (client) encrypted newcamd:15000-client 127.0.0.1 granted (Tivusat, au=auto (1 reader))
2017/05/20 11:22:35 6E7B489F c (newcamd) user Tivusat authenticated successfully (Tvheadend)
2017/05/20 11:22:35 6E7B489F c (newcamd) AU enabled for user Tivusat on reader tivusat2
2017/05/20 11:24:02 5AD4454D r (reader) tivusat2 [nagra] Tivusat emmtype=global, len=142 (hex: 0x8E), cnt=1: written (777 ms)
2017/05/20 11:24:07 5AD4454D r (reader) tivusat2 [nagra] Tivusat emmtype=global, len=142 (hex: 0x8E), cnt=2: written (777 ms)

2017/05/20 11:24:12 5AD4454D r (reader) tivusat2 [nagra] Tivusat emmtype=global, len=142 (hex: 0x8E), cnt=3: written (779 ms)

These are the tvheadend log. It seems that there is no error

2017-05-20 11:23:58.312 subscription: 0005: "epggrab" unsubscribing
2017-05-20 11:23:58.440 subscription: 0007: "HTTP" subscribing on channel "Rai 3 HD", weight: 100, adapter: "TurboSight TBS 5927 DVB-S/S2 #0 : DVB-S #0", network: "Tivusat", mux: "11765.84V", provider: "Rai", service: "Rai 3 HD", profile="pass", hostname="192.168.2.6", client="VLC/2.2.5.1 LibVLC/2.2.5.1"

Saen Acro

in oscam live log you must see(ecm) lines

Matej Munih

When I try to play a tivusat channel in VLC, in oscam live log I can only see the following informations:

2017/05/20 11:41:40 5BAA7E62 c (client) encrypted newcamd:15000-client 127.0.0.1 granted (Tivusat, au=auto (1 reader))
2017/05/20 11:41:40 5BAA7E62 c (newcamd) user Tivusat authenticated successfully (Tvheadend)
2017/05/20 11:41:40 5BAA7E62 c (newcamd) AU enabled for user Tivusat on reader tivusat2
2017/05/20 11:42:02 33C2C9EE r (reader) tivusat2 [nagra] Tivusat emmtype=global, len=142 (hex: 0x8E), cnt=1: written (782 ms)
2017/05/20 11:42:07 33C2C9EE r (reader) tivusat2 [nagra] Tivusat emmtype=global, len=142 (hex: 0x8E), cnt=2: written (778 ms)

2017/05/20 11:42:12 33C2C9EE r (reader) tivusat2 [nagra] Tivusat emmtype=global, len=142 (hex: 0x8E), cnt=3: written (777 ms)

No ecm lines

Again, if I switch to DVBAPI I am able to view the tivusat channel

I don't know if it matters, but under "DVB inputs" -> "services" I putted "1" under "force usage of CA etc..." for every tivusat encrypted channel. Look at the screenshot

Saen Acro


[newcamd]
key = 0102030405060708091011121314
port = porta_che_vuoi@183D:005411

version of oscam ?
"how to build latest oscam"

Matej Munih

Oscam version 11384

Joe User

While I have not done extensive testing, I never had a problem with the simultaneous use of two adapters with the DVBAPI connection to oscam. The DVBAPI protocol uses the adapter number as an index and is able to keep track of multiple adapters at the same time. If you have a problem with it, you should write a bug report so it can be fixed.

Saen Acro

Is your test include this situations


tree /dev/dvb
/dev/dvb
├── adapter0
│   ├── demux0
│   ├── dvr0
│   ├── frontend0
│   └── net0
├── adapter1
│   ├── demux0
│   ├── dvr0
│   ├── frontend0
│   └── net0
├── adapter10
│   ├── demux0
│   ├── dvr0
│   ├── frontend0
│   └── net0
├── adapter11
│   ├── demux0
│   ├── dvr0
│   ├── frontend0
│   └── net0
├── adapter12
│   ├── demux0
│   ├── dvr0
│   ├── frontend0
│   └── net0
├── adapter13
│   ├── demux0
│   ├── dvr0
│   ├── frontend0
│   └── net0
├── adapter14
│   ├── demux0
│   ├── dvr0
│   ├── frontend0
│   └── net0
├── adapter15
│   ├── demux0
│   ├── dvr0
│   ├── frontend0
│   └── net0
├── adapter2
│   ├── demux0
│   ├── dvr0
│   ├── frontend0
│   └── net0
├── adapter3
│   ├── demux0
│   ├── dvr0
│   ├── frontend0
│   └── net0
├── adapter4
│   ├── demux0
│   ├── dvr0
│   ├── frontend0
│   └── net0
├── adapter5
│   ├── demux0
│   ├── dvr0
│   ├── frontend0
│   └── net0
├── adapter6
│   ├── demux0
│   ├── dvr0
│   ├── frontend0
│   └── net0
├── adapter7
│   ├── demux0
│   ├── dvr0
│   ├── frontend0
│   └── net0
├── adapter8
│   ├── demux0
│   ├── dvr0
│   ├── frontend0
│   └── net0
└── adapter9
    ├── demux0
    ├── dvr0
    ├── frontend0
    └── net0

16 directories, 64 files

and this


tree /dev/dvb/
/dev/dvb/
├── adapter0
│   ├── ca0
│   ├── ca1
│   ├── ci0
│   ├── ci1
│   ├── demux0
│   ├── demux1
│   ├── demux2
│   ├── demux3
│   ├── dvr0
│   ├── dvr1
│   ├── dvr2
│   ├── dvr3
│   ├── frontend0
│   ├── frontend1
│   ├── frontend2
│   ├── frontend3
│   ├── net0
│   ├── net1
│   ├── net2
│   └── net3
├── adapter1
│   ├── ca0
│   ├── ci0
│   ├── demux0
│   ├── demux1
│   ├── dvr0
│   ├── dvr1
│   ├── frontend0
│   ├── frontend1
│   ├── net0
│   └── net1
├── adapter2
│   ├── demux0
│   ├── demux1
│   ├── demux2
│   ├── demux3
│   ├── dvr0
│   ├── dvr1
│   ├── dvr2
│   ├── dvr3
│   ├── frontend0
│   ├── frontend1
│   ├── frontend2
│   ├── frontend3
│   ├── net0
│   ├── net1
│   ├── net2
│   └── net3
└── adapter3
    ├── ca0
    ├── ca1
    ├── ci0
    ├── ci1
    ├── demux0
    ├── demux1
    ├── demux2
    ├── demux3
    ├── dvr0
    ├── dvr1
    ├── dvr2
    ├── dvr3
    ├── frontend0
    ├── frontend1
    ├── frontend2
    ├── frontend3
    ├── net0
    ├── net1
    ├── net2
    └── net3

4 directories, 66 files

Joe User

No and neither is the original poster's. He wants to use just two adapters, so what exactly is your problem??? Why do you push your problems on others??? Stop giving bad advice because your unique setup does not work. Don't tell people DVBAPI does not work when it works just fine for MOST people. You have wasted a lot if HIS time just because YOU have a problem with DVBAPI. Again, if you have a problem, create a bug report with some logs instead of giving bad advice to others.