CCcam Tutorial - Some more infos of how to 8

CCcam Tutorial - Some more infos of how to 8

Let’s look at the following example: F: user3 pass3 5 0 1 { 0:0:3, 0100:000080:1 } is set to 5, the client receives all the cards up to a distance of 5 hops from the server is set to 0, the client does not have access to the server local key file is set to 1, the client receives remote EMM is set to 0:0:3, the client receives all the cards, and can reshare them 2 hops further. 000080:1, with the exception of this card, that cannot be reshared. The option allows the server to limit access even to a specific TV service. Start and stop scripts

CCcam Tutorial - Some more infos of how to 9

So far, we used Telnet to start CCcam and check our tests. We shall now look at the scripts that start and stop CCcam. The script procedure changes according to the image in use. Gemini image All the scripts for Gemini images are found in the /usr/script directory for DB 7020si series and in var/script for DB500s and DB7000 series. It is possible to have listed in Blue Panel any EMU related script, if these are starting with _cam (e.g. CCcam_cam.sh). Note: to enable any script, its attributes/Chmod must be set to 755. The Gemini original scripts start with a list of CAMID's. A sector is allocated to each EMU. This list of CAMID’s is only providing information and can be ignored. CAMID must be set as follows: CAMID=6000 CAMID is required to sort the Blue Panel list. Each CAMID must be listed only once. This will enable the Gemini image to identify the EMU by its number. If the Dreambox requires it, then Gemini will search the script according to the number saved during its creation and will initialize it. If Gemini does not find the script, the following error message will be returned “camid not found”. This is not a fatal error. It means that no script has been found with that CAMID number.

&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&

CCcam Tutorial - Some more infos of how to 10

The available scripts (ending with _cam.sh) can be read when starting Enigma. They can also be read from the Blue Panel, Cam Settings, ALL cam, Update. Therefore, no need to worry if an EMU is not listed in the Blue Panel. CAMNAME="CCcam-1.2.0" CAMNAME represents the name that will be displayed in the Blue Panel. The length of the name must be set according to the skin in use. Else, it may not appear properly, or completely ZAPTIME=6 When changing from the current EMU to a different EMU, ZAPTIME sets the time required by the EMU in use to display a service. INFOFILE="ecm.info" This is the file where the current ECM are saved case "$1" This is where the start/stop script begins The start/stop setting is read at the start of the script start) echo "[SCRIPT] $1: $CAMNAME" /var/bin/CCcam -v ;; start) is the value of the setting, and will start the following script ECHO "(script) $1: # $$CAMNAME>" This is simply displaying the script name, the setting value and the name of the CAM /var/bin/CCcam – v Cccam is now started; in the example the –v (verbose) setting is used ;; End of the start script stop) echo "[SCRIPT] $1: $CAMNAME" killall CCcam ;; stop) This is the setting value and the following script will be launched ECHO "(script) $1:" # $$CAMNAME>"- killall CCcam the EMU stops ;; End of the script *) $0 stop exit 1 ;; esac

%%%%%%%%%%%%%%%%

CCcam Tutorial - Some more infos of how to 11

If, in addition to CCcam, you want to start NewCS, then you must add it. However, it is necessary to hold CCcam for 3 seconds. This will prevent CCcam to read the CI slots before NewCS. echo "[SCRIPT] $1: $CAMNAME" /var/bin/newcs sleep 3 /var/bin/CCcam -v .. If you want to stop them .. echo "[SCRIPT] $1: $CAMNAME" killall newcs killall CCcam .. The names must be correct, respecting also the capital letters. To try the script with Telnet simply type /var/script/emu_cam.sh start And that's all folks !!!!!!! Satelite Regards, Gotcha_GT



%%%%%%%%%%%%%%%%%%%%%

CCcam Tutorial - Some more infos of how to 3

Web Server and other EMU’s connection settings: The CCcam webinfo server provides information about the current CCcam status and its connections through a web page. This option provides clear information about all the connected clients, the active clients, as well as the servers status. By default, the webinfo server runs on port 16001. Therefore, to access the webinfo sever using your browser, type http://your_dreambox_ipnumber:16001. If set in your CCcam config file, you will be asked to enter the user name and password. In our example, there must be a defined access of a client to a server. If the access is defined, then the communication is established, and the information’s are displayed. This is an example of what the client webinfo server page looks like. The top section displays information about the clients who have been active during the past 20 seconds, as well as the amount of ECM received. The bottom part represents a list of all the users as well as a traffic summary. The local traffic differs from the remote traffic, and it is therefore displayed separately. Connected clients: 4 +---------+------------+------------+------------+---------+-----+--------+----------------------+----------+ Username Host Connected Idle time ECM EMM Version Last used share Ecm time +---------+------------+------------+------------+---------+-----+--------+----------------------+----------+ User1 xx.xx.10.1 00d 01:19:3200d 00:00:01518 (509)0 (0)1.2.1 Last used share Ecm time User2 xx.xx.10.2 00d 00:46:2500d 00:00:10174 (167)0 (0)1.2.1 Last used share Ecm time +---------+------------+------------+------------+---------+-----+--------+----------------------+----------+ +---------+---------------------------------------+ Username Shareinfo +---------+---------------------------------------+ User3 local 500:021500 1(0) User4 remote 919:000000 280(280) remote 1801:000501 2(0) +---------+---------------------------------------+ An example of what the webinfo server page looks like is reported here under. On the right side, it is listing the server CAID’s along with the amount of requested ECM’s. The local or remote traffic are separated again. Server connections: 1 +----------------------+------------+---------+--------+----------------+-------+-------------------------------+ Host Connected Type Version NodeID Cards CAID/Idents +----------------------+------------+---------+--------+----------------+-------+-------------------------------+ 192.168.1.4:12000 00d 15:15:58CCcam-s2s1.2.1 5d341729df599d5a 2 remote 919:000000 60(46) 00d 01:33:02CCcam-s2s1.2.1 local 4a70:000000 67(0) +----------------------+------------+---------+--------+----------------+-------+-------------------------------+ Log using a Syslog utility In all our examples, so far, we used the Telnet command. However, this is not the best solution to launch the EMU in –dv mode and check possible errors. 3CSyslog represents an alternative solution. This utility is a Freeware, and can be downloaded from the web http://support.3com.com/software/utilities_for_windows_32_bit.htm First of all, you need to apply the following settings in the CCcam configuration file. Both SHOW TIMING and DEBUG must be set to YES. # if timing should be shown in OSD and debug output # default is no (turned off) # SHOW TIMING : yes # turns debugging on and off # default is no (turned off) # DEBUG : yes Then, enable the syslog option in your DreamBox. On Gemini images, this is found in Blue Panel, Extra Settings, Sys/Kernel Log. Press OK, and press it again to select Syslog/Daemon. Now enable all the options including the remote logging option. Fill in your PC IP number, and use port 514 (UDP)