## newcamd spidernetwork

Posted on March 17th, 2011 by cardshare in Card Share

The example is not entirely correct, in fact: Its not correct at all!
It would give you the following error:

[ Chameleon2 ] Checking login returned -1

I’ve edited your example to make it correct:

Code:

1111
yes
myShares

xxxxxxx.no-ip.info
2222 — Peer Port
myShares

2- ’Someone else’s’ newcs.xml

Code:

2222
yes
myShares

myShares

Now that’s quite a difference, and let me explain it a little bit:

First of all the setting is for dividing different groups! A myShares will not be able to share its cards to a hisShares. With the setting you can block access to certain cards for a certain ’group’.

Anyway, this setting is best left at its default (default = myShares)! Since the setting doesn’t work yet (as you can read in the example newcs.xml that comes with newcs 1.62). I personaly don’t find that function even that usefull, even if it would work.

Secondly: As you see, only one of the two sharers is , the other is only . Not a & section for both – pointing to each other!
That’s because newcs will automatically be bi-directional connected!
The newcs from example 1 above, will contact the newcs from example 2 – will the find the correct section there (a matching username, password and realm) and passes on its own details so that both the newcs’s automatically are connected!
See it sort of as the following way, it’s just like a phonecall, 2 participants but only one needs to phone up the other. Both phoning up to each other to get in contact wouldn’t work!

Who like’s to play and who like’s to play is something you deal with when you exchange ’locals’.

## Mbox How To

Posted on March 17th, 2011 by cardshare in Card Share

You can NOT reply to this topic.
Only the moderators can add or change here.
This topic refers always to the latest version of Mbox. (we will try to keep it updated)

Ok, here we go.

To start Mbox you need to configure mbox.cfg first.
These parameters you must set before you can start Mbox:

D: { 0 }
//D: { x }
//x=0 -> disable
//x=1 -> enable dbox2 cw writing
//x=2 -> enable STAPI for IPBOX
//x=3 -> enable STAPI for Kathrein

T: { /tmp/ }
// T option -> where to store temp files … (share.info,debug.txt ,etc.)
// T: { folder_path_to_files, example: T: { /tmp/ } }

K: { /var/keys/ }
// K option -> where is cwshare.cfg file
// K: { folder_path_to_files, example: K: { /var/keys/ } }

P: { /tmp/pmt.tmp }
// P option -> PMT location (Dont used with linux and windows)
// you must be tuned to channel so image can generate this file
// { /tmp/pmt.tmp } for resivers and images that create this file Mode option
// M: { x }
// x=0 -> local mode no NET
// x=1 -> NET mode
// default 0

Z: { 12 } { 127.0.0.1 8000 }
// Z option -> control sending/writing current informations
// Z: { xy } { IP port }
// x=0 -> don’t print time stamp (in console screen and in debug file)
// x=1 -> print time stamp ( …. )
// y=0 -> no writing/sending informations to debug file/destination IP
// y=1 -> send informations to destination IP but not in debug file
// y=2 -> write informations to debug file but don’t send to destination IP
// y=3 -> write/send informations to debug file/destination IP
// IP port -> destination IP and UDP port where to send informations

Only debug file: Z: { 12 } { 127.0.0.1 8000 }
only send debug to IP: Z: { 11 } { 127.0.0.1 8000 }
Both file and IP: Z: { 13 } { 127.0.0.1 8000 }

L: { 1 }
// L option -> how mbox to menage virtual card(s) with level 0
// ( only for peer(s) who have and can reshare virtual cards but don’t want to use LEVEL 0 card(s) for them self)
// L: { x }
// x=0 -> don’t load any virtual cards with LEVEL 0, you can’t use them for your self
// x=1 -> load all virtual cards with LEVEL 0 ,you will be using them for your self
// default 1

If you run Mbox on a server then you can’t use level0 cards so you have to set:
L: { 0 }

If you don’t use a brascet and you must set some other options after the brascet then don’t leave it empty.
Put a zero in it so Mbox knows it’s not used.
Example: C: { 127.0.0.1 15000 dummy dummy 01 02 03 04 05 06 07 08 09 10 11 12 13 14 } { 0 } { 0 }

When using Mbox and Newcs on the same box/server then Mbox can see those cards as local.
But you must make a connection ( C-line in cwshare.cfg) with IP 127.0.0.1.
Only then you will have these cards as local in your Mbox server.

About D line in cwshare.cfg file …
Now you can set what provids boxids you want to reshare with another peer(s)

This is standard D line
=======================
D: { IP { port1 port2 { pass { level1 level2 }}}}

This is my new upgraded D line
===============================
D: { IP { port1 port2 { pass { level1 level2 }}}}
{ 0000 } { 0 } send filter
{ 0000 } { 0 } receive filter

D: { IP { port1 port2 { pass { level1 level2 }}}}
{ xxyy !!in hex!!!} { provid-boxid-boxid;provid;provid-boxid; …!!in hex!!!} send filter
{ xxyy !!in hex!!!} { provid-boxid-boxid;provid;provid-boxid; …!!in hex!!!} receive filter

for both brascets

xx -> 00 disabled
xx -> 01 allow only this cards for provid to be reshared received
xx -> 02 denied only this cards for provid to be reshared received

yy -> how much provids is in next brascet dont caculate boxids

1st example:
============

D: { IP { port1 port2 { pass { level1 level2 }}}}
{ 0102 } { 0001006A;0001006C-0A0A-0B0B; }
{ 0102 } { 00010080;00010081-0A0A-0B0B; }

{ 0102 } { 0001006A;0001006C-0A0A-0B0B; }

xx is 01 ,ALL cards for (0001006A) provid is SENT to peer AND cards with boxid 0A0A,0B0B for provid 0001006C, ALL others provids(cards) will NOT be sent!!

