Saturday, September 8, 2007

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. 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 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="" 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/ 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 +----------------------+------------+---------+--------+----------------+-------+-------------------------------+ 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 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)

CCcam Tutorial - Some more infos of how to 7

UPshare and DOWNshare: limiting access to Caid’s, Providers, and Services. CCcam offers the possibility to set each cards access independently. The syntax is as follows: F: { caid:id:downhops, caid:id:downhops, ... } { caid:id:sid, caid:id:sid, ... } To understand how to limit access to each card, let’s look at the following example: F: user2 pass2 0 1 0 { 0100:000080, 0622:000000:1, 0500:000000:2 } is set to 0, the client can only access the server local cards is set to 1, the client can have access to the server local key file is set to 0, the client cannot do any remote EMM is set to 0100:000080, the client does not have access to Canal+ France card. is set to 0622:000000:1, the client receives Canal+ NL, but cannot reshare it. is set to 0500:000000:2, the client receives a Viacces provider, and can reshare it 1 hop further. Therefore, in addition to limiting server access, allows the server to define how far the client can reshare the server cards. This is set in the downhops field.

CCcam Tutorial - Some more infos of how to 6

For instance, there is a key change at the server side. Therefore, a new key will be sent via satellite. The new key will be recognized by the server as soon as it is tuned to the correct TV service. If the remote EMM is enabled, then each client will receive the same update as soon as the client is also set to the same TV service. The client’s box will perform what is called REMM (Remote EMM). By default, this is set to 1. Example 1 F: user2 pass2 0.1.0 In this example, user1 will only receive the server local card, the server is set to share the local key file, and the remote EMM is disabled. Example 2 F: user1 pass1 3 0 0 In example 2, user 1 can reach the cards 3 hops away from the server, in addition to the server local card; the server is set to forbid access to the local key file; the remote EMM is disabled.

CCcam Tutorial - Some more infos of how to 4

Advanced Settings Hops CCcam clients have the possibility to reshare their server connections. This feature is known as “cascading”, and works really well with CCcam. Let’s see how it works. For instance, we have 4 users or groups where the 1st one is directly linked to the 2nd one, the 2nd one is directly linked to the 3rd one, the 3rd one is directly linked to the 4th one. The “cascading option” enables the 1st user or group to be linked with the 4th. box1 <----> box2 <----> box3 <----> box4 ^----1 hop-----^ ^-----------2 hops-----------^ ^--------------------3 hops-------------------^ If box1 receive a key from box4 (procedure known as ECM), this key will go through 3 groups, which are known as HOPS. In the following example, the client will have access to the server local cards, as well as those located 2 hops further. F: user1 pass1 2 Therefore, if the server is located in box2, box1 will have access to box2 as well as box3 and box4

Uphops, local keyfiles and remote EMM setting procedures. F: identifies the username you assign to the client identifies the password you assign to the client allows the client to have access to the server’s other clients cards. If set to 0, then the client will only have access to the server local cards; if set to 1, then the client will have access to the cards at a distance of 1 hop from the server; if set to 2, access will be as far as hop 2, and so on. is enables the local key file sharing option. If set to 1, then the server key file is shared; else, if set to 0, it is not shared. However, the client can choose whether to accept this option or not. If the client wishes to receive the server keyfile, then this must be set by adding “yes” in the C: line as follows: C: 12000 user3 pass3 yes If a client does not want to use this option, the C: line will be C: 12000 user3 pass3 no. By default, is set to 1. This option is very useful when there are many groups in the network.In this case, instead of updating the Softcam.key file of each client, it will be enough to update the server only. enables the remote EMM autoupdate feature. If it is set to 1, then the user will have access to EMM on the local card, else, if set to 0, the client will not have access.

CCcam Tutorial - Some more infos of how to 2

CCcam Tutorial - Some more infos of how to 2

