Foros ZackYFileS

Foros ZackYFileS (http://foros.zackyfiles.com/index.php)
-   DREAMBOX (http://foros.zackyfiles.com/forumdisplay.php?f=185)
-   -   problemilla, sharing con azul (http://foros.zackyfiles.com/showthread.php?t=313270)

Maikeln 23/04/2005 17:31

problemilla, sharing con azul
 
Tengo 2 dream 7000 en red y la que no tiene la pitufa solo funciona bien el paramount, los demas canales cada vez que cambio tengo que recargar el newcamd para que se vean.

cardserv.cfg

USER = "user" "pass" lan "ip del cliente" 12000 au

#
# upper card slot
#
SERIAL_PORT = 0
TCP_PORT = 10000
EMM-G = yes
EMM-S = yes
EMM-U = yes
SPECIAL_FEATURES = yes
disable_pin = no


newcamd.conf

CWS = "ip de la dream" 10000 "user" "pass" 01 02 03 04 05 06 07 08 09 10 11 12 13 14 lan cardserv


He estado mirando para probar con gbox pero no encuentro ningun manual claro.

Un saludo.

Cierzo 23/04/2005 21:57

¿Podrías poner lo que tienes en el cardserv.cfg de la "cliente" en el apartado de los "serial port"?, tal vez ahí esté el problema.

Tambien puedes probar a usar otro cliente. Yo uso mgcamd y me va mucho mejor que newcamd.

Saludos

Cierzo 23/04/2005 23:09

Ya puesto comprueba tambien que el nombre del server no es el mismo en los dos cardserv.cfg.

Desde lejos puedes tener conflicto con:
- Numero de puerto de los tarjeteros
- Nombre de servidor.

Prueba a lanzar el cliente sin el cardserver (te quedarás sin tarjeteros locales)
Comprueba en el newcamd.conf del cliente que no tienes otro CWS = .... 10000 ....

O pon los ficheros completos para ver que pasa.

Saludos

Maikeln 24/04/2005 07:56

cardserv.cfg

#
# /var/tuxbox/config/cardserv.cfg
#
# The new cardserver can run several cards at once. It detects cards being
# inserted and removed from configured card readers. Every card uses its
# own TCP port to listen for incoming client connections. Card readers, that
# are configured, but where no card is inserted, will not be initialized.
# Supported are both serial ports of dbox2 (SERIAL_PORT = 0, 1), Dreambox
# cardreaders (SERIAL_PORT = 0 (upper), SERIAL_PORT = 1 (lower)) and the
# Dreambox's serial port (SERIAL_PORT = 2). Supported CA systems are Seca,
# Viaccess, Irdeto, Conax, Cryptoworks and Nagra1. Irdeto cards (or some of
# them) probably won't work in the Dreambox cardreaders, due to driver issues.
# In fact, the only Irdeto cards, that were successfully tested in Dreambox
# cardreaders, are the new Premiere cards and I2 cards. Premiere cards will ONLY
# work with betad (no sharing allowed for Premiere). Betad is a small subset
# of cardserver, using Unix Domain Sockets to communicate with newcamd. Also
# betad will only understand a very small subset of the options described here.
# Each instance of betad will only be able to serve exactly one card, while one
# instance of cardserver can serve multiple cards at the same time. Therefore
# betad is not able to handle the sc8in1. Betad configuration file is called
# betad.cfg. There is no special manual for betad.cfg, we everyone will be able
# to figure out, which cardserv.cfg options, described below, will also work in
# betad.cfg and which won't.
# Configuration consists of global (all cards) and local (single card) options.
# betad.cfg will of course only have one local (single card) section. The
# global section is located at the beginning of the file before the first
# SERIAL_PORT option. The SERIAL_PORT option is a "divider" between the global
# and the local sections, it also is a divider between options for different
# cards. The SC8IN1_SLOT options is a similar divider, but it divides only
# between different cards in the sc8in1 cam and the first SC8IN1_SLOT options
# has to preceeded by a SERIAL_PORT option. Some options may appear in the
# global as well as in local sections, in the case the option in the global
# section is a default for all cards, that don't have the same option in their
# particular local section. Options that appear in an incorrect section will
# be rejected with a "parse error" and the cardserver won't start. Betad will
# also reject all cardserver options, that aren't necessary or allowed for its
# operation. betad will understand the following options, of used correctly:
# SERIAL_PORT, BAUDRATE, USER, PARITY, CARD_DETECT_INVERT, CARD_DETECT_BIT and
# IGNORE_CARD_DETECT_SWITCH.
#
# You can also start cardserver multiple times by specifying different cfg
# files in the command line. Use only the name of the cfg file, the path of the
# file is always fixed to /var/tuxbox/config (dbox2, Dreambox) or /etc (i386)
#
# (G) = global section only
# (L) = local section only
# (A) = all sections
#
# 14 byte des key for the connection (A)
# DESKEY = 01 02 03 04 05 06 07 08 09 10 11 12 13 14
#
# id name of the cardserver (G)
# SERVER_NAME = cardserv
#
# debug port, lists all cards and their open connections (G)
# just telnet to it
# DEBUG_PORT = 12002
#
# entitlement port, lists entitlements of Seca, Conax and Cryptoworks cards
# just telnet to it
# ENTITLEMENT_PORT = 12003
#
# optional admin options (G)
# port for incoming camdcmd connections
# password and 14 byte des key for admin connections
# ADMIN_PORT = 12004
# ADMIN_PASSWORD = secret 00 00 00 00 00 00 00 00 00 00 00 00 00 00
#
# Userlist (A)
# there can be multiple users, user 1 always do AU for the card
# additional AU users can be defined by adding "au" at the end of the USER line
# keep in mind that your card number will be sent to all AU users
# global user preceed local users in terms of userid
# lan/wan/spider gives the type of connection
# lan = local area network
# wan = wide area network (those connections can be rebuild with camdcmd wanon)
# connections from cardspider to "wan" declared cards in cardserver are not
# possible
# spider = acts like wan, but allows connections from cardspider
# <username> <password> <lan/wan/spider> <newcamd hostname> <newcamd incoming cws port> (A)
# everything starting from <lan/wan> is optional (reverse login is optional)
# USER = dummy dummy lan dbox2 12000
# two examples for additional AU users
# USER = dummy2 dummy2 lan dbox2 12000 au
# USER = dummy3 dummy3 au
#
# CLIENT_CONNECT_TIMEOUT (in 100ms) (G)
# max time to wait for a login at a newcamd client
# CLIENT_CONNECT_TIMEOUT = 20
#
# debug options (A) - show network and card init, ecm and emm packages
# DEBUG_INIT = no
# DEBUG_NET = no
# DEBUG_ECM = no
# DEBUG_EMM = no
#
# Serial Port (Phoenix/Multicam) (Section divider)
# The first SERIAL_PORT options ends the global section
# On Dreambox SERIAL_PORT = 0 is the upper card slot,
# SERIAL_PORT = 1 is the lower card slot and 2 is the
# actual serial port.
# All numbers SERIAL_PORT = 3 and higher on Dreambox will use /dev/usb/tts/X
# devices for Phoenix on USB-to-RS232 adapters. This feature depends on a
# driver for your particular SB->RS232 adapter being insmod into the kernel of
# your image, your particular USB->RS232 driver supporting RS232 handshaking
# signal generation and on the particular card used. Basically this feature
# should be considered unstable and for advanced users only. The BAUDRATE option
# is not available for SERIAL_PORT = 3 and higher on Dreambox and would be
# rejected with a parse error
# SERIAL_PORT = <no> begins a single card's local section
# SERIAL_PORT = 0
#
# Serial Port (sc8in1) (section devider)
# SERIAL_PORT = <no> sc8in1 begins a sc8in1 description
# SC8IN1_SLOT must follow immediately to start a local section
# SERIAL_PORT = 1 sc8in1
#
# sc8in1 slot (sc8in1 sub section divider)
# valid slots are 0-7, 0 being the left most connector on the sc8in1
# SC8IN1_SLOT = 1
#
# Parity - serial communication parameter for the smartcard (L)
# The default is on, which is correct for all cards except Irdeto
# This is for reading the ATR only, after the ATR has been recognized by
# cardserver, it automatically switches to the correct communication parameters
# Some Irdeto cards work with PARITY = on also, some need PARTIY = off, so just
# test it. Dreambox cardreaders don't need this option, so it will be rejected
# for SERIAL_PORT = 0, 1 on Dreambox
# PARITY = on
#
# CARD_DETECT_BIT (L)
# different Phoenix readers sometimes use different serial lines to detect an
# inserted card, here you can specify, which line cardserver should use for a
# particular card. Possible values are CTS, DCD and DSR
# Default is CTS for sc8in1 and dbox2 serport 1, DCD otherwise
# Will be rejected for SERIAL_PORT = 0, 1 on Dreambox (internal cardreaders)
# CARD_DETECT_BIT = DCD
#
# Baudrate (L) (DBOX2/DREAMBOX versions ONLY!)
# Baudrate selection for the dbox2/Dreambox server. Allows to run 6 MHz with
# 3.579 MHz crystal and (theoretically) the other way around.
# Keep in mind, running anything but Irdeto cards at 6 MHz is overclocking!!!
# Irdeto card at 3.57 MHz: BAUDRATE = 5727
# other card at 6 MHz: BAUDRATE = 16128
# Default is 9622, which is correct for all except Irdeto cards at 3.579 MHz
# 3579545 Hz / 372 = 9622 bit/s (see iso 7816)
# This option will be rejected on I386 and on Dreambox ports other than
# SERIAL_PORT = 2
# BAUDRATE = 9622
#
# TCP port (L) - the port listening for connections for a particular card
# TCP_PORT = 2000
#
# EMM options - block EMM-U, EMM-G or EMM-S (A)
# EMM-G = no
# EMM-S = no
# EMM-U = no
#
# For iso cardreaders that close the card switch contact instead of opening it,
# when a card is inserted (L)
# Will be rejected for SERIAL_PORT = 0, 1 on Dreambox (internal cardreaders)
# CARD_DETECT_INVERT = yes
#
# Disable Pin (L) Seca only
# suppress all pin enter requests on Seca cards
# be very careful with this feature, if you have ordered PPV events or have
# prepaid Jetons on your card, if this is enabled, cardserver will use them
# up on any ppv event without ever asking
# DISABLE_PIN = yes
#
# Special features (only for some cards) (L)
# SPECIAL_FEATURES = no
#
# Exclude services - Some providers offer a PPV preview by allowing a card
# to decrypt a certain number of ECMs of each PPV event before it has to be
# bought. Sharing such a card with other people allows them to "steal" this
# PPV preview. With this option, you can tell cardserver to not ask the card
# to decrypt ECMs for certain services, except if user 1 (the EMM user) asks
# for them. Each blocked service has to be listed with its service id.
# A service id is a 16-bit number and has to be given in hex.
# camdcmd offers a possibility to change the list of blocked services without
# restarting cardserver (if for example you have bought a PPV event and now
# want to share it).
#
# Block single service (L)
# EXCLUDE_SERVICE = 13a9
# You can also block a range of service ids, the following blocks all services
# from 02be to 02c8
# EXCLUDE_SERVICE_MULTIPLE = 02be:02c8
#
# Boxkey (for Nagra1 cards only) (L)
# 8 byte des boxkey of your nagra smartcard. This boxkey is needed for proper
# use of your card, otherwise you'll get incorrect control words
# BOXKEY = 11 22 33 44 55 66 77 88
DESKEY = 01 02 03 04 05 06 07 08 09 10 11 12 13 14
SERVER_NAME = cardserv
DEBUG_PORT = 14000
ENTITLEMENT_PORT = 14001
ADMIN_PORT = 14002
ADMIN_PASSWORD = secret 00 00 00 00 00 00 00 00 00 00 00 00 00 00
USER = local local lan dreambox 12000
USER = "user" "pass" wan "ip del cliente para el rlogin" 12000 au
USER = "user" "pass" wan "ip del cliente para el rlogin" 12000 au
#
# upper card slot
#
SERIAL_PORT = 0
TCP_PORT = 10000
EMM-G = yes
EMM-S = yes
EMM-U = yes
SPECIAL_FEATURES = yes
#disable_pin = yes
#
# lower card slot
#
SERIAL_PORT = 1
TCP_PORT = 10001
EMM-G = no
EMM-S = no
EMM-U = no
SPECIAL_FEATURES = no
#
# serial port for fhenix
#
#SERIAL_PORT = 2
#TCP_PORT = 10002
#EMM-G = no
#EMM-S = no
#EMM-U = no
#SPECIAL_FEATURES = no


newcamd.conf del cliente


# /var/tuxbox/config/newcamd.conf
#
# newcamd mandatory settings
#
# What Demux API is used? (1 = very old, 2 = rel (Dreambox), 3 = head (VDR))
DEMUX_API = 2
# on PPC version: What Box is used? Valid options are DBOX2, DM7000 and DM5600
# on I386 version this parameter is ignored
BOX_TYPE = DM7000
# Which device for writing control words should be used?
# Valid options are CA, SDEV or GTX
# (SDEV and GTX = /proc/bus/gtx, CA = /dev/caX or /dev/dvb/card0/caX)
CONTROL_WORD_DEVICE = CA
# What CA0 API is used?
# 3 for recent DVB-S driver or recent Dreambox drivers (dream.o from 1.07.3)
# also for ca1 use on dbox2
# 2 for older Dreambox driver (ca.o or dream.o up to 1.07.2)
# no effect on PPC version if CONTROL_WORD_DEVICE = GTX or SDEV
CA_API = 3
# output control words to /proc/bus/gtx in 16 byte or 4096 byte packets
# no effect on I386 version or on PPC version, if BOX_TYPE = DREAMBOX
GTX_OUTPUT_MODE = 16
# This is important for channels which frequently change between free and
# encrypted broadcasts. The change will be reflected in the PMT. If you
# don't want your picture to stop when the channel goes from free access
# mode to encrypted mode, either your zapper (zapit/Enigma) or newcamd
# itself has to keep track of PMT changes. Recent Enigma versions do this,
# so you can set PMT_UPDATE_WATCH to no. Recent Zapit versions also have
# this option, but it is not compiled by default. So when using Zapit
# without PMT updates, you need to enable newcamd to monitor the PMT
# (PMT_UPDATE_WATCH = yes). Having both zapper and newcamd monitor
# the PMT at the same time, can lead to all kind of instabilities and
# should therefore by avoided, even if it seems to work at first.
PMT_UPDATE_WATCH = no
# Use emulator?
EMU = yes
# if both control word server and emulator keys are available for the
# channel, which method should be tried first?
PREFER_EMU = yes
# deactivates the dbox2 Betacrypt CAM
# this has to be set to yes on Dreambox
DISABLE_CAM = yes
# use dbox2 Betacrypt CAM for caids 06, 17 or both (00)?
CAM_CASYS = 17
# Autoupdate for Emu and Control Word Servers
# AU is always yes if there are Betacrypt UDS control word server
# connected to newcamd
AU = yes
#
# newcamd debug options
#
# dumps all ca systems used by a channel on the console
SHOW_ALL_CA_SYSTEMS = no
# On Screen Display, neutrino, enigma or none
OSD = none
# Recent Enigma versions come with a new option "Use http authentication"
# in the Expert Setup menu. If this option is enabled, the Enigma web server
# requires all clients to authorize themselves with username (root) and
# password (usually dbox2 or dreambox). The following option tells newcamd
# about the authentication username and password to use for the web server
# in order to be able to display its on screen information.
OSD_WEB_LOGIN = root:dreambox
# print debug messages about ECM handling
DEBUG_ECM = yes
# print debug messages about EMM handling
DEBUG_EMM = no
# print debug messages about Control Word Server (CWS)
DEBUG_CWS = yes
# print debug messages about dbox2 CAM (cam-alpha.bin)
DEBUG_CAM = yes
# print command message to/from dbox2 CAM as hex strings
DEBUG_CAM_HEX = no
# print all plain control words used
SHOW_CW = no
# hex dump of entire PAT
SHOW_PAT = no
# hex dump of entire PMT
SHOW_PMT = no
# hex dump of entire ECM
SHOW_ECM = no
# hex dump of entire CAT
SHOW_CAT = no
# hex dump of entire EMM (AU)
SHOW_EMM = no
# show network ECM messages being sent and received from/to the cardservers
SHOW_CWS_ECM = no
# show network EMM messages being sent and received from/to the cardservers
SHOW_CWS_EMM = no
# hex dump of EMMs with wrong signature
EMM_REPORT_WRONG_SIG = no
# delay between channel zap and appearance of the OSD
OSD_WAIT_TIME = 2000
#
# newcamd optional settings
#
# Delay between reception of new control word and writing them into
# the CSA registers
# this is a default, can be changed for each individual key in keylist
DEFAULT_CW_DELAY = 500
# reload config on every channel zap
RELOAD_CONFIG_ON_ZAP = yes
# reload keylist on every channel zap
RELOAD_KEYLIST_ON_ZAP = no
# write osd ca info to file
# CA_INFO_FILE = /tmp/cainfo.txt
#
# newcamd mandatory settings for control word servers (cws)
#
# Cardserver list
#
# <hostname> <port> <username> <password> <14 byte triple-des key in hex> <lan/wan> <cardserver name>
#
# wan connections will be dropped and rebuild if newcamd is told so by camdcmd
# (see admin options)
#
# hostname = uds to use betad, port is the serial port in that case
#
#CWS = 127.0.0.1 10000 local local 01 02 03 04 05 06 07 08 09 10 11 12 13 14 wan cardserv
#CWS = 127.0.0.1 10001 local local 01 02 03 04 05 06 07 08 09 10 11 12 13 14 wan cardserv
CWS = "ip del servidor" 10000 "user" "pass" 01 02 03 04 05 06 07 08 09 10 11 12 13 14 wan cardserv
#CWS = 127.0.0.1 10002 local local 01 02 03 04 05 06 07 08 09 10 11 12 13 14 wan cardserv
#
# newcamd optional settings for using control word servers (cws)
#
# Timeout for cardserver login in 100ms
CWS_CONNECT_TIMEOUT = 20
# Port to listen for incoming cardserver connections (reverse login)
# and/or admin connections
CWS_INCOMING_PORT = 12000
# Port to get a list of all connected cardservers, just telnet to it
CWS_DEBUG_PORT = 12001
#
# newcamd admin control options
# (incoming port is the same as CWS_INCOMING_PORT)
#
# <password> <14 byte des key>
#
ADMIN_PASSWORD = secret 00 00 00 00 00 00 00 00 00 00 00 00 00 00


En realidad es un servidor y dos clientes a traves de internet y el rlogin tampoco es que me vaya muy fino tampoco.

Cierzo 24/04/2005 09:41

A través de internet. Entonces las variables son más y es más probable el fallo.

En cualquier caso, y antes de ver lo que falla os recomiendo que, por seguridad, cambieis la deskey y el nombre del servidor.

Luego, dando por supuesto que el cardserv que has puesto es el del server, prueba lo siguiente:
- Edita el cardserv.cfg del cliente y cambia la linea que pone TCP_PORT = 10000 por otro número (p.e. 10100), con eso te evitarás conflicto con el servidor local, aunque luego ya veo que no lo usas en el newcamd.conf.

En el newcamd.conf local:
- Amplía el timepo de timeout por si le cuesta más hacer la conexión (CWS_CONNECT_TIMEOUT), p.e. 40

- Añade la linea CWS_KEEPALIVE = yes (si las versiones de newcamd son posteriores a 5.24)

Si tienes un router por medio hay que redireccionar puertos:
En el servidor el 12000
En el cliente el 12000 (para el rlogin)

Con internet mi recomendación de cambio de cliente es más fuerte, el newcamd no realiza reconexiones si, por lo que sea, se pierde la comunicación (y un ECM perdido es suficiente) mientras que el mgcamd sí. El mgcamd utiliza el dichero newcamd.conf para conectarse y es muy sencillo de configurar para que lo haga.

Saludos.

avila1 24/04/2005 12:10

[QUOTE]Con internet mi recomendación de cambio de cliente es más fuerte, el newcamd no realiza reconexiones si, por lo que sea, se pierde la comunicación (y un ECM perdido es suficiente) mientras que el mgcamd sí. El mgcamd utiliza el dichero newcamd.conf para conectarse y es muy sencillo de configurar para que lo haga.[/QUOTE]
Te importaría ampliar un poco esa información, yo tengo algunos problemas con newcamd y me gustaría probar con otro cliente.
Se puede utilizar en un cliente-servidor por ejemplo mgcamd y en otros el newcamd???
O todos deben de utilizar los mismo?
Gracias anticipadas.
Un saludo.

Cierzo 24/04/2005 13:05

newcamd es un cliente, esto es recible los datos de alguien. En este caso cardserver.

Cardserver manda los datos en un determinado formato, cualquier cliente que los entienda los puede utilizar. Yo he probado y me he conectado correctamente con newcamd, camx y mgcamd. No lo he conseguido con gbox y le tengo unas ganas...

Bueno, volviedo al tema.

Newcamd tiene su fichero de configuración. en él se le dice de donde va a coger los datos.
Lo mismo ocurre con camx.

Pero mgcamd tiene, en su fichero de configuración (/var/keys/mg_cmd) unas lineas que permiten conectarse a servidores de red utilizando otros ficheros de configuración (newcamd, camd3 y radegast). Es decir, basta con decirle que actue como cliente newcamd y automaticamente leera el fichero (/var/tuxbox/config/newcamd.conf).

Ahora lo interesante.
Newcamd no tiene (y si hacems caso al leeme que le acompaña, no lo tendrá nunca) la posibilidad de restablecer una conexión perdida. Las conexiones se establecen cuando se arranca el cliente o cuando se arranca el servidor (eso del reverse login) pero, si por el camino dejan de verse (problemas en la linea) no lo harán hasta que uno de los dos se reinicie, algo que me fastidia bastante ya que, p.e. no puedes fiarte de programar una grabación y largarte)

Mgcamd tiene una linea para reconectar, por defecto son 600 segundos (10 minutos) pero yo lo he bajado a 45 y se recupera muy bien de cortes de la linea. Se que puedo estar hasta eso de un minuto sin señal, pero con el newcamd no la recuperaba nunca.
He probado bastante y hasta ahora todo va bien.

Lo unico que echo de menos es que lanzando el proceso del newcamd desde terminal me aparecía la hora en la que ocurría cualquier cosa (aparte de toda la información de conexión, que es una gozada) y con el mgcamd no veo nada.

Sobre tu cuestion de redes mixtas, creo que esta claro. Una máquina (yo he probado con una dreambox7000, una 5620 y un pc con linux) lanza el proceso cardserver y se podrán conectar todos aquellos clientes que tenga en su cardserv.cfg. Los clientes pueden ser con cualquier cosa que lo lea: unos con uno, otros con otro y además, cambiarse de cliente cuando les apetezca sin tener que tocar el servidor.

Saludos

Maikeln 24/04/2005 15:47

Gracias por la info Cierzo. Por lo que comentas la "solucion" a los cortes seria que los clientes utilizaran mgcamd. Con gbox como seria?, hay algun manual donde poder sacarle punta?

Cierzo 24/04/2005 15:59

Cita:

Iniciado por Maikeln
la "solucion" a los cortes seria que los clientes utilizaran mgcamd

No se si es la solución, lo que sí se es que lo ha sido para mi.


[QUOTE=Cierzo] No lo he conseguido con gbox y le tengo unas ganas...[/QUOTE]
De hecho, ni siquiera se si es posible.



Saludos

Maikeln 24/04/2005 16:02

el gbox es un cliente-servidor, no?

Cierzo 24/04/2005 16:22

Sí, como otros cuantos.

Lo que no se es si puede actuar de cliente de otros

avila1 26/04/2005 23:47

Gracias. Este finde haremos pruebas.
Un saludo.

Maikeln 27/04/2005 10:02

Estoy intentando solucionar lo de la reconexion cuando cae la linea con el mgcamd y no consigo que reconecte aqui os dejo el mg_cfg del cliente a ver si sabeis por donde anda el fallo. Solo reconecta cuando reinicio en el cliente el mgcamd. Lo mismo que me pasaba con el newcamd

Un saludo.

# EMM messages
# 00 don't show any EMM's (default)
# 01 show only valid EMM's
# 02 show valid and bad EMM's with complete data display
M: { 01 }

# ECM messages
# 00 don't show any ECM's
# 01 show only valid ECM's (default)
# 02 show valid and bad ECM's with complete data display
C: { 01 }

# AU
# 00 is ignored (default)
# 01 enable AU
# 02 AU Auto
A: { 00 }

# key update
# 01 update only new keys, default setting
# 02 update all keys (used for valid PMK checking)
U: { 01 }

# key files folder
# 00 keyfiles in /var/keys
# 01 keyfiles in /var/tmp
T: { 00 }

# network mode, use summ for several clients
# 00 no network (default)
# 01 newcamd netclient
# 02 radegast netclient
# 04 camd3 netclient
G: { 01 }

# network retry
# 00 disable (default)
# 01 retry every new ecm
# 02 try to connect to offline shares every 10 min
# 03 both
N: { 01 }

# network ecm timeout in seconds
# defaut is 10
K: { 10 }

# newcamd dead routes retry, sec
Q: { 45 }

# network shares priority
# 00 newcamd, radegast, camd3 (default)
# 01 camd3, radegast, newcamd
# 02 newcamd, camd3, radegast
P: { 00 }

# on screen display type
# 00 No OSD (default)
# 01 neutrino
# 02 enigma
O: { 00 }

# on screen display Options
# 03 default
# 01 show emu ecm
# 02 show network shares messages
# 04 show decoding failed / fta
# 08 show emm keys update
S: { 03 }

# send messages to UDP, default Port 28007
# 00 Off (default)
# 01 On
L: { 00 } 172.16.1.1 28007

# cache ecm pids and data used to open channels,
# store pids in /tmp/ca_cache.list at exit, load at startup,
# same syntax as restore.list
# 00 Off (default)
# 01 Ecm pids cache
# 02 Ecm data cache
# 03 both caches
H: { 00 }

# reread files on zap:
# 00 No (default)
# 01 config (including priority and ignore, but not replace/cache)
# 02 config and keys
# 03 both
R: { 00 }

# debug
# 00 off (default)
# 01 on
D: { 00 }

Cierzo 27/04/2005 10:33

Cita:

Iniciado por Maikeln
# network retry
# 00 disable (default)
# 01 retry every new ecm
# 02 try to connect to offline shares every 10 min
# 03 both
N: { 01 }


Yo, aquí tengo esto:

[CODE]# network retry
# 00 disable (default)
# 01 retry every new ecm
# 02 try to connect to offline shares every 10 min
# 03 both
N: { 03 }[/CODE]
El resto, practicamente igual.

Tambien puedes probar a aumentar un poco el tiempo de newcamd retry
[CODE]# newcamd dead routes retry, sec
Q: { 45 }
[/CODE]
a ver si es que lo has acortado mucho (a mi con ese valor me va bien, pero...)

Saludos

Maikeln 27/04/2005 12:50

De lujo Cierzo, reinicio el newcamd que hace de server y los clientes reconectan sin problemas, luego probare cuando se corte la linea a ver como se porta.

Asias

Cierzo 27/04/2005 12:58

Yo para las pruebas soy un poco mas brusco que eso de esperar:


En un cliente:
- Resetea la linea adsl (si el router lo permite)
- Resetea el router (y si no lo permite apagalo (espera unos segundos) y enciendelo, o desenchufalo (espera unos segundos) y enchufalo)
- Desconecta el cable que va al teléfono y vuelve a conectarlo (una vez de forma inmediata, otra esperando a que la imagen se congele)

Vamos, que solo me falta el látigo. :-/



Saludos

chiruk_latin 27/04/2005 21:06

yo quiero hacerles una pregunta....
yo estoy con lo del CS y resulta que el router no me deja descargar cosas de internet a velocidad rasonable lo maximo 5KB y ya le abri los port y todo eso pero nada , que pasa si desconecto el router y conecto directo mimodem con mi PC ???? abra problemas despues para conectarme con el CS??

gracias y saludos

Maikeln 27/04/2005 21:21

en un principio creo que no, pero deberias de mirar eso de los 5kb

chiruk_latin 27/04/2005 22:40

a que te refieres con mirar lo de los 5KB????

gracias por la pronta respuesta

Maikeln 28/04/2005 06:46

me parecio poca velocidad esa conexion, por nada mas, por lo del router y demas.

chiruk_latin 28/04/2005 22:18

aha ok , ami tambien me parece raro siendo que tengo 8 mb

don_80 10/05/2005 20:14

Hola amigos,no quiero meterme y dar la lat, pero....

Ya que las actualizaciones no funcionan, se dice que la camd3735 lo hace, pero a mi no me funciona.
Diria que utiliza la camd3 3715 que funciona el cs dpm!
Y como yo compro los partidos de el barca y< el madrid de antemano con el deco original, funciona estupendamente!

Saludos

Pete 10/05/2005 23:44

don_80, ¿entiendo que dices que con camd3 3.715 puedes ver los eventos PPV comprados en tu azulita en la Dream?
Nunca he usado este EMU, ¿puedes poner como configurarlo para usar los tarjeteros?

Saludos.

Pete 11/05/2005 00:12

Me contesto yo solo, hay que editar el camd3.config:

PORT=24110
DEBUG=2
CONSOLE=1
USERS=/var/keys/camd3.users
SERVERS=/var/keys/camd3.servers
KEYS=/var/keys/camd3.keys
#SOCKET=/tmp/camd.socket
SLOT=/dev/sci1:2:1:1:1:998:slotoben:password2
SLOT=/dev/sci0:2:1:1:1:999:slotunten:password3


Saludos.

Ordep 11/05/2005 12:29

[B]#chiruk_latin, quizás esto te de una pista. Por consumo de recursos y de mayor a menor: primero el cardsharing, luego el Spider y por último gbox. Por consumo me refiero al ancho de banda que consumen(valga la redundancia), c/u de los programas antes mencionados. De todas formas, se ve claramente que tienes un problema con la config. de tú router o modem adsl. Saludos [/B]

pikip 11/05/2005 14:16

Tenia entendido que cardspider consumia mucho más ancho de banda de cardsharing (porque las peticiones se envian a todos y cada uno de tus peers).

don_80 13/05/2005 15:21

No, no me entiendas mal:
La camd3 funcioa para el cs muy bien. por no decir estupenda!
los ppv hay que comprarlos en el deco original.
hasta ahora no se que funcione, le pregunte al maestro doz de cuando va a venir este feature, pero de momento a esperar.
ya casi solo queda para cs la vieja newcamd528, la gpre17 y la camd3.


La franja horaria es GMT +2. Ahora son las 04:33.

Powered por vBulletin™ Version 3.8.10
Copyright © 2024 vBulletin Solutions, Inc. All rights reserved.
Traducido por vBsoporte - vBulletin en español
ZackYFileS - Foros de Debate