yy is 02 ,there is only 2 provids in next bracket dont caculate boxids

{ 0102 } { 00010080;00010081-0A0A-0B0B; }
xx is 01 ,ALL cards for (00010080) provid is RECEIVED from peer AND cards with boxid 0A0A,0B0B for provid 00010081, ALL others provids will be IGNORED!!

yy is 02 ,there is only 2 provids in next bracket dont caculate boxids

2nd example:
============

D: { IP { port1 port2 { pass { level1 level2 }}}}
{ 0202 } { 0001006A;0001006C-0A0A-0B0B; }
{ 0202 } { 00010080;00010081-0A0A-0B0B; }

{ 0202 } { 0001006A;0001006C-0A0A-0B0B; }
xx is 02 ,ALL cards for this (0001006A) provid is NOT sent to peer AND cards with boxid 0A0A,0B0B for provid 0001006C, ALL others provids(cards) are !!

yy is 02 ,there is only 2 provids in next bracket dont caculate boxids

{ 0202 } { 00010080;00010081-0A0A-0B0B; }
xx is 02 ,ALL cards for (00010080) provid is NOT RECEIVED from peer AND cards with boxid 0A0A,0B0B for provid 00010081, all others provids will be received!!

yy is 02 ,there is only 2 provids in next bracket dont caculate boxids

NOTICE: MBOX WILL NOT COMPLAIN IF YOU USE OLD D LINE STYLE !!!!!!!!!!!!!

Connecting to newcamd server program Newcs
==========================================

example:
C: { server_ip server_listening_port username password des_key } { x } { xxxxyyyyxxxyyyy;……}
C: { 127.0.0.1 15000 dummy dummy 01 02 03 04 05 06 07 08 09 10 11 12 13 14 } { 10 } { 0100006a:0100006B;}

[second brascet] -> { x } max. number ecms in buffer ,decimal !!!!!

[third brascet] { 0100006a:0100006B;} is used if you want to change caidprovid from what newcs detected to caidprovid to use with gboxx protocol so 0100006A will be 0100006B in gboxx protocol

Resending ECM(s) on timeout interval
====================================
O: { xxxx yyyy }

example:
O: { 4000 2000 }

4000 (4 seconds)-> resend current ecm on boxid if no dcw
2000 (2 seconds)-> wait 2 more seconds for dcw ,if no dcw on time resend ecm(s) to all boxid’s

NDS system ->Resending ECM(s) on timeout interval
=================================================
N: { xxxx yyyy }

example:
N: { 400 200 }

default disabled…

=============================
X+: { xxxxyyyy:zz;xxxxyyyy:zz; } // zz -> max. is 30 !!!!!

example:
X+: { 0100006A:15; }

With X+ active, for caidprovid:0100006A max. cards for use is 15.

About the 12000.list or the port.list:
You need the 12000.list file to run Mbox with your local cards!!!
If you are sure that your card can decrypt all Sids then put ONLY this in the port.list file:
SF: { 0000 }

Now you must make file called “port.list” in
K: path (look your settings in mbox.cfg)

“Port” is newcs port, look into the newcs.xml file and search for newcamd_port.
Code:

……
12000
…….

So the file will be called 12000.list.
If you have 17050 then the filename will be 17050.list

Pls use SID pids , CHIDs for Irdeto or G line, because now mbox send only one ECM and wait response from newcs before it send new ECM.

//this is for forbiden SID pids or Irdeto chids ..
//example
SF: { 04A0 } -> forbiden SID pid -> your card cant decrypt this channel
SF: { 0220 }
IF: { 0203 } -> forbiden Irdeto ChID -> your card cant decrypt this ChID
IF: { 0302 }
G: { 0100006A } -> dont list and reshare this provid from your card if card cant decrypt that, mbox will just flood newcs with bad ECMs for this provid.

//max forbiden SID pids or ChIDs is 150.
//max G lines is 15.

//OR to enable SID pids or Irdeto chids
//example
SA: { 04A0 } -> enable SID pid -> your card can decrypt this channel
SA: { 0220 }
IA: { 0203 } -> enable Irdeto ChID -> your card can decrypt this ChID
IA: { 0302 }
G: { 0100006A } -> dont list and reshare this provid from your card if card cant decrypt that, mbox will just flood newcs with bad ECMs for this provid.

//NOTE: YOU CANT MIX FORBIDEN AND ENABLED PIDS.

You don’t need the add.data file to run Mbox!!!

The add.data file gives you the option to:

- change I,X,O,N line
- to delete running D line
- to add new D line(without filter rules)
- to resend “R” hello msg to all peers while mbox is running.

Write new values in “add.data” file and put it in folder from P: line. (look your settings in mbox.cfg)

NOTE: Max time to wait before changes take affect is 2 minutes, new values for I,X,O,N will NOT be saved in cwshare.cfg but new D or C line will be saved.

#D: { ip { port1 port2 { pass { level1 level 2 }}}} -> remove running D line
D: { ip { port1 port2 { pass { level1 level 2 }}}} -> add new D line without restarting mbox,new D line will be saved in cwshare.cfg
R ->Resend hello msg to all peers
X: { x } -> Change running X value
I: { x } -> Change running I value
O: { xxxx yyyy } -> Change running timeout intervals
N: { xxxx yyyy } -> Change running timeout intervals for NDS system
C: { server_ip server_listening_port username password des_key } { x } { xxxxyyyyxxxyyyy;……} -> add new C line
#
#
__________________

## The way to successful Cardsharing

Posted on March 17th, 2011 by cardshare in Card Share