How to connect a client to a server: The F line launches the server, whilst the C line launches the client, and this is all you need. Should the client wish to share its subscription cards with the server, then you need to add a C line at the server, and an F line at the client. Log Diagnostic Should you wish to check whether the connections are working properly, then use the CCcam –dv Telnet command. This option will give you the possibility to check the log and make sure all is ok.It may be useful for beginners to do it with Telnet, and, once experienced, it may also be done using the the automatic script found in the blue panel. This is what the dialogue between the 2 decoders should look like: 1) 11:55:06.977 CCcam: found betacrypt caid: 0x1702 ecmpid: 0x100a id: 0x0 2) 11:55:06.978 CCcam: found betacrypt caid: 0x1722 ecmpid: 0x100a id: 0x0 3) 11:55:06.978 CCcam: found nagra caid: 0x1801 ecmpid: 0x1642 id: 0x0 4) 11:55:06.978 CCcam: cam[0] set PMT for sid=a 5) 11:55:06.979 CCcam: start EMM 6) 11:55:06.996 CCcam: cam[0] ecm even nok caid:0x1702 id:0x0 pid:0x100a Premiere Sat (19E) tunneled Nagra (took 0.0010 seconds) 7) 11:55:07.061 CCcam: cam[0] ecm even nok caid:0x1722 id:0x0 pid:0x100a Premiere Kabel (19E) tunneled Nagra (took 0.0003 seconds) Lines 1) 2) and 3) display information about the service encryption Pre***e is displayed with the 3 possidble CAID’s: 1702 tunnel Nagra = betacrypt for DVB-S 1722 tunnel Nagra = betacrypt for DVB-C 1801 plain Nagra (not used or only on s04 card) = unused. The Pre**er provider is usually written with 6 digits.In this case, the service ID is 100a and identifies Pre**er1. Line 4) “Start EMM” marks the point where CCcam starts looking for keys. The 2 following lines list the local server replies.In this example, the replies are negative ecm even nok caid:0x1722. This is normal as there are no cards in the receiver. The query lasted 0.0003s. We then find the queries sent to the server: 8 ) 11:55:07.194 CCcam: remote ecm -> 0x1702(0x000) 9) 11:55:07.331 CCcam: remote ecm <- ok (took 0.1364 seconds) 10) 11:55:07.333 CCcam: cam[0] ecm even ok caid:0x1702 id:0x0 pid:0x100a Pre***re Sat (19E) tunneled Nagra (took 0.1383 seconds)>code< ecm even ok caid:0x1702 means that this query has been successfully transmitted through the LAN in 0.1383s. killall CCcam marks the end of the log

CCcam Tutorial - Some more infos of how to 1

This tutorial will help you master the full potential of this excellent CAM. The following tools are required to be able to use the CCcam on your Dreambox: 1) Linux compatible editor, such as Ultraedit32,Notepad ++ or Crimson Editor (freeware) 2) FTP software like FlashFXP 3) A syslog utility like 3csyslog (freeware) 4) A Telnet utility, the Windows integrated tool will do the job Installing CCcam The CCcam archive is composed of 2 files, a bin file and a config file. In the original RAR archive, the authors have saved the Dreambox binary file as CCcam.ppc, whilst the config file is the same as for any version. It is suggested to rename the binary file in CCcam as it will help make the following Telnet procedures easier. Copy the bin file to /var/bin and set the rights (attributes) to 755. Copy the config file to /var/etc/ We are now ready to check in details how CCcam really works, using the Telnet utility In Windows, Start RUN and type Telnet (or your Dreambox IP number) and click OK Login (root) Now do the following: Type cd /var/bin to go to /var/bin, check whether you are in the correct directory (for Linux ls=dir), check the file colour, the CCcam file should be green. At the prompt, type “CCcam –dv” making sure to match the file name as well as capital letters. The –dv command will give you the possibility to see each step that CCcam does, through an activity log that should look like the following one: 1) 16:09:26.209 CCcam: =================================== 2) 16:09:26.212 CCcam: starting CCcam 1.2.0 compiled on Jul 5 2006@21:12:46 3) 16:09:26.212 CCcam: =================================== 4) 16:09:26.276 CCcam: online using nodeId 578103ff60952939 5) 16:09:26.305 CCcam: DM70x0 detected 6) 16:09:26.307 CCcam: create 2 cam device(s) 7) 16:09:26.920 CCcam: provider num: fff830 8 ) 16:09:26.920 CCcam: provider key: (hier steht die abonummer) 9) 16:09:27.120 CCcam: provider num: 021c00 10) 16:09:27.121 CCcam: provider key: (hier steht die abonummer) 11) 16:09:27.215 CCcam: card added to broker with caid 500 12) 16:09:28.018 CCcam: card added to broker with caid 4a70 13) 16:09:28.072 CCcam: added 389 keys from /var/keys/SoftCam.Key 14) 16:09:28.132 CCcam: added 541 keys from /var/keys/AutoRoll.Key 15) 16:09:28.133 CCcam: static cw not found or bad 16) 16:09:28.134 CCcam: read_ignorefile: cannot open /var/keys/CCcam.ignore or not found 17) 16:09:28.135 CCcam: server started on port 12000 If you suspect something is not correct, and would like to check the ECMS answers, these will appear directly on your DB when zapping channel. Just start a second Telnet session, type the command ps and press Enter. The active processes will be displayed and should look like the following example: 1: root@dm7020:~> ps 2: PID Uid VmSize Stat Command 3: 1 root 608 S init [2] 4: 2 root SWN [ksoftirqd/0] 5: 3 root SW< [events/0] 6: 4 root SW< [khelper] 7: --- extra lines removed--- 8: 599 root 2100 S /var/bin/CCcam_1.2.1 9: 600 root 2100 S /var/bin/CCcam_1.2.1

