welke versies incubuscamd kunnen verbinden met cccam 2.1.2

[Ome Merde]

ik ga het vanavond weer even proberen.

 

als ik de cccam-regel aanpas richting mijn dreambox op de slaapkamer dan heb ik wel beeld, echter is dit van korte duur.

ik heb ong. 3 minuten normaal beeld, hierna begint ie te blokken om vervolgens vast te slaan. dan krijg ik ook geen beeld meer op BVN.

na een reboot werkt het weer (even).

 

ik heb gisteren dat 0.5.5 sifteam image V2 (van 22-08 jl.) geflased in incubusCamd 0.93 er ingezet.

 

 

 

merDe

[Ome Merde]

ik snap er niks van. ik krijg het gewoon niet aan de praat. het zal aan mij liggen (ik heb hem werkende gezien afgelopen week-end) maar ik staak de strijd. ik heb er geen tijd voor.

 

 

 

merDe

[bash!]

Merde,

 

PM of mail mij de config eens... kijk ik hem ff na

 

Gr,

 

BaZ

[Ome Merde]

mijn incubusCamd.conf :

 

Code:

############################################################################### incubusCamd configuration file                                             ## All configuration options in this file observe the same format:            ##     <configuration_name>=<configuration_value>                             ##                                                                            ## Each section are [<section_name>:<option_1>:<option_x>] like.              ##                                                                            ## No matter about white spaces on any place or UNIX/DOS style files          ########################################################################################################## general configuration ############################[General]# Enable (1) or disable (0) background execution# 0 - Off# 1 - On#background_execution=0# This sets the level of console output for debugging:# 0 - No debug messages, 1 - First level debug messages, 2 - Second level debug messages,# 3 - Print all debug messages#debug_level=0# This option enables (1) or disables (0) the writing of debug information to the# console.#log_to_console=0# This option enables (1) or disables (0) the writing of console output to a log file#log_to_file=0# When log_to_file is set to 1, this is the path and filename to write console# ouput to.#logfile_name=/var/bin/incubusCamd.log# This is the path and filename to read SoftCam.Key file# by default it will be searched in the /var/keys directory#softcamfile_name=/var/keys/SoftCam.Key# This is the path and filename to read prio file# by default it will be searched in the /var/bin directory, or in /etc, or in /var/keys#priofile_name=/var/keys/incubusCamd.prio# Used to activate on-screen messages. Username and password required if# HTTP authentication is enabled on enigma.# 0 - Off# 1 - On#on_screen_messages_show=1on_screen_messages_username=rooton_screen_messages_password=on_screen_messages_key_update=0on_screen_messages_wait_for_key_update=0on_screen_messages_ecm=0on_screen_messages_emm=0# When activated, incubusCamd will listen on the specified port for connections. All# log activity will be broadcast in real-time to connected clients.#console_logs_broadcast=0console_logs_broadcast_port=666# Enable/disable incubusCamd web interface (default port is 668).# 0 - Disable# 1 - Enablewebif=1webif_port=668########################### provider configuration ############################# All parameters are in hexadecimal notation.# Each section is defined by the provider id value.# If you don't know the provider id value then use the provider id "000000" and ca id "0000".# On provider 000000 caid 0000 goes all provider wich are not declared. If the provider# is declared then the cam will use the provider founded.#[Prov:000000:CaID:0000]# ----------------------------------------------------------------------------# this provider is a stand-in for all cards and all caid not declared previously## You can select wich type of priority to assign on each caid/prov combination# priority name available are: card,emu,cs# card: internal card reader# emu: internal emulator# cs: card share protocols# each type must be separated by a comma## you can also set to use only cs and nothing more, to do it insert on each comma "cs"# example: check_priority=cs,cs,cs # only cs in this case# example: check_priority=card,emu,emu # no cs in this case# obviously this is not suggested but if you prefer to disable an option you should do it in this way# you can also declare only one type: check_priority=cs# or two types: check_priority=cs,emu# and so oncheck_priority=cs,emu,card# You can select wich protocol will be used first for the current caid/prov combination# protocol name available are: newcamd,cccam,gbox,radegast,camd33,camd35,aroureos# each protocol must be separated by a comma## you can also declare only one type: cs_protocol_order=cccam# or two types: cs_protocol_order=cccam,newcamd# and so oncs_protocol_order=cccam,gbox,newcamd,camd35,camd33,radegast,aroureos# Enable (1) or disable (0) emm process when a cs protocol is used# 0 - Off# 1 - On#process_emms_on_cs_mode=0# Enable (1) or disable (0) emm g type process# 0 - Off# 1 - On#process_emm_g=0# Enable (1) or disable (0) emm s type process# 0 - Off# 1 - On#process_emm_s=0# Enable (1) or disable (0) emm u type process# 0 - Off# 1 - On#process_emm_u=0# Enable (1) or disable (0) seca 3 ecm pid handler# when is set to On, it will try to use seca 3 ecm pid# before try seca 2 ecm pid, otherwise seca 2 pid will # be selected firstly# 0 - Off# 1 - On#seca3_handler=1#[Prov:000501:CaID:1833]#check_priority=cs,emu,card#cs_protocol_order=cccam,newcamd,gbox,camd35,camd33,radegast,aroureos#process_emms_on_cs_mode=0#process_emm_g=0#process_emm_s=0#process_emm_u=0#seca3_handler=0########################### servers configuration ############################[servers]## This is the section for the multi-server configuration.## URL of card-server to use, formats are as follows:## newcamd://<username_31>:<password_31>@<hostname>:<port>:<caid_4>:<prov_id_6>/<des_key_14>/[EMM]# aroureos://@<hostname>:<port>:<caid_4>:<prov_id_6>/[EMM]# radegast://@<hostname>:<port>:<caid_4>:<prov_id_6>/[EMM]# camd33://<username_10>:<password_10>@<hostname>:<port>:<caid_4>:<prov_id_6>/[aes_key_16]/[EMM]# camd35://<username_32>:<password_32>@<hostname>:<port>:<caid_4>:<prov_id_6>/[EMM]# gbox://<localhost>:<localport>:<password_8>@<peer_address>:<peer_port>:<peer_pass_8>/[EMM]## cccam://<username_20>:<password_32>@<hostname>:<port>/<receive_emu_shared>/[EMM]# where <receive_emu_shared> should assume value "yes" (without quotes, if you like to receive emus data shared by the server) or "no" (this is assumed by default)### NOTE: The "EMM" suffix is optional and tells the card-server client whether# to send EMM's to the card-server or not. Enabling or disabling this only# has effect if the card-server is configured to accept emms from this client.## NOTE 2: The "card_server_url" is not the same as previously declared in the prov/caid section# use how many server as you like## i.e:#card_server_url=cccam://dreambox:merde@192.168.1.77:8010#card_server_url=cccam://username:password@yourname.dyndns.org:15000#card_server_url=gbox://yourname.dyndns.org:6666:password@hisname.dyndns.org:6666:peer_pass#card_server_url=cccam://username:password@hostname:port#card_server_url=newcamd://username:password@192.168.0.100:10550:0500:028800/0102030405060708091011121314#card_server_url=radegast://@192.168.0.100:10550:0100:000065#card_server_url=aroureos://@yourhostname.dyndns.org:10666:0500:007C00#card_server_url=camd35://username:password@192.168.0.50:14150:0603:000000#card_server_url=camd33://username:password@192.168.0.50:10550:0603:000000 # cam33 without AES encryption#card_server_url=camd33://username:password@192.168.0.50:10500:0604:000000/01020304050607080910111213141516 # cam33 with AES encryption########################### CaIDs tunneling configuration ############################[CaIDTunnel]## All values are in hex notation# In this file you can configure what CAIDs/PIDs incubusCamd should tunnel to another CAID## situation 1: this caid, all idents, on all channels will use the tunnel_caid# caid:tunnel_caid## situation 2: this caid/ident pair will use the tunnel_caid# caid:tunnel_caid:ident## situation 3: this caid/ident pair, on channel 'sid' will use the tunnel_caid# caid:tunnel_caid:ident:sid## i.e:##1833:1702:000000:0082 # this one should tunnel premiereHD nagra3 into betacrypt cards#1833:1702:000000:0081 # this one should tunnel premiereHD nagra3 into betacrypt cards

 

 

merDe

 

 

[Lex_luthor]

Weet je zeker dat je ze allemaal nodig hebt?:

 

cs_protocol_order=cccam,gbox,newcamd,camd35,camd33,radegast,aroureos

 

Ik zou deze regel als volgt wijzigen:

 

"cs_protocol_order=cccam"

 

Gebruik je alle mogelijkheden van deze regel?:

"check_priority=cs,emu,card"

 

Probeer anders eens eerst een optie

check_priority=cs,cs,cs

of

check_priority=cs,card,cs

 

Heb je in CCcam config de volgende regel opgenomen?:

 

SERVER LISTEN PORT : 8010

[CB1]

Hij heeft wel beeld maar loopt na een paar minuten weer vast.

De CS_protocol enz heb je gelijk in maar dat heeft hij ook al geprobeerd.

Poortnummer klopt anders had hij helemaal geen beeld.

nu heeft hij nlb er op staan maar nu zapt hij weer heel traag ook met de seca3_handler op 1.

De config file rechtstreeks uit mijn box die lekker loopt in zijn box geplaatst en zapt ook traag.

Priofile van mijn box in zijn box zapt traag.

 

Wel vreemd.

Zelfde img zelfde conf en prio en toch traag zappen en hier goed.

 

Gr Cb1