I have seen many new members lately on this forum. At the same time many similar questions have been raised over and over again.
I’m writing this just to make it easier for new members to find answers for their questions about cardsharing.
I will focus on the use of a Dreambox as Sharing receivers and the CCcam protocol.
Remember that a newbie is just an inexperienced expert
ATTENTION! All this information is for test purpose and should only be used within your own household. No one except yourself is responsible for any damage this can cause or any law you might break.
What hardware you’ll need is based on how your house looks like, where you want to watch TV, how big server you want to have and so on.
What we all need is a Dreambox of some kind.
A computer with internet connection.
If you have the computer in one room and the Dreambox in another room far away you will need either a long Ethernet cable or use another solution to connect your PC to your Dreambox.
I can recommend the use of 2 Homeplugs, it’s a really user friendly alternative.
Read more about Homeplugs here: HomePlug Powerline Alliance – Wikipedia, the free encyclopedia
If you want to be able to handle a large number of peers you need a pc as server, more about that later.
Not much to say here.
Make sure you have enough space around it to let the air circulate freely and cool down the Dreambox.
Connect the cable from your satellite dish (if you use a satellite dish) to your Dreambox tuner.
Connect the network cable to the Dreambox.
Connect power cord.
Switch on.
To be able to share with another CCcam server or even many servers you need to set up an network.
First of all you need a static ip in some way. Either you have one from your ISP or you can set one up for yourself.
You should have all information needed if you did step 4.1.
For example
PC ip = 192.168.1.141
Dreambox ip =192.168.1.142
Default gateway = 192.168.1.1
DNS Server = 216.104.63.7
Remember to switch DHCP OF
Now you need to port forward all traffic trough one port to the Dreambox ip.
Default port is 12000 but this can be changed in the config (CCcam.cfg).
Now we need to have the software to make the Dreambox work properly.
First we flash an image to the Dreambox.
There are different images to choose from and it’s up to you what you prefer.
But let’s chose a PLI image for this guide.
Search this site for the newest image.
Instructions can be found here:

7025/7025+
Dream-Multimedia-Tv GmbH

800
Dream-Multimedia-Tv GmbH

600
Dream-Multimedia-Tv GmbH

500+
Dream-Multimedia-Tv GmbH
Next step is to install CCcam
Remember that this might change on newer images but the basics will probably be the same.
In the today’s most recent image:
Click green button
then click softcams and chose CCcam and install.
Remember to change your default cam to CCcam.
There aren’t really any software that you have to install but there are some that makes everything easier.
This is more or less an must have.
An DNS Updater is a software that constantly checks your public ip and links it to your static ip.
Many ISP have dynamic ip’s which means that you’ll get a public ip that will change once in a while.
It doesn’t mater if you’ll set a static ip in your PC, you’ll still have a public ip that will change.
Therefore you will use a DNS Updater to fix this problem and always link your DNS servername which you will register for to your static ip.
There are a few to chose from but I will recommend two:

DynDNS
Register here
DynDNS Services: DNS, Domain Names, EMail Routing

http://cdn.dyndns.com/windows/DynUpSetup.exe

or if that link does not work you will find it here
DynDNS Support

No-ip
No-IP™ Free – Free Dynamic DNS – DDNS

Or if you want to see all services look here
Enterprise Managed DNS and Mail Services, 100% DNS Uptime, Domain Registration No-IP™

You can use this to edit your CCcam.cfg.
This is pretty easy, just open the program and insert the ip for your router and Dreambox.
You can change the language to English.
Open CCcamInfoPHP_v0.8.2\htdocs\config.php in notpad and change the line you see below to match your server info.

Code:
$CCCamWebInfo[] = array("192.168.1.xxx","16001","root","dreambox"); // for CCcam webinterface with user and pass Now open the file located in CCcamInfoPHP_v0.8.2\server\Apache\php.ini Find this section Code: ;;;;;;;;;;;;;;;;;;;; Resource Limits ;;;;;;;;;;;;;;;;;;;; and change the line: max_execution_time = 30 <---- Change this to a higher value like 60 Now you can start CCcamInfoPHP by clicking on CCcamInfoPHP v0.8.2.exe (or CCcamInfoPHP vX.X.X.exe). 6.3.2 Versions before 0.8.2 If you use a windows PC you need to install some server that can handle PHP. WAMP server is one that does that. Download it here: http://www.en.wampserver.com/ Install WAMPserver in C:\wamp The zipped file should include a lot of folders and files extract CCcamInfoPHP to C:\wamp\www\ Now you should find a file in the www folder called config.php. Open that file in a text editor like notpad. In that file you will find this lines: Code: //examples of server definitions$CCCamWebInfo[] = array("IP","PORT","USER","PASS"); // for CCcam webinterface with user and pass$CCCamWebInfo[] = array("IP","PORT"); // for CCcam webinterface with different port than default and without user and pass$CCCamWebInfo[] = array("IP");

Here you should edit IP to your dreambox ip.
Port to webinterface port.
Default Port is 16001
Default pass is dreambox

If you have many peers you might need to change some parameters in

Code:
\wamp\Apache2\bin\php.ini

If you don’t have that file, try this one

Code:
\wamp\bin\apache\apache2.2.6\bin\php.ini

Find this lines in that file (you can open the file in notpad).

Code:
;;;;;;;;;;;;;;;;;;;; Resource Limits ;;;;;;;;;;;;;;;;;;;;max_execution_time =max_input_time =;max_input_nesting_level =memory_limit =

Make sure you have at least this values:

Code:
max_execution_time = 300     ; Maximum execution time of each script, in secondsmax_input_time = 60 ; Maximum amount of time each script may spend parsing request data;max_input_nesting_level = 64 ; Maximum input variable nesting levelmemory_limit = 128M      ; Maximum amount of memory a script may consume (128MB)

http://localhost/index.php
or
http://localhost/somefolder/index.php
Now you need to have someone to cardshare with.
If you don’t already have you can try to find someone in the free section here:
Remember to read the rules before posting.

