source: ipk/source/emus_incubuscamd_0_88/var/keys/incubusCamd.conf.incubus@ 3075

Last change on this file since 3075 was 521, checked in by civer, 17 years ago

-added all latest ipk sources

File size: 6.1 KB
Line 
1##############################################################################
2# incubusCamd configuration file #
3# All configuration options in this file observe the same format: #
4# <configuration_name>=<configuration_value> #
5# #
6# Each section are [<section_name>:<option_1>:<option_x>] like. #
7# #
8# No matter about white spaces on any place or UNIX/DOS style files #
9##############################################################################
10
11########################### general configuration ############################
12[General]
13# Enable (1) or disable (0) background execution
14# 0 - Off
15# 1 - On
16background_execution=1
17
18# This sets the level of console output for debugging:
19# 0 - No debug messages, 1 - First level debug messages, 2 - Second level debug messages,
20# 3 - Print all debug messages
21debug_level=3
22
23# This option enables (1) or disables (0) the writing of debug information to the
24# console.
25log_to_console=1
26
27# This option enables (1) or disables (0) the writing of console output to a log file
28log_to_file=0
29
30# When log_to_file is set to 1, this is the path and filename to write console
31# ouput to.
32logfile_name=/var/bin/incubusCamd.log
33
34# Used to activate on-screen messages. Username and password required if
35# HTTP authentication is enabled on enigma.
36on_screen_messages_show=1
37on_screen_messages_username=root
38on_screen_messages_password=
39on_screen_messages_key_update=1
40on_screen_messages_wait_for_key_update=0
41on_screen_messages_ecm=0
42on_screen_messages_emm=0
43
44#When activated, camd will listen on the specified port for connections. All
45#log activity will be broadcast in real-time to connected clients.
46console_logs_broadcast=1
47console_logs_broadcast_port=666
48
49########################### provider configuration ###########################
50#
51# All parameters are in hexadecimal notation.
52# Each section is defined by the provider id value.
53# If you don't know the provider id value then use the provider id "000000" and ca id "0000".
54# On provider 000000 caid 0000 goes all provider wich are not declared. If the provider
55# is declared then the cam will use the provider founded.
56#
57
58[Prov:000501:CaID:1833]
59# ----------------------------------------------------------------------------
60# Decoder type indicates whether the cam will attempt to decode this provider
61# in software, or through a card-server. Supported values are:
62#
63# 0 - Use internal softcams.
64# 1 - Connect to a card sharing protocol card-server.
65decoder_type=1
66
67# URL of card-server to use, formats are as follows:
68#
69# newcamd://<username>:<password>@<hostname>:<port>/<des_key>
70# aroureos://@<hostname>:<port>
71# radegast://@<hostname>:<port>
72#
73# Example:
74# newcamd://foo:bar@192.168.0.100:12345/0CE3476FF2E1C9D9A0A109B371E3
75#
76# Multiple card-server url's can be specified for server fail-over.
77# If the emu fails to connect or fails to get valid CW's, it will try to
78# connect to other servers in a round-robin fashion.
79#
80# Up to 16 servers can be added from index 0 to 15.
81#
82# You can choose also to select a cccam or gbox server, but they must be declared
83# in the "servers configuration" section ( [Servers] ).
84# e.g. : if you want to use a cccam server for a provider you must put it on
85# the parameter card_server_url_0=cccam://
86# NO MATTER the value after the double slash because server configuration is
87# made in the section [Servers].
88# Only for newcamd, radegast and aroureos is usefull to put correct connection
89# parameters because they are provider dependent.
90#
91#
92# Example i want to use mine card into the slot with newcs for prov 0501 on nagra3 (caid 1833)
93card_server_url_0=newcamd://username:password@192.168.0.100:10550/0102030405060708091011121314
94
95[Prov:000000:CaID:0000]
96# this provider is a stand-in for all cards and all caid not declared previously
97#
98# For example I choose to use cccam protocol on all other provider.
99#
100decoder_type=1
101card_server_url_0=cccam://
102
103########################### servers configuration ############################
104[Servers]
105#
106# This is the section for the multi-server configuration.
107#
108# URL of card-server to use, formats are as follows:
109#
110# cccam://<username>:<password>@<hostname>:<port>/<receive_emu_shared>/[EMM]
111# 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)
112#
113# gbox://<localhost>:<localport>:<password>@<peer_address>:<peer_port>:<peer_pass>/[EMM]
114#
115# NOTE: The "EMM" suffix is optional and tells the card-server client whether
116# to send EMM's to the card-server or not. Enabling or disabling this only
117# has effect if the card-server is configured to accept emms from this client.
118#
119# NOTE 2: The "card_server_url" is not the same as previously declared in the prov/caid section
120# use how many server as you like
121#
122# card_server_url=cccam://<username>:<password>@<hostname>:<port>
123# card_server_url=cccam://<username>:<password>@<hostname>:<port>
124# card_server_url=gbox://<localhost>:<localport>:<password>@<peer_address>:<peer_port>:<peer_pass>
125# card_server_url=cccam://<username>:<password>@<hostname>:<port>
126# card_server_url=gbox://<localhost>:<localport>:<password>@<peer_address>:<peer_port>:<peer_pass>
127card_server_url=cccam://<username>:<password>@<hostname>:<port>
128
129########################### CaIDs tunneling configuration ############################
130[CaIDTunnel]
131#
132# All values are in hex notation
133# In this file you can configure what CAIDs/PIDs incubusCamd should tunnel to another CAID
134#
135# situation 1: this caid, all idents, on all channels will use the tunnel_caid
136# caid:tunnel_caid
137#
138# situation 2: this caid/ident pair will use the tunnel_caid
139# caid:tunnel_caid:ident
140#
141# situation 3: this caid/ident pair, on channel 'sid' will use the tunnel_caid
142# caid:tunnel_caid:ident:sid
143#
144# i.e:
145# 1833:1702:000000:0082 # this one should tunnel premiereHD nagra3 into betacrypt cards
146# 1833:1702:000000:0081 # this one should tunnel premiereHD nagra3 into betacrypt cards
147
Note: See TracBrowser for help on using the repository browser.