Project

General

Profile

Bug #3291

OSCAM DVBApi Connection via /tmp/camd.socket not working

Added by Acid Rain over 4 years ago. Updated over 4 years ago.

Status:
Invalid
Priority:
Normal
Assignee:
-
Category:
Descrambling
Target version:
-
Start date:
2015-11-12
Due date:
% Done:

0%

Estimated time:
Found in version:
4.1.9xx
Affected Versions:

Description

Hi!

Since newest TVHeadEnd Version my DVBApi Connection didn't work.
capmt: Oscam: Cannot connect to /tmp/camd.socket:9000 (Name or service not known); Do you have OSCam running?

Configuration is like:
https://tvheadend.org/boards/13/topics/18471

Error occurs since i have selection menu in CA of different DVBApi Versions.
On older Version of TVHeadEnd I don't had to set a port for DVBApi ;(
Don't know exact Version of TVHeadEnd whree it works.
But I think in 4.1.3xx everything worked.

Even switched OSCam Revision from 101xx to current revision (11xxx)

Port /tmp/camd.socket exists, user root Group root and 777 rights...

History

#1

Updated by Jaroslav Kysela over 4 years ago

  • Status changed from New to Invalid

If you use the net protocol, you must use connection through network (for example: 127.0.0.1:9000) not socket. See help (boxtype = pc).

#2

Updated by Acid Rain over 4 years ago

Ok!
I'll test it today afternoon.
But also tested with IP and Port, no Connection was possible. :(

Afternoon I'll know more, thank you so far.

#3

Updated by Acid Rain over 4 years ago

Ok!
Very very thanks!
My big fault... :(

Are over "OSCam net protocol (rev >= 10389)" EMMS written?

oscam config:

[dvbapi]
enabled                       = 1
au                            = 1
pmt_mode                      = 4
listen_port                   = 9000
user                          = tvh
read_sdt                      = 2
write_sdt_prov                = 1
boxtype                       = pc

Cat CAClient:

{
        "mode": 5,
        "camdfilename": "OSCAM IP ADRESS",
        "port": 9000,
        "class": "caclient_capmt",
        "index": 1,
        "enabled": true,
        "name": "tvh" 
}

#4

Updated by Acid Rain over 4 years ago

oscam.user

[account]
user                          = tvh
caid                          = 098E
au                            = 1
group                         = 1

#5

Updated by B C over 4 years ago

Acid Rain wrote:

Are over "OSCam net protocol (rev >= 10389)" EMMS written?

yes, they are

#6

Updated by Jaroslav Kysela over 4 years ago

Note that I added mode 6 - which should be same like mode 5, but through the unix socket for new oscam.

Also available in: Atom PDF