When you have found someone to cardshare with you need to exchange C- and Flines.
Let’s go through the basic with Flines and Clines
The CCcam.cfg file is located in your Dreambox.
You can access it from your PC with DCC.
FTP to location:

Code:
var/etc

Right click on CCcam.cfg and chose edit.
The Fline is basically the same as creating a user account on your server.
In your config you have a Friend section that is the part where you should add the Flines.
The Cline is more like a connection string that you give to your peers so that they can connect to your server.
To be able to connect they need to have an account on your server (the Fline).
F: myfriend abc123 3 0 0 { 0:0:3 }
The part behind the password is privileges and restrictions.
3 0 0 { 0:0:3 }

This user gets all cards at a maximum of 3 hops away from us,
and get’s to share them down two further levels beyond his own level.
C: biocide.******.org 12000 myfriend abc123 no { 0:0:3, 100:3, 100:4 }
no { 0:0:3, 100:3, 100:4 }
no = don’t receives friends emus
{ 0:0:3 = how many hops down you want to receive cards from that server
, 100:3, 100:4 } = here you can block cards from that server
Summary of Clines and Flines
F: myfriend abc123 3 0 0 { 0:0:3 }
C: the Cline that were sent to you.
F: an Fline that match the Cline that was sent to you
C: your.server.org 12000 myfriend abc123 no { 0:0:3, 100:3, 100:4 }
There are much more you can do in the Cline and Fline but this is the basic that I think everyone should know about.
There are a lot of fake and old cards that are being shared and slowing down the servers, therefore you need to block all those cards.
Here is a list with old and fake cards:
First of all I want to say that using the method below will block all cards that you don’t choose to receive.
This also means that you will only share the cards that you decide to receive.
Remember that your peers might want cards that you don’t receive because you blocked them, and therefore they can see you as a not so interesting peer.
no { 0:0:1 } This means that you take all cards on hop1.
If you want any card on hop2 you’ll add:
no { 0:0:1, 90f:0:2, b00:0:2, anycard, anycard, anycard }
In this example I chose to get
90f:0 = “Viasat (5E/75E/1W)” on hop2
b00:0 = “Focus(1W) / C+Nordic(1W) / DigiAlb(16E) / MTV(19.2E)” on hop2
The last number is hop:
90f:0:2

## Howto MultiProtocolCardServer MPCS + CCcam

Posted on March 15th, 2011 by cardshare in Card Share

This howto ´ll show you the installation for Debian linux with Multi Protocol Card Server or short MPCS. If you use it, you´ll have a very symbiotic cs, which can handle many different cs-protocolls on the same time and if you want, with only one common card-source.
For further informations look into the doc-directory of mpcs.
The MPCS is originally written by Dukat from streamboard.

You should use this description for installation of the os and mpcs in case of a fresh system-install.

To use cccam and mpcs together on a fresh system, you should first install debian-linux codename-lenny, followed by the steps for cccam install by CC_share. (without OS-install offcourse

a) You can also combine this tutorial with “Howto: Building Debian Linux server with CCcam” to use a cccam server and mpcs as cardserver.
or (and)
b) You can also combine this tutorial with “Howto install a NewCS Server on Debian Linux” to use a NewCS and mpcs as cardserver.
In case of point a or – (and) b mixes on existing os you must upgrade your system from debian etch to debian lenny to be able to use the current mpcs binary.
In this case you can copy and paste the following command in your putty terminal
code:

vim /etc/apt/sources.list

Edit your current debian etch paths by changing every “etch” into “lenny”.
To do that, you have to push the “i” button on your keyboard to enable the editmode of vim.

Now you must push “i” on your keyboard to edit the values
example before

deb Debian — Security Information etch/updates main contrib non-free
deb-src Debian — Security Information etch/updates main contrib non-free

deb Index of /debian-volatile etch/volatile main contrib non-free
deb-src Index of /debian-volatile etch/volatile main contrib non-free

example after
code:

deb Debian — Security Information lenny/updates main contrib non-free
deb-src Debian — Security Information lenny/updates main contrib non-free

deb Index of /debian-volatile lenny/volatile main contrib non-free
deb-src Index of /debian-volatile lenny/volatile main contrib non-free

Save it by pushing “Esc” followed by “ZZ” on your Keyboard.

Next commands are
Code:

vim /etc/apt/preferences

Now you must push “i” on your keyboard to edit the values
code:

Package: *
Pin: release a=etch
Pin-Priority: 700

Package: *
Pin: release a=lenny
Pin-Priority: 650

Save it by pushing “Esc” followed by “ZZ” on your Keyboard.

Let´s start now with the installation on a fresh system.

Needed tools are a terminal programm like “putty” and a ftp proggy like “filezilla”.
I would also suggest to use VIM, a linuxcompatible editor for windows. If you use this one as standard, from now on you have also a good training for editing files in debian linux. You can select it in the settings menue of “Filezilla” under the tabs “edit”,”settings”,”File editing”. Choose the option “Always use default editor” and browse to the install path of VIM, select the gvim.exe and write the attribute -y into the default editor window after “C:\your\path\to\gvim.exe -y”. Save it by pressing “OK” and now your standard appz for editing files in filezilla is VIM.
You can download the actual MPCS here “Streamboard | Ihnen wird der Zutritt zu dieser Seite verwehrt.” after registration. I would give you a link from eurocardsharing, but i did´nt find it here.
May be they will create now a mpcs-section, or may be, it´s hidden.

