OSCam/en/examples/Reader: Unterschied zwischen den Versionen
ValD (Diskussion | Beiträge) (Translated to English.) |
ValD (Diskussion | Beiträge) K (Removed the German language warning.) |
||
Zeile 1: | Zeile 1: | ||
[[Kategorie:OSCam]] | [[Kategorie:OSCam]] | ||
{{OSCamHomeLinks}} | {{OSCamHomeLinks}} | ||
== Example Reader Configurations == | == Example Reader Configurations == |
Version vom 16. März 2011, 02:13 Uhr
OSCam Übersicht OSCam Home OSCam Accueil OSCam Home
Example Reader Configurations
The reader is the module that allows OSCam server to translate ECMs received from clients into CWs, which are sent back to clients for decrypting channels. There are two types of readers: hardware readers, which are somehow connected to the machine which runs OSCam server, and remote readers, which are running on different machines than the one running the OSCam server.
For the hardware readers, OSCam needs to know what type the reader is, how it is connected to the machine, what protocol it "speaks", and what subscription cards are inserted in that device.
For the remote readers, OSCam must know the IP address and port where to connect, the protocol spoken, and how to authenticate itself (username/password). Again, you can specify subscriptions that can be found there.
The following list shows example configurations for the supported readers.
Serial-Mouse compatible reader
[reader] label = myserialmouserreader detect = cd protocol = mouse device = /dev/ttyS1 group = 1 caid = 0100 services = myservice,thisservice
USB-Mouse compatible Reader
[reader] label = myusbmousereader detect = cd protocol = mouse device = /dev/ttyUSB0 aeskey = 0102030405060708090a0b0c0d0e0f10 group = 2 caid = 0200
Camd3.78x Reader
[reader] label = mycamd378xreader protocol = cs378x device = 192.168.0.1,1234 account = user,password group = 3
Newcamd Reader
[reader] label = mynewcamdreader protocol = newcamd key = 0102030405060708091011121314 device = 192.168.0.2,2345 account = user,password group = 4
CCcam Reader
[reader] label = mycccamreader protocol = cccam device = 192.168.0.3,3456 account = user,password group = 5 caid = 0300,0400,0500 cccversion= 1.2.3 cccbuild = 4567
PCSC Reader
[reader] label = mypcscreader protocol = pcsc device = 0 aeskey = 0102030405060708090a0b0c0d0e0f10 group = 6 caid = 0600
Smargo Smartreader+
# EXAMPLE 1 [reader] label = mysmargoreader protocol = smartreader device = 001:002 aeskey = 0102030405060708090a0b0c0d0e0f10 group = 7 caid = 0700 # EXAMPLE 2 [reader] label = mysmargoreader protocol = smartreader device = Serial:Reader 1 detect = cd mhz = 600 cardmhz = 600 emmcache = 1,3,2 group = 7 services = my_services
Internal Reader
[reader] label = myinternalreader protocol = internal device = /dev/sci0 group = 8 caid = 0800
Constant CW
[reader] label = myconstantcw protocol = constcw device = /var/keys/constant.cw group = 9
gbox
[reader] label = mygboxreader protocol = gbox device = host.example.com group = 11 caid = 1100
Build >= #4605 First commit of gbox module (for developer use only!!!).
It only supports a single peer, no server-side, no clever sid stuff, ignores filters, is buggy, doesn't poll for server status, doens't handle cards correctly, doesn't make use of the right hello commands, ignores other commands, checksums aren't used, no webif integradion, no docs etc. et.c etc. so please, at this stage DO NOT USE IT, PLEASE DON'T POST BUGS/TICKETS/FORUM THREADS/EMAILS/PMS etc.
Also, this commit might break other stuff too; please expect that!
Smargo Special
First, read about udev => http://en.wikipedia.org/wiki/Udev
Smargo readers do not offer clear identification in a standard manner, at least before firmware 1.04. Starting from firmware 1.04, one can assign a clear identifier with the Smargo tools. To find out how to set the identifier (the clear name), please refer to the Smargo tool documentation, which should be included in the Smargo tools package.
The following example shows three Smargos and a MasterCRD on Debian Linux.
We remove all Smargos from the PC and attach them in sequence, while using Smargo tools to identify each device, as follows:
cd /where/the/smargotools/are # change directory to where Smargo tools are
# Attach first Smargo WITHOUT card, in a different USB slot, and then... ./srp_tool -n 1 # we assign identifier "1" to this device, later assigned to OSCam as "Serial:Reader 1"
# Attach another Smargo, then... ./srp_tool -n 2 # we assign identifier "2" to this device, later assigned to OSCam as "Serial:Reader 2"
# and so on...
An example using udev-rules:
# provide new udev-rules vi /lib/udev/rules.d/10-usb-name-for-example.rules
# then type as follows:
# Smargo 1 SUBSYSTEMS=="usb", KERNEL=="ttyUSB*", ATTRS{serial}=="Reader 1", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", SYMLINK+="smargo1", MODE="0666" # Smargo 2 SUBSYSTEMS=="usb", KERNEL=="ttyUSB*", ATTRS{serial}=="Reader 2", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", SYMLINK+="smargo2", MODE="0666" # Smargo 3 SUBSYSTEMS=="usb", KERNEL=="ttyUSB*", ATTRS{serial}=="Reader 3", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", SYMLINK+="smargo3", MODE="0666" # MasterCRD over Serial connector ************************* SUBSYSTEMS=="usb", KERNEL=="ttyUSB*", ATTRS{idVendor}=="4711", ATTRS{idProduct}=="4712", SYMLINK+="masterCRD", MODE="0666"
Finally, modify oscam.server as follows:
[reader] label = my_smargo1 protocol = smartreader # or "mouse" device = Serial:Reader 1 # /dev/smargo1, if "mouse" detect = cd mhz = 600 cardmhz = 600 emmcache = 1,3,2 group = 1 [reader] label = my_smargo2 protocol = mouse # or "smartreader" device = /dev/smargo2 # Serial:Reader 2, if "smartreader" detect = cd mhz = 368 cardmhz = 368 emmcache = 1,3,2 group = 2 # and so on...
Diese Seite in anderen Sprachen - This page in other languages - Cette page dans d'autres langues - Queste pagine in altre Lingue
[[OSCam/de/{{#titleparts:OSCam/en/examples/Reader|3|3}}|Deutsch]] [[OSCam/en/{{#titleparts:OSCam/en/examples/Reader|3|3}}|English]] [[OSCam/fr/{{#titleparts:OSCam/en/examples/Reader|3|3}}|Français]] [[OSCam/it/{{#titleparts:OSCam/en/examples/Reader|3|3}}|Italiano]]