HOW TO ESTABLISH A LAN CARDSHARING PROCESS <"CCcam Protocol"> BETWEEN 2 DMBoxes

[arboristman]

c/p



HOW TO ESTABLISH A LAN CARDSHARING PROCESS <"CCcam Protocol"> BETWEEN 2 DMBoxes
Quote:
HOW TO ESTABLISH AN INTERNAL (LAN) CARDSHARING PROCESS , BASED ON "CCcam <Server/Client> Protocol" , BETWEEN 2 DMBoxes :
A COMPLETE GUIDE + CASE STUDY (Encryption system : ******** 2 / CAId : 0x500)
THE BELOW TUTORIAL IS FOR EDUCATIONAL REASONS ONLY (REPRODUCTION PROHIBITED WITHOUT PERMISSION)



Quote:
INTRODUCTION NOTE
- THE FOLLOWING INSTRUCTIONS ARE VALID :
i> FOR ALL DMBox Models (DREAM MULTIMEDIA "FAMILY" - DM 500/600PVR/7000/7020/7025). HOWEVER , FOR PRACTICAL REASONS , TWO (2) OF THEM WERE CHOSEN TO BE TESTED : a> THE "Best Seller" DM 500s ("CARDSERVER") & b> THE LATEST DM 7025s ("CLIENT")
ii> FOR ANY VERSION OF "CCcam" Emulator USED (THE LATEST VERSION IS "CCcam 2.0.3" + THE ASSOCIATED Configuration File "CCcam Config")
iii> FOR ANY FIRMWARE'S RELEASE INSTALLED (Linux OS/GP2 Project - Latest Versions : GP2 4.00 <Cardserver> & GP2 3.00 <Client>)

- MODEM-ROUTER USED DURING THE "CARDSHARING PROCESS" : DRAYTEK'S Security Router "VIGOR 2800 ADSL 2/2+" (VERY STABLE ,
FUNCTIONAL & FULLY SUPPORTED BY VARIOUS FIRMWARE OFFICIAL VERSIONS , DEVELOPED ACCORDING TO THE LOCAL DSLAM INSTALLED IN DIFFERENT COUNTRIES).
Quote:
{Information Link : Products Center -- Vigor2800}
{Support Center Link : Support Center -- FAQ}
{Documentation , Tools & Firmware Upgrade Link : Support Center -- Downloads}
Quote:
A> NECESSARY EQUIPMENT FOR A LAN CONNECTION
1> ADSL CONNECTION (over PSTN or ISDN)

2> Modem-Router ADSL 2/2+ (Annex A or Annex B) with at least 2 ETHERNET ports {Desktop PC + Cardserver <DMBox 500/600PVR/7000/7020> OR Desktop PC + Client <DMBox 7025>}

3> Ethernet Cables RJ-45 (cat. 5 or cat. 6)

4> DMBox 500/600PVR/7000/7020 <CARDSERVER>

5> DMBox 7025 <CLIENT>

6> A WINDOWS Based PC (MS WINXPPRO + SP2) with 10/100 MBit Compatible Ethernet Interface and an "FTP Client" application installed ("FILEZILLA CLIENT 2.2.32")

7> An Official ******** 2 Card (CAId : 0x500)


Quote:
B> PRELIMINARIES
Quote:
HOW TO CONNECT THE DMBoxes TO THE PC AND TO THE INTERNET
I> USING THE Dynamic Host Configuration Protocol (DHCP) , via the Modem-Router

i> Go to the configuration interface of your MODEM and ENABLE the DHCP Option.

LAN/General Setup/DHCP Server Configuration : Activate (CHECK) the "Enable Server" Option

The Modem-Router is now the default Internet Gateway which acts as a DHCP Server , in order to automatically distribute to each device of
the LAN (PC , DMBox) its own <Internal> LAN IP Address.

ii> Connect the PC and the DMBox to the modem-router , via cables RJ-45 (Ethernet Cables)

iii> Configurations on the DMBoxes