The OS-install is, if still needed, very easy.
Just choose and download a debian-lenny iso matching to your architecture from Debian — Debian-Installer (i use the i386 netinstall version), burn it to a cd with burning software like nero or imageburn and start your installation on a fresh pc.
Choose the expert install option, choose your language, country, keyboardsettings and press enter by the next options until you come to the point with installercomponents to choose, select openssh-client-udeb and network-console.
Go on by pressing enter and go to the point with network-installation, choose, if not automatically recognized, your network hardware and press enter again. Now you´ll be asked for the network configuration way, where you choose the manual option.
Here you can give the ip-adress for your new system. This should be differ only in the last 3 digits from your existing network stations.
For example your windows pc has 192.168.178.3, then this ip can be 192.168.178.4 .
After pressing enter you can leave the next value like it is, because depending on your ip-adress the system has auto-recognized the right value for netmask here.
The next steps are gateway and DNS-server, also auto-recognized, so you can go on by pressing enter again.
Finally you can check your network-parameters and if everything looks fine, select yes and go on.
You can choose a computer and domainname now and go on with installation over network (SSH) by the next option.
Choose it, confirm it and after pressing enter follow the hints on screen.
From now on you can access your server remotely wih putty. After login choose expert-install again and you can configure clocksettings and timezone (i suggest to leave it on system defaults).
The next point is disk detection so select it and go on with disks partitioning.
Choose “Guided partitioning” then select “Guided – use entire disk”, select your hd-model and choose “Separate /home, /usr, and /tmp partitions”.
Then select “Finish partitioning and write changes to disk” and confirm it with “yes” in the next window.
Then go on with “Install the base system” and wait until it´s done.
Now you can select the kernel to install. It´s okay to select the system default option.
The next step is to configure udev where i choose the “generic: include all available drivers” option.
Now configure the package manager and answer “use a network manager” with yes. http is here ok. Select your country for debian archive mirror
and select one of them.
If you use a proxy, then you can enter this in the next window or, if not, leave this field blank. In the next window choose “yes” to be able to use ALSO NON-FREE software.
After 3 minutes or so you can also select the “volatile updates” option and continue with “Select and install software”
so if you´ve time enough, you can say YES in the next window and play a little popularity-contest-Q&A-game, but it´s allright if you say NO here.
In a little while you can select software to install. For our solution it´s enough to select the “web-server” option only.
If it´s done, you can select “Install the GRUB boot luder on a hard disk” and answer the next quest with “NO”.
Now you must choose, where to install the GRUB boot loader. The next entry is your decision, what to choose. I give a password here.
I´m sorry, but the OS installation comes to it´s end by the next step.
There are only 2 last quest´s, where the first is, what type of systemclock you use and the second in the “INSTALLATION COMPLETE” window.
I think, you can answer it for yourself, what´s the right selection here.
The following steps are for systems with complete “CC_share like” installation and for complete new installations.
code:

