1st Script
copy this in gbox_cam.sh
---------------------------------------
CAMNAME="GbOx_CCcam"
USERNAME=""
ZAPTIME=8
CAMID=970
DVBSET=1
INFOFILE="ecm.info"
# end
# This method cleans up /tmp folder of gbox files
remove_tmp ()
{
rm -rf /tmp/*info* /tmp/*gbox* /tmp/*online* /tmp/*share* /tmp/Newcs* /tmp/atack* /tmp/debug*
}
# This method starts Gbox > CCcam (That order)
start_cam ()
{
/var/script/AES_Gbox.sh &
sleep 5
/var/bin/gbox &
sleep 30
/var/bin/CCcam_2.0.3 &
}
# This method stops gbox and CCcam and then calls the tmp cleanup method
stop_cam ()
{
touch /tmp/gbox.kill
/bin/prockill gbox
/bin/prockill CCcam_2.0.3
killall -9 newcs cs2gbox 2> /dev/null
remove_tmp
}
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
--------------------------------------
rename ur cccam ver in CCcam_2.0.3 or CCcam_2.0.4 ,CCcam_2.0.5
and reboot
this scrip is for Gemini i have test it it works very will u have gbox and cccam together .
----------------------------------------
You just have to take care about the name of both cams. It must be the same as the cam files in your dreambox.
You need about 30 sec delay between the start of gbox and the start of CCcam : even if gbox starts first , CCcam will take your local card (it is faster) so you will appear with no local for your gbox partners.
Thursday, October 15, 2009
CCCam Tutorial for 7020
DM 7025 & "CCcam Protocol" : how to establish a LAN Cardsharing process (VIACCESS 2)
A> NECESSARY EQUIPMENT FOR A LAN CONNECTION
- ADSL CONNECTION (over PSTN or ISDN)
- Modem-Router with at least 3 ethernet ports
- Cables RJ-45 (cat. 5 or cat. 6)
- DMBox 500/56XX/600/7000/7020
- DMBox 7025
- PC (WIN XP) with 10/100 MBit Compatible Ethernet Interface and an FTP Client installed (FILEZILLA CLIENT 2.2.31)
- An Official Subscription Card VIACCESS 2 (CAId : 0500)
B> PRELIMINARIES
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. The Modem-Router is now the default Internet Gateway which acts as a
DHCP Server , in order to distribute automatically to each device of the LAN (PC , DMBox) its own Local IP Address.
ii> Connect the PC and the DMBox to the modem-router , via cables RJ-45
iii> Configurations on the DMBoxes
- DM 500/56XX/7000/7020
Go to "Menu/Mainmenu/Setup/Expert setup/Communication Setup :
*ENABLE the DHCP option and CONFIRM the option "Enable Network"
*Connection Type : LAN
*Port : 80
Green button to SAVE the above configurations
- DM 7025
Go to Menu/Setup/System/Network :
* "Use DHCP" : YES
PRESS the OK button to confirm the choice
iv> Configurations on the PC :
Start/Control Panel/Network Connections/Local Area Connection/Properties/Internet Protocol (TCP/IP)/Properties :
- CHECK the following options : "Obtain an IP address automatically" & "Obtain DNS server address automatically"
- Go to Advanced/Default gateways : ADD the IP address of the Modem-Router
II> USING Personalized settings
- For the DMBoxes
The elements to be modified are the following :
- IP Address : Associate to the DMBoxes 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 : Set the Primary (Public) IP address of your ISProvider. You could also set the Local Internal IP address of the Modem-router. It's up to you.
- Gateway : Set the Local IP address of the Modem-router
- CHECK the option : "Enable Network"
PRESS the OK/Green button to SAVE the configutations.
- For the PC
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 :
*Router's Local Internal IP address : 192.168.1.1
*PC's Local IP address : 192.168.1.2
*Default Gateway : 192.168.1.1 (router's IP address)
*DNS server addresses : ISP's main & alternative public IP addresses OR the Router's Local IP address (192.168.1.1)
**DMBoxes's LAN IP addresses :
- 192.168.1.3
- 192.168.1.4
**Gateway : 192.168.1.1 (the router's Local IP address)
**Nameserver : 192.168.1.1 (the router's IP address) OR the ISP's Primary IP address
C> DM 7025 & VIACCESS 2 CARD : HOW TO ESTABLISH A LAN "CARDSHARING PROCESS"
- DMBox 500 : CARDSERVER
- CARDSERVER'S IMAGE (img) : GP2 V. 3.50 MaxVar
- CARDSERVER'S LAN IP Address : 192.168.1.3
- CARDSERVER'S Username / Password : local / local
- DMBox 7025 : CLIENT
- CLIENT'S IMAGE (nfi) : GP2 V. 2.30
- CLIENT'S LAN IP Address : 192.168.1.4
- CLIENT'S Username / Password : user / pass
- Protocol to use during the Cardsharing process : "CCcam 1.7.1-Complete" Emu
a) CARDSERVER & CCcam Protocol {"CCcam 1.7.1" : Cardserver Emu}
- Blue Panel/Addons/Download & Install/Cam/"CCcam 1.7.1"
- Blue Panel/Addons/Download & Install/Cam-config/"CCcam-Config 1.7.1"
- Blue Panel/Right-Left Buttons/Selection of the "CCcam 1.7.1" Emu /
Green Button (Stop/start Cam) to activate the selected Emu
- Run the Filezilla 2.2.31 FTP Client on your PC and press "Quickconnect"
(http://sourceforge.net/project/showf...group_id=21558)
Address : 192.168.1.3 (Menu/Setup/System/Network/IP Address)
User : root
Password : dreambox
Port : 21
- 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/User/Client) Line :
F: {based on caid:id:sid}
* ClientUsername : user
* Clientpwd : pass
* MaxUphopsLimit ("Cascading") = 0,1,2,3,4,5,6,7,8,9,10
- If Uphops = 0 , the Friend/User gets ONLY the Administrator's LOCAL CARDS
- If Uphops = 1,2,3,4,5,6,7,8,9,10 , the Friend/User gets ALL Administrator's CARDS at a maximum of 1,2,3,4,5,6,7,8,9,10 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,6,7,8,9,10 further levels beyond his/her own}
* 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 {Optional}
** The SHARE PORT (ServerPort) = 12000 (by default)
The Server's (DM 500) Cardreader Slot "recognizes" the Smartcard's CAId (0500/VIACCESS) , 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") 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) Line :
C: {yes-optional}
* ServerIpAddress : 192.168.1.3
* ServerPort : 12000 (by default)
* ServerUsername : local
* Serverpwd : local
This is how the "CCcam cfg" file must look like :
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 1.7.1" EMU/GREEN BUTTON : stop/start "CCcam 1.7.1" emu to reactivate and apply the modifications.
There are SEVERAL , EQUALLY VALUABLE , COMBINATIONS between , and parameters.
That's why , you must read carefully the explanations appearing in the configuration options of "CCcam-Config 1.7.1" 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 1.7.1"/CCcam Protocol} , according to the CCcam-Team :
b) CLIENT & CCcam Protocol {"CCcam 1.7.1" : Client Emu}
-Blue Panel/Addons/Download & Install/Camd/"CCcam 1.7.1"
-Blue Panel/Addons/Download & Install/Camd Config/"CCcam-Config 1.7.1"
-Blue Panel/Right-Left Buttons/Selection of the "CCcam 1.7.1" Emu/Green Button (Stop/start Cam) to activate the selected Emu
-Run the Filezilla 2.2.31 FTP Client on your PC and press "Quickconnect" (http://sourceforge.net/project/showf...group_id=21558)
Address : 192.168.1.4 (Get the information from : Menu /setup/ System/ Network/IP Address)
User : root
Password : - (for the DM 7025 there's no need for pwd-however you can type "dreambox")
Port : 21
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) Line :
C: {yes-optional}
* ServerIpAddress = the Cardserver's (DM500) LAN Ip Address = 192.168.1.3
* ServerPort = the SHARE PORT = 12000 (by default)
* ClientUsername = user
* Clientpwd = pass
* WantEmus = yes {Optional , but necessary if the Client desires to activate the "ShareEmus" option (on the Server's F Line)}
This is how the "CCcam cfg" file must look like :
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 1.7.1" EMU/GREEN BUTTON : stop/start "CCcam 1.7.1" emu to reactivate and apply the changes.
The LAN Cardsharing Process is about to begin , thanks to the powerful "CCcam Protocol" ("CCcam 1.7.1-Complete" Emu) and its (various & interesting) configuration options (via the associated "CCcam-Config 1.7.1" file).
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/Radegast/NewCS) and contributes to the establishment of a successful & fully operational cardsharing process.
A> NECESSARY EQUIPMENT FOR A LAN CONNECTION
- ADSL CONNECTION (over PSTN or ISDN)
- Modem-Router with at least 3 ethernet ports
- Cables RJ-45 (cat. 5 or cat. 6)
- DMBox 500/56XX/600/7000/7020
- DMBox 7025
- PC (WIN XP) with 10/100 MBit Compatible Ethernet Interface and an FTP Client installed (FILEZILLA CLIENT 2.2.31)
- An Official Subscription Card VIACCESS 2 (CAId : 0500)
B> PRELIMINARIES
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. The Modem-Router is now the default Internet Gateway which acts as a
DHCP Server , in order to distribute automatically to each device of the LAN (PC , DMBox) its own Local IP Address.
ii> Connect the PC and the DMBox to the modem-router , via cables RJ-45
iii> Configurations on the DMBoxes
- DM 500/56XX/7000/7020
Go to "Menu/Mainmenu/Setup/Expert setup/Communication Setup :
*ENABLE the DHCP option and CONFIRM the option "Enable Network"
*Connection Type : LAN
*Port : 80
Green button to SAVE the above configurations
- DM 7025
Go to Menu/Setup/System/Network :
* "Use DHCP" : YES
PRESS the OK button to confirm the choice
iv> Configurations on the PC :
Start/Control Panel/Network Connections/Local Area Connection/Properties/Internet Protocol (TCP/IP)/Properties :
- CHECK the following options : "Obtain an IP address automatically" & "Obtain DNS server address automatically"
- Go to Advanced/Default gateways : ADD the IP address of the Modem-Router
II> USING Personalized settings
- For the DMBoxes
The elements to be modified are the following :
- IP Address : Associate to the DMBoxes 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 : Set the Primary (Public) IP address of your ISProvider. You could also set the Local Internal
- Gateway : Set the Local
- CHECK the option : "Enable Network"
PRESS the OK/Green button to SAVE the configutations.
- For the PC
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 :
*Router's Local Internal
*PC's Local
*Default Gateway : 192.168.1.1 (router's IP address)
*DNS server addresses : ISP's main & alternative public IP addresses OR the Router's Local IP address (192.168.1.1)
**DMBoxes's LAN IP addresses :
- 192.168.1.3
- 192.168.1.4
**Gateway : 192.168.1.1 (the router's Local IP address)
**Nameserver : 192.168.1.1 (the router's IP address) OR the ISP's Primary IP address
C> DM 7025 & VIACCESS 2 CARD
- DMBox 500 : CARDSERVER
- CARDSERVER'S IMAGE (img) : GP2 V. 3.50 MaxVar
- CARDSERVER'S LAN IP Address : 192.168.1.3
- CARDSERVER'S Username / Password : local / local
- DMBox 7025 : CLIENT
- CLIENT'S IMAGE (nfi) : GP2 V. 2.30
- CLIENT'S LAN IP Address : 192.168.1.4
- CLIENT'S Username / Password : user / pass
- Protocol to use during the Cardsharing process : "CCcam 1.7.1-Complete" Emu
a) CARDSERVER
- Blue Panel/Addons/Download & Install/Cam/"CCcam 1.7.1"
- Blue Panel/Addons/Download & Install/Cam-config/"CCcam-Config 1.7.1"
- Blue Panel/Right-Left Buttons/Selection of the "CCcam 1.7.1" Emu /
Green Button (Stop/start Cam) to activate the selected Emu
- Run the Filezilla 2.2.31 FTP Client on your PC and press "Quickconnect"
(http://sourceforge.net/project/showf...group_id=21558)
Address : 192.168.1.3 (Menu/Setup/System/Network/IP Address)
User : root
Password : dreambox
Port : 21
- 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/User/Client) Line :
F:
* ClientUsername : user
* Clientpwd : pass
* MaxUphopsLimit ("Cascading") = 0,1,2,3,4,5,6,7,8,9,10
- If Uphops = 0 , the Friend/User
- If Uphops = 1,2,3,4,5,6,7,8,9,10 , the Friend/User
In other words the Client is allowed (by the Administrator) to share the Card down to other clients {1,2,3,4,5,6,7,8,9,10 further levels beyond his/her own}
* 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
** The SHARE PORT (ServerPort) = 12000 (by default)
The Server's (DM 500) Cardreader Slot "recognizes" the Smartcard's CAId (0500/VIACCESS) , 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") 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) Line :
C:
* ServerIpAddress : 192.168.1.3
* ServerPort : 12000 (by default)
* ServerUsername : local
* Serverpwd : local
This is how the "CCcam cfg" file must look like :
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 1.7.1" EMU/GREEN BUTTON : stop/start "CCcam 1.7.1" emu to reactivate and apply the modifications.
There are SEVERAL , EQUALLY VALUABLE , COMBINATIONS between
That's why , you must read carefully the explanations appearing in the configuration options of "CCcam-Config 1.7.1" 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 1.7.1"/CCcam Protocol} , according to the CCcam-Team :
b) CLIENT
-Blue Panel/Addons/Download & Install/Camd/"CCcam 1.7.1"
-Blue Panel/Addons/Download & Install/Camd Config/"CCcam-Config 1.7.1"
-Blue Panel/Right-Left Buttons/Selection of the "CCcam 1.7.1" Emu/Green Button (Stop/start Cam) to activate the selected Emu
-Run the Filezilla 2.2.31 FTP Client on your PC and press "Quickconnect" (http://sourceforge.net/project/showf...group_id=21558)
Address : 192.168.1.4 (Get the information from : Menu /setup/ System/ Network/IP Address)
User : root
Password : - (for the DM 7025 there's no need for pwd-however you can type "dreambox")
Port : 21
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) Line :
C:
* ServerIpAddress = the Cardserver's (DM500) LAN Ip Address = 192.168.1.3
* ServerPort = the SHARE PORT = 12000 (by default)
* ClientUsername = user
* Clientpwd = pass
* WantEmus = yes {Optional , but necessary if the Client desires to activate the "ShareEmus" option (on the Server's F Line)}
This is how the "CCcam cfg" file must look like :
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 1.7.1" EMU/GREEN BUTTON : stop/start "CCcam 1.7.1" emu to reactivate and apply the changes.
The LAN Cardsharing Process is about to begin , thanks to the powerful "CCcam Protocol" ("CCcam 1.7.1-Complete" Emu) and its (various & interesting) configuration options (via the associated "CCcam-Config 1.7.1" file).
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/Radegast/NewCS) and contributes to the establishment of a successful & fully operational cardsharing process.
CCcam.cfg How to ?
Okay i'll try to explain how the config works with CCcam.
To add a user you have to put a F line in the config :
F: user password 3 1 0 { 0:0:5 }
user gets all our cards at max distance(hops) of 3
He has the right to use our emu keys 1, no rights to emu keys change into 0
He has NO AU rights 0, right for AU change into 1
Furthermore he has the right to reshare all our cards 4 more times { 0:0:5 }
When number is here { 0:0:1 } he can only watch himself and he has no reshare rights.
NEVER GO ABOVE NUMBER 5!! because the distance is to far then. ( like GBOX { 5 5 })
You can set portnumber by changing this rule :
# SERVER LISTEN PORT: 12000
into
SERVER LISTEN PORT: number you want.
To connect to a CCcam server you have to add a C line:
C: ip/dyndns_server port user password yes
The yes on the end says you want to use your rights for emu keys
To connect to a newcamd server you have to add A N line:
N: ip/dyndns port user password deskey hops_away
To connect to a radegast server you need to add a R line:
R: IP/dyndns port CAID(4digits) providerID(6digits) hops_away
To connect to a Camd3 server you have to add a L line:
L: IP/dyndns port CAID(4digits) providerID(6digits) hops_away
These are the basics of the config for CCcam.
Expert setup follows
(03-30-2007 09:39 AM)
OK here we go, the above settings are the basics now we go further.
With a Cccam server you are always in controll
You decide how much your friend is going to see and how far he can reshare it
F: user password 0 0 0 { 0:0:1 }
Says that user gets only our local cards:0 and he only can watch it himself he has no reshare rights.
When changing the zero into 1 user gets our local cards and all vitual cards at a max distance of 1 hop.
If number is 2 then a max distance of 2 hops etc.
Don't exceed number 5 because the distance is then too far away for stable picture
In case U have 2 local cards and U only want that user get to see 1 u can do this excample:
Card 1 = provider CDS 0100 00006A
Card 2 = provider Premiere 1702 000000
Now you want that user only gets to see your CDS card and not the premiere card do the following
F: user password 3 1 0 { 0:0:5, 0100 00006A:1, 1702:0:0 }
This user gets all cards at maximum distance of 3 hops except 1702 because he has no rights to it :0.
He gets to reshare all our cards(local and virual) 4 times except for provider 0100 0006A because of :1.
Say you want the user to have the right to reshare 0100 0006A 2 times further then change the :1 into 3
So you see U decide what your friend(s) are entitled to see and how many rights they get, wants your card is set to reshare level 3 nobody but yourself can change that.
If you have questions feel free
In the latest versions of CCcam it's possible to control your hops you are receiving from your peers.
Thats realy a good option now you are in control how many shares online you have.
Heavy testing for me said that 2500 shares online is maximum.
To control receiving hops just add { 0:0:x } at the end of the C line, where x is the number of hops you want to receive.
So: C: dyndnds port user passwd no { 0:0:2 } only gives me shares from that peer with max count of 2.
Important: If you dont use yes/no behind the C lines add them or:
( { 0:0:2 } ) make it like this otherwise it won't work
To add a user you have to put a F line in the config :
F: user password 3 1 0 { 0:0:5 }
user gets all our cards at max distance(hops) of 3
He has the right to use our emu keys 1, no rights to emu keys change into 0
He has NO AU rights 0, right for AU change into 1
Furthermore he has the right to reshare all our cards 4 more times { 0:0:5 }
When number is here { 0:0:1 } he can only watch himself and he has no reshare rights.
NEVER GO ABOVE NUMBER 5!! because the distance is to far then. ( like GBOX { 5 5 })
You can set portnumber by changing this rule :
# SERVER LISTEN PORT: 12000
into
SERVER LISTEN PORT: number you want.
To connect to a CCcam server you have to add a C line:
C: ip/dyndns_server port user password yes
The yes on the end says you want to use your rights for emu keys
To connect to a newcamd server you have to add A N line:
N: ip/dyndns port user password deskey hops_away
To connect to a radegast server you need to add a R line:
R: IP/dyndns port CAID(4digits) providerID(6digits) hops_away
To connect to a Camd3 server you have to add a L line:
L: IP/dyndns port CAID(4digits) providerID(6digits) hops_away
These are the basics of the config for CCcam.
Expert setup follows
(03-30-2007 09:39 AM)
OK here we go, the above settings are the basics now we go further.
With a Cccam server you are always in controll
You decide how much your friend is going to see and how far he can reshare it
F: user password 0 0 0 { 0:0:1 }
Says that user gets only our local cards:0 and he only can watch it himself he has no reshare rights.
When changing the zero into 1 user gets our local cards and all vitual cards at a max distance of 1 hop.
If number is 2 then a max distance of 2 hops etc.
Don't exceed number 5 because the distance is then too far away for stable picture
In case U have 2 local cards and U only want that user get to see 1 u can do this excample:
Card 1 = provider CDS 0100 00006A
Card 2 = provider Premiere 1702 000000
Now you want that user only gets to see your CDS card and not the premiere card do the following
F: user password 3 1 0 { 0:0:5, 0100 00006A:1, 1702:0:0 }
This user gets all cards at maximum distance of 3 hops except 1702 because he has no rights to it :0.
He gets to reshare all our cards(local and virual) 4 times except for provider 0100 0006A because of :1.
Say you want the user to have the right to reshare 0100 0006A 2 times further then change the :1 into 3
So you see U decide what your friend(s) are entitled to see and how many rights they get, wants your card is set to reshare level 3 nobody but yourself can change that.
If you have questions feel free
In the latest versions of CCcam it's possible to control your hops you are receiving from your peers.
Thats realy a good option now you are in control how many shares online you have.
Heavy testing for me said that 2500 shares online is maximum.
To control receiving hops just add { 0:0:x } at the end of the C line, where x is the number of hops you want to receive.
So: C: dyndnds port user passwd no { 0:0:2 } only gives me shares from that peer with max count of 2.
Important: If you dont use yes/no behind the C lines add them or:
( { 0:0:2 } ) make it like this otherwise it won't work
Mbox Config Tutorial
Mbox Tutorial
- You should remove all G-Lines And Y lines form your Gbox's cwshare.cfg before you run Mbox unless you use a different cwshare.cfg in a different path with G and Y lines removed ( set for different path in mbox.cfg than the one for Gbox )or Mbox won't run .
- You can use same ignore.list and ident.info for gbox with mbox, they go in the same path /var/keys ( unless you change the path in the settings as explained in this Tut )
- Unlike Gbox, Mbox can not read local cards directly ( not yet at least ) , that is why you need Newcs so you can share your local and have it appear as Local to other peers - explanation in examples here.
- A working cwshare & newcs example added to end of tutorial.
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 <- use this
if you can
// { 1/tmp/camd.socket } for enigma 1
// { 2/tmp/camd.socket } for enigma 2
Now for the start of Mbox you need to know where the mbox.cfg path is.
The default path for mbox.cfg is /var/keys/
For other paths you must start mbox with path as argument!!!
For some receivers like Ipbox and Kathrein there is no /var/keys/ so you must
start mbox always with arguments.
Example:
without arguments
./mbox or ./var/bin/mbox
with arguments
./mbox /data/keys/mbox.cfg or ./var/bin/mbox /data/keys/mbox.cfg
To STOP Mbox you need to create mbox.kill.
Put this mbox.kill in the temp dir of Mbox.T: path (look
your settings in mbox.cfg)
Example T: { /tmp/ }: touch /tmp/mbox.kill
Other parameters of mbox.cfg that are interesting:
M: { 1 }
// M option -> 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 }
About the cwshare.cfg:
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)
- two formats are supported - the normal gbox dline format & Mbox new dline format-
This is standard D line ( gbox format )
=======================
D: { IP { port1 port2 { pass { level1 level2 }}}}
This is my new upgraded D line ( To use for Mbox exchange -Mbox format-)
===============================
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 } {
xxxxyyyy:xxxxyyyy;......}
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...
Add more cards for CaidProvid
=============================
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:
......
12000ort> .......
12000ort> .......
So the file will be called 12000.list.
If you have 17050then 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.
About the add.data file:
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.
"add.data" file will be deleted after reading (read add.data.example)
!
#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 } {
xxxxyyyy:xxxxyyyy;......} -> add new C line
===========================================
Here is An example of a working cwshare.cfg and newcs.xml ( you must adjust according to your own set-up )
cwshare.cfg :
I: { 02 }
O: { 4000 2000 }
N: { 400 200 }
M: { xxxxx.dyndns.info { SamePASS of your GBOX }} <-- Same line in your gbox's cwshare, do not change anything here .
Add a similar Cline to read your Local as follows - It depends on your newcs.xml ( explained below -note matching colors- ).
C: { 127.0.0.1 34000 dummy dummy 01 02 03 04 05 06 07 08 09 10 11 12 13 14 } { 0 } { 0 } <-- check above for { 0 } { 0 } , it depends on your card .
your same Dlines from gbox goes here now.
NewCS example : for a local Irdeto card in lower slot of DM ( single slot boxes = lower slot ) Pay SPecial attention to colored parts and how they're matched.. these are the most important that will be used in the Cline we mentioned above.
newcs.xml ( found in /var/tuxbox/config )
lower
sci
600
/dev/sci0
odd
normal
Yes
Yes
No
No
No
0000000000000000
000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000
No
000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000
00000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 000000000000
No
yes
34000
Yes
no
0000
round
No
16000
localhost
20
-1
8080
yes
newcs
newcssam
admin
NewCSpwd
normal
init
normal,init
1001
normal,init
Yes
newcs
01 02 03 04 05 06 07 08 09 10 11 12 13 14
dummy
dummy
127.0.0.1
on
off
No
mpcs
dummy
No
No
No
lower
smargo
0
* Since we chose the port 34000 in our newcs.xml and therefore in our Cline in cwshare .. we must create a file called 34000.list that goes in /var/keys ( try putting the line SF: { 0000 } in this file till you figure out what needs to be put according to above tutorial .. depends on the card you have .
If you have 17050then 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.
About the add.data file:
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.
"add.data" file will be deleted after reading (read add.data.example)
!
#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 } {
xxxxyyyy:xxxxyyyy;......} -> add new C line
===========================================
Here is An example of a working cwshare.cfg and newcs.xml ( you must adjust according to your own set-up )
cwshare.cfg :
I: { 02 }
O: { 4000 2000 }
N: { 400 200 }
M: { xxxxx.dyndns.info { SamePASS of your GBOX }} <-- Same line in your gbox's cwshare, do not change anything here .
Add a similar Cline to read your Local as follows - It depends on your newcs.xml ( explained below -note matching colors- ).
C: { 127.0.0.1 34000 dummy dummy 01 02 03 04 05 06 07 08 09 10 11 12 13 14 } { 0 } { 0 } <-- check above for { 0 } { 0 } , it depends on your card .
your same Dlines from gbox goes here now.
NewCS example : for a local Irdeto card in lower slot of DM ( single slot boxes = lower slot ) Pay SPecial attention to colored parts and how they're matched.. these are the most important that will be used in the Cline we mentioned above.
newcs.xml ( found in /var/tuxbox/config )
* Since we chose the port 34000 in our newcs.xml and therefore in our Cline in cwshare .. we must create a file called 34000.list that goes in /var/keys ( try putting the line SF: { 0000 } in this file till you figure out what needs to be put according to above tutorial .. depends on the card you have .