- DM 500/600PVR/7000/7020 {CARDSERVER'S IMAGE (img/nfi) : GP2 V. 4.00}

Go to Menu/Mainmenu/Setup/Expert setup/Communication Setup :
*ENABLE (CHECK) the "DHCP" Option and CONFIRM the options : a> "Enable Network" & b> "Enable Online-Test" (Checkmarks)
*Connection Type : LAN
*Port : 80
Green button to SAVE the above configurations

- DM 7025 {CLIENT'S IMAGE (nfi) : GP2 V. 3.00}

a> Go to Menu/Setup/System/Network/Device Setup/Select Network Adapter/eth 0 :
* "Use DHCP" : YES
PRESS the OK button to confirm the choice

b> Go to Menu/Setup/System/Network/Nameserver Setup :
* "Nameserver 1" (DNS Server 1) : The Internet Service Provider's Primary (Public) IP Address
* "Nameserver 2" (DNS Server 2) : The Internet Service Provider's Alternative (Public) IP Address

iv> Configurations on the Desktop PC :

Start/Control Panel/Network Connections/Local Area Connection/Properties/Internet Protocol (TCP/IP)/Properties :
- CHECKMARK the following options : "Obtain an IP address automatically" & "Obtain DNS server address automatically"
- Go to Advanced/Default gateways : ADD the Router's LAN IP address

II> USING Personalized settings

1> DO NOT ACTIVATE the Router's DHCP Server capability <OPTIONAL>

2> For the DMBoxes (GP2 Firmware Releases/Linux OS)

- DM 500/600PVR/7000/7020 {CARDSERVER'S IMAGE (img/nfi) : GP2 V. 4.00}

Go to Menu/Mainmenu/Setup/Expert setup/Communication Setup :

DO NOT ENABLE/ACTIVATE the Receiver's DHCP Option (so that you can manually assign to the DMBox the LAN IPAddress of your choice , EVEN IF THE ROUTER'S DHCP SERVER CAPABILITY IS ACTIVATED)

* The elements to be modified are the following :
- IP Address : Assign to the DMBox/Server a Local IP address starting from 192.168.xxx.xxx , because this type of address is "private" and cannot be refound on the Network
- Nameserver (DNS Server) : Set the Primary (Public) IP address of your ISProvider. You could also set the Local Internal <LAN> IP address of the Modem-router. It's up to you.
- Gateway : Set the Local <LAN> IP address of the Modem-router
- CONFIRM the options : a> "Enable Network" & b> "Enable Online-Test" (Checkmarks)
** Netmask : 255.255.255.0 (by DEFAULT)
*** Connection Type : LAN
**** Port : 80
PRESS the Green button to SAVE the above configutations.

- DM 7025 {CLIENT'S IMAGE (nfi) : GP2 V. 3.00}

a> Go to Menu/Setup/System/Network/Device Setup/Select Network Adapter/eth 0 :
* "Use DHCP" : NO (so that you can manually assign to the DMBox the LAN IPAddress of your choice , EVEN IF THE ROUTER'S DHCP SERVER CAPABILITY IS ACTIVATED)
* IP Address : Assign to the DMBox/Client a Local IP address starting from 192.168.xxx.xxx , because this type of address is "private" and cannot be refound on the Network
* Netmask : 255.255.255.0 (by DEFAULT)
* Use a Gateway : YES
* Gateway : Set the Local <LAN> IP address of the Modem-router
PRESS the OK button to confirm the choices & to activate the settings

b> Go to Menu/Setup/System/Network/Nameserver Setup :
* "Nameserver 1" (DNS Server 1) : The Internet Provider's Primary (Public) IP Address
* "Nameserver 2" (DNS Server 2) : The Internet Provider's Alternative (Public) IP Address

3> For the PC (Operating System : "MS Windows XP Pro + SP2")

Start/Control Panel/Network Connections/Local Area Connection/Properties/Internet Protocol (TCP/IP)/Properties :
- CHECK the option "Use the following IP address" and set :
i> IP address : 192.168.xxx.yyy
ii> Subnetmask : BY DEFAULT , 255.255.255.0
iii> Default gateway : the Local IP address of the Modem-router (192.168.xxx.zzz)
- CHECK the option : "Use the following DNS server addresses" and set as "preferred" & "alternate" the Public IP addresses (primary and secondary) of your ISProvider

FOR EXAMPLE :
Quote:
*Router's Local Internal <LAN> IP address : 192.168.1.1
*PC's Local Internal IP address : 192.168.1.2
*Default Gateway = the Router's <LAN> IP address : 192.168.1.1
*DNS server addresses : ISP's main & alternative public IP addresses OR the Router's (Gateway) Local IP address (192.168.1.1)

**Cardserver's <DM 500/600PVR/7000/7020> LAN (Local) IP Address : 192.168.1.3
**Client's <DM 7025> LAN (Local) IP Address : 192.168.1.4
**Gateway : 192.168.1.1 (the router's Local IP address)
**Nameserver (DNS Server) : ISP's main & alternative IP addresses OR the Router's (Gateway) LAN IP address (192.168.1.1)

Quote:
C> HOW TO ESTABLISH A LAN "CARDSHARING PROCESS" BETWEEN 2 DMBoxes : CASE STUDY (******** 2 CARD <CAId : 0x500>)
- DMBox 500 : CARDSERVER
- CARDSERVER'S IMAGE (img) : GP2 V. 4.00 MaxVar
- CARDSERVER'S LAN (Local) IPAddress : 192.168.1.3
- CARDSERVER'S Username / Password : server / svrpass

- DMBox 7025 : CLIENT
- CLIENT'S LAN (Local) IPAddress : 192.168.1.4
- CLIENT'S IMAGE (nfi) : GP2 V. 3.00
- CLIENT'S Username / Password : user / usrpass

- Protocol to use during the Cardsharing process : "CCcam 2.0.3-Complete" Emu

Quote:
a) CARDSERVER <DM 500> & CCcam Protocol {"CCcam 2.0.3" : Cardserver Emu}
- Blue Panel/Addons/Download (Gemini-Server)/Cam/"CCcam 2.0.3-Complete"
- Blue Panel/Addons/Download (Gemini-Server)/Cam-Configs/"CCcam-Config 2.0.3"
- Blue Panel/Right-Left Buttons/Selection of the "CCcam 2.0.3" Emu /
Green Button (Stop/start Cam) to activate the selected Emu

- Download (SourceForge.net: Files) & Install on your PC the "Filezilla 2.2.32 FTP Client" application (the "setup.exe" File for 32-bit Windows).

Run the "Filezilla 2.2.32 FTP Client" :
* Address = the receiver's LAN IPAddress : 192.168.1.3 [you can get the information from : Menu/Mainmenu/Setup/Expert setup/Communication Setup]
* User : root
* Password : dreambox
* Port : 21
PRESS "Quickconnect"

- Go to var/etc/ and download from the DM 500 straight to your PC (double click or drag & drop) the "CCcam cfg" file. Open it with WordPad.

Just add the following F ("Friend/Client") Command Line :

F: <ClientUsername> <Clientpwd> <MaxUphopsLimit> <ShareEmus> <AllowEmm> <DownshareLimitsPerShare>
<DownshareLimitsPerShare>{based on caid:id:sid}

* ClientUsername : user
* Clientpwd : usrpass
* MaxUphopsLimit ("Cascading") = 0,1,2,3,4,5 (DEFAULT=5)
- If Uphops = 0 , the Friend/User <CLIENT> gets ONLY the Administrator's LOCAL CARDS
- If Uphops = 1,2,3,4,5 , the Friend/User <CLIENT> gets ALL Administrator's CARDS at a maximum of 1,2,3,4,5 hops away. In other words , the Client is allowed (by the Administrator) to share the Card down to other clients {1,2,3,4,5 further levels beyond his own}
- In case of NO APPEARANCE of the "Uphops" parameter in the "F" Line , the command is still valid and preconfigured by the "CCcam-Team" at the DEFAULT VALUE (=5)
* ShareEmus = 0 , 1 {Optional}
- If ShareEmus = 0 , the Client gets NO Emus
- If ShareEmus = 1 (DEFAULT) , the Client receives Emu shares {the corresponding C Line on Client must have a "yes" entry in
the "wantemus" parameter}
* AllowEmm = 0 , 1 {Optional}
- If AllowEmm = 0 , the Client is not allowed to send to the Administrator Emm (Key updates)
- If AllowEmm = 1 (DEFAULT) , the Client is allowed to send Emm (Key updates)
* DownshareLimitsPerShare {Optional}
* DownshareLimitsPerShare <based on caid:id:sid> {Optional}

** The SHARE/LISTEN (TCP) PORT : The ServerPort = 12000 (by DEFAULT)

The Server's (DM 500) Cardreader Slot "recognizes" the Smartcard's CAId (0x500/********) , so there's NO NEED for additional configuration {Server's LAN Ip Address / Server's name / Server's pwd}. In other words , there's NO NEED for the Administrator to add a C ("Connection/Client") Command Line , in order to allow to the Server to connect to itself via the SharePort. Anyway , EVEN IF IT'S USELESS , you could add the following C ("Connection/Client") Line :

C: <ServerIpAddress> <ServerPort> <ServerUsername> <Serverpwd> <WantEmus>{yes-optional}

* ServerIpAddress : 192.168.1.3 (LAN)
* ServerPort : 12000 (by default)
* ServerUsername : server
* Serverpwd : svrpass

This is how the CARDSERVER'S (DM 500) "CCcam cfg" file must look like :
Quote:
"CCcam cfg - Wordpad"

F: user usrpass
{C: 192.168.1.3 12000 server svrpass yes} <OPTIONAL>
SERVER LISTEN PORT : 12000
INFO LISTEN PORT : 16000
HTML INFO LISTEN PORT : 16001
ZAP OSD TIME : 0
OSD USERNAME : root
OSD PASSWORD : dreambox
SHOW TIMING : yes
MINI OSD : yes
DEBUG : yes
DISABLE EMM : yes
EXTRA EMM LEVEL : yes
SOFTKEY FILE : /var/keys/SoftCam.Key
AUTOROLL FILE : /var/keys/AutoRoll.Key
STATIC CW FILE : /var/keys/constant.cw
CAID IGNORE FILE : /var/keys/CCcam.ignore
LOG WARNINGS : /tmp/warnings.txt
According to the above settings of the "F" Line , the Friend/User <CLIENT> :
- gets all administator's shares at a MAXIMUM distance of 5 hops away (the administrator's local cards + max 5 hops away). In other words , he is allowed to share down to his own Friends/Clients
- is also able to receive emu shares {the corresponding "C" Line on Client's "CCcam cfg" file has a "yes" entry in the "wantemus" parameter}
- is allowed to send to the administrator emm.

Close the session and upload from the PC straight to the DM 500 (var/etc) the modified "CCcam cfg" file.
BLUE PANEL/SELECTION of the "CCcam 2.0.3" EMU/GREEN BUTTON : stop/start "CCcam 2.0.3" emu to reactivate and apply the modifications.

There are SEVERAL , EQUALLY VALUABLE , COMBINATIONS between <ShareEmus> , <AllowEmm> and <DownshareLimitsPerShare> parameters. That's why , you must read carefully the explanations appearing in the configuration options of "CCcam-Config" file and define the rules of the Cardsharing Process according to your own needs (personalized settings).

Those are the official Configuration Options/Settings of the "CCcam cfg" File {"CCcam-Config"/CCcam Protocol} , according to the "CCcam-Team" :
Quote:
################################################## ####################
# friends #
################################################## ####################
# syntax for to add a friend user to CCcam with the max up hops limit (default = 5)
# sharing of emus (default = 1), allow emm (default = 1), and optional
# downshare limits per share (default = no limits) and optional
# downshare limits per share based on caid:id:sid
# and optional timeslots in which share is valid (to block channels on box of children after 19:00 for instance)
# if no timeslot is defined 24 hrs a day is used
# emus are shared only one level down, even if no limits given
#
# max username length 20
# password length 'unlimited'
#
#F: <username> <password> <uphops> <shareemus> <allowemm> ( { caid:id(:downhops), caid:id(:downhops), ... }
#{ caid:id:sid, caid:id:sid, ... } { begintime-endtime, ... } ) hostname/ip address
#
# example:
#
# F: user1 pass1
#
# user1 gets all our shares at max 5 hops from us
# (our local cards + max five hops away). He can share down to his own
# clients. He also receive emu shares (if he has 'yes' behind his C: entry),
# and is allowed to send us emm.
#
# F: user2 pass2 0 1 0 { 0100:000080, 0622:000000:1, 0500:000000:2 }
#
# user2 gets only our local cards but no 0100:000080.
# and our 0622:000000 cards only for himself (1 hop down),
# and 0500 cards for himself plus one additional hop down.
# He also gets our emus, and is NOT allowed to send us emm (updates).
#
# F: user3 pass3 5 0 1 { 0:0:3, 0100:000080:1 }
#
# user3 gets all cards at a maximum of 5 hops away from us,
# and get's to share them down two further levels beyond his own level.
# But he is not allowed to share 0100:000080 down to other users.
# He gets no emus from us, and he is allowed to send us emm.
#
# F: user4 pass4 5 0 1 { 0:0:3, 0100:000080:1 } { 0100:000080:15df }
#
# user4 gets all cards at a maximum of 5 hops away from us,
# and get's to share them down two further levels beyond his own level.
# But he is not allowed to share 0100:000080 down to other users.
# He gets no emus from us, and he is allowed to send us emm.
# He is also not allowed to view channel 0100:000080:15df
#
# F: user4 pass4 5 0 1 { } { } { 12:00-17:00, 19:00-20:00 }
#
# user4 gets all cards at a maximum of 5 hops away from us,
# and get's to share them down two further levels beyond his own level.
# the share is only valid between 12:00 and 17:00 and between 19:00 and 20:00
# outside these hours the share will not give cw's to the client
#
#
# F: user5 pass5 5 1 1 { } { } { } 192.168.1.1
#
# user5 gets all cards at a maximum of 5 hops away from us
# user5 is only allowed to connect from the host 192.168.1.1
#

################################################## ####################
# connections #
################################################## ####################
# syntax for to add a client connection to other CCcam
# add yes on end to use friends emus (non public private key/emu,etc...),
# but only works when corresponding F line on server has '1' for <shareemus>
# optional limits just like F line, but for incoming shares (ignore shares more than 'uphops' away)
#
#C: <hostname> <port> <username> <password> <wantemus> ( { caid:id(:uphops), caid:id(:uphops), ... } )
#
#note: if {} limits are added, <wantemus> cannot be omitted. Use either yes or no.
#
# example:
#
# C: someserver.somedomain 12000 user1 pass1
# C: 192.168.1.2 12000 user2 pass2
# connects to CCcam without use of friends emus
#
# C: 192.168.1.2 12000 user3 pass3 yes
# connects to CCcam, and receives friends emus also.

# syntax for to add newcamd server connection
#
#N: <ip> <port> <username> <pass> <des(14byte)> <nr_of_hops_away (default: 1)> <stealth mode (default: 0)>
#
# example:
#
# N: 127.0.0.1 10000 dummy dummy 01 02 03 04 05 06 07 08 09 10 11 12 13 14
#
# add a newcamd card, give it an offset of 2 hops, in the share list
#
# N: 127.0.0.1 10000 dummy dummy 01 02 03 04 05 06 07 08 09 10 11 12 13 14 2
#
# stealthy login on newcamd server:
#
# N: 127.0.0.1 10000 dummy dummy 01 02 03 04 05 06 07 08 09 10 11 12 13 14 1 1
#
# stealth modes: 0 = disabled, 1 = mgcamd new, 2 = mgcamd old, 3 = evocamd, 4 = generic

# syntax for to add radegast server connection
#
#R: <ip> <port> <ca4> <id6> <nr_of_hops_away (default: 1)>
#
# example:
#
# R: 127.0.0.1 678 0100 000080

# syntax for to add camd3 connection
#
#L: <ip> <port> <username> <pass> <ca4> <id6> <nr_of_hops_away (default: 1)>
#
# example:
#
# L: 127.0.0.1 567 dummy dummy 0100 000080

# syntax for add gbox connection
#
#G: <pass> <localhost> <localport> <peerpass> <peeraddress> <peerport>
#
# support optional limits just like C line (ignore shares more than 'uphops' away)
# { caid:id(:uphops), caid:id(:uphops), ... }
#
# example:
#
# G: AABBCCDD my.address.tv 2500 12345678 peer.address.tv 2500

################################################## ####################
# Other config settings #
################################################## ####################
# server shall listen on this port pro incoming connections
# default port is 12000, disable server with parm -s or set port 0
#
#SERVER LISTEN PORT : 12000

# server can give some info about server and client connections
# and cardinfo using telnet or webbrowser.
#
# Switch on/off access to info
# default is yes
#
#ALLOW TELNETINFO: no
#ALLOW WEBINFO: no

# The webinfo service can be protected with a username and password.
# This is switched off by default
#
#WEBINFO USERNAME : <username>
#WEBINFO PASSWORD : <password>

# The telnetinfo service can be protected with a username and password.
# This is switched off by default
#
#TELNETINFO USERNAME : <username>
#TELNETINFO PASSWORD : <password>

# default port for telnet is 16000
# default port for web is 16001
# supported commands:
# info
# activeclients
# clients
# servers
# shares
# providers
# entitlements
# example use:
# echo servers | telnet localhost 16000
# go with your browser to http://ip_CCcam_server:16001
#
#TELNETINFO LISTEN PORT : 16000
#WEBINFO LISTEN PORT : 16001

# time in seconds to keep On Screen Display active.
# default is 0 (turned off)
#
#ZAP OSD TIME : 3

# username used to show popup (default : root)
#OSD USERNAME : root

# password used to show popup (default : dreambox)
#OSD PASSWORD : dreambox

# port used to show popup (default : 80)
#OSD PORT : 80

# Serial reader config. Add as many as you have attached too your system
# replaces old name 'PHOENIX READER PATH', but still works.
# default is none
# optionally add readertype : phoenix,mouse,uniprog,sc8in1,smartreader+
# (when non readertype given defaults to uniprog (e.g. for mastera))
#
# SERIAL READER : <device> <type>
#
# example
#
#SERIAL READER : /dev/tts/0

# Serial reader smartcard write delay.
# Setting to finetune smartcard write speed, optimal setting depends on speed of system, and
# speed of card. Default value is calculated, but can overrule by setting.
# Use number of microseconds delay between bytes, 0 = no delay, -1 = calculated default
# Note: huge difference between values 0 and 1, because of schedular overhead
#
# SMARTCARD WRITE DELAY : <device> <delay>
#
# example, 10ms write delay on smartcard in reader attached to /dev/ttyUSB0
#
#SMARTCARD WRITE DELAY: /dev/ttyUSB0 10000
#
# NOTE on sc8in1; because 8 smartcards are used on the same devicename, use
# devicename_0 .. devicename_7 for settings which require devicename to make
# settings per smartcard. example /dev/ttyS0_0, /dev/ttyS0_1 ..
# example, 8ms write delay between bytes to smartcard on last sc8in1 channel, attached to /dev/tts/0
#
#SMARTCARD WRITE DELAY: /dev/tts/0_7 8000

# Smartcard clock speed override
# Setting override specified speed for smartcard.
# Don't add setting unless you're sure what you're doing.
# In 99% of the cases the reader selects the optimal speed.
# Adding this setting either slows your card down, or might destroy it.
#
# SMARTCARD CLOCK FREQUENCY : <device> <freq>
#
# example
#
#SMARTCARD CLOCK FREQUENCY: /dev/ttyUSB0 5500000

# if timing should be shown in OSD and debug output
# default is no (turned off)
#
#SHOW TIMING : yes

# enables mini OSD which shows server(type), cardreader, keys or fta only
# default is no (turned off)
#
#MINI OSD : yes

# turns debugging on and off
# default is no (turned off)
#
#DEBUG : yes

# should CCcam try to read and parse newcamd.conf for server connections
# default is no (turned off)
#
#NEWCAMD CONF : yes

# configure what EMM blocker you want. Add as many as readers you have attached
# default is blocking nothing
#
# B: /dev/sci0 01
# 00 - nothing
# 01 - sa blocked
# 02 - ua blocked
# 04 - ga blocked
# and sum of for combinations
#
#examples
#
#B: /dev/tts/0 07
#B: /dev/sci0 01

# disable all local EMM readers
# saves lots of CPU, but you won't get any updates anymore
# (unless you get updates from your clients)
#
# default: no
#
#DISABLE EMM : yes

# with this setting you can
# allow a client on two hops away
# to send the updates to the cardserver
#
# default : no
#
#EXTRA EMM LEVEL : yes

# overrule the *** boxkey (4 byte hex)
#
# BOXKEY: <device> <byte1> <byte2> <byte3> <byte4>
#
#example
#
#BOXKEY: /dev/sci0 00 11 22 33

# set card pin
# * please be very careful with this option as you could lock your card *
#
# PIN: <device> <pin>
#
#example
#
#PIN: /dev/sci0 1234

# overrule the ****** camkey (8 byte hex), default 11 22 33 44 55 66 77 88
#
# CAMKEY: <device> <byte1> <byte2> <byte3> <byte4> <byte5> <byte6> <byte7> <byte8>
#
#example
#
#CAMKEY: /dev/sci0 11 22 33 44 55 66 77 88

# overrule the ****** camdata (64 byte hex)
# trailing zero bytes can be omitted
# default for unknown ASC's is 11 22 33 44 55 66 77 88 00 00 .. 00, known ASC's have other defaults
#
# CAMDATA: <device> <byte1> <byte2> <byte3> <byte4> <byte5> <byte6> ... <byte64>
#
#example, when only the first 15 camdata bytes are nonzero
#
#CAMDATA: /dev/sci0 11 22 33 44 55 66 77 88 99 aa bb cc dd ee ff

# custom add id's for BEEF patched cards
#
# BEEF ID: <ident1> <ident2> <ident3> <ident4> <ident5> <ident6> <ident7> <ident8> <device>
#
#example
#
#BEEF ID: 4101 0 0 0 0 0 0 0 /dev/sci0

# what Softcam.Key should CCcam try to read
# defaults to /var/keys/SoftCam.Key
#
#SOFTKEY FILE : /var/keys/SoftCam.Key

# what AutoRoll.Key should CCcam try to read
# defaults to /var/keys/AutoRoll.Key
#
#AUTOROLL FILE : /var/keys/AutoRoll.Key

# what constant.cw should CCcam try to read
# defaults to /var/keys/constant.cw
# file content can be like
#
# ca4:id6:sid4mtpid4:ecmpid4:key16(01 02 03...)
#
#STATIC CW FILE : /var/keys/constant.cw

# in this file you can configure what CAIDs CCcam should prefer or ignore
# defaults to /var/etc/CCcam.prio
# file content can have ignores (I) and prio lists (P)
#
# note 1: I line affects both for ecm and emm (receive no emm on ignored systems)
# P line only affects ecm choice (emm still received for all available systems, not just the priority system)
#
# note 2: ident 0 means 'all idents'. So 'caid:0' is the same as 'caid'.
#
# note 3: for some systems (e.g. nagra (caid 18xx)), the ident is not known at the time the
# prio lists are checked. In that case, matching is done on caid only, even if the P line
# defines nonzero idents. So for example '1801:401' behaves the same as '1801' in a P line
# I lines work differently, they are checked two times, once before ecm or emm is received, again
# after ecm or emm are received (and nagra ident should be known)
# P lines are only checked once, before ecm received.
#
# note 4: if a P line contains caid:ident pairs which are not available for the current
# channel, that P line is not used for that channel.
# Example, channel has systems 626, 1801:401 then P line with "1801,100:96,626" is ignored by that channel,
# because channel doesn't have 100:96.
# But P line with "1801" works, and also "626,1801" will work for channel
#
# note 5: P lines are parsed in the order in which they are found in the prio file.
# Only the first matching P line is used
#
# situation 1: ignore allways this caid, all idents, on all channels
# I: caid
#
# situation 2: ignore allways this caid/ident pair
# I: caid:ident
#
# situation 3: ignore this caid/ident pair, on channel 'sid'
# I: caid:ident:sid
#
# situation 4: when both caid1 and caid2 exist for a channel, prefer caid1 over caid2
# P: caid1, caid2
#
# situation 5: when caid1:ident1 till caidN:identN exist for a channel, use them in order of this list.
# P: caid1:ident1, caid2:ident2, .., caidN:identN
#
# situation 6: when caid1:ident1 till caidN:identN exist for channel 'sid', use them in order of this list.
# Sid on first caid/ident pair identifies sid for which list is used. All other sids ignore this list.
# P: caid1:ident1:sid, caid2:ident2, .., caidN:identN
#
#CAID PRIO FILE : /var/etc/CCcam.prio

#
# In this file all provider idents are defined
# The info from this file is being used in the web interface
# format:
# <caid><ident> "Provider description"
#
# PROVIDERINFO FILE : /var/etc/CCcam.providers

#
# In this file all channel idents are defined
# The info from this file is being used in the web interface
# format:
# caid:ident:sid "Channel description"
#
# CHANNELINFO FILE : /var/etc/CCcam.channelinfo

# write wrong logins to file
# defaults is off
#
#LOG WARNINGS : /tmp/warnings.txt

# global setting for stealthy login to newcamd/newcs server, N line can overrule
# stealth modes: 0 = disabled, 1 = mgcamd new, 2 = mgcamd old, 3 = evocamd, 4 = generic
# default: 0
#
#NEWCAMD STEALTH : 0

# load balancing between identical cards, list device names of card readers containing identical cards,
# optionally followed by a list of service id's which are to be excluded from loadbalancing
#
# LOADBALANCE : <device1> <device2> .. <devicen> { <exceptsid1>, <exceptsid2> .. , <exceptsidn> }
#
# multiple loadbalance groups can be configured, by adding multiple lines
# warning: restart is required, when loadbalance group config changes
#
#example 1: load balance requests for three identical cards
#
# LOADBALANCE : /dev/ttyS0 /dev/ttyS1 /dev/ttyS2
#
#example 2: load balance requests for two almost identical cards, sid 0df3 and 0de1 are only available
#on one of the cards, so requests for these sids shouldn't be loadbalanced
#
# LOADBALANCE : /dev/ttyS5 /dev/ttyS6 { 0df3,0de1 }

# in version 1.2.1 and lower there was a problem which could lead to disconnecting clients
# in version 1.4.0 network load was significantly reduced
# in version 1.7.0 dangerous password bug was fixed
# in order to take advantage of these fixes, all clients should upgrade
# with this setting you can force that clients at least use a certain version otherwise they are denied when logging in
#
# default : accept all versions
#
#example 1: avoid disconnecting clients problem
#
#MINIMUM CLIENT VERSION : 1.3.0
#
#example 2: achieve network load decrease
#
#MINIMUM CLIENT VERSION : 1.4.0
#
#example 3: don't allow potentially wrong passwords (pre 1.7.0 has password bug)
#
#MINIMUM CLIENT VERSION : 1.7.0

# ****** smartcards: option to disable smart chid checking for ****** smartcards.
# Default, only chids advertised by card are accepted.
# This avoids a lot of unwanted card traffic
#
# But if smartcard has hidden/unknown chids, all chids should be tried.
# In that case specify 'TRY ALL CHIDS' option for cardreader.
# Use with care, enabling option causes more card traffic.
# Only use setting when some channels don't work without it.
# note: if even this setting don't help decode all channels, try using
# commandline arg -l, to disable all self-learning features (warning: slower)
#
#TRY ALL CHIDS : <device>
#
#example: card in /dev/ttyUSB0 gets ecm for all possible chids, not
#just the chids it officially supports
#
#TRY ALL CHIDS : /dev/ttyUSB0

# perform smartcard post init commands
#
# POSTINIT <device> <filename> (<autodelete>)
#
# send commands in 'filename' to 'device', and delete 'filename' when
# optional 'autodelete' argument nonzero
#
#example:
#
#POSTINIT /dev/sci0 /tmp/postinit
#
#example /tmp/postinit contents:
#c134000003000000
#c13201000a

# Option to override autodetected dvb api version. Restart needed.
#
#DVB API: <value>
#
# <value> <1 = no dvb, 1 = dvb api 1, 3 = dvb api 3
#
# WARNING: only use when autodetect fails!
#
#example, disable nonworking dvb hardware:
#DVB API: -1
Quote:
b) CLIENT <DM 7025> & CCcam Protocol {"CCcam 2.0.3" : Client Emu}
- Blue Panel/Addons/Download/Download (Gemini-Server)/Cam/"CCcam 2.0.3-Complete"
- Blue Panel/Addons/Download/Download (Gemini-Server)/Cam-Configs/"CCcam-Config 2.0.3"
- Blue Panel/Right-Left Buttons/Selection of the "CCcam 2.0.3" Emu/Green Button (Stop/start Cam) to activate the selected Emu
- Download (SourceForge.net: Files) & Install on your PC the "Filezilla 2.2.32 FTP Client" application (the "setup.exe" File for 32-bit Windows).

Run the "Filezilla 2.2.32 FTP Client" :
* Address = the receiver's LAN IPAddress : 192.168.1.4
a> IF THE RECEIVER'S DHCP Option IS DISABLED , you can get the information from :
Menu/Setup/System/Network/Device Setup/Select Network Adapter/eth 0/"IP Address"
b> IF THE RECEIVER'S DHCP Option IS ACTIVATED , you can get the information from ROUTER'S Configuration Interface :
Diagnostics/ARP Cache Table/Ethernet ARP Cache Table/"IP Address" & "MAC Address"
* User : root
* Password : - (for the DM 7025 there's no need for pwd-however you can type "dreambox")
* Port : 21
PRESS "Quickconnect"

- Go to /etc/ and download from the DM 7025 straight to your PC (double click or drag & drop) the "CCcam cfg" file. Open it with WordPad. Just add the following C ("Connection/Client") Line :

C: <Server's LAN IPAddress> <ServerPort> <ClientUsername> <Clientpwd> <WantEmus>{yes-optional}

* Server's LAN IPAddress = 192.168.1.3
* ServerPort = the SHARE PORT = 12000 (by default)
* ClientUsername = user
* Clientpwd = usrpass
* WantEmus = yes {Optional , but necessary if the Client desires to activate the "ShareEmus" option (on the Server's F Line)}

This is how the CLIENT'S (DM 7025) "CCcam cfg" file must look like :
Quote:
"CCcam cfg - Wordpad"

C: 192.168.1.3 12000 user usrpass yes
SERVER LISTEN PORT : 12000
INFO LISTEN PORT : 16000
HTML INFO LISTEN PORT : 16001
ZAP OSD TIME : 0
OSD USERNAME : root
OSD PASSWORD : dreambox
SHOW TIMING : yes
MINI OSD : yes
DEBUG : yes
DISABLE EMM : yes
EXTRA EMM LEVEL : yes
SOFTKEY FILE : /var/keys/SoftCam.Key
AUTOROLL FILE : /var/keys/AutoRoll.Key
STATIC CW FILE : /var/keys/constant.cw
CAID IGNORE FILE : /var/keys/CCcam.ignore
LOG WARNINGS : /tmp/warnings.txt
Close the session and upload from the PC straight to the DM 7025 (/etc) the modified "CCcam cfg" file.
BLUE PANEL/SELECTION of the "CCcam 2.0.3" EMU/GREEN BUTTON : stop/start "CCcam 2.0.3" emu to reactivate and apply the changes.

The LAN Cardsharing Process is about to begin , thanks to the powerful "CCcam <Client-Server> Protocol" (Latest Version :"CCcam 2.0.3-Complete" Emu) and its various configuration options (via the associated "CCcam-Config" file).

CONCLUSIONS :
a>
Quote:
The "CCcam" Emu can be used , AT THE SAME TIME , as a "Cardserver" (on DM 500) and as a "Client" Emulator (on DM 7025). Via its configuration options , it can be totally compatible with other "Camd Server-Protocols" (Newcamd/Camd3.8xx/Radegast/NewCS/GBox) and contributes to the establishment of a successful & fully operational cardsharing process.
b>
Quote:
EVERY USER WHO WISHES TO PARTICIPATE IN A CARDSHARING PROCESS (BASED ON "CCcam" Protocol) AS A "Client" , MUST DOWNLOAD , INSTALL & ACTIVATE (VIA THE BLUE PANEL) THE "CCcam" Emulator + THE ASSOCIATED Configuration File.
THE USER/"CLIENT" HAS TO "OPEN" THE "CCcam cfg" FILE (THE Configuration File ASSOCIATED TO THE "CCcam-Client" Emulator) , IN ORDER TO ADD A "C" COMMAND LINE ("C" : CLIENT)
c>
Quote:
THE ADMINISTRATOR WHO SHARES THE OFFICIAL CARD (OWNER OF THE "DMBox-Cardserver") MUST ALSO DOWNLOAD , INSTALL & ACTIVATE (VIA THE BLUE PANEL) THE "CCcam" Emulator + THE ASSOCIATED Configuration File.
THE ADMINISTRATOR MUST "OPEN" THE "CCcam cfg" FILE (THE Configuration File ASSOCIATED TO THE "CCcam-Server" Emulator) , IN ORDER TO ADD AN "F" COMMAND LINE ("F" : FRIEND)
SO :
Quote:
- THE "DMBox-Client" CONNECTS TO THE "DMBox-Server" VIA THE "C" LINE.
- THE "DMBox-Server" COMMUNICATES WITH THE "DMBox-Client" VIA THE "F" LINE.
GENERAL ADVICE :
AFTER HAVING SUCCEEDED TO ESTABLISH A FULLY OPERATIONAL CARDSHARING PROCESS , it is strongly recommended that Administrators and Users/Clients CHANGE the DMBox's "Login ID/Password" (anyone with the server's details can login into the web control page of your DMBox or ftp).

GO to the PC :
Start/Run/type "cmd" (Command Prompt) <Enter>
Type "telnet 192.168.xxx.xxx" (the DMBox's Local <LAN> IP address) <Enter>
dreambox login : type "root" <Enter>
password : type "dreambox" <Enter>
type "passwd" <Enter>
DEFINE A NEW PASSWORD (of your choice) <Enter>
CONFIRM (re-enter) THE NEW PASSWORD

REMEMBER : From now on , any attempt of transfering data or files from the PC to the DMBox and vice-versa (via FTP or Telnet) won't succeed UNLESS you enter the NEW Username and Password.





MY REGARDS :
- TO THE FORUM ADMIN TEAM
- TO MY COMPATRIOTS IN GREECE

credit to:
KONPETR