Friday, September 7, 2007

شرح تشغيل وتسجيل الافلام بين الدريم وهارد الكمبيوتر

هذا الشرح للتشغيل وتسجيل الافلام بين للدريم وهارددسك الكمبيوترالشرح على صورة فريق الجيمنى
و وندوز فيستا وهو لايفرق بينة وبين وندوز xpاولا نقوم بعمل اسم مستخدم جديد في الكمبيوتر للدريم بوكس
Control Panel\User Accounts\Manage Accounts\Create New Accountاكتب اسم مستخدم جديد على سبيل
المثال dreamboxاختار Administrator ومن ثم اضغظ على create accountالان ستشاهد ان تم اضافة اسم dreambox مع المستخدمين
اضغظ على الاسم dreamboxاضغظ على Create Password للعمل باسوورد للمستخدم
انتهينا الان من عمل حساب جديد للدريم الان سنعمل شيرنج للهارد الكمبيوتر على الشبكة 1- افتح My Computer2- بالماوس رايت كلك على الهارد c3- اختار share4- اضغظ على Advanced sharing1- علم على share this folder2- اضغظ على Permission

ومن ثم اضغظ على addبعدها اضغظ على advanced1- اضغظ علىFind Now2- اختار اسم المستخدم الذى اضفتة مسبقا dreambox3- اضغظ على ok وايضا ok للنافذة التى تليهاعلم على اسم المستخدم بالماوس ومن ثم اعطة صلاحيات التحكم باختيار مربعات allowاضغظ على ok ومن ثم applay

الان انتهينا من الخطولت اللازمة للكمبيوتر الخطوات التاليةللدريم بوكس اولا نقوم بفتح التلنت من خلال run ونكتبtelnet 192.168.X.Xمع مراعاة ايبي للدريم لديكاكتب الامر التالي mkdir /mnt/hardcالان من ريموت للدريم ادخل علىmenu/setup/expert setup/communication setup/mount1- اكتب ايبي الكمبيوتر2- اختار CIFS3- اكتب اسم الملف او الهارد الذي تمعمل لة شيرنج مسبقا في الكمبيوتر4- اكتب مسار الملف في للدريم للظهور ملفات الهارد فية /mnt/hardc5- اختار rw6- اتركة كما هو 7- اكتب اسم المستخدم الذى تم اضافتة في الكمبيوتر8- اكتب الباسوورد الذى تم اضافتة للمستخدم في الكمبيوتر9- اضغظ على mountهذى الرسالة تخبرك بنجاح العملية

للمشاهدة ملفات الهارددسك في للدريم من الريموت ادخل علىmenu/file mode/root/mnt/hardcهنا ستشاهد جميع ملفات الهارد ويمكنك الدخول على الملف الذى يحتوى على الافلام وتشغيلهاوللتسجيل على هارددسك الكمبيوتر من الريموت اضغظ على الزر الازرق واختارExtras settings/recordاختار الملف /mnt/hardc/movieومن ثم اضغظ على saveاضغظ على زر التسجيل وسيبدأ التسجيل في الكمبيوتر