mkdir /emu
mkdir /emu/mpcs
mkdir /emu/script
mkdir /emu/log
chmod 777 /emu
chmod 777 /emu/*
chown /emu
chown /emu/*
vim /emu/script/mpcs

Now you must push “i” on your keyboard and insert the following
Code:

#!/bin/sh
CAMNAME=”MPCS Server”
# end

# This method starts MPCS
start_cam ()
{
/emu/mpcs/mpcs &
sleep 2
}
# This method stops MPCS
stop_cam ()
{
pkill mpcs
}
case “$1″ in start) echo “[SCRIPT]$1: $CAMNAME” start_cam ;; stop) echo “[SCRIPT]$1: $CAMNAME” stop_cam ;; restart) echo “Restarting$CAMNAME”
stop_cam
start_cam
;;
*)
“$0″ stop exit 1 ;; esac exit 0 Save it by pushing “Esc” followed by “ZZ” on your Keyboard. Next commands are code: chmod 755 /emu/script/mpcs ln /emu/script/mpcs /bin/mpcs aptitude install proftpd During the install of proftpd comes a quest to select YES if you shure to install it, so you have to select YES. On the next question you should choose “stand-alone”. Rename mpcs-pre_09e to mpcs and use your ftp programm (filezilla) to upload mpcs, ignore.list, mpcs.ac, mpcs.cert, mpcs.conf, mpcs.guess, mpcs.ird, mpcs.server, mpcs.services, mpcs.srvid and mpcs.user to /emu/mpcs. Next command is code: ln -s /emu/mpcs/ignore.list /usr/local/etc/ignore.list ln -s /emu/mpcs/mpcs.ac /usr/local/etc/mpcs.ac ln -s /emu/mpcs/mpcs.cert /usr/local/etc/mpcs.cert ln -s /emu/mpcs/mpcs.conf /usr/local/etc/mpcs.conf ln -s /emu/mpcs/mpcs.guess /usr/local/etc/mpcs.guess ln -s /emu/mpcs/mpcs.ird /usr/local/etc/mpcs.ird ln -s /emu/mpcs/mpcs.server /usr/local/etc/mpcs.server ln -s /emu/mpcs/mpcs.services /usr/local/etc/mpcs.services ln -s /emu/mpcs/mpcs.srvid /usr/local/etc/mpcs.srvid Use putty again to give mpcs execution rights Code: chmod 755 /emu/mpcs/mpcs Now you can simply start, stop or restart newcs in telnet by typing code: mpcs start mpcs stop mpcs restart You should also use a config update script to update your mpcs.users file to a specified time in the night to prevent freezers in the primetime during updating your mpcs.users file Code: vim /emu/script/configupdate_mpcs.sh Now you must push “i” on your keyboard and insert the following Code: #!/bin/sh #Script to process new config and backup old one. SOURCE=/emu/mpcs TARGET=/usr/local/etc FILE=mpcs.user BACKUPDIR=/var/backup CONFIGOLD=mpcs.oldie if test -f$SOURCE/$FILE ; then echo “New Config Present” if test -d$BACKUPDIR ; then
if test -f $BACKUPDIR/$CONFIGOLD ; then
echo “Removing OLD config file from backup directory”
rm $BACKUPDIR/$CONFIGOLD
else
echo “No OLD config to remove.”
fi

if test -f $BACKUPDIR/$FILE ; then
echo “Renaming Backup to old config”
cp $BACKUPDIR/$FILE $BACKUPDIR/$CONFIGOLD
rm $BACKUPDIR/$FILE
else
echo “No Backupfile present yet”
fi
if test -f $TARGET/$FILE ; then
echo “Copying Original config to Backup directory”
cp $TARGET/$FILE $BACKUPDIR rm$TARGET/$FILE else echo “No Original Config File Present!?!?” fi else echo “Backup directory does not exist.” echo “making new directory” mkdir$BACKUPDIR
if test -f $TARGET/$FILE ; then
echo “Copying Original config to Backup directory”
cp $TARGET/$FILE $BACKUPDIR else echo “No Original Config File Present!?!?” fi fi echo “Moving New config file to “$TARGET
cp $SOURCE/$FILE $TARGET rm$SOURCE/$FILE else echo “No New Config present, Nothing to process” fi exit Save it by pushing “Esc” followed by “ZZ” on your Keyboard. Next commands are Code: chmod 755 /emu/script/configupdate_mpcs.sh cd /etc vim crontab Now you must push “i” on your keyboard and insert the following at the bottom Code: 00 3 * * * root /emu/script/./configupdate_mpcs.sh >>/emu/log/configupdate_mpcs.log 2>&1 Save it by pushing “Esc” followed by “ZZ” on your Keyboard. With the next settings mpcs will start on the next reboot. Code: vim /etc/rc.local Now you must push “i” on your keyboard and insert the following line in the free line before “exit0″ Code: /bin/mpcs start & Save it by pushing “Esc” followed by “ZZ” on your Keyboard. To prepare your mpcs for the use with cccam, mbox, evocamd and mgcamd you must prepare your cardreader in mpcs.server, assign caids to ports in mpcs.conf and create your user entries in mpcs.users. I choose the newcs-protocol in my examples and the provider premie*e including the HD-Channels. Check also the file /emu/log/mpcs.log after your first start of mpcs. For further details read the files in the doc directory of mpcs. You have to edit your mpcs.server with this values. To do that enter the following code: vim /emu/mpcs/mpcs.server Now you must push “i” on your keyboard code: [reader] Label = N3HD Protocol = mouse Device = /dev/ttyS1 EMMCache = 1,3,2 Fallback = 0 Detect = CD #CAID = 1702 Group = 1 Save it by pushing “Esc” followed by “ZZ” on your Keyboard. In the mpcs.conf you can activate and edit your prefered protocol like this code: vim /emu/mpcs/mpcs.conf Now you must push “i” on your keyboard code: [global] Nice = -1 MaxLogsize = 100 ClientTimeout = 5 Level = 15 ClientMaxIdle = 120 CacheDelay = 20 BindWait = 60 ResolveDelay = 15 LogFile = /emu/log/mpcs.log #LogFile = stdout Sleep = 0 [monitor] Port = 0 NoCrypt = 127.0.0.1 NoCrypt = 10.0.0.0-10.255.255.255 NoCrypt = 172.16.0.0-172.31.255.255 NoCrypt = 192.168.0.0-192.168.255.255 HideClient_TO = 1 AULow = 120 MonLevel = 1 [anticasc] enabled =1 numUsers =1 sampleTime =3 penalty =0 acLogFile =/tmp/aclog.log fakeDelay =200 samples =10 denySamples =9 [newcamd] Key = 0102030405060708091011121314 #Port = 17000@1833:FFFFFF Port = 17000@1702:FFFFFF;17001@1833:FFFFFF;17002@1801:FFF FFF #[radegast] #Port = 60000 #User = tuner #Allowed = 192.168.178.10-192.168.178.20 #[cs378x] #Port = 11005 #Port = 11005@1702:FFFFFF;11006@1722:FFFFFF;11007@1801:FFF FFF;11008@1833:FFFFFF #[cs357x] #Port = 11005 #[gbox] #Password = 9ADFA417 #MaxDist = 4 #CardInfos = cards.info #IgnoreList = ignore.list #OnlineInfos = share.onl #Locals = 17220000,18010501,0D220400 #[camd35] #Port = 11005 Save it by pushing “Esc” followed by “ZZ” on your Keyboard. To activate some users you´ve also to edit the mpcs.users file in this way code: vim /emu/mpcs/mpcs.users Now you must push “i” on your keyboard code: [account] User = au Pwd = au Group = 1 MonLevel = 0 AU = N3HD CAID = 1702,1801,1833 #Betatunnel = .:,.: Betatunnel = 1833.0081:1702,1833.0082:1702 Save it by pushing “Esc” followed by “ZZ” on your Keyboard. A working N-line for cccam would look like this, if cccam runs on the same computer: N: 127.0.0.1 17000 au au 01 02 03 04 05 06 07 08 09 10 11 12 13 14 For the HD-Channels you´ll need a extra line like this, where port 17001 is assigned to caid 1833 which is used by the HD-Channels: N: 127.0.0.1 17001 au au 01 02 03 04 05 06 07 08 09 10 11 12 13 14 Preparation for CCcam on the same pc code: mkdir /emu/cccam mkdir /var/etc mkdir /var/keys chmod 777 /emu/cccam chown /emu/cccam vim /emu/script/cccam Now you must push “i” on your keyboard code: #!/bin/sh CAMNAME=”CCcam Server” # end # This method starts CCcam start_cam () { /emu/cccam/CCcam.x86 & sleep 2 } # This method stops CCcam stop_cam () { pkill CCcam.x86 } case “$1″ in
start)
echo “[SCRIPT] $1:$CAMNAME”
start_cam
;;
stop)
echo “[SCRIPT] $1:$CAMNAME”
stop_cam
;;
restart)
echo “Restarting $CAMNAME” stop_cam start_cam ;; *) “$0″ stop
exit 1
;;
esac
exit 0

Save it by pushing “Esc” followed by “ZZ” on your Keyboard.

code:

chmod 755 /emu/script/cccam
ln /emu/script/cccam /bin/cccam
chmod 755 /emu/cccam/CCcam.x86
vim /emu/script/configupdate_cccam.sh

Now you must push “i” on your keyboard
code:

#!/bin/sh
#Script to process new config and backup old one.
#Script designed and written by CC_Share
SOURCE=/emu/cccam
TARGET=/var/etc
FILE=CCcam.cfg
BACKUPDIR=/var/backup
CONFIGOLD=CCcam.old
if test -f $SOURCE/$FILE ; then
echo “New Config Present”
if test -d $BACKUPDIR ; then if test -f$BACKUPDIR/$CONFIGOLD ; then echo “Removing OLD config file from backup directory” rm$BACKUPDIR/$CONFIGOLD else echo “No OLD config to remove.” fi if test -f$BACKUPDIR/$FILE ; then echo “Renaming Backup to old config” cp$BACKUPDIR/$FILE$BACKUPDIR/$CONFIGOLD rm$BACKUPDIR/$FILE else echo “No Backupfile present yet” fi if test -f$TARGET/$FILE ; then echo “Copying Original config to Backup directory” cp$TARGET/$FILE$BACKUPDIR
rm $TARGET/$FILE
else
echo “No Original Config File Present!?!?”
fi
else
echo “Backup directory does not exist.”
echo “making new directory”
mkdir $BACKUPDIR if test -f$TARGET/$FILE ; then echo “Copying Original config to Backup directory” cp$TARGET/$FILE$BACKUPDIR
else
echo “No Original Config File Present!?!?”
fi
fi
echo “Moving New config file to “$TARGET cp$SOURCE/$FILE$TARGET
rm $SOURCE/$FILE
else
echo “No New Config present, Nothing to process”
fi
exit

Save it by pushing “Esc” followed by “ZZ” on your Keyboard.

code:

chmod 755 /emu/script/configupdate_cccam.sh
cd /etc
vim crontab

Now you must push “i” on your keyboard
code:

00 3 * * * root /emu/script/./configupdate_cccam.sh >>/emu/log/configupdate_cccam.log 2>&1

Save it by pushing “Esc” followed by “ZZ” on your Keyboard.

To put cccam in bootsequence use
Code:

vim /etc/rc.local

Now you must push “i” on your keyboard and add this line at the bottom
code:

/bin/cccam start &

Save it by pushing “Esc” followed by “ZZ” on your Keyboard.

If you now add this 2 lines to your CCcam.cfg you´ll be connected to your card in mpcs via newcs protocoll

N: 127.0.0.1 17000 au au 01 02 03 04 05 06 07 08 09 10 11 12 13 14
N: 127.0.0.1 17001 au au 01 02 03 04 05 06 07 08 09 10 11 12 13 14

code:

mpcs start
mpcs stop
mpcs restart

cccam start
cccam stop
cccam restart

Now you should reboot the server and check that MPCS and CCcam are running.

## Basic definitions in Gbox

Posted on March 15th, 2011 by cardshare in Card Share

Share-configuration
The template is:
Server
M: { { }}

D: { { port_from port_to { { }}}}
Client

M: { { }}

D: { { port_from port_to { { }}}}
• => IP-address of the box. If this is going over the internet, use the WAN-IP-
• => Encryption-key of the box
• => The IP- or DNS-address of the person you want to connect to.
• => Port you want to use on the box. If this is going over the internet, this
needs to be forwarded if behind a router! UDP!!
• => Port that the other sided uses on the box.
• => Share-level for the LOCAL cards.
• => Share-level for cards you receive from others.
Assuming the server has the IP-address 192.168.1.10 and the client 192.168.1.11:
Find the file /var/keys/cwshare.cfg and alter the following lines accordingly:

Server

M: { 192.168.1.10 { 1234ABCD }}
D: { 192.168.1.11 { 8019 8020 { DCBA4321 { 5 5 }}}} # Client
Client
M: { 192.168.1.11 { DCBA4321 }}
D: { 192.168.1.10 { 8020 8019 { 1234ABCD { 5 5 }}}} # Server
This will off-course work over the internet! Use the WAN-IP-address or Just use a DynDNS or no-

================================================== ===========
Analyzing logging
So, you’ve got things sorted, and you want to take a look at what’s what. Well, actually, there are
6 files to be viewed, of which 4 are permanent:
• /var/tmp/share.info => shows the cards you receive from others
To make things easy, I took myself as an example. I did this on my dreambox:
/tmp > cat share.info
CardID 0 at 192.168.2.102 Card 0100006A Sl:3 Lev:0 dist:1 id:87F4
CardID 1 at 192.168.2.102 Card 0100006B Sl:3 Lev:0 dist:1 id:87F4
CardID 2 at 192.168.2.102 Card 0100006C Sl:3 Lev:0 dist:1 id:87F4
CardID 3 at 192.168.2.102 Card 0100006D Sl:3 Lev:0 dist:1 id:87F4
CardID 4 at 192.168.2.102 Card 06260000 Sl:11 Lev:0 dist:1 id:87F4
OK, to break things down I’ll use the first line:
CardID 0 => ranking-number of the card the way they are sorted… Alphabetically
o
on Card-number.
at 192.168.2.102 => IP-address of where they are coming from
o
Card 0100006A => Card-number. This is how the card is identified
o
Sl:3 => Displays the slot the card is in at the provider, when run on a Linux-PC
o
up to 18 has been seen.
Lev:0 => Amount of hops I’m allowed to reshare. Zero.
o
dist:1 => Amount of hops the card is at. In this case: 1.
o
id:87F4 => Identification-number for gbox that is providing the card.
o
• /var/tmp/share.log => Same as share.stat, only that this displays the real-time data.
• /var/tmp/share.onl => shows who’s on-line
Again, I’ll use myself as an example:
/tmp > cat share.onl
1 192.168.2.102 192.168.002.102 87F4 2.01
1 => 1 is on-line, 0 is offline.
o
192.168.2.102 => The entry you use in cwshare.cfg.
o
192.168.002.102 => The way gbox translated cwshare.cfg to an actual IP-
o
87F4 => Identification-number for gbox on the other end.
o
2.01 => Version-number of gbox on the other end.
o
• /var/tmp/share.stat => Same as share.log, only that this displays the stats over the
entire running-time, and of the last 5 minutes.
Hello_I/O=> Number of hello’s or “handshakes” between 2 peers.
o
ECM_I/O/F => ECM received (In), sent (Out) and Forwarded by gbox.
o
CW_I/O/F => Control Words received (In), sent (Out) and Forwarded by gbox.
o
Control Word is the reply to an ECM request.
GSMS_I/O => Messages received (In) and sent (Out) and by gbox.
o
loc_up and loc_down => LOCAL Network traffic. (Probably filters defined by the
o
internet standard, 10.x.x.x / 127.x.x.x / 192.268.x.x / 169.254.x.x)
inet_up and inet_down => Network tracfic in and out of internet. (Probably
o
every other IP-addres different from what I mentioned 1 point before?)
• atack.txt => Shows a misconfiguration or someone that is trying to connect to you
without being authorized to do so.
An example. On my server I mutilated the key for the client (that means the line starting
with D. On the client the atack.txt is created and filled with a number of messages:
o
EDB2097E (32) Sun Aug 7 16:32:09 2005
This means that someone it trying to connect using a wrong password.
I then remove the server completely out of the config:
INTRUDER ALERT: IP 192.168.002.102 Port 3101 (PASS 2346A4B2 ID 87F4
o
unknown) Sun Aug 7 16:40:50 2005
You see the difference?
goneOFFLINE: BAD IP|PORT (DynDNS Peer1) Actual IP Peer1/Localport (IP-
o
address from local DNS Resolve/Localport) Tue Aug 23 12:55:02 2005
This message says that the actual IP-address off the Peer doesn’t match with
what gbox thinks it should be.
• Debug.txt => Can take all message generated by gbox. Depends on what you put after
Z: in the file gbox_cfg
->HelloL to => Initial request to every “D:-line” in cwshare.cfg
o
->Hello1 to => Second request if first not answered to (quickly enough)
o
->Hello2 to => Third request if first not answered to (quickly enough)
o
->HelloR to => I think this means Reconnect to peer if timed out? Anyone?
o
->HelloW to => Don’t know. Anyone?
o
->HelloS1 to => Don’t know. Anyone?
o
->Here? to => Repetitive request every x seconds to see if peer has come on-
o
line.
Reply to Hello L/1/2/R from Peer, Or first request after Peer
o
reboot? Anyone?
o
Hello from”. Anyone?
->Hello to => Reply to “<- Hello from".
o
||CW (->1) blocked from Peer1 to Peer2/GboxID Peer2 => Don’t know
o
actually. Anyone?
ECM (1->1) from Peer1 forwarded to Peer2 (GboxID Peer2 )
o
CW (->1) from Peer2 forwarded to Peer1 => Here you see a request being
relayed to someone else, and the answer to that request. In (1->1), the first “1″
stands for the slot the card is in at the supplier, “->1″ stands for the amount of
hops the message has to travel to that supplier. In (->1) “1″ stands for for the slot
the card is in at the supplier.
o
->CW (->1) send to Peer1 (527 ms) => This is a request from Peer1 to a local
card, the reply and the time it took to read the card and supply the key.
dbox2 Peer1 is not responding 6 times => Well, that says enough I think?
o
goneOFFLINE: Removing Peer1 from list, seems offline => Sets Peer1 from
o
1 to 0 in share.onl, after not responding 6 times.
• online.log => Shows the coming and going of peers. Creation of this file depends on the
line N: in cwshare.cfg
comeONLINE : Welcome PEER1 IP xxx.xxx.xxx.xxx/ Sun Sep
o
4 16:22:45 2005 => PEER1 comes online
goneOFFLINE: Removing PEER1 from list, seems offline Sun Sep 4
o
17:45:39 2005 => PEER1 doesn’t respond anymore
IP update : PEER1 was xxx.xxx.xxx.xxx now xxx.xxx.xxx.xxx Sun Sep 4
o
17:45:53 2005 => PEER1 has a new IP-address
comeONLINE : Welcome PEER1 IP xxx.xxx.xxx.xxx/ Sun Sep
o
4 18:01:05 2005 => PEER1 is back on-line again!

Credits go To Anakin

Gbox Cfg by cuba
GBOX_CFG

In your gbox_cfg file you have following lines

Z: { 01 12 } dream ip 8024

G: { 03 }

C: { 01 }

M: { 01 }

A: { 00 }

U: { 01 }

H: { 01 }

T: { 00 }

O: { 03 } dream ip

L: { 00 } dream ip 8029

W: { 00 00 } 9600

V: { F0 35 } => configurations for reading slot and com-ports

V: { F0 00 } nothing
V: { F0 10 } slot 1
V: { F0 20 } slot 2
V: { F0 30 } both slots
V: { F0 35 } both slots + com ports
V: { F0 05 } only com ports
V: { F0 31 } Sc8in1
V: { 00 05 } Dbox2 multicam

Instead of dream Ip you must the the IP of your PC. And for make it possible that your programmer is read you must use following line as described
V: {F0 05 }